Ticket to Development Capabilities Mapping Report (with L4 text)																							TICKETtoDEVCAP_text_spec
fg_source	fg_title	"devcap_id"	devcap_name	description	change_date	l4.l4_id	l4.l4_text	
AB_ZZ_01	Reliability, Maintainability, and Availability (RMA)	no data				NO DATA	L3 mapped directly to verification criteria. L4's are not needed to decompose RMA's L3 into subsystem components. RMA L3's will be verified by inspection  of the systems operations. RMA white paper provides the mapping of RMA L3s to verifiable system functions.  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00605	The BMGT shall run in accordance to ECS mode conventions.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00610	The BMGT shall be able to operate automatically (automatic mode) as well as under direction of parameters provided by DAAC staff (manual mode)	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00615	When started, the BMGT shall operate in automatic mode by default, i.e., unless explicitly overridden by command line parameters. [NOTE: The expectation is that all routine export in the absence of errors is performed via automatic export.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00620	The BMGT shall allow the DAAC staff to specify mappings between ESDT versions and groups.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00625	The BMGT shall allow the DAAC staff to define the group names; group names shall consist of up to twelve characters, compatible with the Data Pool rules for collection group names specified in S-DPL-40535. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00635	The BMGT shall allow DAAC staff to enable a collection for export of collection information separately from enabling the collection for export of granule metadata; by default, new collections are not enabled for export. [NOTE: Neither the collection information nor any of the granules in the collections will be exported if a collection is currently not enabled for export of collection information.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00640	The BMGT shall allow DAAC staff to enable a collection for export of granule metadata if the collection is enabled for export of collection metadata. [NOTE: While a collection is not enabled for export of granule metadata, metadata inserts and changes for its granules will not be included in export operations.  Once a collection was enabled for granule export, it will remain so until the collection is removed from the inventory.  It is assumed that if a DAAC wants to hide the collection in ECHO, it would use an ECHO provider interface in that case.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00650	The BMGT shall export the following changes to metadata of collections enabled for collection export: a. insertion of new collections into the ECS inventory, b. removal of collections from the ECS inventory, c. updates to collection metadata contained in the BMGTCollectionMetadata.dtd defined in the ECS-ECHO ICD. [NOTE: It is assumed that DAACs will use ECHO interfaces to hide and unhide collection rather than using the BMGT export mechanism for this purpose.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00655	The BMGT shall export collection inserts and updates to collection metadata by re-exporting all collection metadata referenced by and in accordance with the BMGTCollectionMetadata.dtd defined in the ECS-ECHO ICD.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00660	The BMGT shall export collection deletions by exporting the collection deletion information in accordance with the   XML element in the BMGTCollectionMetadata.dtd defined in the ECS-ECHO ICD. [NOTE: This requires a change to the BMGTCollectionMetadata.dtd to add the collection deletion information.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00662	The BMGT shall export collection version numbers without leading zeroes. [NOTE: ECHO requires this for backwards compatibility.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00665	The BMGT shall consolidate the events for collections within an automatically generated export package such that a collection is exported only once in that package.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00670	The BMGT shall create one and only one ECSMETC file per collection group and export cycle or manual export operation. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00675	The BMGT shall generate a single ECSMETV file for an export cycle exporting all valids referenced by and in accordance with the BMGTValidsMetadata.dtd if one or more ECSMETC products were generated during that execution or if there was a valids change during the export cycle.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00680	The BMGT shall generate the following types of export files as necessary to meet the export requirements specified in other L4s: a.  for valids, ECSMETV files following the BMGTValidsMetadata.dtd b.  for collection metadata, ECSMETC files following the BMGTCollectionMetadata.dtd c. for granule metadata, ECSMETG files following the BMGTGranuleMetadata.dtd d. for granule QA updates and Browse link updates, ECSMETU files following the BMGTUpdateMetadata.dtd e. for Browse metadata, ECSBBR / BRF files following the BMGTBrowseMetadata.dtd f. for public Data Pool URL changes, BulkURL files following the BMGTUpdateMetadata.dtd g.  ECS browse files referenced in the ECSBBR / BRF files h. for updates to granule visibility, granule visibility export files following the BMGTUpdateMetadata.dtd.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00685	The BMGT shall export the following changes to inventory metadata of science granules that belong to collections enabled for granule metadata export: a. insertion of a science granule into the ECS inventory b. logical deletion of a science granule from the ECS inventory and undoing of such a deletion c. hiding and un-hiding of a science granule via update to a Boolean visibility attribute called Visibility, as specified in the ECHO granule xsd schema d. marking a science granule as deleted from archive e. moving a science granule to a different collection f. updating the core QA metadata of a granule g. adding or removing links between a science granule and browse granules h. updating any other granule metadata that are part of the BMGTGranuleMetadata.dtd i. adding a science granule to the public Data Pool j. removing a science granule from the public Data Pool k. changes to public Data Pool URLs of science granules (for example, as might result from a collection move) 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00690	The BMGT shall export the full set of science granule metadata referenced by and in accordance with the BMGTGranuleMetadata.dtd defined in the ECS-ECHO ICD for the following changes provided that the collection to which the granule belongs is enabled for granule metadata export: a. insertion of a science granule into the inventory b. moving a science granule to a different collection if the target collection is enabled for granule metadata export c. updating any science granule metadata other than those referenced in requirement S-BGT-00695 and S-BGT-00700 d. undoing a previous logical deletion of a science granule	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00695	The BMGT shall export updates to science granule metadata referenced by and in accordance with the BMGTUpdateMetadata.dtd defined in the ECS-ECHO ICD for the following changes: a. hiding and un-hiding of a science granule via update to the granule visibility attribute b. updating the core QA metadata of a granule c. updating the links between a science granule and its browse granules  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00700	The BMGT shall export changes to the public Data Pool URLs for science granules in a BulkURL file in accordance with the BMGTUpdateMetadata.dtd defined in the ECS-ECHO ICD and separate from other granule metadata updates, to include: a. adding a public Data Pool URL for a science granule b. deleting a public Data Pool URL for a science granule c. updating the public Data Pool URL of a science granules [NOTE: URL changes are exported in a separate file because they are not included in the bulk metadata files archived in ECS.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00705	The BMGT shall export the removal of granules from the public Data Pool that were identified for removal by a Data Pool pre-delete run immediately following the completion of the pre-delete run (i.e., regardless of export cycle boundaries). 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00710	The BMGT shall export the removal of granules from the public Data Pool that occurred as part of a Data Pool clean up run immediately following the completion of the cleanup run (i.e., regardless of export cycle boundaries), except for granules whose removal was already reported (e.g., because of requirement S-BGT-00705), and subject to the constraints in S-BGT-00750 and S-BGT-00755. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00715	The BMGT shall re-export the Data Pool URL and visibility attribute for any granules for which it exports granule metadata updates by exporting the full set of science granule metadata as per requirement S-BGT-00690. [NOTE: When exporting the full metadata for a granule in ECSMETG, all granule metadata not included in ECSMETG must also be exported so the external metadata clearinghouse can perform a full granule replacement.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00720	The BMGT shall include in the BulkURL file exported after Data Pool pre-delete or cleanup runs, also any other removals of granules from the public Data Pool that were not exported before, subject to the constraints in S-BGT-00750 and S-BGT-00755. [NOTE: The intent of this requirement is to communicate granule removals to the external metadata clearing house as early as possible Note that in case of a predelete / finishdelete cleanup sequence, URL removals are reported during the predelete phase, not during the finishdelete phase.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00725	The BMGT shall include an entry in the ECSMETG file for a granule that identifies the granule and the   and conforms BMGTGranuleMetadata.dtd defined in the ECS-ECHO ICD, for the following changes: a. logical deletion of a science granule from the ECS inventory b. marking a science granule as deleted from archive c. moving a science granule to a different collection if the source collection is enabled for granule metadata export 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00730	The BMGT shall consolidate the granule events reported in ECSMETG- or ECSMETU files within an automatically generated export package such that the granule is exported only once within the package. [NOTE: For example, if a granule is inserted, then has its core QA metadata updated, and then the cloud cover attribute is updated, only one set of metadata changes is exported for the granule - in this case, its complete set of  metadata in the ECSMETG file. Note that events reported in BulkURL files are consolidated separately.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00735	The BMGT shall not export granule events if the deletion of the collection containing the granules is exported within the same package.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00740	The BMGT shall consolidate the public Data Pool URL changes of granules such that at most one URL change for a granule is reported per metadata export package. [NOTE: For example, if a granule is inserted and removed from the public Data Pool within the same export cycle, no URL is exported.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00745	The BMGT shall not report a public Data Pool insert for a granule if at the time of the creation of the export file, the granule is no longer in the public Data Pool or no longer in the ECS inventory. [NOTE: This prevents exporting URL information that is already obsolete at the time of export.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00750	The BMGT shall not report the removal of a granule from the public Data Pool if the removal of the granule from the ECS inventory is reported in the same export package or was exported in a previous export package. [NOTE: This is to prevent reports of spurious errors.  The external metadata Clearinghouse will remove the URL as part of removing the granule from its inventory.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00755	The BMGT shall not report the removal of a granule from the public Data Pool if the insert of the granule into the public Data Pool has not yet been reported. [NOTE: This is to prevent reports of spurious errors.  The external metadata Clearinghouse will remove the URL as part of removing the granule from its inventory.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00760	The BMGT operator GUI shall allow DAAC staff to view, define and maintain the maximum size of ECSMETG files.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00765	The BMGT shall create separate ECSMETG files within a metadata export package per collection group and segment them such that each ECSMETG segment does not exceed a maximum size configured by DAAC staff.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00780	The BMGT shall export the following changes to browse metadata:    a. insertion of a browse granule into the ECS inventory once the first link for that browse granule is established b. deletion of a browse granule from the ECS inventory once the last link to that browse granule is removed c changes in cross references between science and browse granules.  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00785	The BMGT shall report insertions of browse granules by providing all applicable metadata referenced by and in accordance with the BMGTBrowseMetadata.dtd defined in the ECS-ECHO ICD. [NOTE: The BrowseGranuleId will be ignored by ECHO and it no longer needs to be filled.  Under no circumstances shall it be used to reflect the UR of cross referenced science granules - the links between science granules and browse granules are reported in the ECSMETG and ECSMETU in accordance with requirements S-BGT-00695 and S-BGT-00690.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00790	The BMGT shall report  deletion of browse granules in the ECSBBR file by providing the deletion time using the   tag in accordance with the ECSBBR DTD .	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00795	The BMGT shall export the browse file for a browse granule when reporting the insertion of a browse granule in the ECSBBR file, in accordance with the ECSBBR DTD.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00800	The BMGT shall create separate ECSBBR files within a metadata export package for each collection group and such that no ECSBBR file contains more than a maximum number of browse granules specified by the DAAC staff. [NOTE: DAACs need to ensure that the different groups will not share the same browse granules.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00805	The BMGT operator GUI shall allow DAAC staff to view, define and maintain the maximum number of browse granules in a single ECSBBR file. [NOTE: Today the limit is in terms of the number of browse cross references.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00810	The BMGT shall be able to create an export package for the following aggregate export workload within an hour or less: a. 10,000 granule inserts b. 25,000 granule deletions c. 50,000 granule QA updates d. 10,000 granule DPL inserts e. 25,000 granule DPL deletions f. 5,000 other granule metadata updates g.. 50 collection inserts or updates h. one (1) ECSMETV product i. 5,000 browse inserts and associated cross references and browse files	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00815	The BMGT shall be able to create export packages for the following exports at the indicated rates: a. granule inserts and deletions at no less than 50,000 inserts or deletions per hour b. granule core QA metadata updates at no less than 100,000 updates per hour c. public Data Pool URL inserts, removals, and changes at no less than 100,000 inserts or removals per hour d. other granule metadata updates at no less than 25,000 updates per hour e. collection metadata exports at a rate of no less than 900 collections per hour f.  bulk browse exports at a rate of no less than 25,000 browse granules per hour, including the accompanying ECSMETV file	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00820	The BMGT shall generate a separate export package for each manual export operation 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00825	The BMGT shall generate a separate export package for each export cycle during automatic operation subject to the exceptions specified in S-BGT-00755. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00830	The BMGT shall assign a consecutive sequence number to each metadata package that it generates, except in manual mode in cases where a package is not exported to the metadata clearinghouse or DAAC staff requests that no sequence number be assigned, or a previously generated package is re-generated as per instructions from DAAC staff (see requirements S-BGT-00955, S-BGT-00940).	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00835	The BMGT shall create a uniquely named directory to hold the files that belong to a single metadata export package.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00840	The BMGT shall name the ECSMETV, ECSMETC, ECSMETG, ECSMETU, and ECSBBR files in a metadata export package in accordance with the file name pattern    . . . . . . .XML, where: a.   is the three letter site identifier as defined in 170-WP-023-001 b.   is V for ECSMETV files, C for ECSMETC files, G for ECSMETG files, U for ECSMETU files, and 'B' for ECSBBR c.   is the twelve letter group identification assigned by the DAAC, except for the ECSMETV file for which this information is omitted d.   shall represent the start of the time period covered by the export, in the form yyyydddhh, where yyyy is the four digit year, ddd the three digit day of the year, and hh the two digit hour of the 24-hour day.  For automatic exports,  e.   shall represent the end of the time period covered by the export using the same format as the  . For automatic exports, this represents the end of the export cycle; and for manual exports, this represents the end of the time period entered manually (if present).  f.   shall represent the time the metadata export package was created, in the format yyyydddhhmmss, where yyyy is the four digit year, ddd the three digit day of the year, and hh the two digit hour of the 24-hour day, mm the 2-digit minute within the hour, and ss is the two digit second within the minute.  g.   shall be a three digit sequence number assigned to each file when the corresponding export type is segmented into multiple files.  h.   shall be a three digit number providing the total number of files into which the export type was segmented.  i.   the 6-digit sequence number assigned to this export package [NOTE: Note that ECSMETU files will be broken up by group similar to the other metadata files, but unlike today.   Note the resultant total file name length of at most 69 characters.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00842	The BMGT shall name the BulkURL files in a metadata export package in accordance with the file name pattern   . . . . . . .XML, where: a. where  ,  ,  ,  ,  ,   and   are as defined in requirement S=BGT-00840 b.   is 'L' for BulkURL files c. for exports of bulk URL deletions after public Data Pool cleanup the   and   represent the time the granules were selected for removal. [NOTE: The resultant total file name length of at most 57 characters]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00843	The BMGT shall name the files in a metadata export package that export granule visibility (i.e., hide/unhide) in accordance with the file name pattern   . . . . . . .XML, where: a. where  ,  ,  ,  ,  ,   and   are as defined in requirement S-BGT-00840 b.   is 'H' for visibility export files [NOTE: The resultant total file name length of at most 57 characters]  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00845	The BMGT shall name ECS browse files in accordance with their internal file name and their file type.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00850	For operation an automatic mode, the BMGT operator GUI shall allow DAAC staff to view, define and update the length of bulk metadata export cycles; such cycles shall be measured in hours and shall be an integer fraction of day, i.e., 24, 12, 8, 6, 4, 3, 2, or one hours long.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00855	The BMGT shall apply any update to the length of a bulk metadata export cycle starting with the first export cycle of the following day.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00860	The BMGT shall consider metadata update events to occur within a given export cycle if the time at which the event occurred is greater than or equal to (>=) the start time of the export cycle and less than ( [NOTE: That is, export cycles are time intervals closed at the start time and open at the end time of the cycle.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00865	The BMGT shall allow DAAC staff to cause the regular execution of automatic bulk metadata exports commensurate with the length of a bulk metadata export cycle. [Note: It is assumed that the DAAC will define cron entries that will ensure that automatic metadata export is started at least once per export cycle.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00870	When executing in automatic mode, the BMGT shall generate a metadata export package for each past export cycle not yet covered by metadata export. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00875	When executing in automatic mode, the BMGT shall detect when the generation of a metadata export package for a previous export cycle did not complete and restart the generation from a suitable check point prior to proceeding to the next export cycle. [NOTE: The checkpoints for restarting an interrupted export operation must be at least at the level of completed output by collection group respectively file type.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00880	When executing in automatic mode, the BMGT shall include in an export cycle the collection metadata for collections that were newly enabled for collection metadata export, at the latest in the export package for the cycle during which the change occurred	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00885	When executing in automatic mode, the BMGT shall include in an export cycle the granule metadata for the granules that belong to collections (as of the end of the export cycle) that were newly enabled for granule metadata export , at the latest in the export package for the cycle during which the change occurred. [NOTE: Automatic export must cover all relevant events. It cannot rely on manual exports previously having exported information because there is no guarantee for these exports to be processed by ECHO in the correct sequence or at all. DAAC staff should not export information manually that is still subject to automatic export, as this would require ECHO to process the information twice.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00890	When executing in automatic mode, the BMGT shall determine whether there are any ECS inventory metadata data events that should have been exported during export cycles that precede the first export cycle of the current export operation, and if so, log these events and then include the current state of the corresponding metadata item (collection, science granule, browse and related links) in the first export cycle of the current export operation. [NOTE: This should never happen, but is intended to guard against errors.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00895	When executing in automatic mode, the BMGT shall ensure that the metadata export package it generates is internally consistent. [NOTE: At a minimum, the ECHO inventory must not be left in an inconsistent state that requires correction via a manual export operation; but it is also undesirable to cause spurious errors in the ingest summary report.  Inconsistencies can occur because the state of the ECS inventory will change while the BMGT generates the export files, causing potential race conditions.  For example, during the BMGT run, a browse granule and cross reference may be added to the inventory after the BMGT generated the ECSBBR export file, but before it generates the ECSMETG file.  If the granule metadata in the ECSMETG file include a reference to the newly inserted browse granule, ECHO would reject the cross reference since the browse was not exported.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00900	When executing in automatic mode, the BMGT shall generate one and only one metadata export package for each export cycle, except in the following case: a. the BMGT shall not generate a metadata export package for export cycles during which there were no inventory metadata changes. [NOTE: For example, if the length of an export cycle was configured to 6 hours and export operations for three cycles were missed for some reason, the next export operation would cover four cycles, i.e., 24 hours. On the other hand, if metadata generation is caught up and the BMGT is started before the end of the current cycle, no metadata package would be generated.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00905	The BMGT shall use local time to establish the boundaries of the bulk metadata export cycles. [NOTE: During transitions between standard time and daylight savings time, the export cycle will be one hour shorter respectively longer. If the DAAC chose an export cycle of one hour, the transition day to daylight savings time will contain one export cycle less.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00910	The BMGT shall provide a 'manual operation' mode which permits the DAAC staff to request specific types of operations via command line parameters or via an input file. [NOTE: The intent is to permit DAAC staff to use this capability to perform historic exports for collections newly made public; and to correct ECHO metadata holdings.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00915	The BMGT shall permit DAAC staff to perform several export operations as part of a single manual invocation. [NOTE: This capability can be limited where different exports require different or conflicting options (e.g., date ranges or inclusion/exclusion of browse.]  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00920	The BMGT shall generate a separate metadata export package for each manual invocation. [NOTE: It will be the responsibility of DAAC staff to communicate with ECHO operations as necessary to ensure that they are ingested in the correct sequence if the packages are intended for export to the external metadata clearing house.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00925	The BMGT shall permit DAAC staff to specify as part of the command line parameters for a manual export operation whether generated metadata files shall be archived in ECS.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00930	The BMGT shall permit DAAC staff to specify as part of the command line parameters whether a manually generated metadata export package shall be exported to the external metadata clearing house.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00935	The BMGT shall permit DAAC staff to specify as part of the command line parameters that a manually generated metadata export package intended for export to the external metadata clearing house shall not be assigned an export sequence number. [NOTE: The place in the processing sequence at which ECHO is to process this export package is subject to negotiation between DAAC and ECHO and is not subject of this ticket.]  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00940	The BMGT shall assign the next available export sequence number to a manually generated metadata export package intended for export to the external metadata clearing house, unless the requested operation was to re-generate an export package for a previously processed automatic export cycle or the DAAC staff explicitly requested that no sequence number be assigned.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00945	The BMGT shall permit DAAC staff to specify a string up to 40 characters long and consisting only of valid Unix file name characters (excluding period) to be included as part of the file names in the metadata export package created by a manual export operation. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00950	The BMGT shall permit DAAC staff to request via a manual export operation the regeneration of an export package for one or several past automatic export operations. [NOTE: DAAC staff would do this if the original package was corrupted, for example, by some hardware fault. If the state of a package is EXPORTED, DAAC staff is expected to coordinate with ECHO to ensure that the package was not and will not be processes by ECHO.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00952	The BMGT shall not permit DAAC staff to request the regeneration of an export package for one or several past automatic export operations for the purpose of export to ECHO if the state of the operation is COMPLETE. [NOTE: If the state of a package is EXPORTED, DAAC staff is expected to coordinate with ECHO to ensure that the package was not and will not be processes by ECHO.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00955	When re-generating an automatic export package that was previously generated, the BMGT shall re-assign the sequence number originally assigned to that package if the package is intended for (re-)export to ECHO.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00960	The BMGT shall permit DAAC staff to request  via a manual export operation the export of the current set of valids, for archiving in ECS only.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00965	The BMGT shall permit DAAC staff to request via a manual export operation the export of one or several collections enabled for collection metadata export, with the collections listed in an input file.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00966	The BMGT shall permit DAAC staff to request via a manual export operation the export of the removal of one or several collections from the inventory, provided the collections are indeed deleted or no longer in the inventory.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00970	The BMGT shall permit DAAC staff to request via a manual export operation the export of science granule metadata for one or several collections enabled for granule metadata export, with the collections specified on the command line or listed in an input file, optionally for a specific time period of science granule insert into the ECS inventory, and optionally request the inclusion of the related browse granules and their metadata. [NOTE: This will produce one or several ECSMETG files containing the metadata for current granules in the specified collections and (if needed) a BulkURL file containing their public Data Pool URLs.  The granules for a collection will not be exported unless the collection is enabled for granule metadata export. Note that if browse granules are included in the export, the export will also include all browse links for the browse granules, i.e., not just those for the exported science granules.  When that occurs, these additional links would be in an ECSMETU file.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00972	The BMGT shall permit DAAC staff to request via a manual export operation the export of browse metadata, optionally for a specific time period constraining the time period during which these browse granules were inserted into the ECS inventory. [NOTE: This will produce ECSBBR export files exporting the current browse granules, and will export the all granule-browse links for the exported browse granules.]  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00975	The BMGT shall permit DAAC staff to request via a manual export operation the export of browse metadata cross referenced with granules in one or several collections, with the collections specified in an input file, optionally for a specific time period constraining the time period during which these science granules were inserted into the ECS inventory. [NOTE: This will produce ECSBBR export files exporting the current browse granules related to these collections, and will export the all granule-browse links for the exported browse granules.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00980	The BMGT shall permit DAAC staff to request via a manual export operation the export to ECHO of the public Data Pool URLs for the science granules of one or several collections, with the collections specified in an input file, optionally for a specific time period of science granule insert into the public Data Pool. [NOTE: This will produce a BulkURL file containing the public Data Pool URLs for the public granules of the specified collections. BulkURL files are not archived and a request to export URLs for archiving only are not valid.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00985	The BMGT shall permit DAAC staff to request via a manual export operation the export of science granule metadata for one or several granules, with the granules specified on the command line or listed in an input file, and optionally request the inclusion of the related browse granules and their metadata. [NOTE: This will produce one or several ECSMETG files and (if needed) a BulkURL and other bulk metadata update files containing the current metadata, current public Data Pool URLs, and visibility flag for the specified granules. Note that if browse granules are included in the export, the export will also include all browse links for the browse granules, i.e., not just those for the exported science granules.  When that occurs, these additional links would be in an ECSMETU file.  A granule will not be exported unless its collection is enabled for granule metadata export and the granule is indeed in the inventory and neither deleted from archive or logically deleted.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00990	The BMGT shall permit DAAC staff to request via a manual export operation the export to ECHO of the public Data Pool URLs for one or several science granules, with the granules specified on the command line or listed in an input file. [NOTE: This will produce a BulkURL file containing the current public Data Pool URLs for the specified granules. A URL will not be exported if the granule is not in the public Data Pool.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-00995	The BMGT shall permit DAAC staff to request via a manual export operation the export of deletions of science granules from the ECS inventory for one or several granules, with the granules specified on the command line or listed in an input file. [NOTE: This will produce one or several ECSMETU files indicating the deletion from the ECS inventory for the specified granules, except for granules that are still in the inventory and not deleted from archive nor logically deleted.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01000	The BMGT shall permit DAAC staff to request via a manual export operation the export the removal of the public Data Pool URLs for one or several science granules, with the granules specified on the command line or listed in an input file. [NOTE: This will produce a BulkURL file exporting the deletion of the specified granules from the Data Pool.  The deletion will not be exported if the granule is in the public Data Pool.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01005	The BMGT shall permit DAAC staff to request via a manual export operation the export of browse metadata for one or several browse granules, with the browse granules specified on the command line or listed in an input file. [NOTE: This will produce ECSBBR export files exporting the specified browse granules, as well as export the corresponding browse links, provided the browse granules are in the ECS inventory and not flagged deleted. Browse cross references will be exported on this occasion in an ECSMETU file.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01010	The BMGT shall permit DAAC staff to request via a manual export operation the export of deletions of browse granules from the ECS inventory for one or several browse granules, with the granules specified on the command line or listed in an input file. [NOTE: Browse granules will not be exported as deleted unless the browse granules are not in the ECS inventory or flagged as deleted.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01015	When a time interval is specified, the BMGT shall interpret it as closed at the beginning date/time and open at the ending date/time, i.e., include events that occurred at a time greater than or equal to (>=) the beginning date time and less than (<) the ending date/time.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01020	When operating in automatic mode for export to the external clearing house, the BMGT shall not omit related inventory updates from export to the external clearing house even if the manual export included the corresponding inventory objects. [NOTE: The BMGT cannot rely on manual operations to export changes to the ECS inventory reliably and in the correct order. The BMGT must export such changes regardless of whether the changed information was included in a manual operation. ] . 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01025	The BMGT shall allow the concurrent execution of manual and automatic export operations in the same mode unless DAAC staff explicitly requests otherwise when starting the manual export. [NOTE: If the DAAC performs a manual run requesting exclusion of concurrent automatic runs, this will affect automatic export of export cycles and of bulk granule deletions following Data Pool cleanup.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01027	Upon starting a manual export operation, the BMGT shall detect concurrent manual export operations in the same mode, inform the operator, and prompt the operator as to whether to continue or exit.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01028	The BMGT shall not perform two automatic export operations concurrently, with the exception of being able to execute  concurrently the automatic export for export cycles and the export of bulk granule deletions following Data Pool cleanup. [NOTE: Other kinds of concurrent automatic executions are superfluous since any automatic execution will process all past un-exported cycles.  This requirement merely prevents undesirable race conditions.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01030	If starting the automatic generation of an export package is not possible because of concurrent export operations as per requirement S-BGT-01025, the BMGT shall start the generation of that package as soon as the conflicting export operations complete package generation. [NOTE: For example, a manual export operation may prevent an automatic export operation from starting; or the regeneration of a package for which the ingest summary reported a failure may be prevented because the generation of the next export package has already started.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01031	The BMGT operator GUI shall indicate on its main monitoring screen whether there is a BMGT export currently in progress,	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01035	The BMGT shall allow DAAC staff to rerun a manual bulk metadata export operation if the generation of the package was interrupted by an error or fault prior to the start of the FTP transfer. [NOTE: The intent of this requirement is to guarantee that if the DAAC staff elects to rerun the export command, BMGT will not cause that export to fail just because it was attempted before, e.g., because of left-over files or rows in the database.  There are separate requirements regulating recovery from errors that occur during FTP operation, see requirements S-BGT-01130 to S-BGT-01150.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01036	The BMGT shall skip the export of inventory objects if it encounters data related errors. [NOTE; A data related error is one that occurs because the data for an ECS inventory object are invalid.  For example, an ill-formed XML file or inconsistencies in some granule or collection data which make it impossible for the BMGT to create the export information for that object would be considered a data error.  On the other hand,  a file open, file read, or DBMS access error is  not considered a data related error. As per requirement S-BGT-01260, the BMGT must log the error and related information, including identifying information for the item that was skipped.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01037	The BMGT shall terminate an export operation if the number of objects or events skipped due to data related errors encountered during package creation exceeds a DAAC configured limit. [NOTE: Whether to count a skipped event or a skipped inventory object in a given situation is subject to design considerations and left open by the requirement.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01038	The BMGT shall terminate the creation of an export package in case of failures (other than data related errors) that persist once the DAAC configured number of retries has been reached. [NOTE: Once the package has been generated, the BMGT is responsible for delivering it to ECHO, retrying indefinitely to do so in case of errors.  DAAC staff will need to cancel the export as per S-BGT-01140 and then manually re-run it if the retries are caused by an irrecoverable error, e.g., a persistent read error when trying to read the package from disk.].	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01039	The BMGT shall update the status of a package to a status of 'PRODUCT GENERATE FAILED' or 'PACKAGE GENERATE FAILED' in line with requirement S-BGT-01250 when the BMGT terminates the creation of an export package prematurely.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01040	The BMGT shall provide the ECSMETV, ECSMETC, ECSMETG, ECSMETU, and ECSBBR files of all automatically generated metadata export packages for ingest into ECS.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01041	The BMGT shall notify DAAC staff via e-mail to a DAAC configurable e-mail address when the creation of an export package encountered data related errors that caused events or inventory objects to be skipped, and include the number of and nature of the skipped objects or events in the e-mail. [NOTE: DAAC staff is expected to use the BMGT log to identify the skipped events and/or objects, determine the appropriate steps needed to correct the problem, and ensure that any missing information is exported to ECHO.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01042	When recovering an automatic export that failed, the BMGT shall regenerate any export files that were affected by data related errors, i.e., during the creation of which events or objects were skipped. [NOTE. BMGT recovery logic may contain provisions to not regenerate completed export files, as per requirement S-BGT-00875. This is undesirable if these files are incomplete due to data related errors - which may have been corrected in the meantime.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01043	The BMGT operator GUI shall allow DAAC staff to view, define and maintain a. the limit for the number of events or inventory objects that may be skipped while generating an export package, which when exceeded will cause the BMGT to terminate the creation of that export package, b. a retry delay and the number of retries to be attempted when the BMGT encounters a failure that is not a data error.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01044	The BMGT operator GUI shall allow DAAC staff to view, define and maintain the retry delay and the number of retries to be attempted when the BMGT encounters a failure that is not a data error.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01045	For metadata export packages intended for ingest into ECS, the BMGT shall generate metadata files needed to ingest the export package into the ECS archive in accordance with the corresponding ECS ESDT specifications and place them into the directory containing the metadata export package.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01046	The abnormal or premature termination of an export operation that was assigned an export sequence number shall not cause a gap in export sequence numbers, i.e., it shall not stall ingest processing by ECHO. [NOTE: If an export package is assigned an export sequence number and that package is then not exported to ECHO, ECHO will not process subsequent packages until it receives a package with that sequence number.  For example, the BMGT cold generate an empty package for the sequence number that otherwise might be missing and transfer it to ECHO.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01047	The BMGT shall derive a temporal coverage for any bulk metadata granules generated during manual export operations that specify archiving in the following manner: a. If the export operation includes granule or collection metadata,  use the earliest insert time of any of the objects (i.e., granules or collections) for which metadata are exported as the beginning of the temporal coverage b. If the export operation does not include granule or collection metadata, use the current time (i.e., the time the operator initiated the export operation) as the beginning of the temporal coverage c. use the current time (i.e., the time the operator initiated the export operation) as the end of the temporal coverage. [NOTE: This is to prevent subsequent errors, since the BMGT granules do require a start and end time to be provided upon ingest into the ECS archive.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01050	The BMGT shall use the beginning and ending date and time of the export cycle respectively the time period specified by DAAC staff for a manual export operation as the temporal coverage of the corresponding bulk metadata granules.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01055	The BMGT shall use the following rules to determine the files that constitute separate granules for the purpose of ingest into ECS: a.  each ECSMETV file is a separate granule b. each ECSMETC file is a separate granule c. the ECSMETG files for the same collection group constitute a granule d. the ECSMETU files for the same collection group constitute a granule e.  each ECSBBR file is a separate granule	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01060	For metadata export packages intended for ingest into ECS, the BMGT shall generate a Product Delivery Record (PDR) file in accordance to the ECS SIPS interface (423-41-57 section 4.5.3) that can be used to ingest the metadata export package: a. in automatic mode always, and b. in manual mode if so directed by the run time parameters supplied by the DAAC staff. [NOTE: This supersedes S-BGT-00090.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01065	The BMGT operator GUI shall allow DAAC staff to view, define and update the polling directory into which to deposit generated PDR files for the ingest of BMGT metadata export packages.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01070	In  automatic mode, the BMGT shall name a PDR file in accordance with the file name pattern  AutomaticExport. . . . .PDR, where  ,  ,  ,  , and   are as defined in S-BGT-00840. [NOTE: This supersedes S-BGT-00100.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01075	In manual mode, the BMGT shall name a PDR file in accordance with the file name pattern  ManualExport.  . . . . .PDR, where  ,  ,  ,  ,  ,   and   are as defined in S-BGT-00840, and   and  [NOTE: This supersedes S-BGT-00100.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01085	The BMGT shall export all automatically generated metadata export packages to an external metadata clearinghouse.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01087	The BMGT shall exclude ECSMETV files from the packages exported to the ECHO metadata clearinghouse.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01090	For export to an external metadata clearinghouse, the BMGT shall generate a manifest file that lists the ECSMETC, ECSMETG, ECSMETU, ECSBBR, and BulkURL and visibility export files in the metadata export package in accordance with the ECHO PackageManifest.xsd.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01095	The BMGT shall name manifest files manifest.xml.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01100	For export to an external metadata clearinghouse, the BMGT shall compress and consolidate the files in a metadata export package into a single file using the Unix zip utility.  This shall exclude browse files, but shall include the manifest file. [NOTE: The PDR and metadata files generated by the BMGT for ingest into ECS are not considered part of an export package.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01105	The BMGT shall name the consolidated compressed export files generated in automatic mode in accordance with the file name pattern  AutomaticExport. . . . .zip, where  ,  ,  ,  , and   are as defined in S-BGT-00840. [NOTE: The length of this file name is 63 characters.] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01110	The BMGT shall name the consolidated compressed export files generated in manual mode in accordance with the file name pattern  ManualExport. . . . . .zip , where  ,  ,  ,  , and   are as defined in S-BGT-00840,   is an optional string provided by DAAC staff as per requirement S-BGT-00945,   and the separating period may be missing as per requirement S-BGT-00935, and   and  [NOTE The length of this file name is 61 characters plus the length of the optional DAAC chosen string (max. 40 characters) if an export sequence number is present, else 54 characters plus the length of the DAAC chosen string .] 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01115	The BMGT shall FTP push a consolidated metadata export package and its browse files to the external metadata clearing house. 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01120	The BMGT operator GUI shall allow DAAC staff to view, define and update the FTP push destination (i.e., host, directory) and login parameters for the external metadata clearing house.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01125	The BMGT shall use the most current FTP push destination (i.e., host, directory) and login parameters for the external metadata clearing house on each FTP push attempt.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01130	The BMGT shall retry FTP push delivery of a metadata export package in case of errors indefinitely unless the delivery is cancelled by DAAC staff.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01135	The BMGT operator GUI shall permit DAAC staff to suspend and resume the BMGT FTP service.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01136	The BMGT operator GUI shall indicate on its main monitoring screen whether the BMGT FTP service is currently executing and whether it is suspended.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01140	The BMGT operator GUI shall permit DAAC staff to cancel the delivery of a metadata export package to the external metadata clearing house. [NOTE: It is assumed that the DAAC staff will need time to fix whatever problem required the cancellation.  As a result, automatic exports that are canceled are not automatically restarted next time an automatic export operation begins.  Rather, the DAAC staff is expected to restart them by performing a manual export operation requesting regeneration of the package and providing appropriate command line instructions such as whether to export and/or ingest the package.  DAAC staff will need to resubmit manual exports that are cancelled if the DAAC staff wishes to re-attempt the export operation.  There is no separate capability to recover or regenerate them.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01145	The BMGT operator GUI shall allow DAAC staff to view, define and update configuration parameters that determine a. the wait time between FTP push retries b. the number of retries that shall trigger an alert	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01150	The BMGT shall trigger an alert when the configured number of FTP push retries has been reached, and clear the alert when a subsequent retry successfully complete the ftp push operation.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01155	The BMGT shall obtain new ingest summary reports from the external metadata clearing house via FTP Pull.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01160	The BMGT shall save ingest summary reports in a directory location configurable by DAAC staff.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01161	The BMGT shall remove the ingest summary reports from the ECHO location from which it was obtained after successfully retrieving and saving it locally.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01165	The BMGT operator GUI shall permit DAAC staff to view, define and update, the directory location for saving ingest summary reports. [NOTE: That directory is assumed to be cleaned up manually.  Under no circumstances shall ECS clean up this directory automatically.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01170	The BMGT shall use the ingest summary report to determine whether the external metadata clearing house reported any errors and whether the external metadata clearing house did not process bulk metadata exports in the designated sequence. [NOTE: Ingest summary reports will comply with the ECHO XML schema.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01175	The BMGT shall record the occurrence of errors in the audit trail maintained for the export package.  	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01180	The BMGT shall recompress and re-transmit an automatic export package to the external metadata clearing house after an operator configurable retry delay if the ingest summary report contains one of the following error responses indicating a retriable decompression or transmission error. a. manifest is corrupt b. manifest is missing c. package files are missing d. there are extraneous package files e. the package was corrupt. [NOTE: Manual export processes that return these errors will be considered failed.  It will be up to the operator to determine the appropriate action, e.g., re-attempting the manual run.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01185	The BMGT shall regenerate, recompress, and re-transmit an automatic export package to the external metadata clearing house if the ingest summary report contains one of the following error responses indicating an error reading one of the transmitted XML files a. ECHO did not process the package due to ECHO operator intervention b. a metadata file failed validation. [NOTE: Manual export processes that return these errors will be considered failed.  It will be up to the operator to determine the appropriate action, e.g., re-attempting the manual run.] [NOTE: It is OK to cause the package to be re-ingested into ECS on that occasion.  When metadata file validation fails, the metadata file is most likely corrupt and thus should be re-ingested into ECS.  If ECHO operations failed the ingest, the reason for that is not known but the safe reaction is to re-ingest the package.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01190	The BMGT shall notify DAAC staff via e-mail to an e-mail address configured by DAAC staff when an FTP alert is triggered and when it is cleared, identifying the bulk metadata export package and nature of the alert in the e-mail subject line and details in the message body (e.g., the nature of the FTP error). [NOTE:  The intent is to keep these notifications compatible with corresponding e-mail alerts from DPL Ingest.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01191	The BMGT operator GUI shall display on its main monitoring page whether there is an FTP alert pending.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01195	The BMGT shall notify DAAC staff of errors identified in the ingest summary report via e-mail to an e-mail address configured by DAAC staff. [NOTE: This includes reporting decompression errors.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01200	The BMGT operator GUI shall permit DAAC staff to view, define and maintain the: a. limit for the time from stating the automatic creation of a metadata export package to the time it begins transmittal, b. time limit for receiving an ingest summary report after a metadata export package was transferred successfully. c. a delay time before trying the re-generation and /or re-compression of automatic export package (e.g., as per S-BGT-01180). 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01205	The BMGT shall notify DAAC staff via e-mail to an e-mail address configured by DAAC staff when an automatic export operation has started but has not begun transmission within a configurable time limit.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01210	The BMGT shall notify DAAC staff via e-mail to an e-mail address configured by DAAC staff when an ingest summary report has not been received within a configurable time limit after completion of successful transmission.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01215	The BMGT shall notify DAAC staff via e-mail to an e-mail address configured by DAAC staff when the external metadata clearing house did not process bulk metadata exports in the designated sequence.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01220	The BMGT operator GUI shall permit DAAC staff to view, define and maintain an e-mail address for notifications regarding bulk metadata export errors and alert.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01225	In e-mail notifications regarding metadata export errors, the BMGT shall identify the bulk metadata export package and indicate the occurrence and nature of the error in the e-mail subject line; and include applicable detailed error information in the e-mail body, such as a pointer to the ingest summary report file and summary error statistics.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01230	The BMGT shall maintain an audit trail for manual and automatic metadata export operations.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01235	The BMGT shall create an audit trail entry for each automatic metadata export cycle and automatic bulk URL export operation, whether or not it resulted in the creation of a metadata export package.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01240	The BMGT shall create an audit trail entry for each manual metadata export operation intended for export to the external clearinghouse if it resulted in the creation of a metadata export package. [NOTE: This wording has been chosen to leave the option to create audit trail entries also for manual export operations that are only intended for archiving if that is desirable from a design perspective.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01245	The BMGT shall include the following information in each audit trail entry: a. metadata export sequence number (if one was assigned), b. start and end of the time period covered by the export (if applicable), c. type of export (i.e., manual or automatic or bulk DPL cleanup), d. DELETED, e. current export status, f. export statistics, g. error statistics (if applicable) as received in the ingest summary report, h. other error information (if applicable), i. time the creation of the metadata export started, j. time the creation of the metadata export package completed, k. time the transmission of the package started, l. time the transmission of the package completed, m. time the ingest summary report from the external metadata clearing house was received n. time of last status update o. name of the export directory p. name of the file containing the ingest summary report sent by the external metadata clearing house (if received) q. retry count r. name of the external clearinghouse (set to be ECHO) 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01250	The BMGT shall maintain the current status of export of a metadata export package to the external clearinghouse as follows: a. STARTED  when processing for the package was initiated b. PRODUCT GENERATED  when all export files were generated c. PACKAGE GENERATED  when the package is ready for export d. TRANSFERRING  while the package is being pushed e. WAITING TO RETRANSMIT  while the package is waiting for another attempt to complete transmission of an export package to the external metadata clearinghouse f. EXPORTED  when the package was transferred successfully g. COMPLETE  when the ingest summary report was received and no errors where found h. COMPLETE WITH ERRORS  when the ingest summary report was received and errors were found (in which case error statistics in the audit trail must have been populated) or events / inventory objects were skipped during export because of errors i. CANCELLING - while a request submitted via the operator GUI to cancel a package is pending j. CANCELED  when the export was cancelled by DAAC staff k. DELETED l. PRODUCT GENERATE FAILED if at least one of the export files in the package could not be generated due to an error (in which case error information in the audit trail must have been populated) m. PACKAGE GENERATE FAILED - if all the files in the export package were generated successfully but the creation of the manifest file or the compression of the files into a compressed export file failed n. PRODUCT REGENERATE  when a package requires complete regeneration because its ingest summary report indicated a corresponding error (the state of the package will change once regeneration started) o. PACKAGE RETRANSMIT - when a package requires re-compression and re-transmission because its ingest summary report indicated a corresponding error (the state of the package will change once re-compression started) p. NEW - state of any audit trail entry for export operations for which the export has not been attempted yet	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01255	The BMGT operator GUI shall allow DAAC staff to display metadata export audit trail information for the N most recent export operations, where N can be configured by DAAC staff.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01256	The BMGT operator GUI shall allow DAAC staff to display metadata export audit trail information for the N most recent export operations that failed or encountered errors, where N can be configured by DAAC staff.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01257	The BMGT operator GUI shall allow DAAC staff to view, define and maintain the number of export operations to include in the displays specified in requirements S-BGT-01255 and S-BGT-01256.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01258	When displaying metadata export audit trail information, the BMGT operator GUI shall display a link to the ingest summary report for that entry if it exists, such that DAAC staff can view the ingest summary by clicking on this link.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01259	When displaying metadata export audit trail information, the BMGT operator GUI shall allow DAAC staff to view export and error statistics, to include at a minimum: a. number of science granule inserts or replacements, updates (separately by QA updates and other updates), and deletions exported in the ECSMETG and ECSMETU files by collection group and in total, b. total number of Data Pool URL inserts, removals, and updates exported in a BulkURL file c. total number of science granule hide/unhide flags exported in a granule visibility export file d. number of browse granule inserts or replacements, and deletions exported in ECSBBR files by collection group and in total e. number of collection inserts or replacements, and deletions exported in the ECSMETC files by collection group and in total, f. whether or not a valids file was exported, g. number of science granules skipped during export due to errors, h number of browse granules skipped during export due to errors i. number of collections skipped during export due to errors j. number of errors reported by ECHO, to the extent that information is available in the ECHO ingest summary report [NOTE: The requirement does not prescribe the manner in which the information is displayed.  For example, the GUI may retrieve it from the database and display in tabular form in the GUI; or the GUI may provide a link to an XML file which contains these statistics.]	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01260	The BMGT shall log all errors and related error information, including events, granules, and collections that were skipped, e.g., when their export was requested during a manual export operation but the corresponding collection was not enabled for export.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01270	The BMGT shall log the start and completion of creating an export package.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01275	The BMGT shall log the start and completion of transmitting an export package to the external metadata clearing house.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01280	The BMGT shall log the manual export options upon start of a manual export operation 	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01282	The BMGT shall remove an export directory once archiving in ECS completed successfully (if the export package was intended for ingest into ECS) and an ingest summary report is received that confirms ingest by ECHO without errors (if the export package was intended for export to ECHO).	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01284	The BMGT shall allow DAAC staff to remove audit trail entries that are older than a specified number of days.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01291	The BMGT shall remove export directories for failed export operations and export operations that reported errors at the latest when removing their audit trail information.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01292	The BMGT operator GUI shall be compatible with the EMD baseline versions of web browsers and operating systems in accordance with Technical Document 910-TDA-042-Rev02, EMD Browsers Baseline.	
BE_7B_01	Export of ECS Inventory Information to ECHO	no data				S-BGT-01293	The BMGT operator GUI shall restrict the ability to define and maintain BMGT configuration parameters to DAAC staff logged in as BMGT Administrators.	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01285	The BMGT shall permit DAAC staff to configure the collections (shortname, version ID, and process level) whose granules are eligible for export of browse links to MISBR granules. [NOTE: The 'process level' signifies the rule that must be used to correlate MISR science granules with the MISBR granule that acts as their browse, and is referred to as 'MISR Level' in other BMGT Level 4 requirements in this ticket.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01290	The BMGT shall permit DAAC staff to configure the MISBR collections (shortname and version ID) eligible for export as browse.	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01300	The BMGT shall export the relationship of a MISR Level 1 granule other than a MIB2GEOP granule with a MISBR granule to the external metadata clearinghouse using the rules specified in requirements S-DPL-46840 and S-DPL-46890 in Ticket DP_72_05 and such that the browse link in ECHO will match the browse link in the Data Pool while the MISR Level 1 is public, provided the corresponding collection was configured as eligible for export of browse links. [NOTE: The manner in which the export is performed must guarantee that a browse link in ECHO will match a browse link in the Data Pool once the URL for the MISR science granule is exported to ECHO until such time as the URL removal is exported.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01305	The BMGT shall export the relationship of a MISR Level 2 or MIB2GEOP granule with a MISBR granule to the external metadata clearinghouse using the rules specified in requirements S-DPL-46870 and S-DPL-46890 in Ticket DP_72_05 and such that the browse link in ECHO will match the browse link in the Data Pool while the MISR Level 2 is public, provided the corresponding collection was configured as eligible for export of browse links. [NOTE: The manner in which the export is performed must guarantee that a browse link in ECHO will match a browse link in the Data Pool once the URL for the MISR granule is exported to ECHO until such time as the URL removal is exported.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01310	The BMGT shall export the relationships of a MISBR granule with MISR Level 1 and MISR Level 2 granules to the external metadata clearinghouse using the rules defined in requirements S-DPL-46830, S-DPL-46860, S-DPL-46890 in DP_72_05 such that the browse links in ECHO will match the browse links in the Data Pool while the MISR Level 1 or MISR Level 2 granules are public, provided the corresponding MISBR collection was configured as eligible for export as browse and the corresponding MISR Level 1 and Level 2 collections were configured as eligible for export of browse links. [NOTE: For previously exported MISR Level 1/2 granules, the browse links will be reported in accordance with the ECSMETU DTD in an ECSMETU file; and if the MISR Level 1/2 granules are exported in the same metadata export package, the browse links will be exported in the ECSMETG file as part of the metadata for these granules.] [NOTE: The manner in which the export is performed must ensure that a browse link in ECHO will match a browse link in the Data Pool once the URL for the MISR science granule is exported to ECHO until such time as the URL removal is exported.] 	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01312	When a MISR Level 1, MISR Level 2 or MISBR granule is published in the Data Pool, the BMGT shall re-export its link(s) if this is necessary to ensure consistency between the ECHO and Data Pool browse links. [NOTE: The BMGT may calculate browse links at the time the granule insert is exported to ECHO. If it does, the BMGT may not always be able to check the browse links in the public Data Pool because the granules may not necessarily published in the Data Pool at the time. In cases where this would cause discrepancies between Data Pool browse links and ECHO browse links, the BMGT would need to export browse link corrections.] 	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01315	Except as noted in other requirements in this ticket, the BMGT shall treat the MISBR collection like any other science data collection.	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01320	When a MISBR granule is inserted into the ECS inventory, the BMGT shall export it as a 'browse granule' in the ECSBBR file and provide the MISBR file as the browse file (using the same naming conventions as today), provided the corresponding MISBR collection is configured for export as browse. [NOTE: The export of MISBR as browse granules is independent of MISBR export as science granules.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01325	When a MISBR granule is deleted from the ECS inventory, the BMGT shall export the removal of the corresponding 'browse granule' in the ECSBBR file, provided the corresponding MISBR collection is configured for export as browse.	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01330	The BMGT shall be able to create an export package for the following aggregate export workload within one hour: a. insertion of no less than 8,600 MISR Level 1 and Level 2 granules that are related to MISBR granules  (with all collections configured for browse export), b.  export of no less than 860 related MISBR inserts and their related browse granule inserts, c.  deletion of no less than 8,600 MISR Level 1 and Level 2 granules that are related to MISBR granules (with all collections configured for browse export), d. export of no less than 860 MISBR deletions and their related browse granule deletions.	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01335	When DAAC staff causes the export of science granule metadata for MISR Level 1 and Level 2 granules as part of a manual export operation, the BMGT shall also export the browse links in accordance with requirements (S-BGT-01305) and (S-BGT-01300) in this ticket and such that they are consistent with any current browse links in the public Data Pool. [This requirement requests that the BMGT dynamically determine and include the browse links for non-public MISR science granules in the resulting ECSMETG file(s).  This ensures that any MISR granule that is referenced in the ECSMETG and already exists in ECHO will retain its browse link after ECHO processed the ECSMETG file(s). Note, however, that if MISBR granules were re-processed, the link may now have a different value than before this export.]   	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01337	The BMGT shall permit DAAC staff to request the export of browse metadata for MISBR granules, optionally for a specific time period during which the MISBR granules were inserted into the ECS inventory. [NOTE: This extends the corresponding manual export requirement for normal browse metadata (S-BGT-00972) to MISBR browse metadata.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01340	The BMGT shall permit DAAC staff to request the export of browse metadata for MISBR granules related with granules in one or several MISR Level 1 and Level 2 collections, with the collections specified on the command line or listed in an input file, optionally for a specific time period during which the science granules were inserted into the ECS inventory. [NOTE: This extends the corresponding manual export requirement for normal browse metadata (S-BGT-00975) to MISBR browse metadata.] 	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01345	The BMGT shall permit DAAC staff to request the export of browse metadata for one or several MISBR granules, with the MISBR granules specified on the command line or listed in an input file. [NOTE: This extends the corresponding manual export requirement for normal browse metadata to MISBR browse metadata.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01350	When DAAC staff causes the export of browse metadata for MISBR granules as part of a manual export operation, the BMGT shall also export only the public browse links associated with each exported MISBR granule in accordance with requirement (S-BGT-01310) in this ticket such that are consistent with current browse links in the public Data Pool. [NOTE: This requirement requests that the BMGT not dynamically determine and export the browse links for non-public MISR science granules.  This in turn ensures that any existing browse links which non-public MISR science granule may have in ECHO remain intact.]     	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01355	The BMGT shall permit DAAC staff to request the export of deletions of browse granules representing MISBR granules for one or several MISBR granules, with the granules specified on the command line or listed in an input file. [NOTE: This extends the corresponding manual export requirement for normal browse metadata to MISBR browse metadata.]	
BE_7B_02	Export of MISR Inventory Information to ECHO	no data				S-BGT-01360	The BMGT shall include browse metadata for MISBR granules among the bulk metadata ingested into ECS.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00010	The AIM CI shall provide an interface to access information that identifies when a new collection was inserted into the ECS inventory.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00015	The AIM CI shall provide an interface to access information that identifies when a collection was removed from the ECS inventory, including the short name and version id of that collection	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00020	The AIM CI shall provide an interface to access information that identifies when a collection was last updated.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00025	The AIM CI shall provide an interface to obtain the metadata of collections in the inventory in an XML format according to the subset of the BMGTCollectionMetadata.dtd that describes the collection information.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00030	The AIM CI shall provide an interface that allows the selection and identification of collections based upon the time interval during which a collection was inserted, last updated, or deleted. [NOTE: This supports S-BGT-00650.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00035	The AIM CI shall provide an interface to access information that identifies when valids information was last updated. [NOTE: This supports S-BGT-00675]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00040	The AIM CI shall provide an interface to obtain the valids information needed to populate the subset of the BMGTValidsMetadata.dtd that describes the valids information.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00045	The AIM CI shall provide an interface to obtain the metadata of science granules in the inventory in an XML format according to the subset of the BMGTGranuleMetadata.dtd that describes the granule information.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00050	The AIM CI shall provide an interface to access information that identifies when the core QA metadata information of a science granule was last updated and the nature of each such updates, i.e., parameter name, QA flag name, and QA flag value.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00055	The AIM CI shall provide an interface to access information that identifies when the browse links of a science granule were last updated.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00060	The AIM CI shall provide an interface to access information that identifies whether a science granule is currently visible or hidden.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00065	The AIM CI shall provide an interface to access information that identifies when the visibility of a science granule was last updated.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00070	The AIM CI shall provide an interface to access information that identifies when a science or browse granule was inserted into the inventory.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00075	The AIM CI shall provide an interface to access information that identifies when a science or browse granule was logically deleted from the inventory or deleted from the archive and make this information available for a configurable length of time after such events occurred even if the granule is physically deleted in the meantime.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00080	The AIM CI shall provide an interface to access information that identifies when a science or browse granule that had been logically deleted from the inventory was undeleted.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00085	The AIM CI shall provide an interface to access information that identifies when the metadata of a browse granule were last updated. [NOTE: This is cannot be integration tested since there is no ECS baseline capability to update the metadata of non-science granules.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00090	The AIM CI shall provide an interface to access information that identifies when a science granule was assigned to a different collection (i.e., its collection version ID was changed) and identifies the previous and new collection.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00095	The AIM CI shall provide an interface to access information that identifies when metadata for a science granule were last updated other than core QA metadata, browse links, granule visibility, or the collection to which the granule belongs.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00100	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the collection to which they belong. [NOTE: This supports manual export as per S-BGT-00970.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00105	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the collection to which they belong and the time interval during which their core QA metadata was updated the last time. [NOTE: This supports automatic export as per S-BGT-00685f and S-BGT-00695b.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00110	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the collection to which they belong and the time interval during which their browse links were updated the last time. [NOTE: This supports automatic export as per S-BGT-00685g, S-BGT-00695c, and S-BGT-00780c.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00115	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the collection to which they belong and the time interval during which a related browse granule was inserted into the inventory. [NOTE: This supports manual export as per S-BGT-00975.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00120	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the collection to which they belong and time interval during which their visibility was updated the last time. [NOTE: This supports automatic export as per S-BGT-00685c and S-BGT-00695a.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00125	The AIM CI shall provide an interface that allows the selection and identification of granules based upon the collection to which they belong and the time interval during which they were inserted into the inventory. [NOTE: This supports automatic export as per S-BGT-00685a and S-BGT-00690a and manual export as per S-BGT-00970.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00130	The AIM CI shall provide an interface that allows the selection and identification of granules based upon the collection to which they belong and the time interval during which they were logically deleted from the inventory or deleted from the archive, and make this possible for a configurable length of time after such events occurred even if the granule is physically deleted in the meantime. [[NOTE: This supports automatic export as per S-BGT-00685b, S-BGT-00685d and S-BGT-00725a, b. The need for retaining event information is mentioned for clarity and is covered by requirements S-AIM-00150 and S-AIM-00155, as well. ]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00135	The AIM CI shall provide an interface that allows the selection and identification of granules based upon the collection to which they belong and the time interval during which their logical deletion from the inventory was undone. [NOTE: This supports automatic export as per S-BGT-00685b and S-BGT-00690d.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00137	The AIM CI shall provide an interface that allows the selection and identification of browse granules based upon the time interval during which their metadata were last updated. [NOTE: This supports automatic export as per S-BGT-00685h and S-BGT-00690c for non-science granules.] [NOTE: This is cannot be integration tested since there is no ECS baseline capability to update the metadata of non-science granules.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00140	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the collection to which they belong and the time interval during which their metadata - other than core QA metadata, browse links, granule visibility, or the collection to which they belong - were last updated. [NOTE: This supports automatic export as per S-BGT-00685h and S-BGT-00690c for science granules.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00145	The AIM CI shall provide an interface that allows the selection and identification of science granules based upon the time interval during which they were last assigned to a different collection and the collection to which they currently belong, respectively the collection to which they did belong before the update. [NOTE: This supports automatic export as per S-BGT-00685e and S-BGT-00690b and S-BGT-00725c.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00150	The AIM CI shall allow DAAC staff to configure the length of time for which valids, collection and science and browse granule event information that the AIM CI maintains for access by the BGT CI shall be retained after the event occurred.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00155	The AIM CI shall retain valids, collection and science and browse granule event information accessed by the BGT CI for the length of time configured by DAAC staff and remove it thereafter where such information is kept in separate event tables. [NOTE: That is, event information is not subject to this cleanup requirement if it is an integral part of the inventory, such as the insertTime, lastUpdate, and deleteEffectiveDate in the various granule and collection inventory tables.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00160	The AIM CI shall provide an interface to obtain the browse metadata required for metadata export, i.e., that is referenced by the subset of the BMGTBrowseMetadata.dtd that describes the browse granule information.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00165	The AIM CI shall provide an interface to access the information that correlates a given science granule with its browse granules	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00170	The AIM CI shall provide an interface to access the information that correlates a given browse granule with its science granules	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00175	The AIM CI shall provide an interface that allows the selection of browse granules based on the collection to which the associated science granules belong. [NOTE: This supports manual export as per S-BGT-00975.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00180	The AIM CI shall provide an interface that allows the selection of browse granules based on the collection to which the associated science granules belong and the time period during which the browse granule was inserted. [NOTE: This supports automatic export as per S-BGT-00780a, S-BGT-00785, S-BGT-00800, and manual export as per S-BGT-00975.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00185	The AIM CI shall provide an interface that allows the selection of browse granules based on the collection to which the associated science granules belong and the time period during which the browse granule was deleted. [NOTE: This supports automatic export as per S-BGT-00780b, S-BGT-00790, and S-BGT-00800.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00190	The AIM CI shall provide an interface to access the location information that is needed to access the browse file(s) for a specific browse granule in the browse archive.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00195	The AIM CI shall provide an interface to access the file name information for browse files.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-AIM-00200	The AIM CI shall support the specification of time intervals for selection purposes that are closed at the beginning date/time and open at the ending date/time, i.e., include items for a time greater than or equal to (>=) the beginning date time and less than (<) the ending date/time.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01365	The BGT CI shall use the provided AIM interfaces to access the following event information maintained by the AIM CI: a.  when a new collection was inserted into the ECS inventory, b. when a collection was removed from the ECS inventory, including the short name and version id of that collection, c, when a collection was last updated, d. when valids information was last updated	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01370	The BGT CI shall use the provided AIM interfaces for the selection and identification of collections based upon the time interval during which a collection was inserted, last updated, or deleted	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01375	The BGT CI shall use the provided AIM interfaces to obtain the metadata of collections in the inventory in an XML format according to the subset of the BMGTCollectionMetadata.dtd that describes the collection information.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01400	The BGT CI shall use the provided AIM interfaces to obtain the valids information it requires for metadata export.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01405	The BGT CI shall use the interfaces provided by the AIM CI to obtain the following event information maintained by the AIM CI: a. when the core QA metadata information of a science granule was last updated and the nature of each such updates, i.e., parameter name, QA flag name, and QA flag value, b. when the browse links of a science granule were last updated, c. whether a science granule is currently visible or hidden, d. when the visibility of a science granule was last updated, e. when a science or browse granule was inserted into the inventory, f. when a science or browse granule was logically deleted from the inventory or deleted from the archive, g. when a science or browse granule that had been logically deleted from the inventory was undeleted, h. when the metadata of a browse granule were last updated, i. when metadata for a science granule were last updated other than core QA metadata, browse links, granule visibility, or the collection to which the granule belongs.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01410	The BGT CI shall use the interfaces provided by the AIM CI to obtain the metadata of science granules in the inventory in an XML format according to the subset of the BMGTGranuleMetadata.dtd that describes the granule information.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01415	The BGT CI shall use the interfaces provided by the AIM CI for the selection of science granules based upon: a. the collection to which they belong, b. the collection to which they belong and the time interval during which their core QA metadata was updated the last time, c. the collection to which they belong and the time interval during which their browse links were updated the last time, d. the collection to which they belong and the time interval during which a related browse granule was inserted into the inventory, e. the collection to which they belong and time interval during which their visibility was updated the last time, f. the collection to which they belong and the time interval during which they were inserted into the inventory, g. the collection to which they belong and the time interval during which they were logically deleted from the inventory or deleted from the archive, h. the collection to which they belong and the time interval during which their logical deletion from the inventory was undone, i. the collection to which they belong and the time interval during which their metadata - other than core QA metadata, browse links, granule visibility, or the collection to which they belong - were last updated, j. the time interval during which they were last assigned to a different collection and the collection to which they currently belong, respectively the collection to which they did belong before the update,	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01420	The BGT CI shall use the interfaces provided by the AIM CI for the selection of science granules based upon the time interval during which their metadata were last updated.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01425	The BGT CI shall use the interfaces provided by the DPL CI to obtain the following event information maintained by the DPL CI: a. when a science granule was inserted into the public Data Pool and information that allows the determination of its public Data Pool URL, b. when a science granule was removed from the public Data Pool unless this information is provided to the BGT in accordance with requirements S-DPL-00260 or S-DPL-00265, c. when a collection was moved or re-assigned in the Data Pool such that the public Data Pool URLs of its granules changed as a result,	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01430	The BGT CI shall use the interfaces provided by the DPL CI for the selection of science granules based upon: a. the collection to which they belong and the fact that they reside in the Data Pool, b. the time interval during which they were removed from the public Data Pool unless they were provided to the BGT in accordance with requirements S-DPL-00260 or S-DPL-00265, c. the time interval during which their public Data Pool URLs changed because their Data Pool collection was moved or re-assigned	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01435	The BGT CI shall provide an interface for use by the DPL CI to identify the science granules as per requirement S-DPL-00260.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01440	The BGT CI shall provide an interface for use by the DPL CI to identify the science granules as per requirement S-DPL-00265.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01445	The BGT CI shall use the provided AIM interfaces to access the following information maintained by the AIM CI: a. information that correlates a given science granule with its browse granules, b. information that correlates a given browse granule with its science granules, c. location information that is needed to access the browse file(s) for a specific browse granule in the browse archive, d. file name information for browse files	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01450	The BGT CI shall use the interfaces provided by the DPL CI for the selection of browse granules based upon: a. the collection to which the associated science granules belong and the time period during which the browse granule was inserted b. the collection to which the associated science granules belong and the time period during which the browse granule was deleted	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-BGT-01455	The BGT CI shall use the provided AIM interfaces to obtain the browse metadata it requires for export.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00235	The DPL CI shall provide an interface to access information that identifies when a science granule was inserted into the public Data Pool and allows the determination of its public Data Pool URL.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00240	The DPL CI shall provide an interface to access information that identifies when a science granule was removed from the public Data Pool.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00245	The DPL CI shall provide an interface to access information that identifies when a collection was moved or re-assigned in the Data Pool such that the public Data Pool URLs of its granules changed as a result.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00250	The DPL CI shall provide an interface that allows the selection and identification of science granules that are in the public Data Pool based upon the collection to which they belong and optionally the time interval during which they were published in the Data Pool. [NOTE: This supports automatic export as per S-BGT-00685i and S-BGT-00700a, and manual export as per S-BGT-00980.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00255	For all science granules removed from the public Data Pool whose removal from the public Data Pool is not identified as per requirements S-DPL-00260 and S-DPL-00265, the DPL CI shall provide an interface that allows their selection and identification based upon the time interval during which they were removed from the public Data Pool. [NOTE: This supports automatic export as per S-BGT-00685j, S-BGT-00700b, and S-BGT-00720.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00260	The DPL CI shall use the interface provided by BGT CI as per requirement S-BGT-01435 to identify to the BGT CI the science granules selected for removal from the public Data Pool during a pre-delete phase of a Data Pool cleanup run. [NOTE: This supports automatic export as per S-BGT-00685j, S-BGT-00700b, and S-BGT-00705.] 	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00265	The DPL CI shall use the interface provided by BGT CI as per requirement S-BGT-01440 to identify to the BGT CI the science granules that were removed from the public Data Pool during a Data Pool cleanup run, unless they had already been identified during the pre-delete phase. [NOTE: This supports automatic export as per S-BGT-00685j, S-BGT-00700b, and S-BGT-00705.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00270	The DPL CI shall provide an interface that allows the selection and identification of science granules based upon the time interval during which their public Data Pool URLs changed because their Data Pool collection was moved or re-assigned. [NOTE: This supports automatic export as per S-BGT-00685k and S-BGT-00700c.]	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00275	The DPL CI shall allow DAAC staff to configure the length of time for which event Data Pool information that the DPL CI maintains for access by the BGT CI shall be retained after the event occurred.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00280	The DPL CI shall retain event information accessed by the BGT CI until it is notified by the BGT CI that event information beyond a certain age is no longer needed and remove that event information upon such notification.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00281	The DPL CI shall provide an interface that can be used by the BGT CI to notify the DPL CI of event information it no longer needs, as per requirements S-DPL-00280.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00282	Upon cleaning up audit trail information as per S-BGT-01284, the BGT CI shall notify the DPL CI that it no longer needs the related event information, using the interface identified in S-DPL-00281.	
BE_7E_01	Use of AIM and DPL Interfaces for Export of ECS Inventory Information to ECHO	no data				S-DPL-00285	The DPL CI shall support the specification of time intervals for selection purposes that are closed at the beginning date/time and open at the ending date/time, i.e., include items for a time greater than or equal to (>=) the beginning date time and less than (<) the ending date/time.	
BE_7E_04	BMGT Updates from NCRs	no data				S-BGT-00641	The BMGT shall allow DAAC staff to enable a collection for export of URL metadata if the collection is enabled for export of collection metadata. [NOTE: While a collection is not enabled for export of URL metadata, metadata Data Pool inserts, deletions and URL changes for its granules will not be included in export operations.  DAAC staff must enable or disable a collection manually via direct interaction with the Data Pool database.  When the DAAC does so, DAAC staff is also responsible for exporting the addition respectively removal of any pre-existing URLs via manual BMGT export.]	
BE_7E_04	BMGT Updates from NCRs	no data				S-BGT-00642	The BMGT shall not include URL metadata in the export operations referenced in S-BGT-00710, S-BGT-00715, and S-BGT-00720 for collections not enabled for URL export.	
BE_7E_04	BMGT Updates from NCRs	no data				S-BGT-00996	The BMGT shall permit DAAC staff to request via a manual export operation the export of deletions of science granules from the ECS inventory for one or several collections, with the collections specified on the command line. [NOTE: This will produce one or several ECSMETG files indicating the deletion from the ECS inventory for the granules in the specified, except for granules that are still in the inventory and not deleted from archive nor logically deleted.]	
BE_7E_04	BMGT Updates from NCRs	no data				S-BGT-01001	The BMGT shall permit DAAC staff to request via a manual export operation the export of the removal of the public Data Pool URLs for one or several collections, with the collections specified on the command line or listed in an input file. [NOTE: This will produce a BulkURL file exporting the deletion of the specified granules in the specified collections from the Data Pool. The deletion will not be exported if the granule is in the public Data Pool.]	
BE_7E_04	BMGT Updates from NCRs	no data				S-BGT-01011	The BMGT shall permit DAAC staff to request via a manual export operation the export of deletions of browse granules from the ECS inventory related to the science granules in one or several collections, with the collections specified on the command line. [NOTE: Browse granules will not be exported as deleted unless the browse granules are not in the ECS inventory or flagged as deleted.]	
BE_7E_04	BMGT Updates from NCRs	no data				S-DPL-18105	The Data Pool Maintenance GUI shall allow DAAC staff to display whether a collection is enabled for URL export or not, but DAAC staff shall not be able to modify that setting via the GUI.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31000	The BMGT shall support the following responses to ECHO error codes returned in the Ingest Summary Report for an automatic export operation:  Responses to Package Errors:   Retry Package Regenerate Package Duplicate Package   Responses to Item Errors:    Ignore Error Re-export Object Re-export Associated Object Re-export Object and Associated Object No Object Re-export 	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31010	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31020	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31030	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31040	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31050	The BMGT shall analyze the ECHO Ingest Summary Report for automatic export packages and assign the BMGT error response specified in Table 6-1 to each ECHO error code.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31060	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31080	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31090	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31100	When analyzing Ingest Summary Reports for manual exports (including manual corrective exports), the BMGT shall ignore ECHO error codes classified as Ignore Error in Table 6-1, and not consider such errors when determining the final outcome of the export as per S-BGT-01250 and S-BGT-01259, for purposes of error statistics as per S-BGT-01245.     [NOTE: In terms of handling ECHO error responses, manual corrective exports will be handled like other manual exports.   For example, manual corrective exports will not be retried in the case of package level errors; and to avoid re-export loops, item errors will never lead to a re-export.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31110	The BMGT shall flag an export as COMPLETE if there were no errors or only errors classified as Ignore Error (see requirement S-BGT-31000d). [NOTE: This requirement modifies the corresponding portion of requirement S-BGT-01250.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31120	The BMGT shall flag an export as COMPLETE_WITH_WARNINGS if there were errors classified as Re-export Object and/or Re-export Associated Object, but no package errors (see requirement S-BGT-31000 for a list of package errors)  and no errors classified as No Object Re-export.  [NOTE: This requirement modifies requirement S-BGT-01250 to add this as a new state.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31130	The BMGT shall flag an export as COMPLETE_WITH_ERRORS if there were errors classified as No Object Re-export and no Package Errors (see requirement S-BGT-31000 for a list of package errors). [NOTE: This requirement modifies the corresponding portion of requirement S-BGT-01250.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31140	The BMGT shall provide as part of the ECHO error statistics available for viewing as part of the audit trail information, the number of ECHO error responses for each type of Item Error classification (i.e.,. Ignore Error, Re-export, No Object Re-export) [NOTE: It is not necessary to distinguish between the several different types of  Re-exports, i.e., S-BGT-31000b,c, and d. This requirement extends requirement S-BGT-01259.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31150	The BMGT shall not send an e-mail notification regarding metadata export errors for errors classified according to S-BGT-31000a (i.e., Ignore Error).  [NOTE: This modifies requirements S-BGT-01225 as follows: When the BMGT only discovers error responses that can be ignored, the BMGT will not notify DAAC staff regarding these errors.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31160	When sending e-mail notifications regarding metadata export errors classified as package errors (see S-BGT-31000), the BMGT shall include the ECHO error code in the e-mail subject.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31170	When sending e-mail notifications regarding metadata export errors, the BMGT shall include a recommendation to contact ECHO staff in the following error situations:  package error PACKAGE_TOO_LARGE general item error SCHEMA_VALIDATION_ERROR collection error OUT_OF_DATE granule error PARTIAL_DELETE_FIELD_INVALID granule error PARTIAL_ADD_UPDATE_TARGET_FIELD_INVALID 	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31180	When sending an e-mail notification regarding metadata export errors, the BMGT shall include in the e-mail body a list of the errors that caused the notification to be sent, including the classification and the number of occurrences for each. [NOTE: This extends requirements S-BGT-01225.  DAAC staff should refer to the Ingest Summary Report referenced in the e-mail to locate these errors, identify the affected objects, and determine the appropriate measures, if any.  The BMGT need not include in this list any errors that were ignored. Note that DAAC staff does not have to respond to errors that caused re-export.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31190	When encountering an error situation classified as Re-export Object or Re-export Object and Associated Object, the BMGT shall queue a re-export action for the object [NOTE: The re-export will either export the complete current metadata for that object or the deletion of the object, depending on the state of the object at the time of re-export  see also S-BGT-31480]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31200	When encountering an error situation classified as Re-export Associated Object or Re-export t and Associated Object, the BMGT shall identify the object whose reference caused the error (i.e., the referenced or browse granule) and queue a re-export action for that object	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31210	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31220	The BMGT shall permit DAAC staff to request the start of a corrective metadata export operation.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31230	The BMGT shall permit DAAC staff to indicate whether the outputs of the corrective export that are eligible for archiving in ECS shall be ingested into the ECS archive, with the default being to do so. 	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31240	The BMGT shall assign an export sequence number to a corrective metadata export operation and shall export the resulting package to ECHO and archive it in ECS if the DAAC staff so indicated as per S-BGT-31230.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31245	The BMGT shall identify corrective exports as such in the audit trail.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31250	The BMGT shall use the file naming conventions for manual export packages also for corrective export packages, but substitute the string CorrectiveExport for the string ManualExport. [NOTE: as per the naming requirements for manual exports, the BMGT will also use all zeroes for the start and end times covered by the export.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31260	The BMGT shall process the re-export queue during manual corrective exports and no other types of  export operations.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31270	When a corrective export is requested, the BMGT shall not accept manual export specifications that request the manual export of any other types of metadata. [NOTE: Corrective exports are limited to processing re-export actions only.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31280	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31290	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31300	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31310	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31320	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31330	The BMGT shall remove all re-export action from the re-export queue after they were processed successfully by a manual corrective export.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31340	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31350	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31360	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31370	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31380	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31390	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31400	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31410	The BMGT shall provide a command line utility that permits DAAC staff to remove queued re-export actions by explicitly identifying these actions either on the command line or in an input file. [NOTE: The utility provides DAAC staff with the ability to clean up queued re-export actions before running a manual corrective export.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31420	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31430	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31440	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31450	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31460	The BMGT shall include that the requested metadata information for all queued re-export actions in the export package generated by the current manual corrective export operation except as specified in S-BGT-31470 and S-BGT-31480. [NOTE: The BMGT will place the requested metadata into the appropriate export files (e.g., ECSMETG, ECSMETU, ECSBBR, BulkURL, Visibility) for the appropriate collection group, but only if that is still consistent with the state of the object in the ECS inventory.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31470	The BMGT shall include granule URL information in re-exports only if the corresponding collection is enabled for granule URL export.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31480	If a re-export action requests the export of inventory metadata for an object that is no longer in the ECS inventory, the BMGT shall not process the re-export action and shall remove it from the queue. [NOTE: It is possible that the export of the removal of an object by the corrective export is redundant.  This will cause ECHO to report an error because it cannot find the object to be deleted.  This error is classified to be ignored and will not cause a re-export loop.]	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31490	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31500	The BMGT shall allow DAAC staff to obtain a re-export queue report listing the currently queued re-export actions, and including for each  the referenced object and its type (collection, science granule, or browse granule), a well as the collection and collection group to which it belongs  the initial export attempt (e.g., time or export cycle), the ECHO error response that caused the action to be placed on the re-export queue 	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31510	The BMGT shall sort the re-export queue report by initial export attempt (most recent first), collection, and type of object.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31520	The BMGT shall allow DAAC staff to filter the re-export queue report (see requirement S-BGT-31500) based on collection and collection group. 	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31525	The BMGT shall allow DAAC staff to specify on the command line the location where to save the re-export queue report, and shall generate a file name for the re-export queue report automatically that identifies it as a re-export queue report and includes the start time of the report.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31530	The BMGT shall allow DAAC staff to obtain a statistical report of the queued re-export actions, listing each collection for which re-export actions are queued together with its collection group, and listing for each the number of re-export actions together with the ECHO error response, with the report sorted according to collection and type of object. In this context, Browse shall be reported as part of the BROWSE collection, but the report shall also contain information associating the Browse with its parent collection.  	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31535	The BMGT shall provide a run-time option to generate a re-export queue report as specified in S-BGT-31500, S-BGT-31510 and S-BGT-tmp10 when performing a manual corrective export.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31540	The BMGT shall allow DAAC staff to obtain the reports specified in S-BGT-31500 and S-BGT-31530 on a regular basis (e.g., via cron entry), as well as on demand (e.g., via command line).	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31545	The BMGT shall allow DAAC staff to specify on the command line the location where to save the re-export queue statistics, and shall generate a file name for the re-export queue statistics automatically that identifies it as containing re-export queue statistics and including the start time of the report.	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31550	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31560	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31570	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31580	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31590	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31600	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31610	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31620	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31630	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31640	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31650	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31660	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31670	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31680	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31690	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31700	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31710	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31720	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31730	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31740	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31750	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31760	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31770	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31780	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31790	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31800	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31810	DELETED	
BE_7F_01	Improved BMGT Handling of Error Responses	no data				S-BGT-31820	DELETED	
BE_S3_01	ASTER On-Demand Via EDG	no data				C-CSS-30770	The Registry Service shall be capable of storing multiple ASTER On-Demand processing options for each of multiple versions of the ASTER L1A or L1B collections.	
BE_S3_01	ASTER On-Demand Via EDG	no data				C-CSS-30780	The Registry Service shall provide capabilities to retrieve ASTER On-Demand processing options information for ASTER L1A or ASTER L1B by ESDT shortname/version.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33510	The GTWAY CI shall retrieve ASTER On-Demand processing option information, from the Registry by ASTER L1A or L1B shortname and version.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33520	The GTWAY CI shall provide inventory search results messages to the V0 Client for ASTER L1A products that contain processing option information for the ASTER products that may be derived from the ASTER L1A products, in accordance with the ECS-V0 ICD.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33530	The GTWAY CI shall provide inventory search results messages to the V0 Client for ASTER L1B products that contain processing option information for the ASTER products that may be derived from the ASTER L1B products, in accordance with the ECS-V0 ICD.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33540	The GTWAY CI shall be able to determine from the metadata associated with a granule and the on-demand processing PSA filter rules, limited to those rules contained in this ticket, which higher level products may be produced for the particular granule.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33550	The GTWAY CI shall provide in the inventory search results message only that processing option information for ASTER products that may be derived from a granule, as determined by the granule PSAs and PSA filter rules for producing derived products.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33560	The GTWAY CI shall provide the capability to receive product request messages from the V0 Client containing ASTER on-demand processing request information.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33570	The GTWAY CI shall provide the capability to process product request messages containing ASTER on-demand processing request information to produce on-demand processing request messages formatted for use by the PLANG CI	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33580	The GTWAY CI shall submit on-demand processing request messages to the PLANG CI	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33590	The GTWAY CI shall break up product requests on a per-granule basis.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33610	The GTWAY CI shall flag the Order Tracking requests for on-demand product orders to indicate that they are on-demand request type.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33620	The GTWAY CI shall, if all requests within an order are on-demand, flag the Order Tracking order to indicate that the order is an on-demand order type.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-DMS-33630	The implementation of the GTWAY CI capabilities for the ASTER On-Demand support via the EDG shall not degrade existing results set processing performance by more than 10 percent.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05230	The PLANG CI shall submit all on-demand DEM product orders to an ECS operator via an email message sent to a configured email address. 	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05240	The PLANG CI shall retrieve from configuration data the email address to which all on-demand DEM product orders are sent for operator action.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05250	The PLANG CI shall determine which profile to run based on the ESDT version of each L1A input granule.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05260	The PLANG CI shall accept an on-demand processing order messages for a higher level ASTER product, from the GTWAY CI.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05270	The PLANG CI shall accept a DEM order request, from the GTWAY CI.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05280	The PLANG CI shall accept an on-demand processing request for an ASTER standard or non-standard L1B product, from the GTWAY CI.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05290	The PLANG CI shall notify the operator in the event that it is not able to properly create a DPR	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05300	The PLANG CI shall accept an on-demand processing order message for multiple higher level ASTER product, from the GTWAY CI.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05310	The PLANG CI shall notify the requester via email when an On-Demand ASTER L1B Product is available only if the order did not originate from the GTWAY CI system.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05320	The PLANG CI shall be able to generate the appropriate data processing requests that are needed to fulfill an order, based on the user supplied input forwarded by the GTWAY CI.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05330	The PLANG CI shall respond to the GTWAY CI for On-Demand Requests within 3 seconds per granule ordered.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05340	The PLANG CI shall not fail requests for which the DPR cannot be correctly created but retain the request for possible operator attention.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05350	The PLANG CI shall, for orders received from the GTWAY CI, accept an order that includes an MSS OrderID and RequestID.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05360	The PLANG CI shall produce on-demand DEM product orders to be sent to an ECS operator which include the details of the order as well as order ID and contact information.	
BE_S3_01	ASTER On-Demand Via EDG	no data				S-PLS-05370	The PLANG CI shall assign configurable distribution priorities to all on-demand product orders.	
BE_S3_02	Export AIRS Browse to ECHO	no data				S-BGT-10300	The BMGT shall include an association between each AIRS granule and its ASBP during the generation of the ECSBBR browse XML file.	
BE_S3_02	Export AIRS Browse to ECHO	no data				S-BGT-10310	The BMGT shall only include AIRS summary browse if the corresponding AIRS ESDTs are included in the list of ESDTs designated for metadata generation.	
BE_S3_02	Export AIRS Browse to ECHO	no data				S-BGT-10320	The BMGT shall convert extracted browse cross-reference information to XML format at a rate of at least 25,000 granules per hour.	
BE_S3_02	Export AIRS Browse to ECHO	no data				S-DSS-90350	The SDSRV shall include AIRS Summary Browse Products in the distribution upon acquire of the ECSBBR granules if AIRS Summary Browse Products are referenced in the ECSBBR granule.     NOTE:  At this time it is anticipated that no changes will need to be made to the SDSRV ECSBBR DLL to accommodate this capability.  The requirement is included however to insure AIRS Summary Browse products get distributed successfully.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20010	The EcOsBulkURL utility shall accept a mandatory input parameter determining if the utility is to run in the 'Insert' mode or the 'Delete' mode.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20020	The EcOsBulkURL utility shall access a list of ESDT shortnames and versions, representing those data collections for which information has been exported to ECHO from ECS by BMGT.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20030	The BMGT shall produce a list of the data collections (ESDT shortnames and versions) that is a subset of the data collections contained in the data pool, for which the BMGT has exported metadata to ECHO.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20040	The EcOsBulkURL utility shall, when running in insert mode, generate an XML representation of the ftp URL information for granule files, metadata and browse files inserted in the Data Pool database, during the   and   used as parameters to run the utility, that had been previously exported to ECHO.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20050	The EcOsBulkURL utility shall use a naming convention for its generated files that includes   a) DAAC id  b) Indication of whether it is an update on inserts or deletes in the Data         Pool  c) Time stamp	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20060	The EcOsBulkURL utility shall, when running in delete mode, extract and export an XML representation of the list of granuleIDs for those granule that have been removed from the Data Pool that had been previously exported to ECHO.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20070	The EcOsBulkURL utility shall place URL insert and deletion file in an area accessible to ECHO via ftp pull	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20080	The EcOsBulkURL utility shall be able to detect and export URL location for DPL holdings that were populated from ECS Archive.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20090	The EcOsBulkURL utility shall start up with a check for EcDlCleanupDataPool created files, which contain delete updates that were not successfully processed previously, and shall produce the delete XML file as a result.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20100	The EcOsBulkURL utility shall log an error if during the generation of the  URL Insert file it is unable to obtain the URL location from the Data Pool database for   a) metadata file.  b) Science granule file(s) (if available)  c) Browse image(s) (if available)	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20110	Each URL Insert and Delete file XML format file shall conform to a Granule-Level Metadata DTD file specified in the document 170-WP-023-005 (Appendix A).	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20120	[DESIRABLE] The EcOsBulkURL utility shall provide an option that produces the XML file for all applicable URLs from the Data Pool, to enable the initial exporting of pre-existing Data Pool URLs.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20130	The EcOsBulkURL utility shall be able to be run in multiple modes concurrently.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20140	The EcOsBulkURL utility shall be able to process granule insert information and add all associated entries to the XML insert file at the rate of 25,000 granules per hour independently of the execution of the BMGT utility or of the Data Pool insert utility.	
BE_S3_04	ECHO Access to Data Pool	no data				S-BGT-20160	The EcOsBulkURL utility shall be able to process granule deletion information and add all associated entries to the XML delete file at the rate of 25,000 granules per hour independently of the execution of the Data Pool Cleanup Utility.	
BE_S3_04	ECHO Access to Data Pool	no data				S-DPL-13600	The Data Pool Cleanup Utility shall invoke the EcOsBulkURL as part of its normal operation, with the -delete parameter.	
BE_S3_04	ECHO Access to Data Pool	no data				S-DPL-13610	The Data Pool Cleanup Utility shall dump all necessary information on deletes into a flat file, path and filename of /usr/ecs/ /CUSTOM/data/DPL/bulkURLDel, if the EcOsBulkURL utility returns a failed status	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50010	The GTWAY CI Inventory Search Result shall include an optional group containing the URL location for science granules residing in the Data Pool.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50020	The GTWAY CI shall have the ability to provide the URL location of metadata files associated with any granules in an inventory search result that reside in the Data Pool.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50025	The GTWAY CI shall have the ability to provide all necessary URL location information to handle multifile granules seamlessly.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50030	The GTWAY CI shall have the ability to provide the URL location of any existing browse images that reside in the Data Pool that are associated with granules in an inventory search result.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50040	The GTWAY CI Inventory Search Result optional group shall contain the expiration date of the science granules located in a Data Pool.     Note: In this context, the expiration date refers as to the time at which the granule (and its associated files) should be removed from the Data Pool.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50050	The GTWAY CI Inventory Search Result optional group shall not include Data Pool granule URL locations for products whose expiration date is in the past.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50070	The GTWAY CI shall not fail or halt the inventory search  result if unable to obtain the URL location for either  a) Science granule file(s)  b) metadata file  c) browse image (if available)    or the expiration time for a particular granule in the inventory search. 	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50080	The GTWAY CI shall log an error if an incomplete set of results is returned from DPL.A complete set of result consists of    a)  metadata file (one)  b)  Zero or more science granule data files  c)  Zero or more browse images  d)  One expiration date 	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50090	The GTWAY CI shall not degrade its performance in Inventory Search Result generation by more than 10%.	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50100	The GTWAY CI shall be able to turn on and off inventory searches into the data pool database.    Note: This is to prevent unnecessary performance degradation in DAACs that do not have a data pool. 	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50110	The GTWAY CI shall format the expiration date for a data pool URL in universal time code (UTC). 	
BE_S3_05	EDG Access to Data Pools	no data				S-DMS-50120	The GTWAY CI shall indicate when the Data Pool Inventory is offline in its inventory result to the EDG. 	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20300	The BMGT shall support collection level configuration information for W*S enabled collections.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20305	The BMGT shall export to ECHO, the WCS URL for each WCS enabled collection using configurable information.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20307	The OWS Binding Utility shall export to ECHO, the WCS URL for granules in the Data Pool which are WCS ready using the ECHO Partial Record Update API.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20310	The BMGT shall export to ECHO, the WMS URL for each WMS enabled collection using configurable information.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20315	The OWS Binding Utility shall export to ECHO, the WMS URL for granules in the Data Pool that are WMS ready, using the ECHO Partial Record Update API.  	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20320	The OWS Binding Utility shall record the successful export of a granules WMS PSA to ECHO, so that the OBU does not export it redundantly.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20325	The OWS Binding Utility shall record successful export of a granules WCS PSA to ECHO, so that the OBU does not export it redundantly.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20330	The OWS Binding Utility shall be capable of exporting to ECHO, the WCS and WMS URLs that failed to export in the event the utility terminated abnormally.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20340	The OWS Binding Utility shall log the following events:   Execution start date and time  Detection of a granule which is ready for export and for which service  Completion status of the granule to be exported  Execution completion date and time  Total number of granules exported for each service  	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20350	The Bulk URL Utility shall export to ECHO, the deletion of the WCS Coverage URL for a WCS ready granule that have been deleted from the Data Pool.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20360	The Bulk URL Utility shall export to ECHO, the deletion of the WMS Coverage URL for a WMS ready granule that has been deleted from the Data Pool.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20370	The Bulk URL Utility shall log the following events during the export of granule deletion events to ECHO:   Detection of a W*S enabled granule which is to be deleted and for which service  Completion status of the granule deletion event to be exported  Total number of W*S enabled granule deletion events exported for each service  	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20380	The BMGT shall export to ECHO, the deletion of the WCS Coverage URL for a collection that has been disabled for that service.	
BE_S5_01	Export Data Pool OGC Content to ECHO	no data				S-BGT-20390	The BMGT shall export to ECHO, the deletion of the WMS Coverage URL for a collection that has been disabled for that service.	
CK_70_01	End-To-End Checksum Capability	no data				C-CSS-80010	A standalone checksum utility shall be provided to compute an ECS checksum	
CK_70_01	End-To-End Checksum Capability	no data				C-CSS-80020	The standalone checksum utility shall be provided for the following operating systems: a. Solaris b. Irix c. Windows 2000/XP d. Linux.	
CK_70_01	End-To-End Checksum Capability	no data				C-MSS-95010	The MSS CI shall maintain a DAAC-configurable list of ECS UserIDs (checksum distribution list) for which checksum type and checksum value parameters should be included in Distribution Notice. [Note: MSS servers should not require a restart in order to recognize changes to this list]	
CK_70_01	End-To-End Checksum Capability	no data				C-MSS-95020	The MSS CI shall provide an interface that can be used by other CI to determine whether checksum type and checksum value should be included in the DN for a given UserID.	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46010	The DPL CI shall provide the capability to compute science file checksums on ECS granules during data pool insert, using any algorithm in the checksum type list.	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46020	The DPL CI shall maintain a DAAC-configurable parameter indicating the percentage of ECS science files with a checksum type and checksum value whose checksums should be verified during data pool insert. [NOTE:  It is acceptable for a server restart to be required in order to recognize parameter changes.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46025	The DPL CI shall maintain a DAAC-configurable parameter indicating the percentage of ECS science files without a checksum type and checksum value for which an ECS checksum should be calculated and stored during data pool insert. [NOTE:  It is acceptable for a server restart to be required in order to recognize parameter changes.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46030	The DPL CI shall verify science file checksums on ECS granules before data pool file insertion for the configured percentage of science files that have an ECS checksum value. [NOTE: For performance reasons, other types of checksums will not be verified during transfer but only after insert.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46031	The DPL CI shall calculate an ECS checksum during data pool file insertion for the configured percentage of science files of ECS granules that have no checksum type and checksum value.	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46032	The DPL CI shall verify science file checksums on ECS granules after data pool file insertion for files with an ECS checksum for which the checksum had been verified or calculated before insertion (i.e., as per S-DPL-46030 and S-DPL-46031), and for the configured percentage of science files that have checksum values of types other than ECS.	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46040	The DPL CI shall generate a retryable failure when a checksum mismatch occurs.	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46042	The DPL CI shall generate an error and fail the Data Pool insert if the checksum type associated with a file is not among the checksum types supported by the DPL CI. [NOTE: Since the validity of the checksum type is verified during ingest, this error condition needs to be tested during unit testing.  It is not testable during integration testing.	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46050	Whenever a checksum is available for a file, be it in the SDSRV inventory or as calculated during Data Pool insert, the DPL CI shall include checksum type and checksum value in the Data Pool inventory. [NOTE: This enables DAACs to verify the checksum of files in the data pool occasionally via utilities.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DPL-46060	The DPL CI shall include checksum type, checksum origin, and checksum value in the .xml files.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45008	The SDSRV CI shall receive an optional indication of whether supplied checksums need to be verified from the INS CI on science granule inserts.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45009	The SDSRV CI shall send the optional indication that it received from the INS CI as to whether supplied checksums need to be verified to the STMGT CI when submitting a file insert request.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45010	The SDSRV CI shall receive and persistently store optional checksum type and checksum value parameters from the INS CI on science granule inserts.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45011	The SDSRV CI shall provide an indication to the STMGT CI when submitting a file insert request for a file without a checksum as to whether the file is eligible for checksumming or not, based on whether the file is a science file or not.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45012	The SDSRV CI shall send optional checksum type and checksum value parameters to the STMGT CI during file insert.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45013	The SDSRV CI shall accept and persistently store optional checksum type and checksum value parameters received from the STMGT CI during a file insert.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45014	When saving a checksum type and value, the SDSRV CI shall set the checksum origin to 'DataProvider' if the checksum value was received from INS, and to 'STMGT' if the checksum value was received from STMGT.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45015	The SDSRV CI shall pass checksum value and checksum type for each file it requests from STMGT to the STMGT CI.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45016	The SDSRV CI shall allow DAAC operations to configure the valid checksum types.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45017	The SDSRV CI shall return an error when the provided checksum type is not valid. [NOTE: Since the validity of the checksum type is verified during ingest, this error condition needs to be tested during unit testing.  It is not testable during integration testing.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45018	The SDSRV CI shall pass checksum value and checksum type for each file it submits for distribution to DDIST to the DDIST CI.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45019	The SDSRV CI shall provide an interface to its database via which other CI can retrieve the checksum type and value for a file.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45020	The SDSRV CI shall include checksum type, checksum origin, and checksum value parameters in the .met file. Effectivity: E3	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45022	The SDSRV CI shall transition the existing checksums while the system continues to operate normally.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45023	The SDSRV CI shall fail a subsetting request if it receives a checksum verification error for one of its files from the STMGT CI.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45027	The STMGT CI shall accept an optional indication for the need of checksum verification on file insert requests.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45028	The STMGT CI shall accept an optional checksum type and checksum value parameter on file insert requests, as well as an indication whether a given file that has no checksum is eligible for checksum calculation (i.e., is a science file).	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45029	The STMGT CI shall return an error if the checksum type parameter indicates the need for a checksum calculation that it does not support. [NOTE: Since the validity of the checksum type is verified during ingest, this error condition needs to be tested during unit testing.  It is not testable during integration testing.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45030	The STMGT CI shall provide the capability to compute an ECS internal checksum value and set the checksum type accordingly during science file insertion.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45031	The STMGT CI shall verify the checksum of a file if so requested by the file insert parameters during science file insertion by re-reading the file from the archive cache.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45032	The STMGT CI shall return a checksum verification in response to a science file insert request if the file fails the requested checksum verification.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45033	The STMGT CI shall impose a DAAC configurable limit on the maximum number of concurrent checksumming operations that a given STMGT server performs.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45034	The STMGT CI shall move a file to a DAAC configurable holding directory if its checksum verification fails, appending a unique qualifier if this is necessary to prevent overwriting a file that already exists in that directory.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45040	The STMGT CI shall provide the capability to compute file checksums, during retrieval, using any valid checksum algorithm (i.e., CKSUM and ECS).	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45050	The STMGT CI shall maintain for each archive a DAAC-configurable parameter indicating the percentage of science files without a checksum type and checksum value for which a checksum should be computed during file insert. [Note:  It is acceptable for a server restart to be required in order to recognize parameter changes.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45060	The STMGT CI shall compute and send to the SDSRV CI an ECS internal checksum for the configured percentage of files without a checksum type and checksum value which the SDSRV indicated as being eligible for checksum calculation (i.e., which are science files).	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45070	The STMGT CI shall maintain for each archive a DAAC-configurable parameter indicating the percentage of science files with a checksum type and checksum value whose checksums should be verified on retrieval. [Note:  It is acceptable for a server restart to be required in order to recognize parameter changes.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45080	The STMGT CI shall verify checksums during retrieval for the configured percentage of science files that have a checksum type and checksum value.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45090	The STMGT CI shall return a retryable error when a checksum verification fails.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45105	The DDIST CI shall interface with MSS to determine whether the DN for a given UserID needs to include the checksum type and checksum value.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45110	The DDIST CI shall include checksum type and checksum value parameters in the Distribution Notice for each file where those parameters exist and where the ECS UserId is a member of the checksum distribution list. [NOTE: This means that where a  checksum type and value for a file do not exist, DDIST shall omit this information from the DN.]	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45115	The DDIST CI shall pass checksum value and checksum type for each file it requests from STMGT to the STMGT CI.	
CK_70_01	End-To-End Checksum Capability	no data				S-DSS-45116	The DDIST CI shall suspend a request if STMGT indicates a checksum validation error for one of its files, and provide an appropriate indication of the nature of the error to the operator on the DDIST GUI.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40010	The INS CI shall accept optional parameters in the PDR FILE_SPEC that specify a checksum type and checksum value associated with a science file. [Note:  Checksums are only supported for science files (e.g., FILE_TYPE = SCIENCE, HDF, or HDF-EOS).  They are not supported for metadata, browse, QA, or PH files.  See also S-INS-40060]	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40020	DAAC operations shall be able to configure the list of valid checksum types that are accepted by the INS CI. [Note:  It is acceptable for a server restart to be required in order to recognize changes to the list.]	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40022	DAAC operations shall be able to make the presence of checksum type and checksum value in a PDR mandatory for selected data providers.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40024	The INS CI shall reject a granule and return a long PDRD error disposition if the checksum type and checksum value parameters are not present for each science file in a PDR from a provider for which the presence of these parameters has been made mandatory.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40030	The INS CI shall reject a granule and return a long PDRD error disposition if the checksum type is not on a list of ECS supported checksum algorithms.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40040	The INS CI shall reject a granule and return a long PDRD error disposition if the checksum type parameter is present and the checksum value parameter is not.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40050	The INS CI shall reject a granule and return a long PDRD error disposition if the checksum value parameter is present and the checksum type parameter is not.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40055	The INS CI shall reject a granule and return a long PDRD error disposition if the checksum value parameter is present and syntactically incorrect.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40060	The INS CI shall ignore checksum type and checksum value parameters for all types of files other than science files.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40070	The INS CI shall send optional checksum type and checksum value parameters to the SDSRV CI during granule insert.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40075	If checksum type and value parameters are present, the INS CI shall use a checksum verification percentage that can be configured by the DAAC by provider to determine whether the checksum should be verified and indicate the need for verification in the checksum parameters  sent to the SDSRV.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40076	The INS CI shall accept indication of a checksum verification error from the SDSRV in response to a granule insert request.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40077	The INS CI shall retry the granule ingest operation a DAAC-configurable number of times in the event that the SDSRV indicates a checksum verification error.	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40080	The INS CI shall accept the optional checksum type and value associated with a science file contained in the Data Notification email message for a cross-DAAC ingest request. [Note: The EcInEmailGWServer will parse the checksum type and value from the DN.  It is assumed that DAAC operations will configure the ECS userID that is used by these orders to receive a checksum in its DN, as specified in S-DSS -45100, S-DSS -45110]	
CK_70_01	End-To-End Checksum Capability	no data				S-INS-40090	The INS CI shall construct a PDR FILE_SPEC using the optional checksum type and checksum value in the Data Notification email message for a cross-DAAC ingest request. [Note: The EcInEmailGWServer constructs the PDR from the DN.  Also note that in this case the checksum will be in the PDR as well as in the .met file of the granule.]	
CK_70_01	End-To-End Checksum Capability	no data				S-OMS-08012	The OMS CI shall interface with MSS to determine whether the DN for a given UserID needs to include the checksum type and checksum value. 	
CK_70_01	End-To-End Checksum Capability	no data				S-OMS-08020	The OMS CI shall include checksum type and checksum value parameters in the Distribution Notice for each file where those parameters exist and where the ECS UserId is a member of the checksum distribution list.	
CK_70_01	End-To-End Checksum Capability	no data				S-PDS-10010	The PDS CI shall interface with MSS to determine whether the DN for a given UserID needs to include the checksum type and checksum value.	
CK_70_01	End-To-End Checksum Capability	no data				S-PDS-10020	The PDS CI shall include checksum type and checksum value parameters in the Distribution Notice for each file where those parameters exist and where the ECS UserID is a member of the checksum distribution list.	
CK_70_01	End-To-End Checksum Capability	no data				S-PDS-10030	The PDS CI shall interface with the SDSRV CI to obtain checksum type and checksum value for each granule file when there is a need to include checksum type and value in the Distribution Notice.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01010	The Data Pool FTP service shall provide the capability to verify science file checksums during data pool download using the checksum algorithms supported by the Release 7.0 ETE Checksum capability.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01020	The Data Pool FTP service shall maintain a DAAC-configurable parameter indicating the percentage of science files for which a checksum will be verified during data pool download, against the checksum computed during Data Pool insert, if available.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01030	The Data Pool FTP service shall provide the capability to configure separately for each instance of the FTP daemon, the DAAC configurable parameter indicating the percentage of science files to verify during download. 	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01040	The Data Pool FTP service shall verify the checksum for science files downloaded via ftp, based on the DAAC-configurable parameter described in S-DPL-01020.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01045	The Data Pool FTP service shall verify the checksum for science files downloaded via ftp which were compressed at insert time, based on the DAAC-configurable parameter described in S-DPL-01020.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01050	The Data Pool FTP service shall write an error message to the FTP daemon log when checksum verification fails during Data Pool download.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01060	The Data Pool FTP service shall write a message to the FTP daemon log when checksum verification succeeds during Data Pool download, indicating the successful verification. 	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01070	The Data Pool FTP service shall return a fatal error code back to the user when checksum verification fails during Data Pool download.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01080	In the event that there was no checksum computed during Data Pool insert for a science file that has been selected for checksum verification during Data Pool download, the Data Pool FTP service shall distribute the science file without computing a checksum.	
CK_70_02	Checksum Verification on Data Pool Download	no data				S-DPL-01090	In the event that there was no checksum computed during Data Pool insert for a science file which has been selected for checksum verification during Data Pool download, the Data Pool FTP service shall generate a log entry indicating the science file was distributed without verifying its checksum.	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DPL-41500	The DPL CI shall provide the capability to compute science file checksums on ECS granules during Data Pool insert, using any of the following checksum algorithms: a.  Unix CKSUM b.  ECS Checksum c.  MD5 Checksum (based on RFC 1321) [Note: MD5 checksum is the new capability being added by this ticket.]	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DPL-41505	The DPL CI shall accept and store the MD5 checksum value in the form of a 32-character lowercase hexadecimal string.	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DPL-41510	The Data Pool FTP service shall provide the capability to verify science file checksums during Data Pool download using any of the following checksum algorithms: a.  Unix CKSUM b.  ECS Checksum c.  MD5 Checksum (based on RFC 1321) [Note: MD5 checksum is the new capability being added by this ticket.]	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DSS-01215	The DDIST CI shall accept and represent the MD5 checksum value in the form of a 32-character lowercase hexadecimal string.	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DSS-07200	The STMGT CI shall provide the capability to compute checksum for an ECS science granule file using any of the following checksum algorithms: a.  Unix CKSUM b.  ECS Checksum c.  MD5 Checksum (based on RFC 1321) [Note: MD5 checksum is the new capability being added by this ticket.]	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DSS-07202	The STMGT CI shall accept and represent the MD5 checksum value in the form of a 32-character lowercase hexadecimal string.	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-DSS-07205	The SDSRV CI shall accept and store the MD5 checksum value in the form of a 32-character lowercase hexadecimal string.	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-INS-01200	The INS CI shall accept the following as valid checksum types when checking for checksum parameters associated with a file to be ingested: a.  CKSUM b.  ECS c.  MD5 [Note: MD5 checksum is the new capability being added by this ticket.]	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-INS-01205	The INS CI shall accept and represent the MD5 checksum value in the form of a 32-character lowercase hexadecimal string.	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-INS-01210	[Desirable] The INS CI shall accept optional parameters in the signal file (XFR file) that specify a checksum type and checksum value associated with the EDOS provided Level 0 data file. [Note: This requirement is to support checksumming for EDOS Level 0 ingest] 	
CK_71_03	End-to-End MD5 Checksum Capability	no data				S-OMS-01212	The OMS CI shall accept and represent the MD5 checksum value in the form of a 32-character lowercase hexadecimal string.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49010	The Data Pool Ingest Service shall checksum the configured percentage of browse and ancillary files (PH, QA, and DAP) from a given provider. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49020	The Data Pool Ingest Service shall use the configurable default checksum algorithm (type) of either cksum, or md5sum to checksum browse and ancillary data files provided without checksum.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49030	For each browse or ancillary file for which a checksum value has been calculated by DPL Ingest, the Data Pool Ingest Service shall store at a minimum the checksum algorithm used, the checksum value calculated and a checksum origin of DPLIngest in the Ingest database. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49040	The Data Pool Ingest Service shall provide checksum data for the configured percentage of  ancillary granule files to the Data Pool Insert Service.  The data include at a minimum the checksum value, the checksum type, and a checksum origin (DPLIngest).	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49050	The Data Pool Insert Service shall record the checksum type, value and origin in the Data Pool database for browse and ancillary data files with checksum information upon registration in the hidden Data Pool by the Data Pool Ingest Service. The last checksum verification date shall be recorded as the time of registration. The checksum origin shall be set to value of DPLIngest.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49060	The Data Pool Insert Service shall calculate the checksum of all browse and ancillary files retrieved from the archive and inserted into Data Pool. This checksum value shall be verified against the checksum value stored in the AIM Inventory database and the last checksum time shall be updated.  If the browse or ancillary file does not have a checksum value in the AIM Inventory database this one will be stored in the AIM Inventory Database, specifying DPAD as the origin.  	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49070	The DataPool Insert Service shall store the computed checksum in the DataPool database for the ancillary files it stages from the archive.  It shall update the DataPool xml file with the checksum value. (Archived browse files are converted to jpg images on insertion to the public DataPool.  These will not be checksummed).	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49080	Upon checksum verification failure, the DataPool Insert Service will update the checksum status in the AIM Inventory database and fail staging with an operator intervention. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49090	Upon checksum verification failure, the Data Pool Insert Service shall log an error message including the following information for each affected file:  Granule ID ESDT ShortName and Version ID Granule insert time Complete file name and path Checksum type Computed checksum Checksum value in database Last time checksum was verified Checksum status (Success or Failure) 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49100	To clarify the method of storing checksum information in the DPL and AIM Inventory databases the following specification is put forth:.  The checksum value will contain the provided value or the first value calculated. The last checksum time will be null for files without a provided or calculated checksum. The checksum verification status will be null until the checksum of the file is verified against a provided or calculated checksum value. This will allow the ECS system to tell the difference between a file that has had the checksum verified and one that has simply performed a calculation of the checksum value. The checksum origin can be one of the following:  DataProvider DPLIngest DPLInsert DPCV ACVU Migration DAAC Operations STMGT 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49110	The DPL CI shall provide a stand-alone Data Pool Checksum Verification Utility (DPCV) to verify the integrity of files resident in the Data Pool. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49120	The DPCV shall verify a Data Pool file by comparing the checksum value in the Data Pool database with the checksum value calculated for the files on disk.  The calculation of the checksum value will use the checksum type specified for the file in the Data Pool database.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49130	The DPCV shall be capable of being scheduled and run as a background process or being run on the command-line by the DAAC operator. Concurrent instances will be supported.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49140	The DPCV shall be able to verify checksum of files based on the following operator input options:  The operational mode in which to run (e.g. OPS, TS1, TS2) Whether to calculate checksum values for files without checksum values. A single or multiple ESDTs specified using the short name and version id Granule that were inserted during a given date range The number of days since the checksum was last verified A list of Data Pool granule ids. Percentage of files satisfying above criteria to checksum 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49150	The DPCV shall allow the DAAC operator to configure the number of milliseconds to sleep between verifying the checksum of each file. This will allow operator to throttle the utilization of system resources.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49160	The DPCV shall update the checksum verification time in the Data Pool database for each file whose checksum was successfully verified.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49170	The DPCV shall record the checksum verification status in the Data Pool database for each file whose checksum failed verification.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49180	Upon checksum verification failure after a configurable number of retry attempts, the DPCV shall write to a process specific log an error message including the following information for each affected file:  Granule ID ESDT ShortName and Version ID Granule insert time Complete file name and path Checksum type Computed Checksum Checksum value in database Last time checksum was verified 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49190	The DPCV log shall include the following statistical summary information for each ESDT:  Start and end time of run Run input parameters Number of files checked, organized by ESDT. Number of files that failed checksum verification, organized by ESDT Percentage of files that failed checksum verification organized by ESDT Total number of files attempted Total number of files that failed Total number of files whose computed checksum does not match Percentage of files that failed checksum verification. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DPL-49200	The DPCV shall output a file that contains granuleIds for which the associated files were not found on disk for use by the OLA repair utilities.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11010	The AIM Inventory database shall store the following checksum related attributes for each browse and ancillary file object  Checksum type Checksum value Last time checksum was verified Checksum Origin Checksum status (Success or Failure)	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11020	The AIM Inventory database shall store two additional fields to represent the checksum status and the last checksum time of a browse file. This is needed to distinguish between the browse file in the browse disk archive and the backup browse file on tape.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11030	The AIM Inventory Insert Utility shall record the checksum information into the AIM Inventory database when the granule information is inserted into the AIM Inventory database if a checksum has been computed for the granule file. The last checksum verification time will be set to the insert time of the granule. This will work the same way for science, browse and ancillary. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11040	The AIM CI shall provide a stand-alone Archive Checksum Verification Utility (ACVU) to proactively check and verify the integrity of files stored on both tape and in the browse disk archive.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11050	The ACVU shall be capable of being scheduled and run as a background process or being run on command-line by the DAAC operator.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11060	The ACVU shall be able to verify checksum of files based on the following operator input options:  A mandatory input parameter to specify the operation mode for checksum verification. Whether to calculate and store the checksum of files that do not have checksums. A single or multiple media (tape) IDs. A single or multiple volume groups. Number of Days since last checksum verification. A list of granule IDs. Percentage of files matching the above criteria to checksum. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11070	The ACVU shall organize the files selected for verification such that it will process all the files selected on one tape in the sequence in which they are stored. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11080	The ACVU shall allow the DAAC operator to configure the maximum number of tape reads it will submit at one time.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11090	The ACVU shall allow the DAAC operator to configure the maximum number of concurrent tapes that can be used for checksum verification.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11100	The ACVU shall verify the computed checksum values against the corresponding values stored in the AIM Inventory database using the checksum algorithm associated with the checksum type stored in the AIM Inventory database. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11110	The ACVU shall update the checksum verification time and status in the AIM Inventory database for each file on a tape or the browse disk archive whose checksum was successfully verified.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11120	The ACVU shall update the checksum status in the AIM Inventory database to specify failed in the case of checksum verification failure.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11130	The ACVU shall either log all granules that it failed to process because the tapes on which they were located were off-line or log the fact that a given media id was not processed because it is off-line. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11140	Upon checksum verification failure after a configurable number of retry attempts, the ACVU shall log an error message including the following information for each affected file:  Media ID Granule ID ESDT ShortName and Version ID Granule insert time Complete file name and path Checksum type Computed Checksum Checksum value in database Last time checksum was verified 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11150	The ACVU shall log the following statistical summary information:  Start and end time of run Run input parameters Number of files checked, organized by ESDT Number of files that failed checksum verification, organized by ESDT Percentage of files that failed checksum verification organized by ESDT Total number of files checked across all ESDTs Total number of files that failed checksum verification across all ESDTs Percentage of files that failed checksum verification across all ESDTs 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11160	The ACVU shall checkpoint its progress and be able to resume and complete a previous run that was interrupted, starting from the last checkpoint.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11170	The ACVU shall be able to checksum files at a rate of 200MB per minute.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-DSS-11180	The ACVU shall not significantly impact the performance of other ECS subsystems.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15100	The OMS GUI shall allow the DAAC operator to control the circumstances under which checksum verification will be performed based on media type and days since last checksum.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15110	For each media type (ftp-pull, ftp-push, scp, CDROM, DLT, or DVD) the OMS GUI shall allow the operator to dynamically specify the minimum number of days since the last checksum was performed on a file before verifying the checksum again.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15120	For data distribution using ftp-push or scp push, the OMS CI shall provide a DAAC configurable capability to dynamically turn off checksum verification for each destination.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15130	The OMS CI shall update the DataPool database after successful checksum verification of a file by setting the last checksum timestamp and the checksum status. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15140	The OMS CI shall generate an operator intervention event upon detection of checksum failure during data distribution and shall identify checksum failure as the reason for the intervention, including the name of the file that failed checksum verification. The checksum status will be marked as failed in the DataPool database. 	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15150	DELETED	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15160	DELETED	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15170	The OMS CI shall allow DAAC operators to limit the number of verification failures before suspension of resources.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15180	The OMS CI shall allow DAAC operators to limit the number of concurrent verifications.	
CK_7F_01	Enhanced End-to-End Checksum Capability for Release 7.22	no data				S-OMS-15190	The OMS CI shall log the following information for each checksum verification:  Granule ID ESDT ShortName and Version ID Granule insert time Complete file name and path Checksum type Computed checksum Checksum value in database Last time checksum was verified Execution time of checksum operation 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40010	The QAMUT CI shall be able to update the metadata QA flags and the corresponding explanation fields in the ECS inventory database.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40020	The QAMUT CI shall be able to update the Science or Operational QA flags and the corresponding explanation fields for a single or multiple data granules at a time.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40030	For data granules with multiple measured parameters, the QAMUT CI shall be able to accept and update QA metadata for all parameters with the same set of QA flag and the explanation field values. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40040	For data granules with multiple measured parameters, the QAMUT CI shall be able to accept and update QA metadata for individual parameter each with a different set of QA flag and explanation field values. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40045	The QAMUT CI shall append the date and time of update, accurate to the minute,  to the explanation fields provided in the request before storing them in the ECS inventory database. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40060	The QAMUT CI shall provide a DAAC configurable e-mail address at which the QA update requests are received. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40065	The QA update request processed by the QAMUT CI shall include the following information:  a. Requester ID   b. QA Flag Type (Science or Operational)  c. QA metadata update request details. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40066	The Requester ID included in the request shall be provided in one of the following format:  a. a valid e-mail address   b. a text string identification for a SCF/DAAC site 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40070	The QAMUT CI shall authenticate  a QA update request by   a. validating the Requester ID included in the request against a list of            valid Requester IDs maintained at the DAAC (and)   b. ensuring that the ESDT to be updated is allowed for the Requester ID.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40075	Upon failure in authenticating the request, the QAMUT CI shall send an e-mail notification to the requester indicating authentication failure. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40077	Upon failure in authenticating the request, the QAMUT CI shall reject the entire request and terminate the processing.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40080	The QAMUT CI shall maintain an operator  configurable list of valid Requester IDs corresponding to the SCF and DAAC sites and the ESDTs that can be updated by each site for the purpose of authenticating the QA update requests. . 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40090	The QA metadata update request details shall specify  the granules to be updated based on   a. ESDT Short name, Version ID and Granule UR (or)   b. ESDT short name, version ID and Local Granule ID (or)   c. ESDT short name, version ID and a temporal window that defines the         acquisition date and time range	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40110	The QA metadata update request based on Granule URs shall include the following information for each granule:  a. ESDT Short Name  b. Version ID  c. Granule UR   d. One or more triplets of  Measured Parameter name, QA Flag and the corresponding explanation field.     (or)A QA Flag, the corresponding explanation field and an indicator to apply this set of values to all measured parameters	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40115	The QA metadata update request based on Local Granule IDs shall include the following information for each granule:  a. ESDT Short Name  b. Version ID  c. Local Granule ID (LGID)  d. One or more triplets of  Measured Parameter name, QA Flag and the corresponding explanation field.     (or)A QA Flag, the corresponding explanation field and an indicator to apply this set of values to all measured parameters	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40120	The QA metadata update request specifying  ESDT and temporal window shall include the following information:  a. ESDT Short Name  b. Version ID  c. Temporal window characterized by the acquisition date and time range.  d. One or more triplets of  Measured Parameter name,  QA Flag value and the corresponding QA Explanation field    (or)A QA Flag, the corresponding Explanation field and an indicator to apply this set of values to all measured parameters	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40125	The temporal window for QA metadata update shall be specified as the time range bounded by the beginning acquisition date and time of the earliest granule and the beginning acquisition date and time of the latest granule. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40130	Operators shall be able to run the QAMUT  CI from the command line.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40140	The QAMUT CI shall provide an operator configurable mode-specific request directory where all QA update request files intended for that mode reside.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40145	The QAMUT CI shall be able to process an individual QA update request file provided via command line, (or) all update request files located in a configured request directory.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40146	Each QA update request file name shall contain the following information as part of its name:  a. Operation mode   b. The SCF or DAAC site name that originated the request  c. Time tag of request accurate to second. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40147	The QAMUT CI shall reject a request and terminate with a non-retryable failure if the operation mode indicated by the request file name does not match the operation mode in which the QAMUT is being executed.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40148	When processing all update request files in a request directory, the QAMUT CI shall process the requests originated from a particular SCF or a DAAC site in order of the request time tag as indicated by the request file names. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40149	A non-retryable failure in processing a request file in the request directory shall not prevent the QAMUT CI from processing the  remaining request files in the directory. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40150	The QAMUT CI shall validate the command line parameters for correct syntax (format and valid range). 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40160	Upon failure in validating the command line syntax (format and valid range), the QAMUT CI shall display an error message and the correct command line syntax.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40170	The QAMUT CI shall validate the syntax (format and valid range) of the QA Flag values included in the request before performing the updates.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40175	For a specific granule in a QA update request, the QAMUT CI shall flag as non-retryable error if a non-existent or an invalid measured parameter name is provided for that granule. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40176	For a specific granule in a QA update request, the QAMUT CI shall flag as non-retryable error if the Granule UR or the Local Granule ID does not exist in the ECS inventory database.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40190	In processing a QA update request, the QAMUT CI shall allow the operator to view, before performing the QA updates, the following information:  a. A list of affected granules identified by ESDT Short Name, Version ID, LGID, dbID, along with the measured parameters and the current and new QA flag values  b. Total number of granules that will be updated.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40200	The QAMUT CI shall, by default, prompt the operator for confirmation before performing the updates.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40205	The QAMUT CI shall display a warning message if it detects that the number of granules to be updated exceeded a DAAC configurable maximum threshold. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40210	In processing a QA update request, the QAMUT CI shall allow the operator to view, after performing the QA updates, the following information:  a. A list of affected granules identified by ESDT Short Name, Version ID, LGID, dbID, along with the measured parameters and the updated QA flag values  b. Total number of granules updated.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40220	The QAMUT CI shall allow the operator to suppress the operator prompts and the display of all messages via a no-prompt command line option.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40230	The QAMUT CI shall suppress all operator prompts if the no-prompt option is specified assuming an affirmative response in these cases.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40232	The QAMUT CI shall provide the following e-mail notification options that can be configured by the operator for each SCF or DAAC.  a. Send e-mail notification upon successful completion of QA updates as well as non-retryable failure.  b. Send e-mail notification only upon non-retryable failure.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40233	The QAMUT CI shall allow an operator to configure a Reply-To: e-mail address for each SCF or a DAAC site to which e-mail notifications are sent.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40235	The QAMUT CI shall allow an operator to set up a list of internal DAAC e-mail addresses to which an e-mail notification is sent or copied upon completion of a QA update run.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40240	The e-mail notification generated by the QAMUT CI upon successful completion or non-retryable error shall include the following information as applicable:   a. The name of the request file being processed.  b. Total number of granules specified in the request  c. Total number of granules updated  d. A list of granules not updated along with specific error messages and reasons for failure in case of errore. Success or error status 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40250	The QAMUT CI shall send an e-mail notification to the requester using the Reply-To: e-mail address configured for the requesting site if available.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40260	If the Reply-To: address is not available, the QAMUT CI shall send an e-mail notification to the From: e-mail address included in the request.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40280	The QAMUT CI shall use a standard name for its log file.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40290	The QAMUT CI shall create a log file if the log file does not already exist.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40300	The QAMUT CI shall append the log messages to the log file if the log file already exists.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40310	The QAMUT CI shall include time stamp and the process ID in all log messages.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40320	The QAMUT CI shall log the name of the request file at the start of processing each request file. 	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40330	For each granule updated, the QAMUT CI shall log the granule ID (dbID) along with the measured parameters, the QA values, and the corresponding explanation fields before and after the update.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40340	The QAMUT CI shall log all warning and error messages encountered during the run.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40350	The QAMUT CI shall log the following information at the end of a run  a. Total number of granules requested  b. Total number of granules updated  c. Run completion or Failure status  	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40360	Upon detecting a non-retryable error in processing a particular granule, the QAMUT CI shall    a. log an error and continue with the rest of the granules in the request. (or)  b. log an error and terminate the entire request (default option).    depending on the processing option set via command line.	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40370	The QAMUT CI shall be capable of performing QA updates for a total of 115,000 granules (each granule containing an average of 6 measured parameters) within a 24 -hour period; the number of granules are distributed as follows:   a. 100,000 granules via update requests based on ESDT and temporal window.  b. 15,000 granules via update requests based on local granule ID (LGID).	
CY_6B_01	Quality Assessment Metadata Update Tool (QAMUT) Performance Enhancement	no data				S-DSS-40390	The QAMUT shall be able to operate in multiple modes concurrently.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99000	ECS shall provide a DDIST Command Line Interface (DCLI) to submit distribution requests for files on disk that are accessible on the DDIST platform or on a file system NFS mounted on the DDIST platform.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99010	The DCLI shall accept a mandatory DDISTMEDIATYPE parameter.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99020	The DCLI shall verify that the DDISTMEDIATYPE parameter is provided and specifies one of the following valid ECS media types, returning a fatal error if not:  FtpPush  FtpPull	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99030	The DCLI shall include the DDISTMEDIATYPE parameter in the distribution request it submits to the DDIST.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99040	The DCLI shall accept the following FTP Push parameters (all strings) if the DDISTMEDIATYPE is FtpPush:  FTPUSER  FTPPASSWORD  FTPHOST  FTPPUSHDEST	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99050	The DCLI shall verify that all four FTP Push parameters are provided if the DDISTMEDIATYPE is FtpPush, and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99060	The DCLI shall include the FTP Push parameters in the distribution request it submits to the DDIST.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99070	The DCLI shall accept an optional DDISTMEDIAFORMAT parameter	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99080	The DCLI shall verify that the DDISTMEDIAFORMAT parameter, if present, specifies a value of 'FILEFORMAT' and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99090	The DCLI shall include the DDISTMEDIAFORMAT parameter in the distribution request it submits to the DDIST.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99100	The DCLI shall accept a mandatory ECSUSERPROFILE parameter.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99110	The DCLI shall verify that the ECSUSERPROFILE parameter is present and refers to an existing MSS user profile or is ECSGuest, and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99120	The DCLI shall include the ECSUSERPROFILE parameter in the DDIST distribution request it submits.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99130	The DCLI shall accept a mandatory ORDERID and a mandatory REQUESTID parameter.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99140	The DCLI shall verify that the ORDERID and REQUESTID parameters are present and refer to an existing MSS order for the same userID as the distribution request, and an existing MSS request for that order, and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99150	The DCLI shall include the REQUESTID parameters in the DDIST distribution request it submits.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99160	The DCLI shall accept an optional PRIORITY parameter.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99170	The DCLI shall verify that the PRIORITY parameter, if present, specifies one of the following ECS priorities and return a fatal error if not:  LOW  NORMAL  HIGH	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99180	The DCLI shall include the PRIORITY parameter in the DDIST distribution request it submits.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99190	The DCLI shall accept an optional UserString parameter specifying a string of a maximum length of 80 characters.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99200	The DCLI shall verify that the UserString parameter does not exceed the maximum length and return a fatal error if it does.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99210	The DCLI shall include the UserString parameter in the DDIST distribution request it submits.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99220	The DCLI shall accept an optional DDISTNOTIFYTYPE parameter.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99230	The DCLI shall verify that the DDISTNOTIFYTYPE parameter, if present, is set to MAIL, and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99240	The DCLI shall accept a mandatory NOTIFY parameter specifying an e-mail address string.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99250	The DCLI shall verify that the NOTIFY parameter is present and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99260	The DCLI shall include the DDISTNOTIFYTYPE and NOTIFY parameters in the DDIST distribution request it submits.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99270	The DCLI shall accept a mandatory tag parameter as a string of up to 20 characters.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99280	The DCLI shall verify that the tag parameter is present and at most 20 characters in length, and return a fatal error if not.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99290	The DCLI shall use the tag parameter to generate an rpcID for the DDIST distribution request it submits.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99300	The DCLI shall generate the identical rpcID only if it receives the identical tag on different submission requests, the generated rpcID otherwise being different.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99310	The DCLI shall accept a list of up to 100 fully qualified file/path names that represent the files to be distributed.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99320	The DCLI shall return a fatal error if less than one and more than 100 file/path names are provided.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99330	The DCLI shall assume the following default values for the corresponding optional parameters if they are not provided:  DDISTMEDIAFORMAT  = FILEFORMAT  PRIORITY = NORMAL  DDISTNOTIFYTYPE = MAIL	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99340	The DCLI shall submit an asynchronous distribution request for the identified files to DDIST.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99350	The DCLI shall, if the submission of the DDIST request fails, return an error that identifies the error as retryable or fatal, as determined by the error status returned from DDIST.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99360	The DCLI shall be able to accept requests for a designated mode.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99370	It shall be possible to submit several requests in a given mode via the DCLI concurrently.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99380	It shall be possible to submit requests via the DCLI in several different modes concurrently.	
DC_SY_01	Distribution Command Line Interface	no data				S-DSS-99390	The DCLI shall be able to receive and process distribution requests through to DDIST at the rate of 40 requests per hour.	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50200	The EWOC shall provide a SOAP web service to accept orders from ECHO. [Iteration 1]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50205	The EWOC order web service will conform to the WSDL definition of the Submit portion of the ECHO 9.0 Order Fulfillment API. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50210	The EWOC shall provide a SOAP web client to forward elements of orders that require external subsetting or production to the appropriate External Processor web service. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50215	The EWOC shall submit external processor orders conformant to the 'Submit' portion of the ECHO 9.0 Order Fulfillment API. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50220	The EWOC shall be able to determine the end point of external processor web services dynamically on a per-order item basis as described in the ESDIS document TBD 423-45-03  Interface Control Document for ECS ECHO WSDL Order Component (EWOC) and External Processing Systems Co-located at the DAACs. 	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50225	The EWOC shall be able to determine if a 'consider processing options' request bundling policy is required of an order as described in the ESDIS document TBD 423-45-03  Interface Control Document for ECS ECHO WSDL Order Component (EWOC) and External Processing Systems Co-located at the DAACs.  [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50230	The EWOC shall provide a SOAP web service to accept order status updates from one or more external processors. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50240	The EWOC shall send to the external processor an acknowledgement of the receipt of an order status update, with an indication of successful or unsuccessful validation of the status update. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50250	The EWOC shall update the order status of the external processing request in MSS, using the order status update received from the external processor. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50260	The EWOC shall provide a SOAP web client to relate the terminal status of orders to ECHO. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50270	The EWOC shall submit order status updates to ECHO no later than 5 minutes after the last line item in an order has reached a terminal state. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50280	The EWOC shall submit order status updates to ECHO which are conformant to the WSDL definition of the 'Close Provider Order' portion of the ECHO 9.0 Order Processing Service API. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50300	The EWOC shall have the capability to process ECHO Order Fulfillment Web Service Submit Requests. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50310	The EWOC shall receive Submit Requests from clients conforming to the ECHO Order Fulfillment Web Service interface definition. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50320	The EWOC shall have the capability to send Submit Responses to a client conforming to the ECHO Order Fulfillment Web Service interface definition. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50330	The EWOC shall send a Submit Response back to ECHO within 60 seconds of receiving the ECHO Order Fulfillment Web Service Submit request. [Iteration 3]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50340	The EWOC shall provide the capability to translate ECHO Order Fulfillment Web Service protocols into ECS system protocols. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50350	The EWOC shall provide the capability to translate ECS system protocols into ECHO Order Fulfillment Web Service protocols. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50360	The EWOC shall provide the capability to receive Submit Requests from External Processor systems, in conformance with protocols defined in the ECHO Order Fulfillment Web Service interface definition. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50370	The EWOC shall support the following media types: a.  CD-ROM b.  DLT c.  DVD d.  Ftp Pull e.  Ftp Push [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50380	The EWOC shall support the tarfile format for the DLT media type. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50390	The EWOC shall support the following formats for the CD-ROM and DVD media types: a.  ISO 9660 b.  Joliet c.  Long Joliet d.  UDF e. Rockridge [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50400	The EWOC shall create an MSS Order and one or more Request objects for a Submit Request submitted by a client. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50410	The EWOC shall submit all data distribution requests to the OMS for registration. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50420	The EWOC shall accept error responses from the OMS for request registration errors. [Iteration 2] [Note: A request that cannot be registered with OMS will be rejected.  Errors that prevent registration include invalid ESDT reference, invalid granule ID, and OMS database errors.]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50430	The EWOC shall not retry submission of a request if the OMS returns an error during registration of a request. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50440	The EWOC shall forward errors returned by the OMS to its clients, with explanatory comments that describe the corrective actions the user should take, and include the appropriate error information in the Submit Response message, in accordance with the ECHO Order Fulfillment Web Service interface definition. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50450	The EWOC shall return an error to the user when it discovers, via interaction with the OMS, that the granule identified in a user request does not exist in the ECS inventory. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50460	The EWOC shall support multiple concurrent requests. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50470	The EWOC shall access data only for the mode in which the application is configured. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50480	The EWOC shall be capable of simultaneous execution in different modes on the same machine. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50490	The EWOC shall be capable of simultaneous execution in different modes on different machines. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50500	The EWOC shall accept a specific mode at startup. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50510	The EWOC shall log the initiation of each request. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50520	The EWOC shall add log entries pertaining to start up. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50530	The EWOC shall add log entries pertaining to shut down. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50540	The EWOC shall log a message upon successful completion of each request. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50550	The EWOC shall log all errors. [Iteration 2]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50600	The EWOC shall register requests for external processing with the OMS. [Iteration 4]  	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50610	The EWOC shall identify the external processor that needs to process an external processing request when registering such a request to the OMS. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50615	The EWOC shall update the status of the MSS requests object based on the response from the external processor. The status will be updated to Pending if the external processing service accepted the request and to Aborted if the external processing service rejected the request. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50620	The EWOC shall process the order items of a Submit Request that contain external processing specifications to determine which entities, an External Processor or OMS, the order items should be directed to. Consequently, the EWOC may direct portions of the Submit Request to OMS and/or one or more external processors. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50640	The EWOC shall generate new MSS request objects consisting of a grouping of order items based on the following rules: 1.  All non-processed items with common physical media type and format will be bundled into a single MSS Request. 2.  All non-processed items of media type ftp pull and common media format will be bundled into a single ECS Request 3.  All non-processed items in an ECS Order of media type ftp push and the following identical media options of user name, password, hostname, port and destination directory will be bundled into a single ECS Request. 4.  All items in an ECS Order requiring processing by the same external processor and that have common media options (see clauses (2) and (3)) will be bundled if,  The submit message specifies a 'consider processing options' request bundling policy and they share identical processing options.  The submit message does not specify a 'consider processing options' request bundling policy.   [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50670	The EWOC shall include the MSS orderID and MSS requestID in the Submit Request message sent to the external processor as described in the ESDIS document TBD 423-45-03  Interface Control Document for ECS ECHO WSDL Order Component (EWOC) and External Processing Systems Co-located at the DAACs.  [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50680	The EWOC shall, in the event of receiving a submit request requiring external processing, send external processing Submit Request messages to External Processing systems in conformance with protocols defined in the ECHO Order Fulfillment Web Service interface definition. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50690	The EWOC shall be able to interface with three or more external processors. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50720	The EWOC shall inform the OMS to flag MSS requests associated with Submit Requests containing external processing options to indicate that they are external processing request type. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50730	The EWOC shall, if all requests within an order are of type 'external processing', inform the OMS to flag the MSS order to indicate that the order is an external processing order type. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50740	The EWOC shall provide the MSS order   identification as part of a submit request to an external processor. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50750	The EWOC shall convey a success status to ECHO when a Submit request results in the successful placement of all subordinate requests with OMS and /or External Subsetters. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50760	The EWOC shall convey a failed status to ECHO when a Submit request results in the failure to place any subordinate requests with OMS and/or External Subsetters. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50770	The EWOC shall convey success status to ECHO when a Submit request results in the immediate failure of one or more (but not all) subordinate requests. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50775	The EWOC shall, in the event of a partial success of a Submit request, invoke the Close Provider Order method of the ECHO Order Processing Service API for each MSS request that failed. The Close Provider Order invocation will detail the granules within that request that failed and the nature of the failure. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50780	The EWOC shall provide a mechanism for ECHO clients to allow users to order products that can be processed by external processors and distributed by the OMS. [Iteration 4]	
DM_7B_01	EWOC (ECHO WSDL Ordering Component) Iteration 4	no data				S-DMS-50790	The EWOC shall supply the OMS with duplicate request checking information when placing a request if configured to do so. That information consists of the checksum of a concatenation of the following information, 1.  the contact email of the order 2.  the user string of the request (if the media type is ftp push) 3.  a list of granule ids [Iteration 4]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60510	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) the following tuning configuration parameters for the Data Pool Insert Service: a. the maximum number of concurrent checksumming operations which the Data Pool Insert Service may dispatch, for each ECS host on which such operations are being executed by the Data Pool Insert Service, b. the maximum number of concurrent archive read from cache operations that may be executed on an ECS Service Host, by host [NOTE: The sum of these limits represents the overall maximum number of concurrent archive read from cache operations], c.  parameters to calculate a time limit for archive cache read operations before assuming that they are hung, consisting of a minimum expected throughput and a time constant reflecting the maximum expected fixed overhead, separate for each ECS Service Host [NOTE: This replaces the current InCacheTimeLimit,] [NOTE: Configuration of the new tuning parameters shall occur via the same GUI page that supports the configuration of the items in S-DPL-16460 in Ticket DP_S6_01.] [NOTE: The time-out value for read from tape operations is independent of ECS Host and allows for the time spent waiting for drive allocation and robot and tape operations.  The time-out is host independent, exists already (OnTapeTimeLimit), and is configurable via the DPM GUI.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60520	The DPL CI shall permit DAAC operators to limit the maximum number of concurrent checksumming operations that may be executing concurrently, separately for each ECS Service Host configured for that purpose and independent of the requesting service. [NOTE: This may be a configuration parameter associated with the QuickServer executing on the respective host.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60530	The Data Pool Maintenance GUI shall permit full capability operators to configure (i.e., enter and edit) the following tuning parameters: a. The maximum number of concurrent Data Pool registration operations b. The maximum number of concurrent Data Pool publishing operations	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60535	The Data Pool Maintenance GUI shall permit full capability operators to configure (i.e., enter and edit) the maximum number of concurrent tape read operations for a single tape.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60540	The Data Pool Maintenance GUI shall permit full capability operators to configure (i.e., enter and edit) the following alert related configuration parameters: a. Deleted, b. the number of time-outs or errors not attributed to other resources that will raise an alert for a service on an ECS host when returned by the same host and service consecutively for different granules or files (examples are SAN file system access errors that are not attributed to the file system being down and checksumming time-outs). c. retry interval for attempts to clear an alert condition, to be used globally for all situations for which there are no specific retry intervals,  [NOTE: The new configuration parameters are not specific to a host, file system, or archive and therefore, can be maintained via the DPM GUI configuration parameters screen.] [NOTE: Similar parameters are also configured for the Data Pool Ingest service as per S-DPL-16482; however, they are not shared and reside in different database tables.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60550	The Data Pool Maintenance GUI shall permit operators to configure the retention time for closed alerts and the time interval at which expired alert information will be cleaned up. 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60560	The Data Pool Maintenance GUI shall permit full capability operators to configure (i.e., enter and edit): a. a time interval between one and ten minutes at which the Data Pool Insert Service will check the status of Data Pool file systems and obtain free space information for them, and b. the percentage of free space which when exceeded or of consumed space which when underrun (compatible with the DPL Ingest GUI) will clear a Data Pool file system full condition. [NOTE: Operators can use the archive and file system monitoring page on the DPL Ingest GUI to monitor archives and file systems. However, as a new capability, the Data Pool Insert Service will also monitor the status of file systems.  It will raise an alert when it discovers that a Data Pool file system is down and clear it when it detects that the file system is back up.  In addition, it will clear the file system full condition when the file system free space has climbed above the configured threshold, i.e., different from today where it waits for Data Pool Cleanup to clear the condition.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60585	The Data Pool Insert Service shall close a Data Pool Insert Service alert for a Data Pool file system when the operator resumes access to that file system by Data Pool inserts manually. [NOTE: Operators resume a file system by marking it available on the DPM GUI.  If they do this for a file system for which a Data Pool Insert Service alert is pending, the alert is closed, and the Data Pool Insert Service will start using it again.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60670	The Data Pool Maintenance GUI shall allow full capability operators to configure an e-mail address to which notifications about alerts shall be sent. [NOTE: The Data Pool Maintenance GUI has no alert monitoring screen.  If the DAAC does not configure such an e-mail address, operators will receive no notification about alerts.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60680	The Data Pool Maintenance GUI shall allow full capability operators to configure an age (in hours) which determines when a granule lock should be considered stale.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60690	The Data Pool Maintenance GUI shall allow full capability operators to configure the percentage of science files for which a checksum using the default checksum type should be calculated and saved in the Data Pool inventory during Data Pool insert if they currently do not have a checksum, or whose checksum should be verified if they already have a checksum type and checksum value. [NOTE: This replaces S-DPL-46020 and S-DPL-46025 in CK_70_01 and overrides any modifications by subsequent NCR.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60710	The Data Pool Insert Service shall raise a Data Pool Insert Service alert for an archive when the target archive file system is down (i.e., is not mounted). [NOTE: Archive reads are performed on ECS Service Hosts. Errors can be caused by archive cache file system being down (see above), or by the host having SAN connectivity problems (which will lead to consecutive archive read errors or time-outs. In that case, the alert will be raised for the ECS Service Host rather than an archive.] [NOTE: This requirement replaces S-DPL-42370 in OD_S4_01 which specifies the behavior for AMASS access and is no longer applicable.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60720	The Data Pool Insert Service shall raise no more than one Data Pool Insert Service alert for a given archive (i.e., even if multiple archive read operations are in progress at that time.)	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60730	The Data Pool Insert Service shall stop dispatching operations that read from an archive (tape or cache) while a Data Pool Insert Service alert is pending for it or while it is manually suspended. [NOTE: This requirement covers S-DPL-42310 in OD_S4_01.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60740	The Data Pool Insert Service shall automatically retry archive access operations for an archive while a Data Pool Insert Service alert remains pending for it using the retry time interval globally configured for alert situations (see S-DPL-60540) and clear the alert when a retry succeeds. [NOTE: In lieu of retries, it is permissible to check the archive file system status at regular intervals and close the alert when one of those checks discovers that the archive is available again.  In that case, the archive checks would have to be at a frequency of at least once every ten minutes.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60750	The Data Pool Insert Service shall resume dispatching operations for an archive when closing a Data Pool Insert Service alert.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60751	The Data Pool Insert Service shall notify OMS when it raises and closes archive alerts. 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60752	The Data Pool Insert Service shall include information regarding the affected archive silo when it notifies OMS about raising and closing archive alerts.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60760	The Data Pool Insert Service shall raise a Data Pool Insert Service alert for a Data Pool file system when one of the following situations occurs: a. the file system is full, b. the file system is down (i.e., not mounted). [NOTE: File system errors encountered by an ECS Service Host that are not diagnosed as the file system being full or down will lead to consecutive errors for that host and a host service alert, signaling that the host may have SAN connectivity problems.] [NOTE: The file system full condition is detected in accordance with S-DPL-45320 in OP_S4_06.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60770	The Data Pool Insert Service shall raise no more than one Data Pool Insert Service alert for a given Data Pool file system.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60780	The Data Pool Insert Service shall stop dispatching archive read operations (from tape or cache) for Data Pool insert requests targeting a Data Pool file system for which a Data Pool Insert Service alert is pending or which is manually suspended. [NOTE: Data Pool insert will not start any new transfers from archive cache to that file system, nor start staging for any granules that target a suspended Data Pool file system.  The latter ensures that staged granules that cannot be transferred to their target location do not accumulate needlessly in the archive cache.  This  requirement covers S-DPL-45330 in OP_S4_06 and adds the file system down condition.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60790	The Data Pool Insert Service shall stop dispatching operations requiring access to a Data Pool file system while a Data Pool Insert Service alert is pending for it. [NOTE:  For example, a checksumming operation for a granule affected by a Data Pool file system alert will not be dispatched; however, if that Data Pool file system is suspended by the operator, the checksumming operation will be executed.  This allows an operator to quiesce use of a file system, letting insert request complete whose files already reside in that file system.  S-DPL-60780 ensures that no new insert request for that file system will be started and use of that file system, therefore, will quickly subside.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60800	The Data Pool Insert Service shall check the free space in Data Pool file systems at an operator configurable time interval (see S-DPL-60560) in order to determine whether a pending file system alert can be closed. [NOTE:  The Data Pool Insert Service will not use the free space information to raise alerts for nearly full file systems, and it will not save the free space information for display on the DPM GUI.  Operators should use the DPL Ingest GUI to monitor archives and Data Pool file systems.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60810	The Data Pool Insert Service shall close a Data Pool Insert Service alert for a full Data Pool file system if it finds during one of the Data Pool File system checks that the amount of free space available in that file system is above the operator configured threshold (see S-DPL-60560). [NOTE: This is in addition to file system full condition possibly being cleared by the Data Pool Cleanup Utility, as per S-DPL-45410 in OP_S4_06.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60820	The Data Pool Insert Service shall close a Data Pool Insert Service alert for a down Data Pool file system if it finds during one of the Pool File system checks that the file system is available again.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60830	The Data Pool Insert Service shall resume dispatching operations for a Data Pool file system when closing a Data Pool Insert Service alert for it. [NOTE: This requirement extends S-DPL-45340 and S-DPL-45350 in OP_S4_06.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60831	The Data Pool Insert Service shall notify OMS when it closes Data Pool file system alerts. NOTE: This augments S-DPL-42390 in Ticket OD_S4_01  	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60840	The Data Pool Insert Service shall raise an operator alert when an attempt to use an ECS service on a particular host (such as checksumming and archive read accesses) results in one of the following errors: a. connection with the service cannot be established (e.g., the service, platform, or network are down), b. connection with the service is lost (e.g., the service or platform terminated abnormally and may be rebooted), c. requests for that service do not complete within an expected, configurable time frame (e.g., checksumming operations take excessively long) or requests for that service return errors that are not attributed to some other resource (e.g., a Data Pool file system or archive being down)  for N different service requests consecutively where N is configurable by DAAC operations (see S-DPL-60540),  d. Deleted. [NOTE:  as per S-DPL-60510, the time out parameters are shared with corresponding Data Pool Ingest time out parameters defined in Ticket DP_S6_01, S-DPL-16460.] 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60850	The Data Pool Insert Service shall raise no more than one operator alert for a given ECS service on a given host.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60860	The Data Pool Insert Service shall no longer dispatch operations for a given ECS service on a given host while an alert is currently pending for it. [NOTE: The expectation is that the Data Pool Insert Service will use other hosts (if available), and re-dispatch any failed operations to these hosts.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60870	The Data Pool Insert Service shall automatically retry connecting to or invoking an ECS service for which it suspended dispatching using the retry time interval globally configured for alert situations (see S-DPL-60540) and clear the alert for that service when a retry succeeds.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60880	The Data Pool Insert Service shall resume dispatching operations for an ECS Service on a given host when closing a Data Pool Insert Service alert for it.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60890	The Data Pool Insert Service shall send notifications when raising and closing alerts to the e-mail address configured for that purpose unless no such e-mail address was configured.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60900	The Data Pool Insert Service shall include the following information in the notifications about operator alerts: a. the resource that caused the alert (e.g., ECS host and service, data pool file system, archive), b. the nature of the alert, c. information regarding the error that caused the alert to be raised.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60910	When inserting granules into the public Data Pool that belong to collections enabled for HEG processing, the Data Pool Insert Service shall obtain the band parameter information from the HDF-EOS file and insert it into the Data Pool inventory without increasing the granule insert time by more than 5 seconds. [NOTE: Extraction of band information for such granules when they are inserted only into the hidden Data Pool is not required but acceptable.  This replaces S-DPL-23900 in WD_S4_02 by reallocating it to the Data Pool Insert Service in general.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60920	When inserting granules into the public Data Pool that belong to collections enabled for HEG processing, the Data Pool Insert Service shall fail the publication of a granule if no band information is available for the granule. [NOTE: This replaces S-DPL-23910 in WD_S4_02.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60921	The Data Pool Insert Service shall not fail the insertion of a granule into the hidden Data Pool (e.g., as requested by OMS) if the band information extraction yields no bands or fails, in case of retriable errors after the required number of retries. [NOTE: This replaces S-DPL-23910 in WD_S4_02.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60922	The Data Pool CI shall provide a mechanism which allows an operator to recover from band tool errors that may have occurred when a granule was inserted into the hidden Data Pool and now prevent the granule from being published. [NOTE: For example, the Data Pool CI may provide a stand-alone tool for extracting the band information and adding it to the Data Pool inventory and then queuing a publishing action for a list of currently hidden granules.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60925	The Data Pool Insert Service shall accept and process requests to insert ingested granules that reside in the hidden Data Pool into the public Data Pool and do so without access to the archive.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60930	The Data Pool Insert Service shall not apply granule replacement logic and prevent file name collisions when inserting granules into the hidden directory structure, such that granules that are ordered but not published will never overwrite another granule in the Data Pool, nor cause a file name collision with another granule in the Data Pool. [NOTE: This modifies earlier requirements regarding file naming for insertion into the non-public Data Pool.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60940	The Data Pool Insert Service shall verify the checksums of science files retrieved from the archive for the configured percentage of science files that have checksum types and values after transferring the files to the Data Pool file system. [NOTE: This replaces S-DPL-46030 and S-DPL-46032 in CK_70_01, thereby removing the special handling for ECS checksums.  All checksum types will now be handled in a similar fashion.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-60950	The Data Pool Insert Service shall calculate a checksum during data pool file insertion for the configured percentage of science files of ECS granules that have no checksum type and checksum value and are retrieved from the archive, using the default checksum type configured via the Data Pool Ingest GUI (see S-DPL-16570.) [NOTE: This replaces S-DPL-46031 in CK_70_01, thereby removing the ECS checksum as the automatic default checksum type.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61000	The Data Pool Insert Service shall use the ports for ECS host services that were configured via the Data Pool Ingest GUI, as per S-DPL-16580 in Ticket DP_S6_01.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61010	The Data Pool Insert Service shall perform checksum operations on the ECS platforms configured for that purpose.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61015	The Data Pool Insert Service shall not checksum a file for the purpose of verifying a checksum on the platform that was used to transfer it from the archive, unless no other platform has been configured for that purpose.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61040	The Data Pool Insert Service shall limit the combined total number of concurrent checksumming operations that it dispatches to an ECS host to the maximum number of checksumming operations configured by the operator for that host (see S-DPL-60510). [NOTE: The intent is to balance the checksum workload across these platforms roughly proportional to the configured number of 'CPU slots'.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61050	The Data Pool CI shall limit the number of concurrent CPU-intensive operations that it executes on an ECS host to a maximum number of checksumming operations configured by the operator for that host (see S-DPL-60520). [NOTE: The intent is to limit the number of checksumming operations regardless of the individual limits configured for each Data Pool Service. For example, if the maximum number of checksumming operations is configured to two for Data Pool Ingest and two for Data Pool Insert, each service may dispatch two checksumming operations concurrently. However, if the combined limit is set to two, only two of these operations will execute; the remainder will need to wait until other operations complete.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61060	The Data Pool CI shall execute requested checksumming operations on a first-in first-out basis when the sum of the checksumming operations dispatched by Data Pool services exceeds the configured combined limit on the number of checksumming operations for that platform.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61070	The Data Pool Insert Service shall cancel a checksumming operation if it does not complete within the time limit established in accordance with the configured time-out parameters and retry the operation until the configured number of maximum retries is exceeded, failing the operation thereafter (see S-DPL-60510 and Ticket DP_S6_01, S-DPL-16460). [NOTE: The number of retries is an existing DPL configuration constant.  Configuring the number of retries to zero would have the effect of failing the read operation without retry. Note that N consecutive failures or timeouts will cause an alert as per S-DPL-60840.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61080	The Data Pool Insert Service shall perform archive read from cache operations on the ECS platforms configured for that purpose.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61090	The Data Pool Insert Service shall observe the configured limits on the number of concurrent archive read-from-cache operations for an ECS Service Host (S-DPL-60510.)	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61100	Once a tape has been selected for mounting, the Data Pool Insert Service shall perform multiple file read operations from the same tape concurrently, subject to the configured limit on the number of concurrent archive tape read operations for a single tape (see S-DPL-60535). [NOTE: The requirement supersedes S-DPL-42350 which imposed an overall limit rather than a limit by tape.  The requirement also aligns NCR 41475 with the new Data Pool Insert Service architecture.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61110	The Data Pool Insert Service shall cancel an archive read-from-cache operation if it does not complete within the time limit established in accordance with the configured time-out parameters (S-DPL-60510), and retry the operation until the configured number of maximum retries is exceeded, failing the operation thereafter. [NOTE: The number of retries is an existing DPL configuration constant.  Configuring the number of retries to zero would have the effect of failing the read operation without retry. Note that N consecutive failures or timeouts will cause an alert as per S-DPL-60840.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61120	The Data Pool Insert Service shall cancel an archive tape read operation if it does not complete within the time limit established in accordance with the configured time-out limit and retry the operation until the configured number of maximum retries is exceeded, failing the operation thereafter. [NOTE: The time limit and the number of retries is an existing DPL configuration constant.  Configuring the number of retries to zero would have the effect of failing the read operation without retry. Note that N consecutive failures or timeouts will cause an alert as per S-DPL-60840.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61130	The Data Pool Insert Service shall limit the number of concurrent Data Pool registration and Data Pool publishing operations to the limits configured by the operator (see -DPL-60530).	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61150	The Data Pool Insert Service shall dispatch all operations for Data Pool insert requests on a first-in first-out basis with the sole exception of reading files from tape into archive cache, which shall be dispatched in accordance with existing requirements (see S-DPL-42330, S-DPL-42340 and NCR 41475). [NOTE: This retains existing requirements for dispatching Data Pool inserts from tape, but supersedes requirements S-DPL-42320 in OD_S4_01 in that inserts from archive cache will be processed in first-in first-out order.  The same applies to publishing request queued by Data Pool Ingest, since they reference granules that are already in the Data Pool, i.e., do not require archive access at all.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61160	The Data Pool Insert Service shall log raising and closing alerts, including the following: a. Identifying information for the resource or service, b. Type of alert and explanation. 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61170	The Data Pool Insert Service shall log suspension and resumption of queues and resources, including the following: a. Identification of the queue or resource. 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61180	The Data Pool Insert Service shall log the start and completion of archive read operations, including the following information: a. Source and target file and path names, b. File size, c. Deleted, d. Insert Request identification, e. Granule identification, f. Tape identification or indication that the read was from cache, g. Outcome.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61190	The Data Pool Insert Service shall log the start and completion of checksum calculations, including the following information: a. File path name, b. File size, c. Type of checksum, calculated checksum and  if applicable  original checksum d. Insert Request identification, e. Granule identification, f. Outcome.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61210	The Data Pool Insert Service shall log the start and completion of band extraction, including the following information: a. granule identification, b. esdt, c. Outcome.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61215	The Data Pool Insert Service shall log the start and completion of Data Pool registrations and publishing operations, including the following information: a. granule identification, b. esdt, c. any parameters passed into the registration or publishing operation d. any returned outcome information.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61216	The Data Pool Insert Service shall log the start and completion of its processing of a Data Pool insert request, including the following information: a. granule ID, b. esdt, c. request source, d. dispatch priority, e. other available action information. [NOTE: This replaces S-DPL-23000.  The remaining events listed in S-DPL-23000 are covered by S-DPL-61180 and S-DPL-61217.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61217	The Data Pool Insert Service shall log the occurrence of retriable and non-retriable errors, including the following information: a. granule identification b. type of error c. severity of errors, including whether retriable or not d. description of the error, including relevant details [NOTE: This replaces S-DPL-23000.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61218	The Data Pool Insert Service shall include the following information in its log entries: a. Unix Process ID b. type of event c. date and time of the event [NOTE: This replaces S-DPL-23200.  Other applicable information requirements for each event are enumerated in the logging requirements for each type of event.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61220	The Data Pool Insert Service shall be able to generate a performance log compatible with the ECS performance log format to provide information about the frequency and duration of the following events: a. Insert requests, separate by publish v. order-only and from tape v. from cache b. Archive access, separate by archive and cache v. tape c. Checksumming d. Deleted e. Band extraction f. Deleted g. DPIU execution h. database transactions (e.g., stored procedure calls), separate by type of stored procedure i. mutex locks, separate by locked resource 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61230	The Data Pool Insert Service shall recover after a fault such that: a. Insert requests will not be processed twice or their processing skipped. b. The state of insert requests at the time of the fault is recovered such that expensive insert steps that were completed at the time of the fault will not be started again (such as archive reads and checksum calculation) and no insert steps will be omitted.[NOTE: This is a design goal that is met if the completion of expensive steps is checkpointed; the step is not considered complete until it was successfully checkpointed.] c. No insert requests will fail or have their retry count incremented just because of the fault recovery. d. Insert requests that were active at the time of the fault will be activated before new work is started. e. Granules that have not completed insertion at the time of the fault will not be visible to external users until their insert is complete. f. The state of alerts and queues will be recovered, to the extent that they have not been changed by the operator during the outage caused by the fault. g. The state of resources will be recovered to the extent that they have not been changed by the operator during the outage caused by the fault. 	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61240	The Data Pool Insert Service shall be able to complete recovery from a fault including restarting Data Pool insert requests that were active at the time of the fault in less than 15 minutes with at least 50,000 insert requests currently queued and at least 100 active at the time of the fault.	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61250	The DPL CI shall provide a utility function which will remove stale granule locks (see S-DPL-60680) on a regular basis in time intervals no longer than the time after which such locks are considered stale. NOTE: That is, if a lock is considered stale after N hours, the frequency with which locks are checked must be at least every N hours.]	
DP_72_01	Data Pool Insert Enhancements	no data				S-DPL-61260	The DPL CI shall log the removal of stale locks and include the lock information (i.e., granule IDs, owner, last update) in the log.	
DP_72_01	Data Pool Insert Enhancements	no data				S-OMS-01610	The OMS CI shall raise an archive alert and suspend staging for an archive when it receives notification from the Data Pool Insert Service about having raised an alert for that archive, unless staging for that archive was suspended manually by the OMS operator.	
DP_72_01	Data Pool Insert Enhancements	no data				S-OMS-01615	The OMS CI shall close any open alert for an archive when it receives notification from the Data Pool Insert Service about having closed an alert for that archive, and resume staging for that archive unless staging for it was suspended manually by the OMS operator.	
DP_72_01	Data Pool Insert Enhancements	no data				S-OMS-01620	The OMS CI shall close any open alert for a Data Pool file system and resume staging to that file system when it receives notification from the Data Pool Insert Service about having closed an alert for that file system. [NOTE: This augments S-OMS-06545 in Ticket OD_S4_01. Note also that OMS does not support the manual suspension and resumption of staging to specific Data Pool file systems.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46110	Ingest of EDOS data shall comply with all L4 requirements in ticket DP_S6_01 that are not superseded by the L4 requirements specific to EDOS, that is, ticket DP_72_02.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46115	The Data Pool Ingest Service  shall not provide a Product Delivery Record Discrepancy (PDRD) to EDOS.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46120	The Data Pool Ingest Service shall check each polling location enabled for EDOS Data Pool ingest for signal files named for Product Delivery Records in accordance with the polling frequency and polling method configured for that polling location unless the polling for that location, host, or provider, or all Data Pool Ingest processing have been suspended.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46122	The Data Pool Ingest Service shall not count transfers of signal files against the corresponding FTP or local file transfer limits. [NOTE:  This extends the exclusions specified in S-DPL-18230 and S-DPL-18235 in Ticket DP_S6_01and shall be verified by design inspection.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46125	During initial validation, the Data Pool Ingest Service shall verify that the EDOS PDR conforms to specifications in ESDIS Document 423-ICD-EDOS/EGS.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46130	The Data Pool Ingest Service shall provide Product Acceptance Notifications (PANs)  for EDOS production data sets (PDS) per ESDIS Document 423-ICD-EDOS/EGS when all granules in an ingest request that needed to be archived in ECS have reached a state of Inserted or some terminal error state.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46135	The Data Pool Ingest Service shall place PANs in a DAAC directory for ftp access  by EDOS.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46140	The Data Pool Ingest Service shall provide only PANs that report errors  to EDOS. [EDOS does not want to receive successful PANs.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46145	The Data Pool Ingest Service shall include the EDOS Ground Message Header in the PAN it provides to EDOS in accordance with ESDIS document 423-ICD-EDOS/EGS.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46150	The Data Pool Ingest Service shall use the Error Dispositions provided in the ESDIS document 423-ICD-EDOS/EGS in the PAN messages returned to EDOS.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46153	The Data Pool Ingest Service shall recognize a retried EDOS PDR from the last modification time of the signal file for the PDR (as obtained by an ls l command).	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46155	If a PDR for an EDOS retried transfer is errored, the Data Pool Ingest Service shall indicate the retry status by incrementing the File Transfer Disposition in the PAN by 128, resulting in a Previous Resent Flag value of 1 per ESDIS document 423-ICD-EDOS/EGS.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46160	For EDOS, the Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) for the DAAC to receive successful PANs in a DAAC-resident directory different from the directory used for PANs that report errors. [EDOS does not want to receive successful PANs.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46165	The Data Pool Ingest Service shall reject an EDOS granule and return an  error disposition of 3 in the PAN if the checksum type and checksum value parameters are not present in the signal file for an EDOS data file [The EDOS-EGS ICD requires that EDOS provide checksums.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46170	The Data Pool Ingest Service shall reject an EDOS granule and return an error disposition of 3 in the PAN if the checksum type provided in a signal file is not on a list of ECS supported checksum algorithms.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46175	The Data Pool Ingest Service shall reject a granule and return an  error disposition of 3 in the PAN if the checksum type parameter is present in the signal file for an EDOS data file and the checksum value parameter is not.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46180	The Data Pool Ingest Service shall reject a granule and return an  error disposition of 3 in the PAN if the checksum value parameter is present in the signal file for an EDOS data file and the checksum type parameter is not.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46185	The Data Pool Ingest Service shall reject a granule and return an error disposition of 3 in the PAN if the checksum value parameter is present in the signal file for an EDOS data file and syntactically incorrect.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46190	The Data Pool Ingest Service shall make any error details related to preprocessing of ingested EDOS data (i.e., metadata extraction) available for display on the operator GUI as part of displaying the error details for the suspended granule or an alert.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46195	The Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) a provider as an EDOS provider using the following information in addition to that listed in ticket DP_S6_01, S-DPL-16110: a. DELETED, b. indication that the provider is EDOS and requires special handling as per ESDIS document 423-ICD-EDOS/EGS, including, for example, a special notification protocol and format and special file naming conventions.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46200	The Data Pool Ingest Service shall extract the metadata from the EDOS granule files and place them into a Data Pool compliant XML metadata file.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46205	The Data Pool Ingest GUI shall permit authorized (i.e., ingest control) operators to configure (i.e., enter and edit) the maximum number of concurrent metadata extraction preprocessing operations:	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46210	The Data Pool Ingest Service shall perform up to but not exceeding the configured maximum number of concurrent metadata extraction operations concurrently.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46215	The Data Pool Ingest Service shall be able to include in its performance log information about the frequency and duration of metadata extraction steps.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46220	The Data Pool Ingest Service shall include in its application log information about the start and completion of metadata extraction steps.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46225	The Data Pool CI shall permit the configuration of ingest data type templates by development. NOTE: The expectation is that this information is configuration management and configured in the database. The configuration may be via database scripts employing SQL commands to add, modify and delete the corresponding information.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46230	The Data Pool CI shall permit the configuration of ingest file type templates by development. [NOTE: The expectation is that this information is configuration management and configured in the database. The configuration may be via database scripts employing SQL commands to add, modify and delete the corresponding information.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46235	The Data Pool CI shall permit the configuration of source MCF information by development. [NOTE: The expectation is that this information is configuration management and configured in the database. The configuration may be via database scripts employing SQL commands to add, modify and delete the corresponding information.]	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46240	The Data Pool CI shall be able to use ingest data type templates configured in the INGST CI.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46245	The Data Pool CI shall be able to use ingest file type templates configured in the INGST CI.	
DP_72_02	Ingest of Level 0 Data from EDOS into the Data Pool	no data				S-DPL-46250	The Data Pool CI shall be able to use source MCF information configured in the INGST CI.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46410	Ingest of ASTER L1A and Browse data shall comply with all L4 requirements in ticket DP_S6_01 that are not superseded by the L4 requirements specific to the ASTER interface, that is, ticket DP_72_03.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46420	During initial validation of an ASTER L1A PDR, the Data Pool Ingest Service shall verify the contents of the PDR against the specifications in version  TBD  of ESDIS Document 423-41-58, ICD between ECS and the LP DAAC.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46430	The Data Pool Ingest Service shall notify the ASTER L1A provider via the configured notification method if an ingest request fails initial validation, collecting and reporting all detected errors using a short or long Product Delivery Record Discrepancy (PDRD) in accordance with version  TBD  of ESDIS Document 423-41-58, ICD between ECS and the LP DAAC.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46440	The Data Pool Ingest Service shall notify the ASTER L1A provider using a short or long Product Acceptance Notification (PAN) constructed and formatted in accordance with version  TBD  of ESDIS document  423-41-58, ICD between ECS and the LP DAAC and using the configured notification method when all granules in an ingest request that needed to be archived in ECS have reached a state of Inserted or some terminal error state.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46450	The Data Pool Ingest Service shall extract the granule metadata from the ASTER L1A PDR and granule files and place them into a Data Pool compliant XML metadata file. [NOTE: The information that must be extracted is specified by configuration information.]	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46460	The Data Pool Ingest Service shall include any metadata extracted from the PDR and granule file for ASTER in metadata validation and insert via the Science Data Server. [NOTE: The information that must be extracted is specified by configuration information.]	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46470	The Data Pool Ingest GUI shall permit authorized (i.e., ingest tuning) operators to configure (i.e., enter and edit) the maximum number of concurrent metadata extraction preprocessing operations.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46480	The Data Pool Ingest Service shall make any error details related to preprocessing of ingested ASTER data (i.e., metadata extraction) available for display on the operator GUI as part of displaying the error details for the suspended granule or an alert.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46490	The Data Pool Ingest Service shall perform up to but not exceeding the configured maximum number of concurrent metadata extraction operations concurrently (see S-DPL-46470).	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46500	The Data Pool Ingest Service shall be able to include in its performance log information about the frequency and duration of metadata extraction steps.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46510	The Data Pool Ingest Service shall include in its application log information about the start and completion of metadata extraction steps.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46520	The Data Pool CI shall permit the configuration of ingest data type template by development.  [Note: The expectation is that this information is configuration management and configured in the database.  The configuration may be via database scripts employing SQL commands to add, modify and delete the corresponding information.]	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46530	The Data Pool CI shall permit the configuration of ingest file type templates by development.  [Note: The expectation is that this information is configuration management and configured in the database. The configuration may be via database scripts employing SQL commands to add, modify and delete the corresponding information.]	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46540	The Data Pool CI shall permit the configuration of source MCF information by development.  [Note: The expectation is that this information is configuration management and configured in the database. The configuration may be via database scripts employing SQL commands to add, modify and delete the corresponding information.]	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46550	The Data Pool CI shall be able to use ingest data type templates configured in the INGST CI.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46560	The Data Pool CI shall be able to use ingest file type templates configured in the INGST CI.	
DP_72_03	Ingest of ASTER L1A and Browse into Data Pool	no data				S-DPL-46570	The Data Pool CI shall be able to use source MCF information configured in the INGST CI.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46630	When ingesting EMOS Detailed Activity Schedule files, the Data Pool Ingest Service shall comply with all L4 requirements in ticket DP_S6_01 that are not superseded by the L4 requirements specific to the ECS- EMOS interface in Ticket DP_72_04.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46635	When ingesting EMOS detailed activity schedule files, the Data Pool Ingest Service shall comply with the polling without delivery record interface specifications in ICD 423-41-63, ICD between EMOS and the SDPS. [NOTE: No PDRD or PAN is supplied.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46640	The Data Pool Ingest Service shall extract the granule metadata from the EMOS Detailed Activity Schedule and place it into a Data Pool compliant XML metadata file. [NOTE: The information that must be extracted is specified by configuration information.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46645	The Data Pool Ingest Service shall include any metadata extracted from the EMOS Detailed Activity Schedule in metadata validation and insert via the Science Data Server. [NOTE: The information that must be extracted is specified by configuration information.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46660	The Data Pool Ingest Service shall make any error details related to preprocessing of ingested EMOS Detailed Activity Schedule  files  (i.e., metadata extraction) available for display on the operator GUI as part of displaying the error details for the suspended granule or an alert	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46666	The Data Pool Ingest GUI shall permit authorized operators to configure (i.e., enter and edit) whether a data provider uses a polling with delivery record or polling without delivery record mechanism.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46669	The Data Pool Ingest GUI shall require that if the transfer type of a Polling without Delivery Record provider is ftp, the polling method for all polling locations for that provider is configured to ftp.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46671	If a data provider is configured to support polling without delivery record, the Data Pool Ingest GUI shall require authorized operators to configure the shortname and version id of the data type that will be ingested for that data provider using the polling without delivery record mechanism.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46676	The Data Pool Ingest GUI shall permit authorized operators to edit the shortname and version id of the data type that will be ingested for a data provider which uses the polling without delivery record mechanism.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46681	If a data provider is configured for polling without a delivery record, the Data Pool Ingest Service shall obtain the shortname and version id of the granules ingested from that provider from the data provider configuration information entered on the Data Pool Ingest GUI.	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46686	The Data Pool Ingest GUI shall disable configuration of the following  parameters for providers which use the polling without delivery record mechanism: a. whether the provider must supply a checksum with each science file, b. the percentage of files from that provider whose checksum must be verified during ingest as an integer number between 0 and 100, c. a valid notification method to be used to notify that provider of ingest errors and completed ingest operations,	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-46691	The Data Pool Ingest Service shall not process an EMOS data file that already was processed by the INGST CI and shall process EMOS data files that were not processed by the INGST CI, and vice versa. [NOTE: This is intended to support transition from INGST to Data Pool Ingest and vice versa without processing an EMOS data file more than once.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47010	The Data Pool Ingest Service shall not process an EDOS Expedited request that already was processed by the INGST CI and shall process EDOS Expedited requests that were not processed by the INGST CI, and vice versa. [NOTE: This is intended to support transition from INGST to Data Pool Ingest and vice versa without processing an EDOS Expedited request more than once.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47015	Ingest of EDOS Level 0 Expedited Data Sets shall comply with all L4 requirements in ticket DP_S6_01 that are not superseded by the L4 requirements specific to Expedited Data Sets, that is, in ticket DP_72_04	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47020	The Data Pool Ingest Service shall check each polling location enabled for EDOS Data Pool ingest for signal files named for Expedited Data Set Delivery Records in accordance with the polling frequency and polling method configured for that polling location unless the polling for that location, host, or provider, or all Data Pool Ingest processing have been suspended. [Replaces S-DPL-46120 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47025	During initial validation, the Data Pool Ingest Service shall verify that the EDOS EDS Delivery Record (EDR) conforms to specifications in ESDIS Document 423-ICD-EDOS/EGS  TBD . [Replaces S-DPL-46125 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47030	The Data Pool Ingest Service shall provide EDS Acceptance Notifications (EANs) for EDOS Expedited Data Sets (EDS) per ESDIS Document 423-ICD-EDOS/EGS  TBD  when all granules in an ingest request that needed to be archived in ECS have reached a state of Inserted or some terminal error state. [Replaces S-DPL-46130 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47035	The Data Pool Ingest Service shall place EANs in a DAAC directory for ftp access by EDOS. [Replaces S-DPL-46135 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47040	The Data Pool Ingest Service shall provide only EANs that report errors to EDOS. [Replaces S-DPL-46140 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47045	The Data Pool Ingest Service shall include the EDOS Ground Message Header in the EAN it provides to EDOS in accordance with ESDIS document 423-ICD-EDOS/EGS  TBD . [Replaces S-DPL-46145  for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47050	The Data Pool Ingest Service shall use the Error Dispositions provided in the ESDIS document 423-ICD-EDOS/EGS (TBD) in the EAN messages returned to EDOS. [Replaces S-DPL-46150 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47055	The Data Pool Ingest Service shall recognize a retried EDOS EDR from the last modification time of the signal file for the EDR (as obtained by an ls l command). [Replaces S-DPL-46153 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47060	If an EDR for an EDOS retried transfer is errored, the Data Pool Ingest Service shall indicate the retry status by incrementing the File Transfer Disposition in the EAN by 128, resulting in a Previous Resent Flag value of 1 per ESDIS document 423-ICD-EDOS/EGS  TBD . [Replaces S-DPL-46155 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47065	The Data Pool Ingest Service shall place errored EANs for pickup by EDOS in the same directory as errored PANs in accordance with ESDIS document 423-ICD-EDOS/EGS  TBD .	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47070	For EDOS, the Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) for the DAAC to receive successful EANs in a DAAC-resident directory different from the directory used for PANs and EANs that report errors. [Replaces S-DPL-46160 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47075	The Data Pool Ingest Service shall reject an EDOS expedited granule and return an error disposition of 3 in the EAN if the checksum type and checksum value parameters are not present in the signal file for an EDOS data file  [Replaces S-DPL-46165 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47080	The Data Pool Ingest Service shall reject an EDOS expedited granule and return an error disposition of 3 in the EAN if the checksum type provided in a signal file is not on a list of ECS supported checksum algorithms. [Replaces S-DPL-46170 for expedited data sets.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47085	The Data Pool Ingest Service shall reject an EDOS expedited granule and return an error disposition of 3 in the EAN if the checksum type parameter is present in the signal file for an EDOS expedited data file and the checksum value parameter is not. [Replaces S-DPL-46175 for expedited data.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47090	The Data Pool Ingest Service shall reject an expedited granule and return an error disposition of 3 in the EAN if the checksum value parameter is present in the signal file for an EDOS expedited data file and the checksum type parameter is not. [Replaces S-DPL-46180 for expedited data.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47095	The Data Pool Ingest Service shall reject an expedited granule and return an error disposition of 3 in the EAN if the checksum value parameter is present in the signal file for an EDOS expedited data file and syntactically incorrect. [Replaces S-DPL-46185 for expedited data.]	
DP_72_04	Data Pool Ingest of Data at the ASDC DAAC	no data				S-DPL-47100	The Data Pool Ingest Service shall assign the highest possible processing priority to ingest requests for EDOS expedited data, regardless of the default priority configured for the EDOS expedited data provider.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46800	The Data Pool Service shall support the capability to represent the public granules in the MISBR ESDT as both science granules and browse granules with discrete expiration settings. Note:  the representation will not take place if the specified ESDT is in the hidden Data Pool and will not be published.  ESDT publications are controlled either by configuring public ESDTs in the DPL Ingest GUI, setting subscriptions with Data Pool Insert actions or by  using the Batch Insert Utility to insert historical data into the Data Pool.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46810	The Data Pool Service shall support soft links in the Data Pool file system from the MISR Level 1 and Level 2 science granules storage area to the public Data Pool browse representation of the MISBR granules.  The supported science ESDTs should be configurable; the default set is identified as Level 1 and Level 2 in Table 1, ticket DP_72_05.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46820	The Data Pool Insert Service shall maintain cross-reference information between each public Data Pool browse representation of a MISBR granule and all corresponding MISR Level 1 and Level 2 science granules in the Data Pool database.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46830	The Data Pool Insert Service shall link the public DPL browse representation of a MISBR granule with public MISR Level 1 science granule(s) based upon the following matching attributes:  SP_AM_MISR_ProductVersion product specific attribute value - granule temporal coverage (the interval between BeginningDateTime and EndingDateTime values for the associated MISR Level 1 science granules must intersect the BeginningDateTime and EndingDateTime interval for the MISBR granule)  - if the MISBR granule has a cameraId of AN, it must be associated to all MISR Level 1 science granules that also have a cameraId of AN.  - if the MISBR granule has a cameraId that is not AN, it must be associated to all MISR Level 1 science granules that have a matching cameraId. Note: this requirement covers the situation when the MISBR granule is published after the publication of its associated MISR Level 1 granule(s) and it must be associated with the MISR Level 1 science granule(s) that are already in the public Data Pool.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46840	The Data Pool Insert Service shall link a public DPL MISR Level 1 science granule with the public browse representation of a MISBR granule based upon the following matching attributes:  - SP_AM_MISR_ProductVersion product specific attribute value  - granule temporal coverage (the interval between BeginningDateTime and EndingDateTime values for the associated MISBR must intersect the BeginningDateTime and EndingDateTime interval for the MISR Level 1 granule)  - if the current MISR Level 1 granule has a cameraId, the linked MISBR browse must have the same cameraId  - Note:  this requirement covers the situation when the MISR Level 1 science granule is published after the publication of its associated MISBR granule.  In this case the MISBR granule to which the links are established must be published as a Browse granule in the Data Pool.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46850	The Data Pool Insert Service shall insert a public DPL MISR Level 1 science granule without a browse linkage in the event that no matching MISBR granules can be identified by the above criteria.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46860	The Data Pool Insert Service shall link the public DPL browse representation of a MISBR granule with public MISR Level 2 science granule(s) based upon the following matching attributes:  - granule temporal coverage (the interval between BeginningDateTime and EndingDateTime values for the associated MISR Level 2 granules must intersect the BeginningDateTime and EndingDateTime interval for the MISBR  granule)  - cameraId of AN for the MISBR only (the cameraId for the correlated MISR Level 2 is irrelevant) Note: this requirement covers the situation when the MISBR granule is published after the publication of its associated MISR Level 2 granule(s) and it must be associated with the MISR Level 2 science granule(s) that are already in the public Data Pool.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46870	The Data Pool Insert Service shall link a public DPL MISR Level 2 science granule with the public DPL browse representation of a MISBR granule based upon the following matching attributes:  - granule temporal coverage (the interval between BeginningDateTime and EndingDateTime values for the associated MISBR must intersect the BeginningDateTime and EndingDateTime interval for the MISR Level 2 granule)  - the MISBR granule must have a cameraId of AN, regardless of the cameraId value of the current MISR Level 2 Note: this requirement covers the situation when the MISR Level 2 science granule is published after the publication of its associated MISBR granule.  In this case the MISBR granule to which the links are established must be published as a Browse granule in the Data Pool.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46880	The Data Pool Insert Service shall insert a public DPL MISR Level 2 science granule without a browse linkage in the event that no matching MISBR granules can be identified by the above criteria.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46890	The Data Pool Insert Service shall link public DPL MISR Level 1 and Level 2 science granules with the most recently inserted MISBR granule in the event that multiple MISBR granules are identified using the specific linkage criteria defined for each type of MISR science granule. Note: if at the time a newer MISBR granule is published its associated MISR Level 1 and Level 2 granules are already in the public DPL and are linked to another MISBR browse granule representation, the old links will be preserved and NO new links will be added.  If the new MISRB granule replaces an older MISBR granule, only the science representation is replaced, the old links are preserved and the new links are added.	
DP_72_05	Support for MISR Browse Linkages in Release 7.20	no data				S-DPL-46900	The test data set with the approximate volume of 0.3TB consisting of 2614 granules should be ingested into the hidden Data Pool and published in under 6 hours. Note:  the 24 hours behavior can be extrapolated from the 6h run.	
DP_7F_01	On-Line Archive	no data				S-AIM-00300	The AIM CI shall identify the list of granules which it flags as logically deleted (i.e., deleteEffectiveDate changed from NULL to non-NULL), or hidden from normal users (i.e., DeleteFromArchive flag changed to H) to the DPL CI, using the agreed interface for this purpose as per S-DPL-08060.	
DP_7F_01	On-Line Archive	no data				S-AIM-00310	The AIM CI shall identify the list of granules which it flags as undeleted (deleteEffectiveDate changed from non-NULL to NULL) or unhidden from normal users (i.e., DeleteFromArchive flag changed from H to a different value) to the DPL CI, using the agreed interface for this purpose as per S-DPL-08080.	
DP_7F_01	On-Line Archive	no data				S-AIM-00320	The AIM CI shall identify the list of granules which it physically deletes from its inventory or flags as deleted from archive (i.e., DeleteFromArchive changed to Y) to the DPL CI, using the agreed interface for this purpose as per S-DPL-08120.	
DP_7F_01	On-Line Archive	no data				S-AIM-00330	The AIM CI shall provide a tape archive repair function that allows DAAC staff to replace the files of individual science granules in the tape archive with their copy from the Data Pool On-Line Archive.	
DP_7F_01	On-Line Archive	no data				S-AIM-00340	The AIM CI shall provide a tape archive bulk repair function that allows DAAC staff to replace science granule files on a specified tape volume with their copies from the Data Pool On-Line Archive.	
DP_7F_01	On-Line Archive	no data				S-AIM-00350	When repairing the copy of a file in the tape archive from its copy in the Data Pool On-Line Archive, the AIM CI verify the checksum of the file and fail the tape archive repair for the corresponding granule if checksum verification fails.	
DP_7F_01	On-Line Archive	no data				S-AIM-00360	The AIM CI shall log each file that failed checksum verification during a tape archive repair.	
DP_7F_01	On-Line Archive	no data				S-AIM-00370	The AIM CI shall allow DAAC staff to invoke its tape archive repair functions via the command line.	
DP_7F_01	On-Line Archive	no data				S-AIM-00380	The AIM CI shall allow DAAC staff to limit the number of concurrent archive writes that it will issue during tape archive bulk repair.	
DP_7F_01	On-Line Archive	no data				S-AIM-00390	The AIM CI shall allow DAAC staff to identify the hosts on which it will perform checksumming operations and limit the number of concurrent checksumming operations it performs on each host during tape archive bulk repair.	
DP_7F_01	On-Line Archive	no data				S-AIM-00400	The AIM CI shall allow DAAC staff to perform bulk tape archive repairs for more than one tape volume in parallel.	
DP_7F_01	On-Line Archive	no data				S-AIM-00410	The AIM CI shall be able to perform bulk repair of a tape volume at a rate of no less than 100 MB/sec in the absence of concurrent workload.	
DP_7F_01	On-Line Archive	no data				S-BGT-01510	The BMGT CI shall export the results of publishing and un-publishing operations.	
DP_7F_01	On-Line Archive	no data				S-BGT-01520	The BMGT CI shall export the results of On-Line Archive repair functions if they affect the URL of a public ECS granule.	
DP_7F_01	On-Line Archive	no data				S-DPL-08010	The DPL CI shall consider all ECS granules that reside in the Data Pool and that are recorded in the ECS inventory maintained by the AIM CI to be part of the Data Pool On-Line Archive, with the following exceptions:  Browse granules shall not be considered part of the Data Pool On-line Archive. Granules that are identified as deleted from archive (i.e., DeleteFromArchive set to Y) in the AIM CI inventory shall not be considered part of the Data Pool On-line Archive.  [NOTE: Granules registered in the AIM inventory may belong to collections that are not defined to the Data Pool.  Those granules will not be part of the Data Pool On-Line Archive, however, they also cannot be inserted into the Data Pool, and cannot be staged and or distributed by ECS software components.  Such granules are generally inaccessible, except perhaps to DAAC unique software.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08020	The DPL CI shall not remove granules from the Data Pool that are part of the Data Pool On-Line Archive as per S-DPL-08010, except as needed in the context of On-Line Archive Repair Functions and when DAAC staff explicitly requests their removal via the Data Pool Cleanup (see S-DPL-08530). [NOTE: In essence, ECS granules other than Browse are not deleted from the Data Pool unless they are first physically deleted or flagged as deleted from archive in the AIM CI inventory.  The exceptions refer to manual deletions performed by the DAAC staff and the case when a Data Pool On-Line Archive repair function needs to remove an existing granule in the course of replacing it with a fresh copy of the same granule.] 	
DP_7F_01	On-Line Archive	no data				S-DPL-08030	The DPL CI shall not remove the ECS granules from the Data Pool whose cleanup is requested by OMS and which are part of the on-line archive as per S-DPL-08010. [NOTE: The requirement is included for clarification only, since S-DPL-08020 prohibits this already.  It does apply also to Data Pool orphans and phantoms that prevent the OMS CI from fulfilling orders unless they are removed.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08040	The Data Pool Ingest Service shall not trigger the cleanup of any ECS granules it has successfully ingested. [NOTE: This replaces requirement S-DPL-18455. The requirement is included for clarification only, since S-DPL-08020 prohibits this already.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08050	The DPL CI shall not make granules public that are currently flagged as logically deleted (i.e., have a non-NULL deleteEffectiveDate), deleted from archive (i.e.,  DeleteFromArchive set to Y), or hidden from normal users (i.e., DeleteFromArchive set to H) in the AIM CI inventory.	
DP_7F_01	On-Line Archive	no data				S-DPL-08060	The DPL CI shall provide an interface to accept a list of granules which the AIM CI flags as logically deleted (i.e., DeleteFromArchive changed to Y) or hidden from normal users (i.e., deleteEffectiveDate changed from a NULL to a non-NULL value). [NOTE: The interface can be via a list of entries in a database table.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08070	The DPL CI shall un-publish granules which the AIM CI identifies as logically deleted or hidden from normal users, if these granules are currently public. [The method by which unpublishing is accomplished is left to the design; however, this AIM output must either be processed automatically, or it must be possible to process this AIM output either via cron or as an additional step in the operational sequence of the corresponding AIM granule deletion steps.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08080	The DPL CI shall provide an interface to accept the list of granules which the AIM CI un-deletes or un-hides. [NOTE: The interface can be via a list of entries in a database table.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08090	The DPL CI shall re-publish granules which the AIM CI identifies as undeleted (i.e., a non-NULL deleteEffectiveDate was cleared) or unhidden (i.e., DeleteFromArchive was changed, previous value was H)  if the granules are not ineligible for publishing as per S-DPL-08050 and belong to a collection which is configured for automatic granule publishing during ingest). [NOTE: The publishing attempt will fail if there is a collision with another public granule and granule replacement is turned off or fails because of other granule replacement conditions, such as the version of the granule that is public is more recent.  The method by which the re-publishing is accomplished is left to the design; however, it must be possible to process this AIM input either via cron or as an additional step in the operational sequence of AIM granule un-deletion steps.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08100	When the Data Pool Insert Service replaces an existing public ECS granule that is part of the Data Pool On-line Archive as per S-DPL-08010 (i.e., because granule replacement is enabled for that collection), the Data Pool Insert Service shall un-publish the granule (i.e., leave it in the hidden Data Pool and not simply remove it from the Data Pool). [NOTE: This augments requirements S-DPL-23520, 23522, 75600, 75602, 75604, 75606, 75608, and 75610.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08110	When the Data Pool Insert Service fails the publication of an ECS granule that is part of the Data Pool On-line Archive as per S-DPL-08010, the Data Pool Insert Service shall leave the granule in the On-Line Archive, i.e., in the hidden Data Pool.	
DP_7F_01	On-Line Archive	no data				S-DPL-08120	The DPL CI shall provide an interface to accept the list of granules which the AIM CI physically deletes from its inventory or flags as deleted from archive (i.e., DeleteFromArchive was changed to Y). [NOTE: The interface can be via a list of entries in a database table.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08130	The DPL CI shall remove the granules from the Data Pool inventory and Data Pool disks when the AIM CI identifies these granules as deleted from archive (i.e., DeleteFromArchive was changed to Y) or physically deleted from its inventory, regardless of whether the granules are currently public or not. [NOTE: This replaces S-DPL-15020. The method by which the removal is accomplished is left to the design; however, this AIM output must either be processed automatically, or it must be possible to process this AIM output either via cron or as an additional step in the operational sequence of the AIM granule deletion cleanup steps.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08140	The DPL CI shall remove public Browse granules from the Data Pool inventory and Data Pool disks if the last science granule that references it is unpublished or removed from the Data Pool entirely. [NOTE:  This extends the corresponding Data Pool cleanup requirement S-DPL-13130.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08150	The DPL CI shall provide an un-publish function which will cause a granule that is currently publicly accessible in the Data Pool to be no longer accessible via the Data Pool Web Access Service or the Data Pool FTP Service, but remain accessible on the Data Pool disks otherwise, for example, via the OMS CI or by a tape archive repair function.	
DP_7F_01	On-Line Archive	no data				S-DPL-08160	The DPL CI shall provide an inventory validation function. [NOTE: This rewords and replaces S-DPL-60010.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08170	DAAC staff shall be able to invoke Data Pool Inventory Validation via command line. [NOTE: This replaces S-DPL-60020, S-DPL-60042, S-DPL-60080, S-DPL-60090, and S-DPL-60240 which require that the validation function be invoked by the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08180	The Data Pool Inventory Validation shall compare the inventories maintained by the DPL and AIM CI for non-Browse granules if requested to do so via command line options, and identify the following discrepancies between the two inventories:  Collections that are not defined in the Data Pool inventory and for which granules exist in the AIM maintained inventory. ECS Granules that are in the Data Pool inventory but not in the AIM maintained inventory. Granules in the AIM maintained inventory that do not belong to collections specified in condition a. and that are not present in the Data Pool inventory. If so requested explicitly via command line options, suppress reporting granules in the AIM inventory that are logically deleted (i.e., have a non-NULL deleteEffectiveDate) but are not present in the Data Pool inventory. If so requested explicitly via command line options, suppress reporting granules in the AIM inventory that are deleted from archive (i.e.,  DeleteFromArchive set to Y) but are not present in the Data Pool inventory. Granules that are public in the Data Pool but are not eligible to be public as per S-DPL-08050. Granules that are in public collections and are eligible to be public as per S-DPL-08050, but are currently in the hidden Data Pool area. Discrepancies in the checksum value for a granule where the granule has non-null checksum value in both inventories. Discrepancies in the checksum algorithm value for a granule where the granule has a non-null checksum algorithm value in both inventories.  	
DP_7F_01	On-Line Archive	no data				S-DPL-08190	The Data Pool Inventory Validation shall log each identified discrepancy between the DPL and AIM inventories.	
DP_7F_01	On-Line Archive	no data				S-DPL-08200	The Data Pool Inventory Validation shall include the status of the corresponding granule in the AIM inventory (i.e., logically deleted, deleted from archive, hidden) and the time the granule was inserted into the ECS inventory when logging discrepancies as per S-DPL-08180c, d, e, f and g. [NOTE: For example, the inventory validation may include the value for the DeleteFromArchive flag and the deleteEffectiveDate in the log.] 	
DP_7F_01	On-Line Archive	no data				S-DPL-08205	The Data Pool Inventory Validation shall include the checksum information of the corresponding granules in the DPL and AIM CI inventories when logging discrepancies as per S-DPL-08180h and i.	
DP_7F_01	On-Line Archive	no data				S-DPL-08210	The Data Pool Inventory Validation shall report the discrepancies between the DPL and AIM inventories that it identifies in an output file such that the output can be used as input to the utilities needed to repair the discrepancies. [NOTE: The utilities may include, for example: Data Pool Cleanup (to repair condition b.), Data Pool Batch Insert (to repair condition c.), a Data Pool un-publish utility (to repair condition f.), and a Data Pool publishing function (which might be performed by the Data Pool batch Insert Utility) to repair condition g. Multiple output files may need to be generated if the utilities needed for the repair do not accept compatible input formats.]  	
DP_7F_01	On-Line Archive	no data				S-DPL-08220	The Data Pool Inventory Validation shall allow DAAC staff to specify the location of the output file(s) reporting the discrepancies between the DPL and AIM inventories.	
DP_7F_01	On-Line Archive	no data				S-DPL-08230	The Data Pool Inventory Validation shall check the syntax of the command line parameters. [NOTE:  The replaces S-DPL-60030 which requires this to be performed by the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08240	The Data Pool Inventory Validation shall display the error and the correct command line syntax if the command line parameters fail the syntax check. [NOTE: This replaces S-DPL-60035 which requires this to be performed by the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08250	The Data Pool Inventory Validation shall accept an optional command line parameter that specifies that orphan checking shall be performed. [NOTE: This replaces S-DPL-60040 which requires the parameters to be accepted by the Data Pool Cleanup Utility. Orphan checking itself is an existing capability and this ticket only lists requirements that changed due to the On-Line Archive.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08260	The Data Pool Inventory Validation shall accept an optional command line parameter that specifies the maximum orphan age in days of the files to be included in the orphan check. [NOTE: This replaces S-DPL-60050 which requires the parameters to be accepted by the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08270	The Data Pool Inventory Validation shall verify that the maximum orphan age parameter specified on the command line is not less than three days. [NOTE: This replaces S-DPL-60055 which requires this to be performed by the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08280	The Data Pool Inventory Validation shall accept an optional command line parameter that specifies that phantom checking shall be performed. [NOTE: This replaces S-DPL-60060 which requires the parameters to be accepted by the Data Pool Cleanup Utility. Phantom checking itself is an existing capability and this ticket only lists requirements that changed due to the On-Line Archive.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08290	The Data Pool Inventory Validation shall accept an optional command line parameter via which the operator can specify up to ten (10) data pool collection groups to be included in the orphan and phantom check. [NOTE: This replaces S-DPL-60070 which requires the parameters to be accepted by the Data Pool Cleanup Utility. Note the exception for Link Checking in S-DPL-08415.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08300	The Data Pool Inventory Validation shall verify that the collection groups specified on the command line are valid Data Pool collection groups. [NOTE: This replaces S-DPL-60075 which requires this to be performed by the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08310	The Data Pool Inventory Validation shall report orphaned files but not remove them from the data pool disks automatically. [NOTE: This replaces S-DPL-60044, S-DPL-60130, S-DPL-60210 which provide for automatic removal of orphans except if nofix is specified.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08320	The Data Pool Inventory Validation shall report orphaned files in an output file such that the output can be used as input to the utility that can repair orphans. [NOTE: The utility is part of the Data Pool On-Line Archive Repair function defined in other requirements.  Orphaned files are repaired by re-establishing the Data Pool inventory entries describing the related granule and its files. Typically, these granules would also be reported as discrepancies when the Data Pool Inventory Validation compares the Data Pool and AIM inventories.  However, the corresponding granules also may no longer be in the AIM inventory, i.e., the files should have been cleaned up during the deletion of these granules from the Data Pool inventory but that clean-up failed for some reason.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08330	The Data Pool Inventory Validation shall allow DAAC staff to specify the location of the output file containing the list of orphaned Data Pool files.	
DP_7F_01	On-Line Archive	no data				S-DPL-08340	The Data Pool Inventory Validation shall report phantom granules but not remove them from the Data Pool inventory. [NOTE: These Data Pool inventory entries will be needed by the Data Pool On-line Archive Repair Function.  This replaces S-DPL-60044, S-DPL-60160, and S-DPL-60210 which provide for automatic removal of phantoms.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08350	The Data Pool Inventory Validation shall report phantom granules in an output file such that the output can be used as input to the utility that can repair them. [NOTE: The utility is part of the Data Pool On-Line Archive Repair function defined in other requirements.  Phantom granules are repaired by restoring any missing files from the tape archive and re-creating any missing Browse links. Typically, these granules would not be reported when the Data Pool inventory validation function compares the Data Pool and AIM inventories.  However it is conceivable that the granule was intended to be deleted and the deletion of the files and links succeeded, but the removal of the inventory entries failed for some reason, in which case the DPL-AIM inventory comparison would report the granule as a discrepancy.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08360	The Data Pool Inventory Validation shall allow DAAC staff to specify the location of the output file containing the list of phantom Data Pool granules.	
DP_7F_01	On-Line Archive	no data				S-DPL-08370	The Data Pool Inventory Validation shall include the pathname of all orphaned files in the corresponding log entry.	
DP_7F_01	On-Line Archive	no data				S-DPL-08380	In the absence of concurrent workload, the Data Pool Inventory Validation shall be able to perform orphan and phantom checking at the rate of at least 1,000,000 files per hour. [NOTE: This replaces S-DPL-60250.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08390	In the absence of concurrent workload, the Data Pool Inventory Validation shall be able to compare AIM and DPL inventories at the rate of at least 1,000,000 granules per hour.	
DP_7F_01	On-Line Archive	no data				S-DPL-08400	If Data Pool Inventory Validation is interrupted by a fault, it must be possible to restart it and resume the interrupted validation, doing so without producing duplicate entries in the output files. [NOTE: This replaces S-DPL-60260. It is desirable for Long-running utilities to be able to resume from a check-point to reduce the run time penalty of a restart, to the extent that this is possible without incurring significant performance penalties for a normal, non-interrupted run.  It's acceptable for a restart to require the presence of a command line option requesting restart.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08410	The Data Pool Inventory Validation shall accept an optional command line parameter that specifies that link verification (i.e., verification of links in the Data Pool area) shall be performed.	
DP_7F_01	On-Line Archive	no data				S-DPL-08415	The Data Pool Inventory Validation shall accept an optional command line parameter that specifies the public or hidden Data Pool directory tree for which link verification shall be performed. [NOTE: This overrides S-DPL-08290 for link checking.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08420	When performing link verification, the Data Pool Inventory Validation shall identify invalid browse links and invalid links in the hidden Data Pool directories (i.e., links whose targets do not exist). [NOTE: This replaces S-DPL-14535 which specifies that hidden granules be ignored by Data Pool validation.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08430	The Data Pool Inventory Validation shall report invalid links but not remove them from the data pool disks automatically.	
DP_7F_01	On-Line Archive	no data				S-DPL-08440	The Data Pool Inventory Validation shall report invalid links in an output file such that the file can be used as input to the Data Pool On-line Archive Repair Function.	
DP_7F_01	On-Line Archive	no data				S-DPL-08450	The Data Pool Inventory Validation shall allow DAAC staff to specify the location of the output file containing the list of invalid links. [NOTE: It is assumed that invalid links will be removed via normal Unix deletion by DAAC staff.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08455	When allowing the specification of a location for the output file that reports the results of an inventory validation, the Data Pool Inventory Validation functions shall accept a pathname relative to the standard path for validation results. [NOTE: The path standard will be established and documented during the design.]  	
DP_7F_01	On-Line Archive	no data				S-DPL-08460	The Data Pool Inventory Validation shall log invalid links.	
DP_7F_01	On-Line Archive	no data				S-DPL-08470	In the absence of concurrent workload, the Data Pool Inventory Validation shall be able to validate links at a rate of no less than 180,000 links per hour.	
DP_7F_01	On-Line Archive	no data				S-DPL-08480	DELETED	
DP_7F_01	On-Line Archive	no data				S-DPL-08490	DELETED	
DP_7F_01	On-Line Archive	no data				S-DPL-08500	DELETED	
DP_7F_01	On-Line Archive	no data				S-DPL-08510	DELETED	
DP_7F_01	On-Line Archive	no data				S-DPL-08520	DELETED	
DP_7F_01	On-Line Archive	no data				S-DPL-08530	The Data Pool Cleanup shall not remove ECS granules from the Data Pool that belong to the on-line archive as per S-DPL-08010, except under the following circumstances:  the granules to be removed were individually identified on the command line or an input file as per requirement S-DPL-13094. [NOTE: un-deletion of these granules in the AIM inventory would not restore them to the Data Pool automatically.] the granules were identified to the DPL CI via the corresponding DPL  AIM interface as physically deleted or flagged as deleted from the archive in the AIM inventory.  [NOTE: This requirement modifies S-DPL-13094, S-DPL-13100, S-DPL-13110, and S-DPL-13120].	
DP_7F_01	On-Line Archive	no data				S-DPL-08540	The Data Pool Cleanup shall remove granules whose granule IDs are individually listed as per S-DPL-13094 regardless of whether these granules are currently public or not.	
DP_7F_01	On-Line Archive	no data				S-DPL-08550	The Data Pool Cleanup service shall skip the cleanup of a granule that is currently in use by the OMS CI and automatically remove such granules on the next cleanup run that occurs after OMS relinquishes use of that granule.	
DP_7F_01	On-Line Archive	no data				S-DPL-08560	The Data Pool Cleanup shall remove all temporary files from the data pool disks whose age exceeds the maximum orphan age unless fixing discrepancies was suppressed. [NOTE: This updates an existing requirement to ensure that this function remains with the Data Pool Cleanup Utility, replacing S-DPL-60180.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08570	The Data Pool Cleanup shall log the temporary files whose age exceeds the maximum orphan age. [NOTE: This re-assigns this function to the Data Pool Cleanup utility, replacing S-DPL-60185.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08580	The Data Pool Cleanup shall log at completion the total number of temporary files that exceeded the maximum orphan age. [NOTE: This updates an existing requirement to ensure that this function remains with the Data Pool Cleanup Utility, replacing S-DPL-60207.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08590	The Data Pool Cleanup shall log at completion the total amount of disk space that was freed up by the clean-up of temporary files. [NOTE: This updates an existing requirement to ensure that this function remains with the Data Pool Cleanup utility, replacing S-DPL-60210.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08600	The Data Pool Insert Service shall include the amount of space freed by the removal of temporary files in its determination as to whether to clear the file system full condition. [NOTE: This replaces S-DPL-13210 and S-DPL-60215, which allocates the responsibility to maintain the file system full condition to the Data Pool Cleanup Utility.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08605	In the absence of concurrent workload, Data Pool Cleanup shall be able to remove at least 50,000 science granules per hour (including removal of their metadata files, data pool inventory metadata, browse links and removal of the related public browse granules).	
DP_7F_01	On-Line Archive	no data				S-DPL-08606	In the absence of concurrent workload, Data Pool shall be able to unpublish at least 50,000 science granules per hour (including removal of their metadata files, data pool inventory metadata, browse links and removal of the related public browse granules).	
DP_7F_01	On-Line Archive	no data				S-DPL-08610	The DPL CI shall provide Data Pool On-line Archive Recovery functions to restore the integrity of granules in the On-Line Archive.	
DP_7F_01	On-Line Archive	no data				S-DPL-08620	DAAC staff shall be able to invoke Data Pool On-line Archive Recovery functions via command line. [NOTE: The repair functions might be implemented by a collection of Data Pool utilities, or a single utility that prepares inputs for other utilities and invokes them.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08630	The Data Pool shall provide an On-line Archive Recovery function that can restore the integrity of granules (including Browse granules) that have files missing, including granules reported as phantoms, provided that the granules are recorded in the DPL and AIM inventory and are not flagged as deleted from archive (i.e.,  DeleteFromArchive is not set to Y). [NOTE: The repair function may use the Data Pool Batch Insert utility to replace the entire granule or just copy missing files back into the Data Pool. The state of the granule  i.e., whether public or not  will be inferred on this occasion from the Data Pool inventory entry.  Note that phantom granules that are no longer in the AIM inventory will be reported and treated as AIM-DPL inventory discrepancies.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08640	The Data Pool shall provide an On-line Archive Recovery function that can restore the integrity of granules (including Browse granules) that have files that are corrupt, provided that the granules are recorded in the DPL and AIM inventories and not flagged as deleted from archive (i.e.,  DeleteFromArchive is not set to Y). [NOTE: The repair function may use the Data Pool Batch Insert utility to replace the entire granule or just replace the corrupt files. The state of the granule  i.e., whether public or not  will be inferred on this occasion from the Data Pool inventory entry.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08645	When restoring files for science granules in the on-line archive that are public, the Data Pool On-line Archive Recovery function shall provide an option that allows DAAC staff to restore also any browse link(s) for that science granule.	
DP_7F_01	On-Line Archive	no data				S-DPL-08646	When restoring files for science granules in the on-line archive that are public and referenced by orders, the Data Pool On-line Archive Recovery function shall also restore any symbolic links required to support orders.	
DP_7F_01	On-Line Archive	no data				S-DPL-08650	The Data Pool shall provide an On-line Archive Recovery function that can restore the integrity of granules that are missing from the Data Pool inventory, provided that the granules are present in the AIM inventory. [NOTE: The repair function may use the Data Pool Batch Insert utility to replace the entire granule or  if the files are present and just the inventory entries are missing - just re-create the missing Data Pool inventory database entries.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08660	When restoring a granule that is missing from the Data Pool inventory, the Data Pool On-line Archive Repair shall attempt to make the granule public if it belongs to a collection configured for automatic granule publishing during ingest unless the granule is in-eligible for publication as per S-DPL-08050. [NOTE: The publishing attempt will fail if there is a collision with another public granule and granule replacement is turned off or fails because of other granule replacement conditions, such as the version of the granule that is public is more recent.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08670	When restoring a public browse granule, the Data Pool On-line Archive Repair shall extract the browse images from the original granule file for insertion into the public Data Pool.	
DP_7F_01	On-Line Archive	no data				S-DPL-08680	The DPL CI shall verify the checksums of any files copied into the Data Pool during On-Line Archive recovery if a checksum for the file is recorded in the AIM inventory.	
DP_7F_01	On-Line Archive	no data				S-DPL-08690	The Data Pool On-line Archive Recovery shall recognize when it needs to stage a granule from a tape that is currently not resident in the tape archive, skip the recovery of that granule and log the reason for skipping the granule and the tape label as part of the error information it logs on this occasion. [NOTE: The precise error handling is TBD during design.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08700	The Data Pool On-line Archive Recovery shall return an exit code indicating whether it encountered an error or not.	
DP_7F_01	On-Line Archive	no data				S-DPL-08710	The Data Pool On-line Archive Recovery shall be able to accept input files from which to read the ECS granule identifiers and/or file and path names and/or instructions needed to perform the repair.	
DP_7F_01	On-Line Archive	no data				S-DPL-08720	The Data Pool On-line Archive Recovery shall be able to accept the outputs created by Data Pool Inventory Validation as input.	
DP_7F_01	On-Line Archive	no data				S-DPL-08730	The Data Pool On-line Archive Recovery shall allow DAAC staff to restore granules which are flagged in the Data Pool inventory as having failed checksum verification, clearing the flag if the restoration was successful. [NOTE: Though Data Pool Checksum Verification (DPCV) will provide an output file listing corrupt granules that can be used as input into Data Pool On-line Archive Recovery, there are other occasions on which granules may fail checksum verification, such as during distribution by OMS.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08740	The Data Pool On-line Archive Recovery shall provide a capability to perform bulk repairs of the On-Line Archive, e.g., in the case of serious disk errors or loss of a Data Pool file system.	
DP_7F_01	On-Line Archive	no data				S-DPL-08750	During a bulk repair, the Data Pool On-line Archive Recovery shall be able to parallelize its operation for improved performance, including the ability to access multiple tape volumes in parallel, perform multiple checksumming and Data Pool disk operations in parallel, and cause concurrent Data Pool registration and publishing operations.	
DP_7F_01	On-Line Archive	no data				S-DPL-08760	During a bulk repair, the Data Pool On-line Archive Recovery shall access granules in the tape archive in sequence of tape volume and relative position on tape.	
DP_7F_01	On-Line Archive	no data				S-DPL-08770	During a bulk repair, the Data Pool On-line Archive Recovery shall allow DAAC staff to limit the number of tape volumes used by Data Pool On-line Archive Recovery concurrently.	
DP_7F_01	On-Line Archive	no data				S-DPL-08780	During a bulk repair, the Data Pool On-line Archive Recovery shall allow DAAC staff to limit the number of concurrent tape read operations the Data Pool On-line Archive Recovery will issue for the same tape.	
DP_7F_01	On-Line Archive	no data				S-DPL-08790	During a bulk repair, the Data Pool On-line Archive Recovery shall allow DAAC staff to identify the hosts on which it will perform checksumming operations and limit the number of concurrent checksumming operations it performs on each host.	
DP_7F_01	On-Line Archive	no data				S-DPL-08800	During a bulk repair, the Data Pool On-line Archive Recovery shall allow DAAC staff to control the number of Data Pool publications it requests. [NOTE: Details regarding the manner in which this will be accomplished are TBD during design.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08810	The DPL CI shall be able to perform bulk repairs of the Data Pool On-line Archive at a rate of no less than 150 MB/sec in the absence of concurrent workload.	
DP_7F_01	On-Line Archive	no data				S-DPL-08820	The DPL CI shall provide a utility that can cause granules that are currently public to be un-published, i.e., transfer granules that are currently public to the non-public state (IsOrderOnly = H or Y), including transferring its files into the non-public area of the Data Pool. [NOTE: The non-public state depends on whether the public granule is currently in use by orders (IsOrderOnly = B) or not (IsOrderOnly = NULL.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08830	DAAC staff shall be able to invoke the Data Pool utility for un-publishing granules via the command line.	
DP_7F_01	On-Line Archive	no data				S-DPL-08840	The Data Pool utility for un-publishing granules shall accept a list of granules to be un-published on the command line or via an input file.	
DP_7F_01	On-Line Archive	no data				S-DPL-08850	The Data Pool utility for un-publishing granules shall accept an input file in the format produced by Data Pool Inventory Validation.	
DP_7F_01	On-Line Archive	no data				S-DPL-08860	The Data Pool utility for un-publishing granules shall log the start and completion of its execution and any errors it encounters.	
DP_7F_01	On-Line Archive	no data				S-DPL-08870	The Data Pool utility for un-publishing granules shall log each un-publishing attempt.	
DP_7F_01	On-Line Archive	no data				S-DPL-08880	The Data Pool utility for un-publishing granules shall return an exit code indicating whether it encountered an error or not.	
DP_7F_01	On-Line Archive	no data				S-DPL-08890	The DPL CI shall provide a utility that can cause granules to be published that are currently in a hidden area of the Data Pool , i.e., transfer granules that are currently in a non-public state (IsOrderOnly = H or Y) to the public state (i.e., IsOrderOnly = B or NULL), including transferring its files into the public area of the Data Pool and leaving links in the hidden area as necessary. [NOTE: The public state depends on whether the non-public granule is currently in use by orders (IsOrderOnly = Y) or not (IsOrderOnly = H.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08900	The Data Pool utility for publishing granules shall be able to trigger granule replacement, i.e., repair unprocessed granule replacement.	
DP_7F_01	On-Line Archive	no data				S-DPL-08910	DAAC staff shall be able to invoke the Data Pool utility for publishing granules via the command line.	
DP_7F_01	On-Line Archive	no data				S-DPL-08920	The Data Pool utility for publishing granules shall accept a list of granules to be published on the command line or via an input file.	
DP_7F_01	On-Line Archive	no data				S-DPL-08930	The Data Pool utility for publishing granules shall accept an input file in the format produced by the Data Pool inventory validation function.	
DP_7F_01	On-Line Archive	no data				S-DPL-08940	The Data Pool utility for publishing granules shall log the start and completion of its execution and any errors it encounters.	
DP_7F_01	On-Line Archive	no data				S-DPL-08950	The Data Pool utility for publishing granules shall log each successful publishing attempt.	
DP_7F_01	On-Line Archive	no data				S-DPL-08960	The Data Pool utility for publishing granules shall return an exit code indicating whether it encountered an error or not.	
DP_7F_01	On-Line Archive	no data				S-DPL-08970	The Data Pool utility for publishing granules shall allow DAAC staff to select all granules in a specified collection for publication.	
DP_7F_01	On-Line Archive	no data				S-DPL-08980	The Data Pool Update Expiration Utility shall not accept updates to the expiration date of an ECS granule if that would cause the granule to be removed from the on-line archive. [NOTE: ECS granules are part of the On-Line Archive and no longer expire.  This extends requirements S-DPL-30010.]	
DP_7F_01	On-Line Archive	no data				S-DPL-08990	In the absence of concurrent workload, the Data Pool Collection Move Utility shall be able to move granules as a rate of no less than 100,000 granules or 100 GB per hour, whichever is less.	
DP_7F_01	On-Line Archive	no data				S-DPL-09000	In the absence of concurrent workload, the Data Pool Collection-to-Group Remapping Utility shall be able to operate at the rate of no less than 350,000 granules per hour. [NOTE: This replaces requirement S-DPL-66105.]	
DP_7F_01	On-Line Archive	no data				S-DPL-09010	The DPL CI shall be able to perform collection remapping operations during preventive maintenance periods during which normal operation is down. [NOTE: This rewords and replaces S-DPL-66095. The requirement represents an operational consideration and is not subject to integration testing.] 	
DP_7F_01	On-Line Archive	no data				S-DPL-09015	The DPL CI shall prevent granule inserts, deletions and state changes that interfere with the concurrent execution of a collection move operation. [NOTE: This augments S-OMS-13000. Utility functions that as per agreement with the DAACs will not be run concurrently with a collection move are exempted from this requirement for this release.  These concurrency situations are not included in the criteria.  The utilities are: Data Pool cleanup, link checking, orphan and phantom checking, and granule unpublishing.] 	
DP_7F_01	On-Line Archive	no data				S-DPL-09020	The Data Pool Batch Insert Utility shall skip ECS granules, i.e., exclude them from the insert operation, which are not in the AIM inventory or are flagged as deleted from archive (i.e.,  DeleteFromArchive set to Y). [NOTE: This rewords and replaces a similar requirement S-DPL-40140.]	
DP_7F_01	On-Line Archive	no data				S-DPL-09030	The Data Pool Batch Insert Utility shall queue an ECS granule for Data Pool publication if the granule is in a collection that is configured for publication during ingest and the granule is not ineligible for publication as per S-DPL-08110, and for insertion into the hidden Data Pool otherwise. [NOTE: This replaces requirement S-DPL-40170.]	
DP_7F_01	On-Line Archive	no data				S-DPL-09040	The DPL CI shall ensure that any retention period or priority specified for an ECS granule in the insert request cannot prevent the retention of the granule in the Data Pool On-Line Archive until the granule is explicitly removed as per S-DPL-08530. [NOTE: Any retentions provided by OMS, the Data Pool Batch Insert Utility, or Data Pool insert actions queued by the Subscription Service or Data Pool Ingest must not conflict with the assured retention of ECS granules in the On-Line Archive.  This augments requirements S-DPL-20100 and S-DPL-21500, which remain valid for non-ECS granules].	
DP_7F_01	On-Line Archive	no data				S-DPL-09050	The Data Pool Insert Service shall skip and log as an error the insert of an ECS granule into the Data Pool if the granule belongs to a collection that is not configured in the Data Pool. [NOTE: This rewords and replaces similar requirements S-DPL-40094 and S-DPL-20350.]	
DP_7F_01	On-Line Archive	no data				S-DPL-09060	The Data Pool Insert Service shall fail a request for staging a granule from a tape that is not resident in the tape archive.	
DP_7F_01	On-Line Archive	no data				S-DPL-09070	The Data Pool Insert Service shall include the reason for the staging error and the label of the required tape in the error details associated with the corresponding insert action when failing a request from a tape that is not resident in the tape archive.	
DP_7F_01	On-Line Archive	no data				S-DPL-09075	The Data Pool Insert Service shall allow the insertion of granules into the hidden Data Pool regardless of whether a collection is enabled for Data Pool publication or not, provided that the collection is defined to the Data Pool. [NOTE: This replaces requirement S-DPL-06260.]  	
DP_7F_01	On-Line Archive	no data				S-OMS-15000	The OMS CI shall not remove ECS granules from the Data Pool. [NOTE: This replaces requirement S-OMS-08230. It can be implemented by having the DPL CI ignore requests from OMS for granule removal, but OMS still needs to make sure it will not remove the corresponding files.]	
DP_7F_01	On-Line Archive	no data				S-OMS-15010	The OMS CI shall cause an operator intervention when the Data Pool Insert Service fails the staging of a granule from a tape that is not resident in the tape archive, identifying the cause for the intervention and including the tape label in the intervention details.	
DP_7F_01	On-Line Archive	no data				S-OMS-15020	The OMS CI shall pass all staging actions for all requests that require access to the tape archive to the Data Pool Insert Service and rely on the Data Pool Insert Service for managing and optimizing tape accesses. [NOTE: This replaces the classification into CHEAP, MODERATE, EXPENSIVE as per S-OMS-06020 and S-OMS-06470;  the use of the physical media and FTP push low/high watermarks as per S-OMS-06025, S-OMS-06030, queuing such requests prior to submission to Data Pool Insert as per S-OMS-06485; and applying tape management policies as per S-OMS-06490.  Requirements S-OMS-02110, S-OMS-02120 and S-OMS-06495 define tape access policies for OMS and are obsolete.] [Note: OMS will continue to honor FTP Pull limits as per S-OMS-06035, in accordance with the results of action #26 of session 1 of the RTR]	
DP_7F_01	On-Line Archive	no data				S-OMS-15030	The OMS CI shall allow DAAC staff to configure a limit on the NOCOST granules and requests (i.e., that applies only to granules and requests that do not require tape access) that are in the staging state concurrently.	
DP_7F_01	On-Line Archive	no data				S-OMS-15040	The OMS CI shall limit the number of NOCOST granules and requests (i.e., granules and requests that do not require tape access) that are in the staging state concurrently to the corresponding DAAC configured limit.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40000	The Data Pool shall include a batch insert utility.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40010	The Data Pool Batch Insert Utility shall be able to accept an ECS Granule List, namely a file consisting of one granule identifier per line in any mix of the following formats as input:    a) ECS UR  b) ECS Local Granule ID  c) ECS granule dbid  d) format in which the granule ID's are saved by EDG	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40020	The Data Pool Batch Insert Utility shall accept an optional command line parameter providing the Unix path name pointing to the input file.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40030	The Data Pool Batch Insert Utility shall assume that the input is provided via standard input if the input path name parameter is missing.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40040	The Data Pool Batch Insert Utility shall accept an optional command line parameter providing a batch label of up to 16 characters.  [Note: use the first 16 characters if the string is too long.  There is no requirement for the batch label to be unique].	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40050	The Data Pool Batch Insert Utility shall use the first 16 characters of the input file name (i.e., excluding directory names) as the batch label if the corresponding command line parameter is missing and the input file name parameter is present.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40055	The Data Pool Batch Insert Utility shall require that a batch label be provided if the granule list is provided via standard input.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40060	The Data Pool Batch Insert Utility shall accept an optional command line parameter specifying a valid retention priority.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40065	The Data Pool Batch Insert Utility shall use the configured default retention priority if none was specified in the command line parameters.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40070	The Data Pool Batch Insert Utility shall accept an optional command line parameter specifying a valid retention period.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40075	The Data Pool Batch Insert Utility shall use the configured default retention period if none was specified in the command line parameters.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40080	The Data Pool Batch Insert Utility shall accept an optional command line parameter specifying whether the granule insert shall include only the metadata file.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40090	The Data Pool Batch Insert Utility shall assume that both science and metadata files are to be inserted if the corresponding command line parameter is missing and the collection is enabled for science and metadata file insert.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40092	The Data Pool Batch Insert Utility shall assume that only metadata files are to be inserted if the corresponding command line parameter is missing and the collection is enabled for  metadata file insert only.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40094	The Data Pool Batch Insert Utility shall skip a granule if the collection is not eligible for inserts	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40100	The Data Pool Batch Insert Utility shall accept an optional parameter providing a valid Theme name.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40105	The Data Pool Batch Insert Utility shall consider a Theme name invalid if the Theme does not exist or is not enabled for data pool insert.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40110	The Data Pool Batch Insert Utility shall accept an optional parameter specifying an insert dispatch priority as an integer from 1 to 255.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40120	The Data Pool Batch Insert Utility shall assume the lowest possible value for the dispatch priority if no dispatch priority parameter is specified.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40130	The Data Pool Batch Insert Utility shall not perform the insert and return an error if any of the parameters have invalid values.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40140	The Data Pool Batch Insert Utility shall skip granules, i.e., exclude them from the insert operation, whose identifier is invalid or that have been flagged as deleted from archive or logically deleted in the SDSRV inventory.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40145	The Data Pool Batch Insert Utility shall skip a granule, i.e., not queue it up for insert, if that granule is currently in the insert action queue with the same batch label and a status other than FAILED.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40150	The Data Pool Batch Insert Utility shall log the provided identifiers of any granules that it skips and the reason for skipping.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40160	The Data Pool Batch Insert Utility shall translate any granule identifier in the input file into an ECS dbid prior to inserting the granule into the Data Pool insert action queue.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40162	The Data Pool Batch Insert Utility shall skip any ECS Local Granule ID identifier in the input file if it does not identify an existing ECS granule or more than one ECS granule.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40164	The Data Pool Batch Insert Utility shall remove the duplicates if any input file contains or results in duplicate dbid.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40170	The Data Pool Batch Insert Utility shall queue a Data Pool insert action for each granule whose identifier is in the input file and is valid, and mark this as an insert that is not from cache.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40180	The Data Pool Batch Insert Utility shall populate the attributes of each insert action with the attributes from the command line parameters and the input file.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40182	Different instances of the Data Pool Batch Insert Utility shall be able to operate in different modes concurrently.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40184	Multiple instances of the Data Pool Batch Insert Utility shall be able to operate in the same modes concurrently.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40200	The Data Pool Batch Insert Utility shall not place any restrictions on the number of granules contained in a single insert batch.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40210	The Data Pool Action Dispatcher (DPAD) shall dispatch insert actions that are flagged as not in cache and that include the insertion of science files by priority, and within the same priority grouped by predicted tape archive location using a combination of ESDT, granule insert time, and/or storage management volume group information for the granule.  [Note: the precise approach is TBD during design.]	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40220	The DPAD shall provide a mechanism that prevents a batch of granule inserts from seriously degrading subscription based data pool inserts, regardless of whether the batch includes science and metadata files, or metadata files only, even if subscription-based inserts refer to granules that are no longer in cache.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40300	The Data Pool Maintenance GUI shall be able to include status, batch label and insert dispatch priority in its action queue display.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40310	The Data Pool Maintenance GUI shall be able to filter the insert action queue by  batch label and status individually and in combination.	
DP_S3_01	Populate Data Pool from ECS Archive	no data				S-DPL-40320	The Data Pool Maintenance GUI shall allow the operator to display for each batch label, a summary of the actions by status.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-13650	The Data Pool Cleanup Utility shall be able to include non-ECS granules and their science, metadata, and browse files in the Data Pool in its cleanup activities. 	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-30400	The Data Pool Update Expiration Utility shall be able to update the expiration of non-ECS granules in the Data Pool just like that of ECS granules.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-32500	The Data Pool Access Statistics Utility shall be able to include accesses to non-ECS granules in the Data Pool in its log extraction.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41005	The Data Pool shall provide a command line utility for inserting non-ECS granules.  [Note: the capability can be provided by the Batch Insert Utility for ECS granules defined in ticket DP_S3_01 or by a separate utility.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41010	The Data Pool Batch Insert utility for non-ECS granules shall accept as input a Non-ECS Granule List containing one absolute path and file name per line.  [Note: There is no need to accept an input file listing both ECS and non-ECS granules.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41020	The Data Pool Batch Insert Utility shall not accept both a Non-ECS Insert List and an ECS Insert List.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41030	The Data Pool Batch Insert Utility for non-ECS granules shall verify that the file names in the Non-ECS Granule List have an XML extension.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41040	The Data Pool Batch Insert Utility for non-ECS granules shall support requirements S-DPL-40020 through S-DPL-40080, S-DPL-40100 through S-DPL-40130, S-DPL-40150, S-DPL-40182, S-DPL-40184 and S-DPL-40200 in ticket DP_S3_01 when processing a Non-ECS Granule List. 	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41045	The Data Pool Batch Insert Utility for non-ECS granules shall skip duplicate entries in the Non-ECS Granule List.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41050	The Data Pool Batch Insert Utility for non-ECS granules shall skip granules in a Non-ECS Granule List, i.e., exclude them from the insert, if the path file name is invalid.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41054	The Data Pool Batch Insert Utility for non-ECS granules shall skip granules in a Non-ECS Granule List, i.e., exclude them from the insert, if an insert action referencing the same XML file is already queued up with a status other than FAILED.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41060	The Data Pool Batch Insert Utility for non-ECS granules shall queue a Data Pool insert action for each valid entry in the Non-ECS Granule List and mark this as an insert action for a non-ECS granule.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41070	The Data Pool Batch Insert Utility for non-ECS granules shall populate the attributes of each non-ECS insert action with the attributes from the command line parameters.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41080	The Data Pool Batch Insert Utility for non-ECS granules shall copy the absolute path and file name of the XML file from the Non ECS Granule List into the queued insert action.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41082	The Data Pool Batch Insert Utility for non-ECS granules shall populate the collection shortname and version in the queued insert action from the corresponding information in the XML file.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41084	The Data Pool Batch Insert Utility shall support requirements S-DPL-40090 to S-DPL-40094.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41086	The Data Pool Batch Insert Utility for non-ECS granules shall be able to queue Non ECS Granules for insert at a rate of not less than ten granules per minute.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41110	The Data Pool Monitoring GUI shall be able to display the XML file and path name for a non-ECS granule insert action. [Note: to save screen real estate when displaying a list of insert actions, this information does not have to be included in the list itself but may be displayed to the operator only upon request.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41120	The Data Pool Maintenance GUI shall allow operators to define non-ECS data pool collections and collection groups and their mapping.  [Note: By definition, collections belonging to non-ECS collection groups are considered non-ECS collections; and collections that belong to ECS collection groups are considered ECS collections].	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41122	The Data Pool Maintenance GUI shall require operators to enter a spatial search type when defining a non-ECS collection.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41124	The Data Pool Maintenance GUI shall offer only the following valid ECS spatial search types for selection by the operator:    a. GPolygon  b. Rectangle (i.e., LLBOX)  c. Not Supported (i.e., spatial coverage does not apply)	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41126	The Data Pool Maintenance GUI shall not permit collections that belong to non-ECS collection groups to duplicate the name of an ESDT currently defined in ECS regardless of letter case. (I.e., checking for name duplication needs to be case insensitive - Aster01 and aster01 need to be considered duplicates).	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41128	The Data Pool Maintenance GUI shall allow operators to update the spatial search type of a non-ECS Data Pool collection if and only if the collection is currently not enabled for insert and the Data Pool contains no granules belonging to that collection.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41129	The Data Pool Maintenance GUI shall allow operators to update the description of a non-ECS Data Pool collection.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41130	The Data Pool Maintenance GUI shall verify that the name of a non-ECS data collection obeys the following rules and reject the definition if it does not:    a. The name starts with a letter.  b. The name dos not contain any special characters except an underscore         ('_').  c. The letters are all capitalized  d. The name is no more than eight characters in length.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41132	The Data Pool Maintenance GUI shall verify that the name of a data collection group obeys the following rules and reject the definition if it does not:    a. The name consists entirely of upper case letters.  b. The name is no more than four characters in length.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41150	The Data Pool Maintenance GUI shall support S-DPL-40300 and S-DPL-40310 in ticket DP_S3_01 for ECS- and Non-ECS insert actions.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41160	The Data Pool Maintenance GUI shall support S-DPL-40320 in ticket DP_S3_01 for Non-ECS insert actions as well as for insert actions for ECS granules.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41170	The Data Pool Action Dispatcher (DPAD) shall dispatch insert actions that are flagged as non-ECS inserts in priority order, and within the same priority, on a first-in first-out basis.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41180	The DPAD shall support S-DPL-40220 in ticket DP_S3_01 regardless of whether a batch is for ECS or non-ECS granules.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41190	The Data Pool Insert Utility (DPIU) shall verify the accessibility of the XML file referenced by a non-ECS granule insert action, and return a fatal error if the file is not accessible.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41200	The DPIU shall parse the XML file, validate its correctness against the DTD, and return a fatal error if it fails validation.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41210	The Data Pool Insert Service shall generate a unique Data Pool internal granule identifier for non-ECS granules.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41220	The DPIU shall retain any non-ECS granule identifier assigned to the granule in the Data Pool inventory. [Note: The operations concept for non-ECS granules assumes it will be provided via the Local Granule ID.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41230	The DPIU shall populate the Data Pool inventory and warehouse from the XML file.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41250	The DPIU shall return a fatal error if any mandatory metadata is missing.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41260	The DPIU shall return a fatal error if the data pool collection whose name and version provided in the XML metadata file does not exist, or is not enabled for the requested type of Data Pool insertion (i.e., metadata only v. metadata + granule), or does not represent a non-ECS collection.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41270	If an external non-ECS granule identifier (i.e., a LocalGranuleId) is provided, the DPIU shall replace any existing granule in the Data Pool with the same non-ECS granule identifier and XML file name [Note: this means that an existing granule can be replaced if non-ECS granule ID is the same. To be safe, we also check the XML file name as verification.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41275	If an external non-ECS granule identifier (i.e., a LocalGranuleId) is provided, the DPIU shall return a fatal error if a granule with the same identifier already exists in the Data Pool inventory, but the XML file names of the new granule and the existing granule are different. [Note: this means that an existing granule will not be replaced if the XML file of the 'replacement'granule has a different name.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41280	If an external non-ECS granule identifier (i.e., a LocalGranuleId) is provided, the DPIU shall return a fatal error if one of the files of the granule being inserted has the same name as that of a file of a different granule (i.e., with different or no external identifier) already existing in the target Data Pool directory.  [Note: this prevents file overwrites among different granules].	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41290	If an external non-ECS granule identifier is not provided (i.e., if there is no LocalGranuleId), the DPIU shall replace any existing granule already residing in the same Data Pool target directory that uses the same XML file name.  [Note:This means that a non-ECS granule can be replaced even if it does not use an external granule identifier as long as it uses the same XML file name. Two granules without external identifier are only assumed to be the same granules if they are allocated to the same target directory and have the same XML file name.  Naturally, if one granule has an external identifier and the other does not or if one granule is an ECS granule and the other is a non-ECS granule, they would be considered different granules..]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41295	If an external non-ECS granule identifier is not provided (i.e., if there is no LocalGranuleId), the DPIU shall return a fatal error if one of the files of the granule being inserted has the same name as that of a different granule (i.e., with external identifier or same target directory but different XML file name) already residing in the same Data Pool target directory.  [Note: this corresponds to the current data pool behavior: duplicate file names that would cause the files of another granule to be overwritten are not allowed.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41300	The DPIU shall determine the data pool target directory for a non-ECS granule based on Data Pool Collection Group, collection name, versionid, and data acquisition date of the granule, or if no acquisition date is available, based on the date of the insert request.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41320	The DPIU shall copy the XML metadata file into the target data pool directory.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41330	The DPIU shall return a fatal error if the insert is not metadata only and no granule file names are specified in the XML file.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41340	Unless the insert is for metadata only, the DPIU shall copy the granule files from a location formed by the absolute path name of the XML file and the file names specified in the XML file into the target data pool directory. 	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41350	The DPIU shall rename the metadata and science files in accordance with the Data Pool renaming rules if the file name contains invalid characters or if a local granule ID is specified in the metadata.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41352	The Data Pool Insert Service shall insert each browse granule that is listed in the browse cross reference into the Data Pool, unless a Browse granule with the same LocalGranuleId already exist in the Data Pool.   	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41354	If a browse granule that is listed in the browse cross reference already exists in the Data Pool, the Data Pool Insert Service shall insert a cross-reference between it and the science granule into the Data Pool inventory.    	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41356	If a browse granule that is listed in the browse cross reference already exists in the Data Pool, the Data Pool Insert Service shall insert links to its files into the science granule target directory, unless the link already exists in that directory.    	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41360	For browse granules that are to be inserted into the Data Pool, the Data Pool Insert Service shall extract each jpeg image from the browse granules referenced in the browse cross reference into a jpeg file.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41362	The Data Pool Insert Service shall skip the insertion of browse granules that are not in HDF format or do not contain jpeg images.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41364	The Data Pool Insert Service shall log any skipped browse granules and the reason for skipping them.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41370	The Data Pool Insert Service shall copy the extracted jpeg files into the target browse directory and create the browse file link(s) in the granule target directory.  [Note: The naming rules for non-ECS browse files and links are the same as for ECS browse files and links.]	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41380	The Data Pool Insert Service shall insert cross references between the science granule and each  inserted browse granule into the Data Pool inventory.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41390	The Data Pool Insert Service shall be able to deal with race conditions that may arise if several non-ECS granules are inserted into the Data Pool concurrently and reference the same browse granule(s).  	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41400	The Data Pool Insert Service shall log the fact that an insert is for a non-ECS granule when logging the queuing, start and completion of a Data Pool insert.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41410	The Data Pool Insert Service shall log the following additional events for non-ECS granule inserts:  a. Start of file transfers from the source location to the target Data Pool        directory  b. Completion of file transfers from the source location to the target Data Pool    directory	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41420	The DPIU shall be able to complete the insertion of a non-ECS granule successfully even if an earlier insert failed due to a fault.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41430	The DPIU shall prevent the partial insertion of non-ECS granules into the Data Pool if a granule insert action cannot be completed due to insert errors and (as a design target) faults.	
DP_S3_02	Accommodate Non ECS Data in Data Pool	no data				S-DPL-41440	The DPIU shall remove the granule, browse and metadata files from the source directory after the insert completes successfully, and leave the files in the source directory if the insert does not complete successfully.  	
DP_S3_03	Support Themes	no data				S-DPL-05550	The Data Pool Web Access Service shall allow users to drill down on themes as an alternative to drill down on Data Pool Collection Groups.  	
DP_S3_03	Support Themes	no data				S-DPL-05560	The Data Pool Web Access Service shall offer a theme for drill down if and only if it is activated for web drill down. 	
DP_S3_03	Support Themes	no data				S-DPL-05570	If the user drilled down on a theme, the Data Pool Web Access Service shall constrain all lower-level drill down steps to the data pool granules that are cross referenced with that theme, and to the data pool collections that contain such granules.	
DP_S3_03	Support Themes	no data				S-DPL-13700	The Data Pool Cleanup Utility shall remove the cross references between themes and granules that are being cleaned up.	
DP_S3_03	Support Themes	no data				S-DPL-13710	The Data Pool Cleanup Utility shall support a command line parameter to restrict the cleanup to the granules of a specific theme.	
DP_S3_03	Support Themes	no data				S-DPL-13720	If the command line parameters restrict cleanup to a specific theme, the Data Pool Cleanup Utility shall clean up a granule that would otherwise qualify for cleanup only if the granule is associated with that theme, and remove the granule entirely if it is not associated with any other theme, otherwise only remove its cross reference with that theme. {Note: This allows operators to cleanup themes selectively.]	
DP_S3_03	Support Themes	no data				S-DPL-13730	The Data Pool Cleanup Utility shall support a command line parameter to request that all cross-references between a specific theme and its granules be removed.	
DP_S3_03	Support Themes	no data				S-DPL-13740	If the command line parameters request the removal of all cross-references for a theme, the Data Pool Cleanup Utility shall remove all these cross-references, i.e., regardless of any other cleanup constraints. 	
DP_S3_03	Support Themes	no data				S-DPL-30450	The Data Pool Update Expiration Utility shall accept a command line parameter that specifies the name of a theme instead of a granule id as part of a 'granule triplet'.	
DP_S3_03	Support Themes	no data				S-DPL-30460	If the command line parameters specify the name of a theme, the Data Pool Update Expiration Utility shall update the expiration date of all granules associated with that theme to a new expiration date if and only if their current expiration is earlier. 	
DP_S3_03	Support Themes	no data				S-DPL-30470	If the command line parameters specify the name of a theme, the Data Pool Update Expiration Utility shall update the expiration priority of all granules associated with that theme to a new expiration priority if and only if their current priority is less. 	
DP_S3_03	Support Themes	no data				S-DPL-30480	The data Pool Expiration Utility shall log the number and total size of the granules expected to be updated prior to applying the update, as well as after the number and total size of the granules that actually were updated after performing the update.  [Note:  This requirement supercedes S-DPL-30140 and S-DPL-30150 from the Synergy II ticket DP_SY_06.]	
DP_S3_03	Support Themes	no data				S-DPL-30490	The Data Pool Update Expiration utility shall display to the operator, before performing the update, the following confirmation information, ordered by collection name and version, and regardless of verbosity setting:    a. the number of granules which will be updated for that collection, and  b. the total size of all granules which will be updated for that    collection.    [Note: This requirement supercedes S-DPL-30060 and S-DPL-30065 from the Synergy II ticket DP_SY_06.] 	
DP_S3_03	Support Themes	no data				S-DPL-30500	The Data Pool Update Expiration utility shall ignore any command line parameter specifying verbose confirmation.	
DP_S3_03	Support Themes	no data				S-DPL-42010	The Data Pool Maintenance GUI shall allow an Operator to define a theme.	
DP_S3_03	Support Themes	no data				S-DPL-42020	The Data Pool Maintenance GUI shall store the information associated with themes persistently in the Data Pool database.	
DP_S3_03	Support Themes	no data				S-DPL-42030	The Data Pool Maintenance GUI shall support the following attributes for a theme:    a. A unique name of up to 40 characters that must start with a letter and must    be compatible with ECS file naming standards (i.e., it must not contain any    characters that are illegal as ECS file names)  b. A description of up to 255 characters.  c. Whether the theme is enabled for inserts or not (default is 'not enabled for    insert')  d. Whether the theme is activated for web drill down or not. (default is 'not    activated for web drill down')	
DP_S3_03	Support Themes	no data				S-DPL-42040	The Data Pool Maintenance GUI shall reject the definition of a theme if its name duplicates the name of an existing data pool collection group or ECS collection, or that of another theme.	
DP_S3_03	Support Themes	no data				S-DPL-42050	The Data Pool Maintenance GUI shall allow an Operator to list the themes in alphabetic order.	
DP_S3_03	Support Themes	no data				S-DPL-42060	When listing themes, the Data Pool Maintenance GUI shall display their name, whether they are enabled for inserts or not, and whether they are active or not.	
DP_S3_03	Support Themes	no data				S-DPL-42070	The Data Pool Maintenance GUI shall allow an Operator to filter the list of themes by the beginning letters of their name, whether they are enabled for insert, and whether they are activated for drill down.	
DP_S3_03	Support Themes	no data				S-DPL-42080	The Data Pool Maintenance GUI shall allow an Operator to select a theme from the displayed list for deletion.	
DP_S3_03	Support Themes	no data				S-DPL-42090	The Data Pool Maintenance GUI shall require the Operator to confirm the deletion of a theme before actually deleting it.	
DP_S3_03	Support Themes	no data				S-DPL-42100	The Data Pool Maintenance GUI shall not permit the Operator to delete a theme that is still cross-referenced with Data Pool granules or subscriptions. [Note: The operator must first run cleanup to remove the cross-references and also delete or edit the insert actions for that Theme].	
DP_S3_03	Support Themes	no data				S-DPL-42110	The Data Pool Maintenance GUI shall allow an Operator to select a theme from the displayed list for viewing.	
DP_S3_03	Support Themes	no data				S-DPL-42120	The Data Pool Maintenance GUI shall allow an Operator to select a theme from the displayed list for editing.	
DP_S3_03	Support Themes	no data				S-DPL-42130	The Data Pool Maintenance GUI shall allow an Operator to edit the description of a theme, as well as whether it is enabled for inserts or not, and whether it is activated for web drill down or not.	
DP_S3_03	Support Themes	no data				S-DPL-42140	The Data Pool Insert Service shall insert a cross reference between a granule and the theme whose name is specified by the insert action if the theme is enabled for insert. [Note: this supports specifying a theme on batch insert]	
DP_S3_03	Support Themes	no data				S-DPL-42150	The Data Pool Insert Service shall insert a cross reference between a granule and the themes associated with the insert actions of the subscriptions that triggered the granule insert if the theme is enabled for insert. [Note: this supports specifying a theme in subscriptions].	
DP_S3_03	Support Themes	no data				S-DPL-42152	If an ECS granule referenced by an insert action already exists in the Data Pool, the Data Pool Insert Service shall add a cross reference between that granule and the theme associated with the insert action, assuming the theme is enabled for insert and is not already cross referenced with that granule. [Note: this allows operators to add existing granules to new themes. This requirement does not apply to non ECS granules since the situation would result in a complete replacement of the existing granule].	
DP_S3_03	Support Themes	no data				S-DPL-42154	If an ECS granule referenced by an insert action already exists in the Data Pool, the Data Pool Insert Service shall extend the expiration time and/or increase the retention priority based on the values in the insert action, if necessary. [Note: That is, if the insert action has a higher priority, then the priority is raised; and if the calculated expiration is later, the expiration is updated.  This requirement does not apply to non ECS granules since the situation would result in a complete replacement of the existing granule].	
DP_S3_03	Support Themes	no data				S-DPL-42160	The Data Pool Insert Service shall fail a granule insert that is associated only with a theme that is not enabled for insert.  [Note: this means that if the granule is also associated with other themes or no theme, its insert will proceed]	
DP_S3_03	Support Themes	no data				S-SSS-11010	The NSBRV CI shall allow an operator who is entering a data pool insert action for a subscription to select the name of a theme to be cross referenced with the action.	
DP_S3_03	Support Themes	no data				S-SSS-11020	The NSBRV CI shall allow an operator who is editing a subscription to disassociate the data pool insert action from the theme it currently references. [Note: this will have no impact on the granules already in the Data Pool or queued up for insert]	
DP_S3_03	Support Themes	no data				S-SSS-11030	The NSBRV CI shall allow an operator who is editing a subscription to change the theme currently being referenced by its data pool insert action. [Note: this will have no impact on the granules already in the Data Pool or queued up for insert]	
DP_S3_03	Support Themes	no data				S-SSS-11040	The NSBRV CI shall allow an operator who is editing a data pool insert action for a subscription that is currently not cross-referenced with a theme to add such a cross reference. [Note: this will have no impact on the granules already in the Data Pool or queued up for insert]	
DP_S3_03	Support Themes	no data				S-SSS-11045	The NSBRV CI shall give the operator an option to request that all existing granules in the Data Pool that were inserted as a result of a subscription, be linked with the theme whose cross reference was added to its insert action. [Note: This may be useful when transitioning the Data Pool from Synergy II to Synergy III]	
DP_S3_03	Support Themes	no data				S-SSS-11050	The NSBRV CI shall allow an operator to list the subscriptions having insert actions associated with a particular theme.	
DP_S3_03	Support Themes	no data				S-SSS-11060	The NSBRV CI shall allow an operator to select one or all subscriptions listed for a theme and suspend them.	
DP_S3_03	Support Themes	no data				S-SSS-11070	The NSBRV CI shall allow an operator to select one or all subscriptions listed for a theme and resume them.	
DP_S3_03	Support Themes	no data				S-SSS-11080	The NSBRV CI shall allow an operator to select any one of the subscriptions listed for a theme and view it.	
DP_S3_03	Support Themes	no data				S-SSS-11090	The NSBRV CI shall allow an operator to select any one of the subscriptions listed for a theme and edit it.	
DP_S3_03	Support Themes	no data				S-SSS-11100	The NSBRV CI shall allow an operator to select one or all of the subscriptions listed for a theme and cancel them.  [Note: this will have no impact on the granules already in the Data Pool or queued up for insert]	
DP_S3_03	Support Themes	no data				S-SSS-11110	The NSBRV CI shall not queue a Data Pool insert action if it is associated with a theme that is not enabled for insert.	
DP_S3_04	Data Pool Validation	no data				S-DPL-05600	The Data Pool Web Access Service must be able to operate correctly and without fault while an inventory validation is in progress.  	
DP_S3_04	Data Pool Validation	no data				S-DPL-42200	The Data Pool Insert Service must be able to operate correctly and without fault while an inventory validation is in progress.  	
DP_S3_04	Data Pool Validation	no data				S-DPL-60010	The Data Pool Service shall include a Data Pool inventory validation function.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60020	The Data Pool inventory validation function shall be invoked by the Data Pool Cleanup utility after successful completion of the cleanup if the command line parameters request inventory validation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60030	The Data Pool Inventory Cleanup Utility shall check the syntax of the new command line parameters pertaining to inventory validation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60035	If the new command line parameters that pertain to inventory validation fail the syntax check, the Data Pool Cleanup Utility shall display the error and the correct command line syntax.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60040	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies that orphan checking shall be performed. 	
DP_S3_04	Data Pool Validation	no data				S-DPL-60042	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies that Data Pool validation but no additional cleanup shall be performed.  [Note: this makes it unnecessary for the operator to specify artificial cleanup parameters to avoid cleaning up granules at the same time).	
DP_S3_04	Data Pool Validation	no data				S-DPL-60044	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies that discrepancies shall be not be fixed, but only logged.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60050	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies the maximum orphan age in days of the files to be included in the orphan check.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60055	The Data Pool Inventory Cleanup Utility shall verify that the maximum orphan age parameter specified on the command line is not less than three days.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60060	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies that phantom checking shall be performed.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60070	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter via which the operator can specify up to ten (10) data pool collection groups to be included in the validation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60075	The Data Pool Inventory Cleanup Utility shall verify that the collection groups specified on the command line are valid Data Pool collection groups.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60080	The Data Pool Inventory Cleanup Utility shall invoke the Data Pool inventory validation function if and only if orphan or phantom checking or both have been requested.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60090	The Data Pool Inventory Cleanup Utility shall pass the command line parameters that control the validation to the Data Pool inventory validation function.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60092	The Data Pool inventory validation function shall always execute in no prompt mode. [Note: To verify what the utility would clean up, the operator would run the utility specifying that discrepancies should only be logged but not fixed.] 	
DP_S3_04	Data Pool Validation	no data				S-DPL-60100	The Data Pool inventory validation function shall include only those files and browse links on disk in the orphan check whose age is equal to or larger than the value of the maximum orphan age specified on the command line.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60110	The Data Pool inventory validation function shall consider a file or browse link included in the orphan check to be an orphan if there is no corresponding entry in the data pool inventory. [Note: browse links are tracked by granule browse cross references in the inventory.]	
DP_S3_04	Data Pool Validation	no data				S-DPL-60112	The Data Pool inventory validation function shall use an operator configurable default maximum orphan age if none is specified on the command line.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60120	Operators shall be able to configure the default maximum orphan age in days.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60130	The Data Pool inventory validation function shall remove all orphaned files from the data pool disks unless fixing discrepancies was suppressed. 	
DP_S3_04	Data Pool Validation	no data				S-DPL-60140	The Data Pool inventory validation function shall log the orphaned files.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60150	The Data Pool inventory validation function shall consider a granule a phantom if any of its files listed in (or implied by) the corresponding entries in the Data Pool inventory are not on the Data Pool disks. [Note: for example, browse links are implied rather than explicitly listed]	
DP_S3_04	Data Pool Validation	no data				S-DPL-60160	The Data Pool inventory validation function shall remove granules affected by a phantom from the inventory, and all its remaining files and links from the Data pool disks unless fixing discrepancies was suppressed. [Note: If the phantom file belongs to a browse granule, the browse granule inventory entry as well as all its cross references and any links remaining on disk need to be removed, as well.  It is permissible for the validation function to recreate a phantom browse link instead of removing its inventory entry.]	
DP_S3_04	Data Pool Validation	no data				S-DPL-60170	The Data Pool inventory validation function shall log the phantom granules.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60175	Log entries for phantom granules shall include the information that needs to be specified by the operator should operations decide to re-insert the granule from the archive into the Data Pool (e.g., expiration date, retention priority, and the names of any thematic collections with which the file was cross-referenced)	
DP_S3_04	Data Pool Validation	no data				S-DPL-60180	The Data Pool inventory validation function shall remove all temporary files from the data pool disks whose age exceeds the maximum orphan age unless fixing discrepancies was suppressed. 	
DP_S3_04	Data Pool Validation	no data				S-DPL-60185	The Data Pool inventory validation function shall log the temporary files whose age exceeds the maximum orphan age. 	
DP_S3_04	Data Pool Validation	no data				S-DPL-60190	The Data Pool inventory validation function shall log the start of a validation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60192	The Data Pool inventory validation function shall include the validation settings in the log entry for the validation start.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60195	The Data Pool inventory validation function shall log the completion of a validation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60200	The Data Pool inventory validation function shall log at completion the total number of orphans that were found if orphan checking was requested.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60205	The Data Pool inventory validation function shall log at completion the total number of phantoms that were found if phantom checking was requested.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60207	The Data Pool inventory validation function shall log at completion the total number of temp files that exceeded the maximum orphan age.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60210	The Data Pool inventory validation function shall log at completion the total amount of disk space that was freed up by the removal of orphans and phantoms.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60215	The Data Pool Cleanup Utility shall include the amount of space freed by the removal of orphans and phantoms in its determination as to whether to clear the 'NoFreeSpace' flag (that prevent Data Pool Inserts from dequeuing).	
DP_S3_04	Data Pool Validation	no data				S-DPL-60220	The Data Pool inventory validation function log entries shall include the date and time of the log entry (at least to the millisecond), and in case of parallel operation, an identification of each parallel execution.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60230	The Data Pool inventory validation function shall include the  pathname of all removed files in the corresponding log entry.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60240	The Data Pool inventory validation function shall log to the same log file that is used by the Data Pool Cleanup Utility by which it was invoked..	
DP_S3_04	Data Pool Validation	no data				S-DPL-60250	The Data Pool inventory validation function shall be able to perform orphan and phantom checking at the rate of at least 200,000 files per hour when there are no discrepancies between the data pool inventory and the data pool disks; and handle discrepancies at a rate of at least 1,000 per hour.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60260	If validation is interrupted by a fault, it must be possible to restart the validation by re-running the cleanup command and without affecting its ability to perform validation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60270	The Data Pool inventory validation function must be able to operate correctly when executing concurrently with Data Pool web and ftp accesses and Data Pool insert operations.  	
DP_S3_04	Data Pool Validation	no data				S-DPL-60280	The Data Pool Inventory Cleanup Utility must prevent concurrent operation of a cleanup with the validation function if this can cause incorrect or severely degraded operation.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60290	The Data Pool inventory validation function shall support multiple modes.	
DP_S3_04	Data Pool Validation	no data				S-DPL-60300	Different instances of the Data Pool inventory validation function shall be able to execute concurrently in different modes.	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-00500	The Data Pool FTP service shall provide a data compression capability upon data download.	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-00510	The Data Pool FTP service shall support the following data compression options to be applied to the data files upon download:    a. No Compression  b. Unix Compression  c. gzip Compression 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-00520	The Data Pool FTP service shall allow a user to specify a particular data compression option to be applied to individual or a group of data files upon download. 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-00530	The data compression options supported by the Data Pool FTP service shall be operator configurable. 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-00540	The Data Pool FTP log shall indicate whether or not compression was used for each data file transferred. 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-00550	The Data Pool FTP service shall log the length of time it takes for transferring each data file. 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-05700	The Data Pool Web access service shall provide a user interface for selecting data compression options for individual or a group of science data files upon data download.	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-05705	The data compression options provided by the Data Pool Web access service shall include the following:    a. No Compression (Default Option)  b. Unix Compression  c. gzip Compression 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-05710	The data compression options supported by the Data Pool Web access service shall be programmer configurable.	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-05720	The Data Pool Web access service shall not provide Unix or gzip compression option  for Browse and metadata files. 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-05725	The Data Pool Web access service shall submit data download requests to the Data Pool FTP service using appropriate compression options specified by the user. 	
DP_S3_08	Compression on Data Pool Download Service	no data				S-DPL-05730	a. The Data Pool Web access service shall allow users to choose specific compression option explicitly for each download activity.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43000	The Data Pool Service shall support the capability to represent the granules in the MISBR ESDT as both science granules and browse granules with discrete expiration settings.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43010	The Data Pool Service shall support browse associations between jpeg image files of the MISBR ESDT and granules from a configurable list of MISR ESDTs, the default set of which is identified as Level 1 and Level 2 in Listing 1 of this ticket.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43020	The Data Pool Insert Service shall maintain cross-reference information between each MISBR image file and all corresponding MISR science granules in the Data Pool database.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43030	The Data Pool Insert Service shall link a MISBR image file with a MISR Level 1 science granule based upon the following matching attributes, where such attributes exist: (a) Camera ID, Orbit ID and MISR product version.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43035	The Data Pool Insert Service shall use the MISR product version defined by the product specific attribute &quot;SP_AM_MISR_ProductVersion&quot; when linking a MISR image file with a MISR Level 1 science granule.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43040	The Data Pool Insert Service shall insert a MISR Level 1 science granule without a browse linkage, in the event that a MISBR granule with a matching Camera ID cannot be found.	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43050	The Data Pool Insert Service shall link a MISBR image file with the most recently inserted MISR Level 2 science granule based upon the following matching attributes, where such attributes exist: (a) Camera ID = &quot;AN&quot; and Orbit ID	
DP_S4_02	Support for MISR Browse in the Data Pool	no data				S-DPL-43060	The Data Pool Insert Service shall insert a MISR Level 2 science granule without a browse linkage, in the event that a MISBR granule with Camera ID = &quot;AN&quot; cannot be found.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15010	The Data Pool Cleanup Utility shall include those granules in the Data Pool cleanup that are in the list of deleted or re-versioned granules maintained by the SDSRV CI and also reside in the Data Pool, unless the cleanup run obtains the list of granules to be deleted from an input file.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15020	The Data Pool Cleanup Utility shall provide a command line option to only include the granules in the SDSRV list of deleted or re-versioned granules in the cleanup.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15030	The Data Pool Cleanup Utility shall not process granules in the SDSRV list of deleted or re-versioned granules in its cleanup run again that were processed before by a cleanup run that completed successfully.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15040	The Data Pool Cleanup Utility shall write to the log a.   The granule ID, short name, and version ID of each granule found in the SDSRV list of deleted or re-versioned granules that has been removed from the Data Pool b.   The total number of those granules that were removed	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15050	The Data Pool Cleanup Utility shall be able to cleanup the granules that are in the Data Pool and the SDSRV list of deleted or re-versioned granules table at the same rate as other granules; and shall not spend more than 1 minute in evaluating the ECS deleted granules table for every 5,000 granules it contains.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15060	The Data Pool Cleanup Utility shall be able to accept as input, the output of the SDSVR Granule Deletion Bulk Search Utility. (Note: The Data Pool Cleanup utility will cleanup any granules which are listed in that input and also reside in the Data Pool).	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15080	The Data Pool Cleanup Utility shall skip the processing of granules it was requested to cleanup but cannot find in the Data Pool.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DPL-15090	The Data Pool Cleanup Utility shall log skipped granules and the reason for skipping, except for granules that were deleted in ECS and skipped because they do not reside in the Data Pool.	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DSS-04586	The SDSRV CI shall be able to provide a list of deleted or re-versioned granules, i.e., of science or browse granules that have been logically deleted, deleted from archive (DFA), or re-versioned (i.e., whose collection version was updated). [NOTE: This list can be a portion of the contents of an SDSRV table that also tracks other granule related events]	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DSS-04587	The list of deleted and re-versioned ECS granules (logically deleted or DFA'ed) maintained by the SDSRV CI  shall contain the following information for each granule: a.   ECS dbid	
DP_S4_03	Propagation of ECS Granule Deletions to Data Pool	no data				S-DSS-04588	The SDSRV CI shall identify errors encountered in maintaining the list of deleted granules	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-00600	The Data Pool FTP Service shall be able to download the files created by the Most Recent Data Pool Insert Utility at the Data Pool top-level directory using anonymous FTP.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-00610	The Data Pool FTP Service shall be able to download the files created by the Most Recent Data Pool Insert Utility at each Data Pool collection level directory using anonymous FTP.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-00615	The Data Pool Cleanup Utility shall delete the files created by the Most Recent Data Pool Insert Utility that are older than 7 days.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70015	The Most Recent Data Pool Insert Utility shall create a file in the collection level anonymous FTP directory that contains a list of files inserted into the Data Pool on a specified date.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70017	The Most Recent Data Pool Insert Utility shall accept as a command line parameter the date specifying the date the file was inserted into the Data Pool. If a date is not provided, the previous day shall be used as a default with a time range of midnight to midnight	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70019	The file created at the collection level by the Most Recent Data Pool Insert Utility shall contain the Short Name, Version Id and file name including the full directory path from the current level.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70021	The Most Recent Data Pool Insert Utility shall accept a date in the format YYYY/MM/DD as input where MM is the two-digit month, DD is the two-digit day and YYYY is the four-digit year.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70023	The Most Recent Data Pool Insert Utility shall log an error message if the date format is incorrect.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70025	The file created by the Most Recent Data Pool Insert Utility shall include only the files inserted on the day specified on the command line.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70027	The Most Recent Data Pool Insert Utility shall create a file at the top level Data Pool directory that lists the unique Group Name, ShortName, and VersionID inserted on the day specified by the input date.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70029	The file created at the top level Data Pool directory shall be named DPRecentInserts_&lt;YYYYMMDD&gt;	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70031	The Most Recent Data Pool Insert Utility shall create a file at each Data Pool collection level directory that lists all of the files inserted for the Short Name and Version ID represented by the collection level directory inserted on the day specified by the input date.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70033	The file created at each Data Pool collection level directory shall be named DPRecentInserts_&lt;ShortName&gt;_&lt;VersionID&gt;_&lt;YYYYMMDD&gt;.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70035	The Most Recent Data Pool Insert Utility shall only permit one copy of itself to execute concurrently in a mode.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70037	The Most Recent Data Pool Insert Utility shall log an error message if there is an attempt to run more than one copy of the utility concurrently in a mode.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70039	The Most Recent Data Pool Insert Utility shall be able to execute concurrently in multiple modes.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70041	The Most Recent Data Pool Insert Utility shall overwrite a file if the file already exists.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70043	The Most Recent Data Pool Insert Utility shall be able to execute as part of a cron job.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70045	The files produced by the Most Recent Data Pool Insert Utility shall be produced within one hour while running under the workload specified in WL_S4_01 24-HR Data Pool Workload.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70047	The Data Pool Most Recent Inserts Utility shall not include order only granules in the listings of recent Data Pool inserts.	
DP_S4_04	Most Recent Data Pool Inserts	no data				S-DPL-70049	The Data Pool Most Recent Inserts Utility shall log an error message if the file can not be written	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66005	The Data Pool Service shall provide a command-line Collection-to-Group Remapping utility that permits operators to re-assign an existing Data Pool collection to a different collection group, whether or not the collection is empty.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66010	The Collection-to-Group Remapping  utility shall take as input: a. the name of the collection b. its current collection group id (for verification) c. the new collection group id	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66015	The Collection-to-Group Remapping utility shall verify that the collection and group names input on the command line are valid collection and group names in the Data Pool database, and shall exit with an explanatory error if not.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66020	The Collection-to-Group Remapping utility shall verify that the specified collection belongs to the collection group specified in the command line and shall exit with an error if it does not.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66025	The Collection-to-Group Remapping utility shall verify that the insertEnabledFlag is turned off for the specified collection, and, if not,  shall exit with a message asking the operator to use the Data Pool Maintenance GUI to set the collection as 'invalid for data pool' for the duration of the remapping operation.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66030	The Collection-to-Group Remapping utility shall verify that no other copy of the utility is running in the same mode, and shall exit with an explanatory error message if so.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66035	The Collection-to-Group Remapping utility shall not allow remapping of any collection to the BRWS group.  The utility shall exit with an explanatory error if an attempt is made to do so.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66040	The Collection-to-Group Remapping utility shall not allow the remapping of the Browse.001 collection to any group. The utility shall exit with an explanatory error if an attempt is made to do so. (Browse.001 is currently mapped to BRWS).	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66045	The Collection-to-Group Remapping utility shall update the collection-to-group mapping information in the Data Pool database to remap the collection to the new group.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66050	The Collection-to-Group Remapping utility shall  modify any affected Data Warehouse fact entries for all granules in the affected collection to reflect the new group association for the collection.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66055	The Collection-to-Group Remapping utility shall determine whether a directory for the new group exists on the Data Pool file system, and if not, it shall create one.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66065	When remapping a populated collection to a new group, the Collection-to-Group Remapping  utility shall relocate the collection directory (and its contents, including all subdirectories and any existing Most Recent Data Pool Inserts collection-level files) on Data Pool disk from the parent directory for the old group to the parent directory for the new group.   This relocation shall not involve physical movement of files. (It is assumed that remapping a Data Pool collection to a new group never involves moving the collection to a new file system.   If the operator wishes to move a collection to a new file system, the utility described in OP_S4_06 shall be used.)	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66070	The Collection-to-Group Remapping utility shall perform its remapping function in such a way as to preserve the validity of previously exported urls for Data Pool granules from the remapped collection. (e.g., urls exported to ECHO, EDG, Order Manager).	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66075	The Collection-to-Group Remapping  utility shall update the file entries in the Data Pool inventory for all granules in the affected collection, to reflect the new parent directory.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66080	The Collection-to-Group Remapping  utility shall be able to detect and recover from an aborted utility run.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66085	The Data Pool Service shall ensure that the remapping of collections to new groups shall not result in fatal insert errors for granules in the remapped collection while the collection is being remapped.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66090	The Data Pool Web Access GUI shall prevent drill down on a collection while the collection is being remapped,  if web access to the granules in the collection during the collection remapping would result in an error.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66095	The Data Pool Service shall ensure that the remapping of collections to new groups shall not result in missed granule deletions by Data Pool utilities (i.e., Cleanup, EcDlGetGranIds) while the collection is being remapped.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66100	The Collection-to-Group Remapping utility shall write the following information to a log file: a. the name of the collection being remapped b. the old parent group c. the new parent group d. the time the utility was invoked f. the time the utility completed the remapping operation g. the fact that a new group level directory was created, if it was i. any errors encountered Log entries shall be timestamped to the millisecond.	
DP_S4_05	Allow Operators to Update Data Pool Collection to Group Mappings	no data				S-DPL-66105	The Collection-to-Group Remapping utility shall remap granules in the affected collection at a minimum rate of 18000 granules per hour (i.e., 5 granules per second).	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-23520	The Data Pool Insert Service shall support the ability to replace ECS science granules and their associated metadata and browse files in the Data Pool.  An ECS granule being inserted into the Data Pool is eligible to replace an existing Data Pool granule if the replacement granule has the same ShortName, VersionId, and Acquisition Date as the original granule, AND also at least one of the following: a. same Data Pool file name as the original granule (Note that the Data Pool file name is the LocalGranuleId from the SDSRV DsMdGranules table, if present; otherwise, the Data Pool file name is the userDataFile name in the SDSRV DsMdFileStorage table.) b. same RangeBeginningTime as the original granule	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-23522	The Data Pool Insert Service shall allow operators to configure whether or not to allow replacement of ECS granules in the Data Pool.	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-75600	The Data Pool Insert Utility shall allow eligible ECS science granules to replace existing ECS science granules in the Data Pool if and only if the Data Pool configuration parameter to allow replacements has been turned on.	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-75602	If the replacement configuration parameter is turned OFF, the Data Pool Insert Utility shall use the current default rules for inserting granules, i.e., a. if  a new granule has the same shortname AND same versionid AND same acquisition date as an existing granule, AND the new granule has the same Data Pool file name as an existing granule , the new granule is rejected as a duplicate; and if a new granule has the same shortname AND same versionid AND same acquisition date as an existing granule, AND the new granule has a different Data Pool file name than the existing granule, the new granule is inserted into the Data Pool, and the old granule also remains in the Data Pool	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-75604	When replacing an ECS science granule, the Data Pool Insert Utility shall remove any existing metadata and science files associated with the original granule, and then insert the appropriate science and metadata files associated with the replacement granule.	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-75606	When replacing an ECS science granule, the Data Pool Insert Utility shall remove all links between the original science granule and any existing browse file(s) associated with this granule in the Data Pool, and shall remove the associated browse file(s) themselves from the Data Pool if they are not associated with any other Data Pool granule.  If the replacement granule has associated browse file(s) (in SDSRV), the Data Pool Insert Utility shall insert these file(s) if they are not yet  in the Data Pool, and shall link them with the replacement granule.	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-75608	When replacing an ECS science granule, the Data Pool Insert Utility shall replace the Data Pool database inventory information for the existing granule with that for the new granule.	
DP_S4_06	Allow Overwrites of Data Pool Inserts	no data				S-DPL-75610	The Data Pool Insert Utility shall log the fact that it is replacing a science granule in the Data Pool.  The log entry shall contain: a. the Data Pool granuleId of the original granule b. the ShortName and versionId of the replacement granule c. the AcquisitionDate of the replacement granule d. the ECS id of the replacement granule e. the reason for the replacement (e.g.,same Data Pool file name; same RangeBeginningTime) f. the insert time g. the fact that associated browse file(s) were unlinked and/or removed	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75010	The Data Pool Maintenance GUI shall allow full capability operators to maintain a list of compression algorithms which may be employed during Data Pool inserts.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75015	For each compression algorithm, the Data Pool Maintenance GUI shall require full capability operators to specify the following information: a. unix command line which runs the compression algorithm (must include sufficient path information to locate the compression algorithm on the x0dps01 host) b.optional default output file name extension c. unix command line which runs the corresponding decompression algorithm, or an indication that no decompression algorithm is necessary	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75020	The Data Pool Maintenance GUI shall allow full capability operators to associate a compression algorithm with a Data Pool collection (both ECS and nonECS collections) by choosing the compression algorithm from a list of predefined compression algorithms.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75025	The Data Pool Maintenance GUI shall allow full capability operators to associate no more than one compression algorithm with a Data Pool collection.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75030	The Data Pool Maintenance GUI shall allow full capability operators to disassociate a compression algorithm from a Data Pool collection.  This disassociation shall only affect future inserts of Data Pool granules in the collection; information about the compression algorithm (and corresponding decompression algorithm) associated with existing granules in the Data Pool shall be preserved.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75035	The Data Pool Maintenance GUI shall allow full capability operators to update information about a compression algorithm. If an operator chooses to update information about a compression algorithm, the Data Pool Maintenance GUI shall warn the operator that updates of the compression algorithm command line and the default output file name extension will only affect future inserts of Data Pool granules in collections associated with the compression algorithm, and that updates of the decompression algorithm command line will affect current Data Pool granules associated with the compression algorithm, as well as future inserts of Data Pool granules in collections associated with the compression algorithm.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75040	The Data Pool Maintenance GUI shall allow full capability operators to remove a compression algorithm from the list of valid Data Pool compression algorithms. (Note:  'validcompression algorithm' refers to the complete corresponding command line sequence; i.e., '/&lt;gzippath&gt;/gzip -1  %infile' is a different valid compression algorithm than '/&lt;gzippath&gt;/gzip -3  %infile', even though both use gzip.)  If any collections are associated with the compression algorithm to be removed, the Data Pool Maintenance GUI shall display the list of collections associated with the compression algorithm, and shall request the operator to confirm removal of the compression algorithm.   If the operator confirms removal, the compression algorithm shall no longer be displayed on the list of valid compression algorithms, and all of its associations to Data Pool collections shall be removed.  This disassociation shall only affect future inserts of Data Pool granules in the affected collections; information about the compression algorithm (and corresponding decompression algorithm) associated with existing granules in the Data Pool shall be preserved.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75045	The Data Pool Maintenance GUI shall allow full capability operators to turn compression ON and OFF.   (NOTE: Turning compression OFF has no effect on existing compressed files in the Data Pool.)	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75050	If compression is turned OFF, the Data Pool Insert Utility shall ignore any compression specifications associated with Data Pool inserts.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75055	If compression is turned ON, the Data Pool Insert Utility shall determine, prior to inserting a granule, whether a compression algorithm is specified for the collection to which the granule belongs.  If so, the Data Pool Insert Utility shall invoke the compression algorithm's command line sequence when inserting each of the science files associated with the granule.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75060	When invoking a compression algorithm during insert, the Data Pool Insert Utility shall substitute the full path name of the file to be compressed for the input file command line parameter.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75065	When invoking a compression algorithm during insert, the Data Pool Insert Utility shall expect the compression algorithm to return the compressed file, with the correct compression extension appended to the original file name, in the same directory in which the Data Pool Insert Utility placed the original file to be compressed.  If there is no compression extension on the compressed file, the Data Pool Insert Utility shall recognize that the original file has been overwritten by the compressed file.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75070	When invoking a compression algorithm during insert, the Data Pool Insert Utility shall insert the compressed file returned by the compression algorithm into the same permanent Data Pool directory as it would otherwise use if the files were to be inserted without compression.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75075	When invoking a compression algorithm during insert, the Data Pool Insert Utility shall remove the original file from the compression algorithm's input file directory after successful completion of the compression algorithm, unless the original file has been overwritten by the compression algorithm.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75080	When invoking a compression algorithm during insert, the Data Pool Insert Utility shall enter the following information in the file table in the Data Pool database: a. name of the compressed file b. size of the compressed file c. size of the original uncompressed file d. unique identifier of compression algorithm used e. elapsed time required to compress the file, in seconds	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75085	The Data Pool Insert Utility shall interpret a status code of 0 returned from the compression algorithm as success, and a non-zero status code returned from the compression algorithm as failure.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75090	The Data Pool Insert Utility shall fail non-retriably the insert of a granule if the compression of any of its files returns a non-zero status code.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75095	The Data Pool Insert Utility shall fail retriably the insert of a granule if it does not find the output file in the expected directory with the expected name.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75100	The Data Pool Insert Utility shall fail non-retriably the insert of a granule if the compression command line sequence fails because the compression algorithm is not visible to the Data Pool Insert Utility.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75105	If the Data Pool Insert Utility performs checksumming for a file that is compressed on insert, the Data Pool Insert Utility shall compute the checksum of the compressed file and store the result in the Data Pool database.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75110	If the Data Pool Insert Utility performs checksumming for a file that is compressed on insert, the Data Pool Insert utility shall continue to compute the checksum of the uncompressed file, verify its checksum against the checksum of the input file, store the checksum of the uncompressed file, and report on any errors.  (See NCRs 37304 and 36028)	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75115	The Data Pool Insert Utility shall not invoke a compression algorithm when inserting metadata or browse files in the Data Pool, no matter whether compression is turned ON or OFF.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75120	The Data Pool Web Access GUI shall not display compression options for downloading individual granules which were compressed at Data Pool insert time.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75125	If a granule displayed on the Data Pool Web Access GUI results page or shopping cart page was compressed at Data Pool insert time, the Data Pool Web Access GUI shall display for that granule: a. an indication that the granule is stored in compressed format	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75130	The Data Pool Web Access GUI shall allow compression operations on all granules in the shopping cart, regardless of whether any individual granules in the shopping cart were already compressed at Data Pool insert time.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75135	The HEG Front End shall decompress files which were compressed at insert time before converting them, using the decompression algorithm provided by the DAAC.  If no decompression algorithm is provided, the HEG Front End shall assume that decompression is not necessary.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75140	The Data Pool FTP Service shall allow downloading of Data Pool files which were compressed at Data Pool insert time.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75145	The Data Pool FTP Service shall not fail on-the-fly compression of Data Pool files regardless of whether the files were already compressed at Data Pool insert time.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75150	The background checksum utility (see NCR 37304) shall use the checksum of the 'as stored' file when comparing to the current checksum.	
DP_S4_07	Support Compression on Data Pool Insert	no data				S-DPL-75155	When invoking a compression algorithm during insert, the Data Pool Insert Utility shall log the following information: a. the time required to compress a file (in seconds) b. the time required to checksum the compressed file (in seconds), if checksumming is performed c. the compression algorithm command line used, including the name of the input file d. the directory path and filename of the compressed file returned by the compression algorithm e. the status code returned from the compression algorithm f. any errors encountered in running the compression algorithm	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40510	The Data Pool Database shall support group ids of up to 12 characters.	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40520	The Data Pool Database shall support the association of a display name of up to 12 characters with each Data Pool group.	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40530	The Data Pool Maintenance GUI shall support the use of group ids of up to 12 characters when performing operations with groups (e.g., adding new groups, displaying group ids).	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40535	The Data Pool Maintenance GUI shall support the following set of valid characters in group ids: A-Z (upper case only), 0-9, and underscore. (NOTE:  This requirement replaces requirement S-DPL-41132 in Ticket DP_S3_02 (Accommodate NonECS Data in Data Pool), which states: 'The Data Pool Maintenance GUI shall verify that the name of a data collection group obeys the following rules and reject the definition if it does not: a. The name consists entirely of upper case letters. b. The name is no more than four characters in length.'	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40540	The Data Pool Maintenance GUI shall allow full capability operators to enter a unique 'display name' of up to 12 characters when creating a Data Pool group.   If no display name is entered, the group id shall be stored as the default display name in the Data Pool database.	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40545	The Data Pool Maintenance GUI shall support the following set of valid characters in display names: A-Z(upper case only), 0-9, underscore, and blank.	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40550	The Data Pool Maintenance GUI shall allow full capability operators to update the 'display name' of  a Data Pool group.	
DP_S4_08	Lengthen Data Pool Group ID	no data				S-DPL-40560	The Data Pool Web Access GUI shall use a group's display name when displaying the group identifier, either as a drill down choice or when displaying previously selected Data Group drill down criteria.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65010	The Data Pool CI shall provide a QA Update Propagation Utility that is executable via a Unix command line.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65020	It shall be possible to combine the Data Pool QA Update Propagation Utility and the QAMUT utility into a single script that can be executed as a cron job.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65030	The Data Pool QA Update Propagation Utility shall accept as input information created by the QAMUT CI that identifies its ECS QA flag updates.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65040	The Data Pool QA Update Propagation Utility shall apply the ECS QA flag updates to the affected Data Pool inventory database entries.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65050	The Data Pool QA Update Propagation Utility shall apply the ECS QA updates to the affected Data Pool metadata files at a rate of no less than 18,000 files per hour.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65060	The Data Pool QA Update Propagation Utility shall apply  QA updates to the Data Pool inventory database at a rate that is no less than the SDSRV QA update rate achieved by the QAMUT.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65070	The Data Pool QA Update Propagation Utility shall be able to recover from a failure such that the application of the QA updates can be completed without error (e.g., by restarting the corresponding Data Pool utility) and without incurring a performance penalty of more than 10 minutes.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65080	The Data Pool QA Update Propagation Utility shall be able to operate in multiple modes concurrently.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65090	The Data Pool QA Update Propagation Utility shall prevent multiple concurrent executions in the same mode.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65100	The Data Pool QA Update Propagation Utility shall log the following information. a. any command line parameters b. any errors.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65110	The Data Pool QA Update Propagation Utility shall skip the update of an XML file that proves inaccessible and continue the execution of the run, but log this event as an error.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DPL-65120	The Data Pool QA Update Propagation Utility shall retry in subsequent runs the propagation of a QA update that was skipped due to an error in an earlier run.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DSS-40355	The QAMUT CI shall be able to recover from a failure while performing or recording its QA updates such that a correct record of the QA updates can be provided without error (e.g., by restarting the QAMUT) and without incurring a performance penalty of more than 10 minutes.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DSS-40410	The QAMUT CI shall provide a record of its QA updates that can be used by the DPL subsystem to propagate the applicable updates to the Data Pool inventory and metadata files.	
DP_S4_09	Propagation of QA Updates to the Data Pool	no data				S-DSS-40420	The QAMUT CI shall be able to provide a record of its QA updates to the DPL subsystem in multiple modes concurrently.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00700	The AOG shall support concurrent registration of WCS and WMS data locations and corresponding metadata.  The number of allowed concurrent registration processes shall be logged at startup. [NOTE: This means that we should have a configuration parameter that controls the number of active WCS/WMS registrations/unregistrations.  The data location information and the path to the WCS/WMS metadata XML files shall be included in an AOG registration XML file.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00710	The AOG shall reject block registration requests if the configured number of concurrently running registrations is exceeded. [NOTE:  this applies to the AOG java client API registration method that provides a synchronous interface to the AOG.  For polling registrations, the AOG will only execute polling requests when registration slots are available.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00720	The AOG shall support a configurable location for an OWS polling area.  If no polling area is configured, the AOG shall not create a polling thread and shall only respond to requests from clients using the AOG Java Client API. [NOTE:   the polling area will contain AOG registration XML files for the data being registered.  For clients using the AOG Java client API the AOG polling area should not be configured.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00730	The AOG shall have a configurable polling interval specified in seconds.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00740	The AOG shall log the following events pertaining to polling and registration:     When polling occurs:   timestamp  active registration slot count  free registration slot count    When registration occurs:             timestamp  active registration slot count  free registration slot count  registration type  xml file name     When registration completes:   timestamp  active registration slot count  free registration slot count  registration type  xml file name  registration exit status    	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00750	The AOG shall FAIL the registration of a resource with an invalid or badly formed AOG registration XML file and shall log an error message describing the error cause.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00760	The AOG shall FAIL the registration of a resource with invalid or badly formed OWS metadata XML files and shall log an error message describing the error cause. [NOTE:  the AOG registration XML file must have references to the location of the WCS/WMS metadata XML files in addition to the actual data files.  XML validation functionality shall be configurable at the AOG level.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00770	The AOG shall FAIL to register data locations for which it has no direct access or read permissions and shall log an error message describing the error cause. [NOTE:  data location information must be included in the AOG XML file.] 	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00780	The AOG shall FAIL polling registrations if the data location information is identical to the polling area location. [NOTE:  this enforces the use of a separate polling area.  There is no restriction on where the data can be stored outside the polling area, as long as the AOG and OWS engine have direct access to it.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00790	The AOG shall register with the OWS inventory the data locations and metadata files placed into the polling area. [NOTE:  the OWS engine will be aware of the registered holdings because the registration makes them part of its inventory.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00800	The AOG shall provide resource unregistration services that will remove all references to the resource being registered from the OWS inventory. [NOTE:  The unregistration operation will be initiated via an AOG unregistration XML file that is placed in the AOG polling area or via a Java Client Unregistration API.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00810	The AOG unregistration service shall not remove resource data files unless specifically indicated in the AOG XML unregistration file. [NOTE: this guards against accidental deletions and is especially useful if data has been registered in its original location.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00850	The AOG shall offer a suite of OWS resource registration/unregistration interfaces via its AOG Java client API. [NOTE:  The initial implementation will allow an AOG interface that specifies the location of the AOG registration / unregistration XML file.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00860	The AOG Java client API registration routine shall register data locations. [NOTE:  we assume that data is already at its desired location, in the OWS storage area or the data provider in-house archive.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00870	The AOG Java client API metadata registration shall support the following mode of registration:   all attributes at once via an XML file (the OWS data provider will have to generate the AOG registration XML file from the metadata values available).    	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00880	The WCS implementation shall comply with OGCs WCS 1.0.0 specification. [NOTE: A minimum subset of services will be supported in this release.  The WCS implementation shall support spatial and temporal subsetting.  Emphasis will be placed on easy integration of new services as opposed to current support of many services.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00890	The WCS implementation shall support HTTP GET requests with Keyword  Value pair encoding. [NOTE:  XML encoding via HTTP POST or GET requests will not be supported in this release.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00900	The WCS implementation shall support a configurable  Service  section of the WCS XML capabilities document. [NOTE:  the XML capabilities document is the response to a WCS GetCapabilities request.  The Service section will be configured for a given WCS instance.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00910	The WCS implementation shall support a configurable  Capability  section of the WCS XML capabilities document. [NOTE:  the XML capabilities document is the response to a WCS GetCapabilities request.  The Capability section will be configured for a given WCS instance.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00920	The  ContentMetadata  section of the XML capabilities document shall contain a sequence of CoverageOfferingBrief elements, one for each coverage. [NOTE:  this implementation of the WCS will not provide access to an image catalog, so if the OWS data provides chooses to OWS enable large amounts of data, the WCS GetCapabilities call might take a long time to generate.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00930	The WCS implementation shall provide a configuration parameter that indicates the maximum number of WCS coverages that are allowed in the WCS Capabilities XML file.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00940	The WCS implementation shall provide a configurable URL to be included in the WCS capabilities document when the number of registered resources exceeds the values of the configured parameter indicating the maximum number of allowed coverages in the XML file. [NOTE:  the URL can be a vendor specific catalog which provides search capabilities are allows the user to determine the name(s) of the coverage(s) of interest.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00950	The WCS implementation shall allow publication and retrieval of FGDC/ISO19115 coverage metadata. [NOTE:  this will be supported via the optional metadataLink child node of CoverageOfferingBrief element.  The implementation will record and provide the specified metadataLink value without any validation.  It is the data providers responsibility to make the metadata available at the specified location.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00960	The data holdings newly registered via AOG shall appear in the XML capabilities document without the need of an OWS engine restart. [NOTE:  this means that the OWS engine will need a mechanism to generate the capabilities document on the fly or update its memory cached capabilities DOM tree periodically so it is in sync with the back end mySQL database.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00970	The WCS implementation shall provide a DescribeCoverage operation that accepts at least one coverage name as a request parameter.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00980	The WCS implementation shall support the EPSG:4326 (European Petrol Survey Group) / WGS84 (World Geodetic System 1984) as its request, response and native CRS (Coordinate Reference System). [NOTE:  data provider specific CRSs will be allowed, but no transformations will be provided in the initial implementation.  Emphasis will be placed on easy integration of coordinate transformations as opposed to current support of many coordinate systems and transformations.  The EPSG:4326 and the WGS:84  are equivalent CRS and they are geographic CRS with coordinates specified in decimal longitude and latitude, e.g. BBOX(-81.695,41.491,-81.681,41.499.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-00990	The WCS implementation shall support the following output format:   GeoTIFF   [NOTE:  It is assumed that the data provider converts its data holdings to GeoTIFF before they register it with the AOG.  It will not be possible to obtain services on data that is not in GeoTIFF format.  However, there will be no explicit limitation of other native format support like HDF-EOS, DTED, NITF, GML.  The important part is that the native formats will be also the output formats without any applied services in this release regardless of what output format will be requested via the GetCoverage request.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01000	The WCS shall only serve data in the format in was registered under. [NOTE:  no output format conversions will be added in this release.  Emphasis will be placed on easy addition of new services as opposed to current support for various output formats.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01010	The WCS implementation shall support at a minimum the none interpolation method. [NOTE:  since emphasis will be placed on easy integration of new services, the possibility of creating hooks for integrating various interpolation methods will also be investigated.  This also means that only the full native resolution of the data will be returned.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01030	The WMS implementation shall comply with OGCs WMS 1.1.1 specification. [NOTE: the WMS 1.3.0 will also be considered.  It was determined via consultations with GIO that 1.1.1 should be implemented, based on its potentially wider client audience and the 1.3.0 incompatibility with the CITE test engine.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01040	The WMS implementation shall support HTTP GET requests with Keyword  Value pair encoding. [NOTE:  XML encoding via HTTP POST or GET requests will not be supported in this release.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01050	The WMS implementation shall support a configurable  Service  section of the WMS XML capabilities document. [NOTE:  the XML capabilities document is the response to a WMS GetCapabilities request.  The Service section will be configured for a given WMS instance.  There will be different service sections for WMS and WCS.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01060	The WMS implementation shall support a configurable  Capability  section of the WMS XML capabilities document. [NOTE:  the XML capabilities document is the response to a WMS GetCapabilities request.  The Capability section will be configured for a given WMS instance.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01070	The WMS implementation shall allow publication and retrieval of FGDC/ISO19115 map metadata. [NOTE:  this will be supported via the optional MetadataURL child node of Layer element in the WMS Capabilities document.  The implementation will record and provide the specified MetadataURL value without any validation.  It is the data providers responsibility to make the metadata available at the specified location.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01090	The WMS implementation shall support the following output image formats:   jpg  png  	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01110	The WMS implementation shall support spatial subsetting (data cropping) on specific layers. [NOTE:  this refers to the noSubsets attribute value of 0 for the layers where cropping can be performed.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01120	The WMS implementation shall support different pixel resolutions, other than the native one for specific layers. [NOTE:  this refers to the fixedWidth and fixedHeight values of 0 for layers where other resolutions can be requested.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01140	The DAAC OWS utility shall provide WCS and WMS registration types.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01150	The DAAC OWS utility shall provide a configuration parameter that points to the OWS dedicated storage area. [NOTE:  OWS_ROOT should point to the OWS dedicated storage area that is directly accessible from the host where the prototype is running.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01160	The DAAC OWS utility shall accept the full path of a file containing a list of DPL granulesIDs to be OWS enabled as an input parameter. [NOTE: the granules being registered have to be present in the DPL inventory as ECS or NON-ECS data.  For both ECS and NON-ECS data the implicit registration is WCS.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01170	The DAAC OWS utility shall log an error message for each granule that is present in the input file but not present in the DPL inventory.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01180	For each granule being registered, the DAAC OWS utility shall generate an AOG registration XML file and place it in the AOG polling area. [NOTE:  the AOG registration XML file is used by AOG to register coverages and layers.  It contains references to the WCS and WMS specific metadata, data location and other registration specific data.  The AOG_POLLING_AREA shall be a configuration parameter for the DAAC OWS utility.  For testing purposes, the AOG can be configured to back up the registration files for later reference.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01190	The DAAC OWS utility shall generate the WCS DescribeCoverage XML file for WCS registrations. [The WCS_1.0.0_ DescribeCoverage.xsd schema is used to describe a WCS coverage.  The XML file will be validated against the schema.  For the GSFC deployment, the XML file shall be generated by parsing the pertinent metadata from the existing Data Pool XML file.  The path to the generated WCS XML file will be placed in the AOG XML file.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01200	The DAAC OWS utility shall generate the WMS Layer XML file for WMS or WMS/WCS registrations. [The WMS_1.1.1_Layer_Section.xsd schema is used to describe a registered WMS layer.  The XML file will be validated against the schema.  For the GSFC deployment, the XML file shall be generated by parsing the pertinent metadata from the existing Data Pool XML file.  The path to the generated file will be placed in the AOG XML file.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01210	The DAAC OWS utility shall convert HDF-EOS data files to the GeoTIFF format. [NOTE:  for NON-ECS data if the granule data file format is already GeoTIFF, the conversion should be skipped.  The OG_S5_06  Deploy DOWS work already provides HDF-EOS to GeoTIFF conversion functionality that will be reused in the standalone OGC archive. The GeoTIFF format has been chosen as the WCS supported format.  The DOWS conversion utility has an XML configuration file that determines the type of GeoTIFFs to be created for each supported ESDT.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01220	The DAAC OWS utility shall place the converted data files in the OWS dedicated storage area if the conversion is needed. [NOTE: the scheme under which the files will be stored in the OWS_ROOT area is based on a OWS_ROOT/data directory organized by date, so that all data that was OGC-enabled in a single day resides in the same area.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01230	The DAAC OWS utility shall FAIL the creation of the AOG registration XML file if any of the existing files in the OWS dedicated storage area would be overwritten. [NOTE: this prevents accidental overwrites of files (GeoTIFFs, WCS/WMS metadata etc.) that belong to resources already registered.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01240	The DAACS OWS utility shall place the full path and filename for the data files being registered in the AOG registration XML file. [NOTE:  we are in fact registering data file locations.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01250	The DAAC OWS utility running in 'Unregistration' mode shall accept as an input parameter a full path and filename of a file containing the resource IDs or DPL granuleIds of the OWS resources to be unregistered.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01260	The DAAC OWS utility running in Unregistration mode shall accept an input parameter that specifies if the data files for the resources being unregistered should also be removed from disk.  The default behavior should be to NOT remove the data files. [NOTE:  the default behavior protects from accidental deletion of data files that reside outside the dedicated OWS storage area and are part of the active inventory of other archiving systems. 	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01270	The DAAC OWS utility running in Registration mode shall accept a file name and path of a file containing a list of GeoTIFF files and associated metadata in the DPL XML format. [NOTE:  this allows registration of coverages that do not exist in the DPL (or ECS) inventory.  It also provides for a testing mechanism that decouples the system from a live datapool instance.]	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01280	The DAAC OWS utility shall allow a configurable path for a local HEG or HEG like utility. [NOTE:  if the LOCAL_COVERSION_UTILITY config parameter exists, the local HEG or HEG like utility shall be used.  If the parameter is not present a CONVERSION_HOST and CONVERSION_PORT set of parameters will dictate how to invoke remote HEG functionality via it new SYN V service API.	
DP_S5_01	Support a Standalone OGC (WCS/WMS) Archive	no data				S-OWS-01290	The standalone OGC enabled archive shall use the ESG integration mechanism defined for HTTP WCS/WMS service providers to register its OpenGIS Web Services (WMS and WCS).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-BGT-21000	The BMGT CI shall not export the Data Pool URLs of granules that are not yet registered in the SDSRV inventory.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-BGT-21010	The BMGT CI shall not export the Data Pool URLs of granules prior to the export of the granule inventory information.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-BGT-21020	The BMGT CI shall not include browse granules in the ECSBBR product until they have been copied to the archive. [NOTE: The ECSBBR granule includes the internal files names of the browse granule.  ECSBBR orders assume that the browse granules can be simply copied from the STMGT disk archive location.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16010	The Data Pool Ingest GUI shall allow multiple operators to monitor and manage Data Pool ingest concurrently from different workstations.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16020	The Data Pool Ingest Service shall support concurrent operation in multiple modes on the same and different hosts.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16030	The Data Pool Ingest GUI shall support monitoring and managing concurrent Data Pool ingest in multiple modes on the same and different workstations. [NOTE: However, a single instance of the GUI will support one and only one mode.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16040	The Data Pool Ingest GUI shall display the mode in which it is operating.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16050	The Data Pool Ingest GUI shall be compatible with the EMD baseline versions of web browsers and operating systems in accordance with Technical Document 910-TDA-042-Rev01, EMD Browsers Baseline.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16060	It must be possible to protect Data Pool Ingest GUI against external access via appropriate configuration of the ECS firewall.  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16070	The Data Pool Ingest GUI shall permit authorized operators (security admin operators) to define the authorizations for each operator that shall apply when that operator uses the Data Pool Ingest GUI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16080	The Data Pool Ingest GUI shall support at a minimum, an authorization and login scheme which allows DAAC operations to distinguish between operators that have view only permissions (view-only operators), operators than can manage ingest requests, e.g., update them or disposition interventions (ingest control operators), those that can alter general configuration parameters (ingest admin operators), those that can alter tuning parameters (ingest tuning operators), and those that can maintain the security information (security admin operators). [NOTE: A map of the GUI capabilities to the authorization levels is part of the PDR materials and reflected in the Level 4 requirements.  It is understood that wherever requirements do not mention a specific authorization requirement, any operator is authorized to perform the function, including view-only operators ]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16085	The Data Pool Ingest Service shall allow a DAAC to disable the authorization scheme, thereby making login optional and giving all operators full rights to view and manage requests and configuration information.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16090	The Data Pool CI shall include measures to prevent the access to temporary files located in the Data Pool by external users, e.g., via anonymous ftp.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16091	The Data Pool CI shall include measures to prevent the access to granules located in the non-public Data Pool directories by external users, e.g., via anonymous ftp, EDG, or ECHO. [NOTE: This includes making the corresponding directories inaccessible to anonymous ftp, preventing the export of granule URL, and not making these granules visible to Data Pool web users.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16095	The Data Pool Ingest Service shall behave like the current ingest from an external system perspective, in terms of PDR validation, error checking, notifications of errors and successful ingest operations, and so forth. [NOTE: The requirement is not subject to direct integration testing.  Rather, the requirements in this document formally capture this behavior and by integration testing those requirements, this requirement is tested indirectly. However, when there is a conflict between backwards compatible behavior at the external interface and the stated requirements, the former overrules any requirements and the offending requirement will need to be updated.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16100	The Data Pool CI shall maintain configuration information, e.g., about data providers, that is also applicable to the INGST CI such that changes made using the INGST GUI or the DPL Ingest GUI can be used by both CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16110	The Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) data providers for Data Pool Ingest, including the following information: a. provider name, b. whether the provider must supply a checksum with each science file, c. the percentage of files from that provider whose checksum must be verified during ingest as an integer number between 0 and 100, d. a valid priority to be assigned to an ingest request from that provider by default, e. a valid notification method to be used to notify that provider of ingest errors and completed ingest operations, f. user name and password needed to perform polling and retrieve the files that need to be ingested, if access is via FTP or scp, g. whether to use active or passive mode in case ftp is used, or scp type and cipher in case of scp usage. [NOTE: It will not be possible to mix ftp/local copy with scp for a single provider. For example, if a provider is configured to use scp, it is assumed that polling and file transfers will use scp and that notifications will use scp or e-mail.] h. the maximum number of granules that may be active for the provider at the same time and the maximum amount of data these granules may contain [NOTE: these parameters match the corresponding provider thresholds, except that the provider threshold for the number of requests was replaced by one for the number of granules,]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16130	The Data Pool Ingest Service shall support a priority range from 0 to 255.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16140	The Data Pool Ingest Service shall provide a mapping of existing ECS priorities to numerical priorities, compatible with the mapping used by the Order Management Service.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16150	The Data Pool Ingest GUI shall allow an authorized (ingest admin) operator to configure (i.e., enter and edit) the following notification methods: a. FTP b. scp c. e-mail d. a combination of (FTP or scp) and e-mail	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16160	The Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) for a provider that uses FTP notification, the related FTP information, i.e., either a reference to a previously defined FTP host or by now defining the FTP host parameters as per S-DPL-16260, the directory into which to place the notification, and the login information.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16170	The Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) for a provider that uses e-mail notification, the e-mail address to which notifications shall be sent.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16180	The Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to configure (i.e., enter and edit) for a provider that uses secure copy notification, the related scp information, i.e., scp host, directory, and login information. [NOTE: scp type and cipher are defined only once per provider and their entry is covered in S-DPL-16110.].	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16200	The Data Pool Ingest GUI shall permit an authorized (ingest admin) operator to remove a data provider provided that the provider is no longer referenced by other configuration information (i.e., polling locations) nor by ingest requests or notifications that are not in a terminal state.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16210	The Data Pool Ingest GUI shall prompt operators for confirmation before removing providers.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16230	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to configure (i.e., enter and edit) polling locations for data providers including the following information for each: a. a name for the polling location, b. polling frequency, expressed as number of seconds no less than 120, c. a valid polling method, d. DELETED, e. for each polling location that is accessed via local polling, the pathname to the local directory that must be polled, f. for each polling location that is accessed via FTP, the related FTP information, i.e., either a reference to a previously defined FTP host or by now defining the FTP host parameters as per S-DPL-16260, and specifying the directory that contains the polling information, g. for each polling location that is accessed via scp, the related scp information, i.e., either a reference to a previously defined scp host, or by now defining the scp host as per S-DPL-16290, and specifying the directory that contains the polling information, h. whether the polling location is enabled for Data Pool ingest [NOTE: a polling location is not accessed for polling purposes unless it is enabled].	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16240	The Data Pool Ingest GUI shall reject the definition of a duplicate polling location, i.e., polling location that uses the same name or the same host and directory as an existing one, including configuring the same host and directory for more than one provider.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16242	The Data Pool Ingest GUI shall prompt the operator to confirm any configuration definitions and changes for providers and polling locations before saving them.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16250	The Data Pool Ingest Service shall support the following polling methods: a. Accessing a remote polling location via FTP or scp, b. Accessing disk storage accessible locally or via nfs via a Unix copy operation.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16255	The Data Pool Ingest GUI shall permit authorized (ingest tuning' and ingest admin) operators to configure (i.e., enter and edit) the following set of Data Pool Ingest tuning configuration parameters for access to local hosts for polling and data transfer: a. the maximum number of concurrent file transfers involving local hosts (excluding polling and notifications), b. whether the local polling, file transfer and transfer of notifications will be timed out, c. if so, parameters used to time out these operations, consisting of the minimum expected throughput (in MB/second) plus an additional wait time in seconds, to be used to identify stuck operations [NOTE:  That is, an operation is considered timed out if its duration exceeds (file size/expected throughput) + wait time], d. Whether local polling and file and notification transfers are subject to automated retry when suspended, and if so, the time interval (in minutes) between automatic retries.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16260	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to configure (i.e., enter and edit) the FTP hosts accessed by the Data Pool Ingest Service, and for each the following set of FTP host parameters: a. a label used by Data Pool Ingest GUI to identify the host, b. host name or ip address	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16261	The Data Pool Ingest GUI shall permit authorized (ingest tuning' and ingest admin) operators to configure (i.e., enter and edit) the following set of FTP tuning parameters for each configured FTP host: a. the maximum number of concurrent FTP operations allowed for that host, b. whether the FTP operations for the host will be timed out c. if so, parameters used to time out FTP transfers, consisting of the minimum expected throughput (in MB/second) plus an additional wait time in seconds, to be used to identify stuck FTP operations. [NOTE:  That is, an FTP transfer is considered timed out if its duration exceeds (file size/expected throughput) + wait time.] d. Whether the host is subject to automated retry when suspended, and if so, the time interval (in minutes) between automatic retries.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16265	The Data Pool Ingest GUI shall reject the definition of a duplicate FTP host, i.e., a host that uses the same label as another host or the same ftp host name or ip address as an existing ftp host.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16267	The Data Pool Ingest GUI shall prompt the operator to confirm any configuration definitions and changes for FTP hosts.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16270	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) a set of default values for FTP tuning parameters to be used for FTP hosts for which no host parameters were explicitly configured.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16290	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to configure (i.e., enter and edit) for each host accessed by the Data Pool Ingest Service via secure copy the following set of scp host parameters: a. a label used by Data Pool Ingest GUI to identify the host, b. host name or ip address	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16293	The Data Pool Ingest GUI shall permit authorized (ingest tuning and ingest admin) operators to configure (i.e., enter and edit) for each host accessed by the Data Pool Ingest Service via secure copy the following set of scp tuning parameters: a. the maximum number of concurrent scp operations allowed for that host, b. whether the scp operations for the host will be timed out, c. if so, parameters used to time out scp transfers, consisting of the minimum expected throughput (in MB/second) plus an additional wait time in seconds, to be used to identify stuck scp operations.  NOTE:  That is, a scp transfer is considered timed out if its duration exceeds (file size/expected throughput) + wait time.] d. Whether the host is subject to automated retry when suspended, and if so, the time interval (in minutes) between automatic retries.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16295	The Data Pool Ingest GUI shall reject the definition of a duplicate scp host, i.e., a host that uses the same label as another host or the same scp host name or ip address as an existing scp host.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16297	The Data Pool Ingest GUI shall prompt the operator to confirm any configuration definitions and changes for scp hosts.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16300	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) a set of default values for scp tuning parameters to be used for scp hosts for which no host parameters were explicitly configured.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16310	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) the maximum number of concurrent scp operations that may be in progress for ingest purposes.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16350	The Data Pool Ingest GUI shall prompt operators for confirmation before removing polling locations.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16360	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to remove polling locations for data providers if they are no longer referenced by ingest requests or notifications that are not in a terminal state.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16370	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to remove ftp host definitions if they are no longer referenced by any existing configurations.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16380	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to remove scp host definitions if they are no longer referenced by any existing configurations.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16382	The Data Pool Ingest GUI shall allow operators to list polling locations and FTP and scp hosts and display the associated configuration information.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16385	The Data Pool Ingest Service shall be able to apply changes to provider, polling and host configuration and tuning information within one minute of them having been entered and saved via the DPL Ingest GUI and without requiring rebooting.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16390	The Data Pool Ingest Service shall not store passwords in the clear.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16400	The Data Pool Ingest Service shall not include passwords in its logs.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16450	The Data Pool Ingest GUI shall permit authorized (ingest admin) operators to configure (i.e., enter and edit) for each data type other than Browse, QA, and PH that is enabled for Data Pool insert (i.e., ESDT and version): a. whether its granules shall be published in the public Data Pool following successful ingest or not, [NOTE: Whether Browse granules are published depends on whether the associated science granules are published, as per current Data Pool requirements. Note that currently, only associated Browse granules, but not QA and PH granules are published in the Data Pool.  If this is changed via NCR, the NCR change must extend to Data Pool Ingest.] b. their default retention time and priority if configured to be published, c. a minimum retention time in the non-public Data Pool area for granules that are not published, plus a default value to be used if no explicit retention has been specified for a data type. [NOTE: Granules in the non-public area are eligible for cleanup when they complete ingest. The DAAC can elect to keep granules in the Data Pool for a minimum amount of time after ingest completed that is configurable by collection and applies even if the granules are hidden, i.e., are not inserted into the public Data Pool, to support ordering, e.g., by subscriptions.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16454	The Data Pool Ingest GUI shall permit operators to list the data types for which ingest configuration parameters have been entered and view their configured parameters.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16456	The Data Pool Ingest GUI shall offer a method that permits operators to quickly select or scan for a subset of existing Data Pool collections in order to enter or view the related Data Pool ingest configuration parameters without having to enter the full ESDT name and version.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16458	The Data Pool Ingest Service shall be able to apply changes to the Data Pool ingest parameters of data types within one minute of them having been entered and saved via the DPL Ingest GUI and without requiring rebooting.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16460	The Data Pool Ingest GUI shall permit authorized (ingest tuning and ingest admin) operators to configure (i.e., enter and edit) the tuning configuration parameters for the Data Pool Ingest Service, to include: a. the maximum number of concurrent CPU-intensive operations such as checksumming, for each ECS host on which such operations are being executed by the Data Pool Ingest Service, b. parameters to calculate a time limit for checksumming operations for each host on which such operations are being executed by the Data Pool Ingest Service (Note that the time limits may need to be configured by checksum type.) c. the maximum number of concurrent file transfers that may be executed on an ECS Service host, by host (to exclude polling and PDRD/PAN notifications) [NOTE: The sum of these limits represents the overall maximum number of concurrent file transfers], and whether the host is enabled to perform scp transfers, d. the maximum number of granules that may be active at the same time and the maximum amount of data these granules may contain [NOTE: the parameters correspond to the totals of the corresponding InGran server thresholds.] e. the maximum number of concurrent archive write operations that may be executed on an ECS Service Host, by host [NOTE: The sum of these limits represents the overall maximum number of concurrent archive write operations], f. parameters to calculate a time limit for archive write operations before assuming that they are hung, consisting of a minimum expected throughput and a time constant reflecting the maximum expected fixed overhead, separate for each ECS Service Host, g. whether to continue to activate ingest requests and granules that require an archive that is currently suspended by the operator or due to an alert.  [NOTE: In this case, the affected granules will be processed up to the point where they require the archive, and then they will accumulate in the archiving queue for the suspended archive, to be dispatched automatically after the archive was resumed.] [NOTE: DPL Insert use of ECS Service Hosts will be configured via the same screen  see Ticket DP_72_01.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16465	The Data Pool Ingest Service shall be able to apply changes to the Data Pool Ingest tuning configuration parameters within one minute of them having been entered and saved via the DPL Ingest GUI and without requiring rebooting. [NOTE: This applies to S-DPL-16255 as well as S-DPL-16460.] 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16475	The Data Pool Ingest Service shall be able to apply changes to the Data Pool Insert tuning configuration parameters within one minute of them having been entered and saved via the DPL Ingest GUI and without requiring rebooting	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16480	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) the general retry configuration parameters, that is, the default number of retries and default retry interval for retriable errors.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16482	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) the following alert related configuration parameters: a. number of consecutive errors and time-outs that will trigger an alert, to be applied to attempts to transfer PDR files, b. number of consecutive file transfer errors for different files that will trigger an alert (to include PAN and PDRD files and time-outs), c. number of consecutive file system access errors for the same file system but for different granules or files that will trigger an alert for a file system, d. number of errors or time-outs returned by the SDSRV metadata validation or insert service consecutively for different granules or files that will trigger an alert for the SDSRV services, e. number of consecutive archiving or checksumming service request time outs for the same service (i.e., on the same host) but different files or granules that will raise an alert for a service, f. retry interval for attempts to clear an alert condition, to be used globally for all situations for which there are no specific retry intervals, g. DELETED, h. a cache warning threshold in terms of percent of consumed cache space which when reached will trigger an operator alert, individually by archive file system, i. a cache full threshold in terms of percent of consumed cache space which is higher than the cache warning threshold and when reached will trigger an operator alert and cause archiving for that archive to be suspended, individually by archive file system, j. a low watermark threshold in terms of percent of consumed cache space which when underrun will clear the cache warning alert referenced in h., individually by archive file system, k. a threshold in terms of percent of consumed cache space which when underrun will clear the cache full alert referenced in i, individually by archive file system, l. the number of consecutive errors not attributed to other resources (such as ftp or scp hosts or polling locations) that will raise an alert for a service on an ECS host when returned by the same service on the same host for different granules or files (an example are SAN file system access errors that are not attributed to the file system being down, which would eventually suspend all services on the host experiencing the problem). [NOTE: Entering values larger than 100% for the alert thresholds is permitted and disables that alert.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16490	The Data Pool Ingest GUI shall permit authorized (ingest tuning and ingest admin) operators to configure (i.e., enter and edit) the default number of retries and a default retry interval for UR translation errors.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16500	The Data Pool Ingest GUI shall permit authorized (ingest tuning and ingest admin) operators to configure (i.e., enter and edit) the default number of retries for checksum verification errors.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16515	The Data Pool Ingest Service shall be able to apply changes to retry and alert related configuration parameters within one minute of them having been entered and saved via the DPL Ingest GUI and without requiring rebooting.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16540	The Data Pool Ingest GUI shall permit authorized ('ingest admin' and 'ingest tuning') operators to configure (i.e., enter and edit) the time interval (in minutes) that specifies when completed requests and closed interventions will be removed from the active tables.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16542	The Data Pool Ingest Service shall allow authorized (ingest admin and ingest tuning) operators to configure (i.e., enter and edit) the retention time (in months) for keeping historic information for requests and system status and throughput (such as alerts and throughput statistics).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16545	The Data Pool Ingest GUI shall permit authorized ('ingest tuning' and 'ingest admin') operators to configure (i.e., enter and edit) the time interval at which free space information for Data Pool file systems shall be obtained, the percent full condition that is to trigger an alert, and a smaller value than the percent full condition that is to clear the alert.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16546	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) the time interval for aggregating and saving throughput statistics.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16547	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure (i.e., enter and edit) the time interval which determines the frequency at which archive cache information will be obtained.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16560	The Data Pool Ingest GUI shall permit all operators to view all Data Pool Ingest configuration parameters that can be maintained via the Data Pool Ingest GUI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16570	The Data Pool Ingest GUI shall permit authorized (ingest tuning and ingest admin) operators to configure (i.e., enter and edit) the available checksum types and related algorithms, as well as the default checksum type that will be used to calculate checksums for files for which no checksum was transmitted by the provider.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16580	The Data Pool Ingest GUI shall permit authorized (ingest tuning and ingest admin) operators to configure (i.e., enter and edit) the ports for ECS services that are invoked via a host agent (e.g., QuickServer), by host on which the service is available.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16600	The Data Pool Ingest GUI shall permit operators to list ingest requests in the active database tables, i.e., not yet archived ingest requests that are or were managed by the Data Pool Ingest Service (i.e., it shall not display active ingest requests managed by the INGST CI). [NOTE: Requests that are managed by the INGST CI cannot be canceled, resumed, etc by the Data Pool Ingest GUI.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16610	The Data Pool Ingest GUI shall display the following information in the list of not yet archived ingest requests: a. request ID, b. data provider, c. request status and if the status reflects an error in at least one of its granules, the type of the error, indicative of the error cause [for classification of errors see S-DPL-17245], and indicating the existence of multiple errors when a single error type cannot be assigned, d. request priority, e. the last time the request status was updated, f. number of granules in the request, and completion status (e.g., number of granules completed processing), g. request size (i.e., data volume). [NOTE: The type of error reflects the error types of the suspended or failed granules. A request can thus have several error types.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16620	The Data Pool Ingest GUI shall permit operators to sort a list of not yet archived ingest requests by a. request ID (descending), b. data provider (ascending), c. request status (ascending), d. time the request was queued (ascending or descending), e. time of last status change (ascending or descending). 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16630	The Data Pool Ingest GUI shall permit operators to filter a list of not yet archived ingest requests by, a. request ID, b. data provider, c. one, several, or all request states, d. type of error, e. time range the request was queued (using the last hour as the default), f. time range of the last status update, g. one or several target archives, h. any combination of a. or (b. and (c. or d.) and (e. or f) and g). [NOTE: If the request has several suspended or failed granules, there may be several error types associated with the request. The request must be included in the filtered list if any of its failed or suspended granules matches the error type specified in the filter criterion. A request may contain granules for more than one archive; if so, the request qualifies under the archive filter if any of its granules are for that archive.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16635	The Data Pool Ingest GUI shall allow an operator to save GUI filter settings across sessions that are tied to the specific login if GUI security is enabled. [NOTE: It is acceptable to save the last filter settings this particular operator used automatically, or alternatively, give the operator the capability to save filter settings explicitly.]  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16636	The Data Pool Ingest GUI shall allow operators to save a single set of default GUI filter settings to apply to all GUI sessions if GUI security is not enabled. [NOTE: It is not acceptable to save automatically the last filter settings since this would be confusing if more than one operator is active at a time.  In this particular case, the filter settings shall only be saved if the operator requests that explicitly.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16640	The Data Pool Ingest GUI shall permit operators to manually refresh a list of not yet archived ingest requests, applying the currently selected sort and filter criteria.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16650	The Data Pool Ingest GUI shall permit operators to automatically refresh a list of not yet archived ingest requests at an operator selected refresh interval of no less than 20 seconds, applying the currently selected sort and filter criteria.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16660	The Data Pool Ingest GUI shall permit operators to select any ingest request in a not yet archived ingest request list for displaying request details.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16670	The Data Pool Ingest GUI shall display all information associated with a request when displaying the details about a not yet archived ingest request, to include: a. request ID, b. DELETED, c. request status and time of last status change, d. request priority, e. data provider, f. mission, g. time the request was queued, h. time the request was activated, i. time the request completed (if the request is complete), j. expiration time and whether the request is considered expired, k. DELETED, l. data volume, number of granules and number of files, m. completion status, in terms of number of granules transferred, preprocessed, archived and inserted, n. PDR file and path name, o. a history of the request status changes, p. annotations, q. polling location from which the request was obtained.  [NOTE: The list of status changes can take the form of a list, ordered by time, showing the time of status change and the new status.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16680	The Data Pool Ingest GUI shall permit operators to display any currently open intervention for a not yet archived ingest request when viewing request details. [NOTE: There is at most one open intervention for a request.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16690	The Data Pool Ingest GUI shall display the list of the granules associated with a not yet archived ingest request when displaying the request details, by default with suspended granules first and then in ascending order of  their position in the PDR, and include the following information in the list: a. granule identification (i.e., sequence number in the PDR), b. data type name and version, c. granule status and if Failed or Suspended, the type of the error [for classification of errors see S-DPL-17245], d. time of last status change, e. granule size.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16700	The Data Pool Ingest GUI shall allow an operator to sort the list of the granules associated with a not yet archived ingest request by state in sequence or reverse sequence of progress as indicated by granule status, and with suspended granules shown first and failed granules shown last, with the default being to show suspended granules first, failed granule last, and the remaining granules ordered in sequence of progress (i.e., the completed ones at the end). [NOTE: See also DAAC feedback on RTR action #89.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16702	The Data Pool Ingest GUI shall permit an operator to select any granule in the granule list of a not yet archived  ingest request and display detailed granule information, to include: a. number of files, b. list of the path names of the associated files and their file types as per PDR, c. if the granule is suspended or failed, detailed error information when available, such as the specific link in the linkage file that failed or the error information returned by the SDSRV or the error details returned by the Data Pool Insert action.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16703	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select in the granule list of a not yet archived ingest request that is not in a terminal state one or several or all granules and request that they be cancelled.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16704	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select in the granule list of a not yet archived ingest request that is not in a terminal state one or several or all granules that are currently suspended (e.g., due to some error) and request that they be retried (i.e., resumed), giving the operator the option to request re-transferring the granule or retrying the last (i.e. failed) ingest step.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16706	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select in the granule list of a not yet archived ingest request that is not in a terminal state one or several or all granules that are currently suspended (e.g., due to some error) and request that they be failed non-retriably (i.e., such that they will be considered failed by the operator and will not cause a subsequent operator intervention).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16710	The Data Pool Ingest GUI shall permit authorized (ingest control) operators to select one, several, or all Data Pool ingest requests in a list of not yet archived ingest requests for cancellation unless they are currently in a terminal state, and provide indication when they have been cancelled (e.g., via changes in the request status).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16720	The Data Pool Ingest GUI shall permit authorized (ingest control) operators to select one, several, or all Data Pool ingest requests in a list of not yet archived ingest requests for suspension unless they are currently suspended or in operator intervention, or in a terminal state, and provide indication when they have been suspended (e.g., via changes in the request status).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16730	The Data Pool Ingest GUI shall permit authorized (ingest control) operators to select one, several, or all Data Pool ingest requests in a list of not yet archived ingest requests for resumption if they are currently suspended, and provide indication when they have been resumed (e.g., via changes in the request status).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16740	The Data Pool Ingest GUI shall permit authorized (ingest control) operators to select one or several Data Pool ingest requests in a request list to update their priority, unless they are in a terminal state, and provide indication when their priority has been changed (e.g., via displaying the updated priority).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16745	The Data Pool Ingest GUI shall prompt an operator who is cancelling or suspending an ingest request or changing its priority for the reason for the request modification.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16750	The Data Pool Ingest GUI shall permit operators to list historic (i.e., archived) ingest requests, regardless of whether they were processed by the Data Pool Ingest Service or the INGST CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16760	The Data Pool Ingest GUI shall display the following information in the list of historic ingest requests: a. request ID, b. data provider, c. request status and if the status reflects an error in at least one of its granules, the type of the error [for classification of errors see S-DPL-17245], and indicating the existence of multiple errors when a single error type cannot be assigned, d. request priority, e. time the request was queued, f. time the request started processing, g. time the request completed, h. number of granules in the request, and completion status (e.g., number of granules completed processing, or data volume completed processing, or percent complete), i. request size (i.e., data volume), j. whether the request was processed by Data Pool Ingest request or by the INGST CI. [NOTE: The historic request list does not simply show the time of last status change, but the time of the three key status changes.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16770	The Data Pool Ingest GUI shall permit operators to sort a list of historic ingest requests by a. request ID (ascending), b. data provider (ascending), c. request status (ascending), d. time the request was queued (ascending or descending), e. time processing for the request was started (ascending or descending), f. time the request was completed (ascending or descending).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16780	The Data Pool Ingest GUI shall permit operators to filter a list of historic ingest requests by a. request ID, b. data provider, c. type of data (i.e., ESDT) contained in the request , d. one, several, or any request states, e. time range the request was started (using the last 24 hours as the default), f. time range the request was completed, g. any combination of b., c., and d., optionally including one of e. or f. [NOTE: That is the operator can include in the filter at most one of the request times, but any combination of request states.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16785	The Data Pool Ingest GUI shall permit operators to refresh the current list of historic ingest requests manually. [NOTE: Automatic refresh is not provided since this is not intended as a monitoring screen.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16790	The Data Pool Ingest GUI shall permit operators to print the current list of historic ingest requests. [NOTE: This can be implemented via the print facility of the web browser, provided that the GUI provides the list to the web browser in a single screen.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16800	The Data Pool Ingest GUI shall permit operators to save the current list of historic ingest requests to a file. [NOTE: This can be implemented via the save facility of the web browser, provided that the GUI provides the list to the web browser in a single screen.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16810	The Data Pool Ingest GUI shall permit operators to select any ingest request in a historic ingest request list for displaying request details.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16820	The Data Pool Ingest GUI shall display the following information associated with a historic ingest request when displaying the request details: a. request ID, b. whether the request was ingested by the Data Pool Ingest Service or the INGST CI, c. DELETED, d. data provider, e. time the request was queued, f. processing start and end time, g. request priority, h. final request status, i. all request timings that are kept as per S-DPL-16890, with timings that are only applicable to Data Pool ingest requests being displayed as n/a for INGST CI requests, j. data volume, k. number of granules and number of files, l. number of successful granules, m. the history of status changes (only applicable to Data Pool ingest requests), n. annotations. [NOTE: With the exception of the status history, this represents information saved in the historic ingest request table.  The list of status changes can take the form of a list, ordered by time, showing the time of status change and the new status.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16830	The Data Pool Ingest GUI shall display the list of the granules associated with an historic ingest request when displaying the request details, sorted by default in the order in which they appeared in the PDR, and include the following information in this list: a. granule identification (e.g., sequence number in the PDR), b. ECS granule ID, if applicable, c. Data Pool granule ID, d. data type name and version, e. granule status, f. granule size and file count, g. processing start and end time, h. retry count, i. total processing time, j. DELETED, k. DELETED, l. DELETED, m. time to checksum.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16840	The Data Pool Ingest GUI shall allow operators to display an ingest request history summary report that contains information compatible with the current ingest request history summary report displayed by the INGST GUI, but adds the capability to differentiate between data ingested via Data Pool Ingest versus the INGST CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16850	The Data Pool Ingest GUI shall allow operators to display an ingest request performance report that contains information compatible with the current ingest request performance report displayed by the INGST GUI, but adds the capability to differentiate between data ingested via Data Pool Ingest versus the INGST CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16860	The Data Pool Ingest GUI shall allow operators to display an ingest granule performance report that contains information compatible with the current ingest granule performance report displayed by the INGST GUI, but adds the capability to differentiate between data ingested via Data Pool Ingest versus the INGST CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16870	The Data Pool Ingest Service shall record ingest throughput in the database, as measured in terms of the number of granules and data volume per configured time interval (see S-DPL-16546): a. by provider b. by FTP or scp host	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16880	The Data Pool Ingest Service shall record information about each ingest request it processes in an ingest historic request table that is backwards compatible with the INGST table InRequestSummaryHeader modified as indicated where the meaning of a field is different in Data Pool Ingest, to include the following: a. RequestID, b. DANFileName, c. ExternalDataProvider, d. IngestType, e. Mission, f. ProcessingStartDateTime, g. ProcessingEndDateTime, h. RequestPriority, i. RequestStateKey, j. TimeToXfer, k. TimeToPreprocess, l. TimeToArchive m. TotalDataVolume, n. TotalFileCount, o. TotalGranuleCount, p. TotalSuccessfulGranules, q. (New) ProcessedBy: to indicate when a request was processed by DPL Ingest, r. (New) TimeToInsert: the Data Pool insert time, s. (New) TimeToChecksum, t. DELETED, u. DELETED, v. DELETED.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16890	The Data Pool Ingest Service shall record information about each granule it processes in an ingest historic granule data table that is backwards compatible with the INGST table InRequestSummaryData modified as indicated where the meaning of a field is different in Data Pool Ingest,: a. RequestID, b. DataGranuleID, c. DataType, d. DataGranuleVolume, e. DataGranuleState, f. NodeName, g. ProcessingEndDateTime, h. ProcessingStartDateTime, i. RetryCount, j. TotalFileCount, k. TimeToArchive, l. TimeToPreprocess, m. TimeToXfer, n. (New) TimeToInsert, o. (New) TimeToChecksum, p. DELETED, q. DELETED, r. DELETED.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16900	The Data Pool Ingest GUI shall allow an operator to display the current status of Data Pool Ingest as part of a Data Pool Ingest Service status page, to include: a. the number of ingest requests currently queued and currently in processing, in total and by provider, b. the number of granules currently queued and currently in processing, in total and by provider, c. the amount of data currently queued and currently in processing, in total and  by provider. d. whether each ingest server function (i.e., polling, processing, and notification) is currently active or not. [NOTE: The ingest status page is intended to provide a summary of the current ingest status to the extent that the GUI design does not already include more detailed status information as part of that page.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16910	The Data Pool Ingest GUI shall display as part of the current status of Data Pool Ingest polling locations, providers, and FTP or scp hosts, arranged by provider and host, listing them and displaying for each whether polling, file transfers, and PAN/PDRD delivery are currently active or suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16920	The Data Pool Ingest GUI shall display as part of the current status of Data Pool Ingest on the Data Pool ingest status page, whether Data Pool ingest is currently active or suspended. [NOTE: The ingest status page is intended to provide a summary of the current ingest status to the extent that the GUI design does not already include more detailed status information as part of that page.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16930	The Data Pool Ingest GUI shall display as part of the current status of Data Pool Ingest on the Data Pool Ingest Service status page, whether sending e-mail to data providers is currently active or suspended. [NOTE: The ingest status page is intended to provide a summary of the current ingest status to the extent that the GUI design does not already include more detailed status information as part of that page.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16940	The Data Pool Ingest GUI shall allow an operator to display the current status of the Data Pool file systems, listing them and displaying for each: a. whether it is currently active or suspended, b. the number of granules currently queued and currently in processing for each target Data Pool file system, c. the amount of data currently queued and currently in processing for each target Data Pool file system, d. free space information maintained in operator configurable time intervals, to include the last time the information was updated. [NOTE:  Since the lists of DPL file systems and archives are displayed on the same screen, it is desirable to make the contents of the lists consistent.  The DPL file system list should include the alert thresholds (like the archive list does).]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16950	The Data Pool Ingest GUI shall allow an operator to display the current status of the archives, listing them and displaying for each a. whether it is currently active or suspended, b. the number of granules currently queued and currently in processing for each archive, c. the amount of data currently queued and currently in processing for each archive, d. the percent of consumed cache space and the corresponding alert thresholds. [NOTE: The term 'archive' refers to an archive cache file system.] [NOTE:  Since the lists of DPL file systems and archives are displayed on the same screen, it is desirable to make the contents of the lists consistent.  The archive list should include the last time the information was updated (like the file system list does).]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16960	The Data Pool Ingest GUI shall allow an operator to display the current status of other ECS services used by Data Pool Ingest, listing them and displaying for each whether it is currently active or suspended. [NOTE: Examples of other ECS services include the science data server and checksumming services on a specific host.  Note that some ECS services are available on more than one platform, in which case the term ECS Service is understood to refer to an instance of that ECS service on a given platform.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16970	The Data Pool Ingest GUI shall display as part of the Data Pool Ingest Service status page, whether any Data Pool file systems, archives, and other ECS services are currently suspended. [NOTE: This is intended to provide an aggregate status of these resources if at the top status page level, unless the GUI design includes the status of each file system, archive, and ECS service in this page already.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16980	The Data Pool Ingest GUI shall allow an operator to manually refresh the screen displaying the current status of Data Pool Ingest.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-16990	The Data Pool Ingest GUI shall permit operators to automatically refresh the screen displaying the current status of Data Pool Ingest at an operator selected refresh interval of no less than 1 minute.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17000	The Data Pool Ingest GUI shall allow an operator to manually refresh the screen displaying the current status of the Data Pool file systems.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17010	The Data Pool Ingest GUI shall permit operators to automatically refresh the screen displaying the current status of the Data Pool file systems at an operator selected refresh interval of no less than 1 minute.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17020	The Data Pool Ingest GUI shall allow an operator to manually refresh the screen displaying the current status of the archives.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17030	The Data Pool Ingest GUI shall permit operators to automatically refresh the screen displaying the current status of the archives at an operator selected refresh interval of no less than 1 minute.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17035	The Data Pool Ingest GUI shall permit operators to automatically refresh the screen displaying the current status of ECS Services at an operator selected refresh interval of no less than 1 minute.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17040	The Data Pool Ingest GUI shall permit authorized (ingest control and ingest tuning) operators to select one or several polling locations used for Data Pool ingest from the list of polling locations for suspension. [NOTE: Any current polling session is allowed to complete, but no new polling cycle for that location will be started.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17050	The Data Pool Ingest GUI shall permit authorized (ingest control and ingest tuning) operators to select one or several polling locations used for Data Pool ingest from the list of polling locations for resumption if they are currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17060	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to select one or several ingest FTP/scp hosts from the list of FTP/scp hosts and suspend them. [NOTE: Current operations involving that host will complete, but no new transfers to or from that host will be started.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17070	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to select one or several ingest FTP/scp hosts from the list of FTP/scp hosts for resumption if they are currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17080	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to select one or several data providers from the list of data providers and suspend them. [NOTE: This suspends polling for all locations for that provider.  Ingest requests for that provider will no longer be activated, but currently active requests will be completed, or if they encounter errors, will be processed until they suspend.  Suspension of a provider has no impact on file transfers or PAN/PDRD delivery.]  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17090	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to select one or several data providers from the list of data providers for resumption if they are currently suspended. [NOTE: This resumes polling for all locations for that provider.  Ingest requests for that provider will be eligible for activation again.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17091	The Data Pool Ingest GUI shall allow authorized (ingest control) operators to suspend Data Pool archiving for an archive. [NOTE: Suspending an archive will not affect ingest requests that are already in progress (they will be allowed to complete), but it will prevent the activation of new ingest requests that include granules for that archive.  However, the DAAC can alter this ingest behavior via configuration, see S-DPL-1646g.  The purpose of suspending an archive is to permit operators to quiesce the operations for an archive, e.g., in preparation for maintenance. To terminate the archiving operations for an archive immediately, the operator would first suspend the archive and then suspend any ingest requests for that archive that are still active.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17092	The Data Pool Ingest GUI shall allow authorized (ingest control) operators to resume Data Pool archiving for an archive if it is currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17100	The Data Pool Ingest GUI shall permit authorized (ingest control and ingest tuning) operators to select one or several Data Pool file systems from the list of Data Pool file systems to suspend their use for Data Pool ingest and archiving. [NOTE: Currently active requests will be allowed to complete, but new requests that require the file system will no longer be activated, unless the operator indicates otherwise, see S-DPL-17112. In accordance with the resolution of RTR action #95, the suspension will be limited to Data Pool Ingest. ]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17110	The Data Pool Ingest GUI shall permit authorized (ingest control and ingest tuning) operators to select one or several Data Pool file systems from the list of Data Pool file systems for resumption of Data Pool ingest and archiving if they are currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17112	The Data Pool Ingest GUI shall allow an authorized (ingest control) operator to indicate that a Data Pool file system that is currently suspended shall not prevent the activation of requests whose granules require that file system provided that the request also includes granules that do not require that file system (see also S-DPL-18272).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17140	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to select one or several ECS services (i.e., hosts that support checksumming or file transfer), or the SDSRV service from the list of services for suspension.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17150	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to select one or several ECS services (i.e., hosts that support checksumming or file transfer), or the SDSRV service from the list of services for resumption if they are currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17160	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to suspend Data Pool ingest processing for new requests. [NOTE: This will cause all further polling to cease and no more requests will be activated. Currently active requests will continue until they are worked off and their provider notifications have been delivered.] 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17170	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to resume Data Pool ingest processing for new requests if it is currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17180	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to suspend sending e-mail notifications to data providers.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17190	The Data Pool Ingest GUI shall allow an authorized (ingest control and ingest tuning) operator to resume sending e-mail notifications to data providers if it is currently suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17200	The Data Pool Ingest Service shall archive and remove information about active requests on a regular basis, leaving only active request information for the last configured number of minutes in the database (see S-DPL-16540).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17215	The Data Pool Ingest Service shall remove closed interventions on a regular basis, leaving only closed interventions for the last configured number of minutes in the database (See S-DPL-16540).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17216	The Data Pool Ingest Service shall add the information associated with interventions (e.g., annotations, outcome) to the request annotation when the interventions are closed.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17220	The Data Pool Ingest Service shall remove historic information on a regular basis, leaving only requests for the last configured number of months in the database (see S-DPL-16542).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17225	The Data Pool Ingest Service shall remove any accumulated system monitoring information (e.g., alerts and throughput information) on a regular basis, leaving only system monitoring information for last configured number of months in the database (See S-DPL-16542).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17230	The Data Pool Ingest Service shall remove temporary information (e.g., files) created in support of processing an ingest request when no longer needed, at the latest when the request and provider notification completed.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17235	The Data Pool Ingest Service shall request an operator intervention whenever a Data Pool ingest request whose PDR was validated successfully encounters an error, except in those cases explicitly excepted by other requirements or when the error situation generates an operator alert. [NOTE: For an example of an exception, see requirement S-DPL-18050.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17240	The Data Pool Ingest Service shall request an operator intervention for a Data Pool ingest request only after there are no more granules in the request to ingest, i.e., all granules have been either ingested successfully, failed during one of the ingest steps, or were previously failed by the operator.  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17245	The Data Pool Ingest Service shall identify the granules that failed during ingest processing for a Data Pool ingest request, providing a classification for the failure reason according to the granule error states listed in S-DPL-18210, as well as detailed error information.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17250	The Data Pool Ingest GUI shall allow authorized operators (ingest control and ingest admin) to configure an optional e-mail address to which notifications about operator interventions shall be sent.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17255	The Data Pool Ingest Service shall include the following information in the notifications about operator interventions: a. provider, request ID, and nature of the error that caused the intervention in the subject line, b. intervention detail that would be displayed on the intervention detail screen as part of the e-mail body.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17260	The Data Pool Ingest GUI shall allow operators to monitor request for operator interventions by the Data Pool Ingest Service such that new interventions can be displayed within 20 seconds of them having been requested by the Data Pool Ingest Service, e.g., by allowing operators to list new and open interventions and allowing the operator to refresh that list manually, as well as via automatic refresh as often as every 20 seconds.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17265	The Data Pool Ingest GUI shall show on the screen that operators use to monitor for operator intervention requests, the following information for each intervention: a. time the intervention request was created, b. data provider, c. request identification d. type of the error causing the intervention [for the list of error types see S-DPL-17245.] e. if available, the identification of the operator currently working the intervention f. if available, the time the intervention was acknowledged [NOTE: If a request has several suspended granules, they may have been suspended for different reasons.  That is, multiple types of errors may be associated with that intervention.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17270	The Data Pool Ingest GUI shall permit an operator to filter open operator intervention requests by a. data provider, b. type of intervention, c. target ECS archive, d. a combination of all three. [NOTE: The target archive would be only of interest as a filter condition if any of the interventions include granules that were suspended due to archiving errors.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17275	The Data Pool Ingest GUI shall permit an operator to sort open operator intervention requests in ascending or descending order of creation time, with descending order (i.e., latest first) being the default.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17280	The Data Pool Ingest GUI shall permit an operator to select an open operator intervention request from the monitoring screen for viewing and disposition.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17282	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select one, several, or all open operator intervention requests from the monitoring screen and resume them.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17284	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select one, several, or all open operator intervention requests from the monitoring screen and cancel them.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17290	The Data Pool Ingest GUI shall permit an operator to select an open operator intervention request, acknowledge and annotate it. [NOTE: An intervention is considered acknowledged when it is viewed the first time.  Thereafter, the intervention is considered open but not new.] [NOTE: The operator may annotate the intervention, for example, if s/he cannot resolve the problem and wants to leave a note for the next shift.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17295	The Data Pool Ingest GUI shall permit an operator to select an open operator intervention and add an annotation.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17300	The Data Pool Ingest GUI shall prefix each operator annotation with a time stamp (date and time) and the operator identification if known.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17310	The Data Pool Ingest GUI shall permit an operator to select and view the Data Pool ingest request associated with an operator intervention request, as well as associated provider, polling location, and PDR file path name.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17320	The Data Pool Ingest GUI shall permit an operator to list the suspended granules that caused the intervention request. [NOTE: It is OK to list all the granules, however, when viewing an intervention, the granules whose suspension caused the intervention must be shown first.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17330	The Data Pool Ingest GUI shall include the following information in the list of granules displayed when viewing intervention details: a. granule identification (e.g., sequence number in the PDR), b. data type name and version, c. granule status and if Failed or Suspended, the type of the error [for classification of errors see S-DPL-17245], d. granule size.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17340	The Data Pool Ingest GUI shall permit an operator to view detailed information about a granule shown as part of the intervention details, to include: a. number of files b. the list of the pathnames associated with the granule and their file types as per PDR c. detailed error information when available, such as the specific link in the linkage file that failed or the error information returned by the SDSRV or the error details returned by the Data Pool Insert action or the specific target archive, location, and error information for granules suspended due to archiving errors. 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17350	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select one, several or all of the granules that caused the intervention request and indicate that they should be failed.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17360	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to disposition an intervention by requesting that the Data Pool Ingest Service retry processing all granules in a request that have not yet completed ingest nor were indicated as failed by the operator, allowing the operator to choose to resume the granule starting by re-transferring it or merely retrying the last (i.e. failed) ingest step.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17370	The Data Pool Ingest GUI shall close an intervention request once the operator has dispositioned it, recording the following information: a. date/time of closure, b. nature of the disposition (i.e., whether the request was resumed or failed), c. if available, the identification of the operator. [NOTE: Closed interventions are no longer displayed in the intervention monitoring screen. Since the outcome of closed intervention is recorded in the request as per S-DPL-17300, closing the intervention will actually cause this information to be included in the annotation that is added to the request.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17380	The Data Pool Ingest GUI shall add an annotation to a request whenever the operator changes an ingest request, e.g., cancels or resumes it, or changes its priority, and record: a. the date/time, b. nature of the status change, c. if available, the identification of the operator, d. an optional annotation (e.g., explaining the reason for the change) if provided by the operator. [NOTE: If there is currently an open intervention for that request, the requirement is to close it and record the resumption or cancellation; otherwise, to record the equivalent of an intervention, but place it immediately into the closed state.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17440	The Data Pool Ingest Service shall raise an operator alert for an FTP host when an attempt to access a polling location via ftp results in one of the following errors: a.  connection with the target host could not be established despite retrying for the number of times as configured for retriable errors (see S-DPL-16480), b.  FTP login failed, c.  there are N consecutive errors while attempting to transfer PDR files from the location, where N is configurable on a global basis (see S-DPL-16482), d. there are N consecutive time-outs while attempting to transfer PDR files from the location, where N is configurable on a global basis (see S-DPL-16261 and S-DPL-16482). [NOTE: Given the small size of PDR files, it is acceptable to ignore the file size in time out calculations during polling, i.e., assume a file size of 0.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17450	The Data Pool Ingest Service shall raise an operator alert for an FTP host when an attempt to transfer files to be ingested via ftp results in one of the following errors: a. connection with the target host could not be established despite retrying for the number of times as configured for retriable errors (see S-DPL-16480), b. FTP login failed, c. file transfer attempts for N different files failed consecutively, where N is configurable on a global basis (see S-DPL-16482), d. the file transfer time exceeded it maximum allowed time as per configuration for that host (see S-DPL-16261) on file transfer attempts for N different files consecutively where N is configured on a global basis (see S-DPL-16482)	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17455	The Data Pool Ingest Service shall raise an operator alert for an FTP host when an attempt to transfer PAN and PDRD notification files results in one of the following errors: a. connection with the target host could not be established despite retrying for the number of times as configured for retriable errors (see S-DPL-16480), b. FTP login failed, c. file transfer attempts for N different PAN or PDRD failed consecutively, where N is configurable on a global basis (see S-DPL-16482), d. the file transfer time exceeded it maximum allowed time as per configuration for that host (see S-DPL-16261) on file transfer attempts for N different files consecutively where N is configured on a global basis (see S-DPL-16482) [NOTE: Given the small size of PDRD and PAN files, it is acceptable to ignore the file size in the time out calculations for notifications, i.e., assume a file size of 0.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17460	The Data Pool Ingest Service shall raise no more than one operator alert each for polling, file transfers, and notification for a given FTP host and separate for each provider where the alert affects only a specific one. [NOTE: That is, separate alerts may be raised for each type of activity to let DAAC operators know when an activity is impacted, and the alert may in addition be provider specific if the error is provider specific.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17470	The Data Pool Ingest Service shall suspend dispatching polling and file transfers, including pulling files referenced in a PDR and transferring PAN or PDRD files, for an FTP host while an alert is currently pending for it if the nature of the error causing the alert would impede the intended operation: a. If the alert is due to an inability to connect with the FTP host, all polling and transfers for that host shall be suspended. b. If the alert is due to a login failure for file retrieval, polling and file transfers from that host for that provider shall be suspended; PAN and PDRD transfers shall continue. c. If the alert is due to a login failure for PAN or PDRD transfer, polling and file transfer operations shall continue; PAN and PDRD FTP transfers for that provider shall be suspended. d. If the alert is due to N consecutive file/PDR transfer failures or file/PDR transfer time-outs, polling respectively file transfer operations shall be suspended; PAN and PDRD transfers shall continue. e. If the alert is due to N consecutive different PAN or PDRD transfer failures or transfer time-outs, polling and file transfer operations shall continue; PAN and PDRD FTP transfers for that provider shall be suspended. [NOTE: The requirement implies that there may be several alert conditions that have different consequences.  As per S-DPL-17460, the alert conditions must be maintained to assure that the appropriate services are suspended and resumed as the conditions are detected or cleared.]  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17480	Unless the FTP host was suspended by the operator, the Data Pool Ingest Service shall automatically retry establishing connection, login, and performing another transfer for an FTP host that is currently suspended, if the FTP host is so configured, using the retry time interval configured for that host, and shall react as follows when a retry succeeds: a. clear the corresponding alert condition and the alert as a whole if there are no other alert conditions for that host, b.  resume dispatching of the operations for that host that were suspended as a consequence of that alert condition. 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17481	The Data Pool Ingest Service shall raise an operator alert for local transfers when an attempt to transfer files to be ingested via local transfer results in one of the following errors:  a. file transfer attempts for N different files failed consecutively, where N is configurable on a global basis (see S-DPL-16482), b. the file transfer time exceeded it maximum allowed time as per configuration for that host (see S-DPL-16255) on file transfer attempts for N different files consecutively where N is configured on a global basis (see S-DPL-16482).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17482	The Data Pool Ingest Service shall raise an operator alert for local polling location when an attempt to access it for polling purposes results in one of the following errors: a. the source directory does not exist, b. the permission to read the directory is denied. c. there are N consecutive errors while attempting to transfer PDR files from the location, where N is configurable on a global basis (see S-DPL-16482), d. there are N consecutive time-outs while attempting to transfer PDR files from the location, where N is configurable on a global basis (see S-DPL-16255 and S-DPL-16482).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17483	The Data Pool Ingest Service shall raise no more than one operator alert each for a given local polling location.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17484	The Data Pool Ingest Service shall raise no more than one operator alert each for local file transfers.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17485	The Data Pool Ingest Service shall suspend polling for a local polling location while an alert is currently pending for it.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17486	The Data Pool Ingest Service shall suspend all local file transfers while an alert is currently pending for local file transfers.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17487	Unless a local polling location was suspended by the operator, the Data Pool Ingest Service shall automatically retry polling it while it is suspended, if local polling and transfers are so configured (see S-DPL-16255), using the retry time interval configured for local polling and tile transfers (see S-DPL-16255), and: a. clear the corresponding alert condition, b. resume polling for the polling location.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17488	Unless local file transfer was suspended by the operator, the Data Pool Ingest Service shall automatically retry performing local file transfers if local polling and transfers are so configured (see S-DPL-16255), using the retry time interval configured for local polling and tile transfers (see S-DPL-16255), and: a. clear the corresponding alert condition, b. resume local file transfers.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17490	The Data Pool Ingest Service shall raise an operator alert for an scp host when an attempt to access a polling location via scp results in one of the following errors: a. connection with the target host could not be established despite retrying for the number of times as configured for retriable errors (see S-DPL-16480), b. scp login failed, c. DELETED, d. DELETED, e. there are N consecutive errors while attempting to transfer PDR files from the location, where N is configurable on a global basis (see S-DPL-16482), f. there are N consecutive time-outs while attempting to transfer PDR files from the location, where N is configurable on a global basis (see S-DPL-16293 and S-DPL-16482).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17500	The Data Pool Ingest Service shall raise an operator alert for an scp host when an attempt to transfer files to be ingested via scp results in one of the following errors: a. connection with the target host could not be established despite retrying for the number of times as configured for retriable errors (see S-DPL-16480), b. scp login failed, c. the source directory does not exist, d. the permission to read the source directory is denied, e. file copy attempts for N different files failed consecutively, where N is configurable on a global basis (see S-DPL-16482), f. file copy attempts for N different files timed-out consecutively, where N is configurable on a global basis (see S-DPL-16293 and S-DPL-16482).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17510	The Data Pool Ingest Service shall raise an operator alert for an scp host when an attempt to transfer PAN and PDRD notification files results in one of the following errors: a. connection with the target host could not be established despite retrying for the number of times as configured for retriable errors (see S-DPL-16480), b. scp login failed, c. the target directory does not exist, d. the permission to write to the directory is denied, c. file transfer attempts for N different PAN or PDRD failed or timed-out consecutively, where N is configurable on a global basis (see S-DPL-16293 and S-DPL-16482).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17520	The Data Pool Ingest Service shall raise no more than one operator alert each for polling, file transfers, and notification for a given scp host and separate for each provider where the alert affects only a specific one. [NOTE: That is, separate alerts may be raised for each type of activity to let DAAC operators know when an activity is impacted, and the alert may in addition be provider specific if the error is provider specific.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17530	The Data Pool Ingest Service shall suspend dispatching polling and file transfers, including pulling files referenced in a PDR and transferring PAN or PDRD files, for an scp host while an alert is currently pending for it if the nature of the error causing the alert would impede the intended operation: a. If the alert is due to an inability to connect with the host, all polling and transfers for that host shall be suspended. b. If the alert is due to a login failure for file retrieval, polling and file transfers from that host for that provider shall be suspended; PAN and PDRD transfers shall continue. c. If the alert was raised during file transfer because the source directory does not exist or the permission to access the source directory was denied, all file transfers for that host and provider shall be suspended; polling and PAN and PDRD notifications shall continue. d. If the alert was raised during PAN or PDRD transfer because of a login failure or non-existence of the target directory or lack of permission to write to the target directory,  PAN and PDRD transfers for that provider shall be suspended; polling and file transfer operations shall continue. e. If the alert is due to N consecutive file/PDR transfer failures or file/PDR transfer time-outs, polling respectively file transfer operations shall be suspended; PAN and PDRD transfers shall continue. f. If the alert is due to N consecutive PAN or PDRD transfer failures or time-outs, polling and file transfer operations shall continue; PAN and PDRD transfers for that provider shall be suspended. [NOTE: The requirement implies that there may be several alert conditions that have different consequences. As per S-DPL-17520, the alert conditions must be maintained to assure that the appropriate services are suspended and resumed as the conditions are detected or cleared.  Though there is currently no such case, a host could support ftp and scp access.  If so, suspensions due to alerts may or may not affect ftp and scp operations, subject to design considerations.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17540	Unless the scp host was suspended by the operator, the Data Pool Ingest Service shall automatically retry establishing connection, login, and performing another transfer for an scp host that is currently suspended, if the scp host is so configured, using the retry time interval configured for that host, and shall react as follows when a retry succeeds: a. clear the corresponding alert condition and the alert as a whole if there are no other alert conditions for that host, b. resume dispatching of the operations for that host that were suspended as a consequence of that alert condition.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17545	The Data Pool Ingest Service shall raise an operator alert for a polling location when an attempt to access a polling location via scp results in one of the following errors: a. the source directory does not exist, b. the permission to read the directory is denied.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17546	The Data Pool Ingest Service shall suspend polling for a polling location while an alert is pending for it. [NOTE: The polling location alert for PDRs referencing data not valid for Data Pool Ingest will be removed as part of the extension of Data Pool Ingest to non-SIPS data.]  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17547	Unless a polling location was suspended manually by an operator, the Data Pool Ingest Service shall automatically retry polling from a polling location while an alert is pending for it using the retry time interval configured for the corresponding host, and clear the corresponding alert condition and resume polling for that location if the retry succeeds.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17560	The Data Pool Ingest Service shall not automatically resume dispatching for data providers and polling locations that were manually suspended by the operator.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17563	The Data Pool Ingest Service shall raise an alert for an archive when one of the following situations occur: a. DELETED, b. DELETED, c. the target archive file system is down (i.e., is not mounted), d. DELETED, e. DELETED, f. the percentage of consumed disk space exceeds the configured cache warning threshold (this condition will not suspend the archive, see-S-DPL-16482), g. the percentage of consumed disk space exceeds the configured cache full threshold (this condition will suspend the archive, see-S-DPL-16482). [NOTE: Archiving operations are performed on ECS Service Hosts.  Archiving errors can be caused by archive cache file system being down (see c. above), or by the host having SAN connectivity problems (which will lead to consecutive archive write errors or time-outs.  In that case, the alert will be raised for the ECS Service Host rather than an archive.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17564	The Data Pool Ingest Service shall raise no more than one operator alert for a given archive.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17565	The Data Pool Ingest Service shall suspend dispatching archive write operations for an archive while an alert is pending for it.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17566	The Data Pool Ingest Service shall automatically retry archiving operations for an archive while an archive is suspended and an alert remains pending, using the retry time interval globally configured for alert situations (see S-DPL-16482), and clear the alert and resume dispatching operations for that archive when a retry succeeds, unless Data Pool archiving for the archive was suspended by the operator.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17567	The Data Pool Ingest Service shall clear the corresponding archive alert when it detects that the consumed cache space for an archive cache has fallen below the low watermark threshold for clearing the corresponding alert (see S-DPL-16482). [NOTE: If both thresholds were exceeded, the archive alert is only cleared after cache use dropped below the low watermark for the cache warning, however, the nature of the alert will change as the low watermark for the cache full alert is underrun.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17568	The Data Pool Ingest GUI shall close an alert for an archive after the operator manually suspended that archive. [NOTE: Operators can manually suspend an archive an alert is pending. If they do this, the alert is closed and the archive is considered manually suspended. Automatic retries will cease.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17570	The Data Pool Ingest Service shall raise an operator alert for a Data Pool file system when one of the following situations occurs: a. the file system is full, b. the file system is down (i.e., not mounted), c. attempts to access that file system failed for N different granules consecutively, where N is configurable on a global basis (i.e., one value for all file systems, see S-DPL-16482). [NOTE: File system errors encountered by an ECS Service Host that are not diagnosed as the file system being full or down will lead to N consecutive errors for that host rather than the file system, signaling that the host may have SAN connectivity problems. However, if the same situation occurs on the Ingest Server host, it will lead to a file system alert, signaling that the Ingest Server host has SAN access problems that may be a SAN or a host related error.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17580	The Data Pool Ingest Service shall monitor the free space in Data Pool file system at an operator configurable time interval (see S-DPL-16545).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17590	The Data Pool Ingest Service shall raise an operator alert for a Data Pool file system when it is reported as more than N% full (i.e., nearly full condition) without suspending ingest and insert operations for that file system and with N being configurable by the operator (see S-DPL-16545).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17600	The Data Pool Ingest Service shall clear any pending operator alert for a Data Pool file system being nearly full when it is reported as less than N% full, with N being configurable by the operator (see S-DPL-16545).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17610	The Data Pool Ingest Service shall raise no more than one operator alert for a given Data Pool file system.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17620	The Data Pool Ingest Service shall mark a Data Pool file system as full if it raises an alert because of that file systems full condition.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17630	The Data Pool Ingest Service shall suspend dispatching ingest operations that use a Data Pool file system while an alert is currently pending for it except if: a. dispatching of ingest operations shall not be suspended if the alert indicates a file system nearly full condition, b. dispatching of archiving operations shall not be suspended if the alert indicates a file system full condition. [NOTE: see S-DPL-17112, S-DPL-18270 and S-DPL-18272 for related requirements.] 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17640	The Data Pool Ingest Service shall resume dispatching ingest operations that use a Data Pool file system for which it raised an alert because it was full when the file system full condition is cleared. [NOTE: The condition is currently cleared by Data Pool cleanup.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17650	The Data Pool Ingest Service shall raise an operator alert when an attempt to access any other ECS service on a particular host (such as the ECS Science Data Server, local file transfers, or agents that dispatch checksumming operations) results in one of the following errors: a. connection with the service cannot be established (e.g., the service, platform, or network are down), b. connection with the service is lost (e.g., the service or platform terminated abnormally and may be rebooted), c. a checksumming service request does not complete within an expected, configurable time frame (e.g., the checksumming operations take excessively long, see S-DPL-16460) for N different service requests consecutively (see S-DPL-16482), d. DELETED, e. the SDSRV metadata validation or insert service request times out or returns an error to N different granules consecutively, with N configurable by the DAAC (see S-DPL-16482), f. an ECS service returns errors for N consecutive granules or files, where the errors are not attributed to some other resource (e.g., a ftp or scp host).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17660	The Data Pool Ingest Service shall raise no more than one operator alert for a given ECS service.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17670	The Data Pool Ingest Service shall no longer dispatch operations for a given ECS service while an alert is currently pending for it.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17680	The Data Pool Ingest Service shall automatically retry connecting to or invoking an ECS service for which it suspended dispatching using a retry time interval that is globally configurable (i.e., that uses the same value for all ECS services, see S-DPL-16482), and clear the alert and resume dispatching operations for that service when a retry succeeds, unless the service was suspended by the operator. [NOTE: Local file transfers do allow for a separately configured retry interval as per S-DPL-16255.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17690	The Data Pool Ingest GUI shall allow authorized (ingest control and ingest admin) operators to configure an optional e-mail address to which notifications about alerts shall be sent.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17700	The Data Pool Ingest Service shall include the following information in the notifications about operator alerts: a. the resource that caused the alert (e.g., ftp host, data pool file system, ECS service), b. the nature of the alert.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17702	The Data Pool Ingest Service shall automatically resume granules that are currently suspended and were suspended in the course of raising an alert because the error occurred for N granules consecutively (for example, due to file system access errors or time out of archive operations), and close any related operator intervention that is currently open if all suspended granules for a request are resumed in this fashion.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17710	The Data Pool Ingest GUI shall display on the Data Pool Ingest Service status page, whether there are any current alerts.  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17720	The Data Pool Ingest GUI shall allow operators to monitor Data Pool Ingest Service alerts such that new alerts can be displayed within 20 seconds of them having been requested by the Data Pool Ingest Service, e.g., by allowing operators to list current alerts and allowing the operator to refresh that list manually, as well as via automatic refresh as often as every 20 seconds.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17730	The Data Pool Ingest GUI shall show on the screen that operators use to monitor alerts, the following information for each alert: a. time the alert was created, b. the resource that caused the alert, c. the type of the alert indicative of the cause for the alert.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17740	The Data Pool Ingest GUI shall permit an operator to filter operator alerts by a. type of resource, b. type of alert, c. a combination of both.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17750	The Data Pool Ingest GUI shall permit an operator to sort alerts in ascending or descending order of creation time, with descending order (i.e., latest first) being the default.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17760	The Data Pool Ingest GUI shall permit an operator to select an alert from the monitoring screen to view detailed information about it, including detailed error information and associated alert conditions. [NOTE: For some alerts, Data Pool Ingest will need to differentiate between several alert conditions which may cause different functions to be suspended, see S-DPL-17470.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17770	The Data Pool Ingest GUI shall permit an authorized (ingest control) operator to select an alert from the monitoring screen to close it.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17780	The Data Pool Ingest GUI shall permit an operator to list the data providers affected by an archive or Data Pool file system alert, and the number of ingest requests, number of granules, and total amount of data currently queued or in processing that are affected by an alert. [NOTE: This overlaps with system monitoring requirements, see S-DPL-16900, S-DPL-16940, and S-DPL-16950.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17790	The Data Pool Ingest Service shall check each polling location enabled for Data Pool ingest for Product Delivery Records (PDR) in accordance with the polling frequency and polling method configured for that polling location unless the polling for that location, host, or provider, or all Data Pool Ingest processing have been suspended. [NOTE: In case of automatic suspension, DPL Ingest will continue to retry at least the operation that caused the suspension.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17800	The Data Pool Ingest Service shall not process a PDR that already was processed by the INGST CI and shall process PDRs that were not processed by the INGST CI, and vice versa. [NOTE: This is intended to support transition from INGST to Data Pool Ingest and vice versa without processing a PDR more than once.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17810	The Data Pool Ingest Service shall start the next polling cycle immediately upon completion for the previous one, if the previous one took longer than the configured polling frequency assumes.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17820	The Data Pool Ingest Service shall not queue an ingest request for the same PDR more than once.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17830	The Data Pool Ingest Service shall assign an initial priority to an ingest request as configured for the data provider.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17840	During initial validation, the Data Pool Ingest Service shall verify the contents of the PDR against the specifications in ESDIS Document 423-41-57, Interface Control Document between the EOSDIS Core System (ECS) and the Science Investigator-led Processing Systems (SIPS), Volume 0, Interface Mechanisms, including verifications that are currently being performed: a. the syntax of the PDR conforms to ESDIS Document 423-41-57, e.g., the keywords and file types are valid, b. all mandatory information is present in the PDR, c. the checksum type is valid and if present, a checksum value is present as well and is syntactically correct (i.e., agrees with the type of checksum, e.g., for MD5 the value must be a 32-character hexadecimal string; for cksum it must be a 32-bit unsigned integer value, for ECS checksum a 64-bit integer value), d. the data type is valid, e. if the data type version is provided, that version of that type is configured for ingest, f. the file count is correct, g. DELETED.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17850	The Data Pool Ingest Service shall log a warning if an expiration date is provided that is incorrect or in the past.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17860	The Data Pool Ingest Service shall reject a granule and return a long PDRD error disposition if the checksum type and checksum value parameters are not present for each science file in a PDR from a SIPS provider for which the presence of these parameters has been made mandatory.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17870	The Data Pool Ingest Service shall reject a granule and return a long PDRD error disposition if the checksum type in the PDR from a SIPS provider is not on a list of ECS supported checksum algorithms.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17875	The Data Pool Ingest Service shall reject a granule and return a long PDRD error disposition if the checksum type parameter is present in the PDR from a SIPS provider and the checksum value parameter is not.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17880	The Data Pool Ingest Service shall reject a granule and return a long PDRD error disposition if the checksum value parameter is present in the PDR from a SIPS provider and the checksum type parameter is not.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17890	The Data Pool Ingest Service shall reject a granule and return a long PDRD error disposition if the checksum value parameter is present in the PDR from a SIPS provider and syntactically incorrect.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17895	The Data Pool Ingest Service shall ignore checksum type and checksum value parameters for all types of files other than science files.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17900	The Data Pool Ingest Service shall notify a SIPS provider via the configured notification method if an ingest request fails initial validation, collecting and reporting all detected errors using a short or long Product Delivery Record Discrepancy (PDRD) in accordance with SIPS ICD Volume 0, ESDIS Document 423-41-57. [NOTE: Errors in the expiration date are not considered validation failures; see S-DPL-17850.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17910	The Data Pool Ingest Service shall use the most recent delivery information for a provider on any notification deliveries performed, including after the information was modified by the operator. [NOTE This is needed if the PAN/PDR deliveries fail, for example, due to a change in the login information.]    	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17915	The Data Pool Ingest Service shall not deliver provider notifications while the delivery of notifications for the provider to that host is suspended. [NOTE: In case of an automatic suspension, Data Pool Ingest will continue to retry at least the operation that caused the suspension.] 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17920	The Data Pool Ingest Service shall not deliver provider notifications via e-mail while the delivery of e-mail notifications is suspended. [NOTE: In case of an automatic suspension, Data Pool Ingest will continue to retry at least the operation that caused the suspension.] 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17970	The Data Pool Ingest Service shall transfer the files for each granule into a temporary Data Pool area that is located on the file system configured for the corresponding Data Pool collection, using the configured transfer method, unless the files already reside in the correct Data Pool location.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17980	The Data Pool Ingest Service shall perform file transfers on the ECS platforms configured for that purpose, subject to the limits of concurrent transfers that may be in progress on each platform (see S-DPL-16460). [NOTE: The intent is to balance the transfer loads across these platforms roughly proportional to the configured number of 'transfer slots'.  Note that scp transfers will be performed only on platforms that are enabled for that purpose.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17985	The Data Pool Ingest Service shall suspend a granule and request an operator intervention if the file transfer for a granule fails, unless the failure signals the need for an operator alert.  	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17990	The Data Pool Ingest Service shall verify the size of a file against its size stated in the PDR, and suspend the granule if the size verification fails.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-17995	The Data Pool Ingest Service shall randomly select science files for which checksums are provided for checksum verification such that on average, checksums are verified for a percentage of the files with checksums that corresponds to the checksum verification percentage configured for that provider.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18000	The Data Pool Ingest Service shall randomly select science files for which no checksums are provided for checksum calculation such that on average, checksums are calculated for a percentage of those files that corresponds to the checksum verification percentage configured for that provider. [NOTE: This was originally configured by archive and can now be configured by provider.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18010	The Data Pool Ingest Service shall include the checksum for a file in the granule metadata, for inclusion in the SDSRV and DPL inventories and Data Pool XML file. [NOTE: The inclusion of checksum information in the SDSRV and Data Pool inventories and XML files is regulated by other, existing L4 requirements.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18015	The Data Pool Ingest Service shall use the checksum algorithm configured for the checksum type of a file to verify that file.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18020	The Data Pool Ingest Service shall use the configured default checksum type to calculate the checksums of files for which no checksum is provided.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18025	The Data Pool Ingest Service shall perform checksum operations on the ECS platforms configured for that purpose, subject to the limits of concurrent CPU intensive operations that may be in progress on each platform (see S-DPL-16460). [NOTE: The intent is to balance the checksum workload across these platforms roughly proportional to the configured number of 'CPU slots'.  As per S-DPL-16460, the limits for CPU-intensive operations apply to all such operations executed by the Data Pool CI, i.e., not just the Data Pool Ingest Service.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18030	The Data Pool Ingest Service shall not checksum a file for the purpose of verifying a provider checksum on the platform that was used to execute its file transfer, unless no other platform has been configured for that purpose. [NOTE:  Currently, the transfer and the checksum operation are usually both performed on the drg-host that is configured as the archive platform for this ESDT.  Today, checksum verification is performed by re-reading the file from archive cache; with Data Pool ingest, checksum verification will re-read the file from the Data Pool file system.  It is, therefore, desirable, to perform checksum verification on a different platform than the one used to transfer the granule into the SAN, to avoid reading the file from the file system cache rather than the file system itself.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18040	The Data Pool Ingest Service shall set checksum origin to 'DataProvider' if the checksum value was received from a data provider, and to DPLIngst when it calculates a checksum for a file for which no checksum was included by the data provider.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18045	The Data Pool Ingest Service shall move a file to a DAAC configurable holding directory if its checksum verification fails (unless the failure signals the need for an operator alert), appending a unique qualifier if this is necessary to prevent overwriting a file that already exists in that directory. [NOTE: The inclusion of checksum information in the SDSRV and Data Pool inventories and XML files is regulated by other, existing L4 requirements.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18050	Unless the granule files already were resident in the correct Data Pool file system and thus, no file transfer took place, the Data Pool Ingest Service shall retry the granule file transfer operations a DAAC-configurable number of times in the event that the granule fails checksum verification and fail the granule non-retriably (i.e., without requesting an operator intervention) if the retries do not succeed (see S-DPL-16500). [NOTE:  This is modeled after the current INGST behavior which fails the granule rather than suspending it. This is considered a hard failure that will result in a PAN reporting a checksum validation error.  There will be no option for the operator to retry the granule.  If this is the only type of failure in the ingest request, Data Pool ingest will not request an operator intervention.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18055	The Data Pool Ingest Service shall translate pointers in linkage files associated with Browse, Production History (PH) and Quality Assurance (QA) granules in accordance with ESDIS Document 423-41-57, and include the resulting linkage information in the metadata for that granule. [NOTE: It is highly desirable that the pointer translation not use the SDSRV CI interfaces.  The inclusion of linkage information in the SDSRV and Data Pool inventories and XML metadata is regulated by other, existing L4 requirements.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18060	The Data Pool Ingest Service shall retry failed linkage translations for a granule up to a DAAC configurable number of times and at a DAAC configurable frequency before suspending it, unless the failure signals the need for an operator alert (see S-DPL-16490).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18065	The Data Pool Ingest Service shall convert metadata files it receives in .met format into XML format for insertion into the Data Pool.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18070	The Data Pool Ingest Service shall convert metadata files it receives in XML format into .met format for insertion into the SDSRV inventory if the granule is to be archived. [NOTE: This capability is needed, for example, to process cross-DAAC ingest operations.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18071	The Data Pool Ingest Service shall interface with the SDSRV CI to validate the metadata of granules that are to be archived.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18072	The Data Pool Ingest Service shall accept the metadata validation response from the SDSRV CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18073	The Data Pool Ingest Service shall suspend a granule that failed metadata validation, unless the nature of the response indicates the need to raise an alert as per S-DPL-17650. [NOTE: That is, an alert is raised and the granule is not suspended if the SDSRV is down or if this is the N-th consecutive error or time-out.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18074	The Data Pool Ingest Service shall make any error details related to metadata validation available for display on the operator GUI as part of displaying the error details for the suspended granule or the alert.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18075	The Data Pool Ingest Service shall insert the granules it ingests into the hidden Data Pool directory structure.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18081	The Data Pool Ingest Service shall not apply granule replacement logic and prevent file name collisions when inserting ingested granules into the hidden directory structure, such that granules that are ingested but not published will never overwrite another granule in the Data Pool, nor cause a file name collision with another granule in the Data Pool.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18082	When inserting ingested granules into the hidden Data Pool that belong to collections enabled for HEG processing, the Data Pool Ingest Service shall obtain the band parameter information and make it available for insertion into the Data Pool inventory, doing so without increasing the granule insert time by more than 5 seconds.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18083	The Data Pool Ingest Service shall not fail ingest of a granule if the band information extraction yields no bands or fails, in case of retriable errors after the required number of retries. [NOTE: The general retry parameters in S-DPL-16480 apply.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18084	The Data Pool Insert Service shall log the start and completion of band extraction, including the following information:  a. granule identification, b. esdt, c. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18095	The Data Pool Ingest Service shall assign the priority of the ingest request to the Data Pool insert actions it queues for the Data Pool Insert Service.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18120	The Data Pool Ingest Service shall place an action into the Data Pool Insert Service queue to insert ingested granules that belong to ECS collections into the public Data Pool if the corresponding Data Pool collection is so configured.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18136	The Data Pool Ingest Service shall suspend granules whose  insert into the hidden Data Pool directory structure fails retriably when the retry count exceeds the configured maximum. [NOTE: Granules that experience a non-retriable Data Pool insert error are suspended immediately.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18140	The Data Pool Ingest Service shall identify all granules in the Data Pool inventory as needing to be copied to the ECS archive until their archive operation has completed.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18170	The Data Pool CI shall permit the successful distribution of granules once they have been ingested into the Data Pool successfully.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18178	The Data Pool Ingest Service shall interface with the SDSRV CI to pre-assign an ECS granule ID to a granule that is being ingested after it has been successfully transferred, checksummed (if applicable), and preprocessed.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18179	The Data Pool Ingest Service shall interface with the SDSRV CI to request insertion of the metadata for an ingested granule into the ECS inventory and provide the pre-assigned ECS granule ID on that occasion.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18180	The Data Pool Ingest Service shall accept the result of a metadata insertion request from the SDSRV CI.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18185	The Data Pool Ingest Service shall suspend a granule whose metadata insert failed, unless the failure indicates the need for an operator alert as per S-DPL-17650.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18190	The Data Pool Ingest Service shall suspend a granule if the SDSRV CI returns a response signaling a non-retriable error, unless the failure indicates the need for an operator alert.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18195	The Data Pool CI shall include the ECS granule identifier assigned to a granule by the SDSRV in the Data Pool inventory metadata and XML file.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18196	The Data Pool Ingest Service shall notify the provider using a short or long Product Acceptance Notification (PAN) constructed and formatted in accordance with the applicable ICD and using the configured notification method when all granules in an ingest request complete ingest (i.e., were archived and their metadata inserted into the ECS inventory) or reached some terminal error state. [NOTE: Data Pool publishing is not part of the ingest process.  Granules that cannot be queued for Data Pool publication may show an error state indicating that fact, but will be reported as having completed ingest successfully.  The Data Pool publishing step will occur asynchronously and decoupled from insert processing and will have no influence on the terminal state of the granule as recorded by Data Pool Ingest.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18200	The Data Pool Ingest Service shall maintain the following request states: a. New when a request is queued or re-queued for ingest, b. Active when a request is activated, c. Partially_Suspended when some but not all of the granules in a request are suspended, that is, some granules in the request are still being processed d. Suspended when a request is suspended, requiring operator intervention to resume it; this includes the situation when all granules in a request are suspended, e. Cancelling while a request is being cancelled, f.  Resuming while a request is being resumed, g. Successful when a request completes successfully, h. Cancelled when a request is cancelled by the operator and none of the granules have completed ingest successfully, i. Partially_Cancelled when a request is cancelled by the operator when some of its granules had already completed ingest successfully j. Failed when all granules in a request failed ingest, k. Partial_Failure when some but not all granules in a request failed ingest. l. Terminated when a new or active request is terminated as part of a cold start. m. Validated after the ingest request (PDR) was validated successfully.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18210	The Data Pool Ingest Service shall maintain the following granule states: a. InsertErr when the granule cannot be inserted into the SDSRV successfully, b. Inserted when the granule metadata was successfully inserted into the SDSRV inventory, c. Inserting while the granule metadata are being inserted into the SDSRV inventory, d. Cancelled when the granule is failed by the operator, e. Cancelling while the granule is being cancelled, f. Checksumming while the granule files are being checksummed g. Checksummed after the granule completed checksumming successfully, h. ChecksumErr when checksumming of a granule file fails i. InitErr when a granule fails before it has started ingest processing , j. New when the granule is queued or re-queued for ingest, k. Preprocessed when the granule was successfully preprocessed, l. Preprocessing while the granule is being preprocessed, m. PreprocErr when a granule fails during preprocessing, n. Resuming while a granule is being resumed, o. Successful when a granule completed ingest successfully, p. Suspended when further processing for a granule is suspended, pending operator intervention, q. DELETED r. Transferred when the granule files were successfully transferred, s. Transferring while the granule files are being transferred, t. XferErr when a granule fails during transfer, u. Archiving while the granule files are being copied to their archive location, v. Archived when the granule files were copied to their archive location successfully, w. ArchErr when the granule fails during archiving x. DELETED, y. TBD if the granule was successfully queued for publication in the Data Pool, z. PubErr if queuing the action to publish the granule in the Data Pool failed [NOTE that the state is merely an indication that the granule failed to queue for Data Pool publication despite having completed ingest successfully and that any PAN sent to the provider will identify that granule as successful) , aa. DELETED, ab. DELETED, ac. DELETED, ad. DELETED, ae. DELETED, af. DELETED.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18220	The Data Pool CI shall recover after a fault such that: a. Ingest requests or granules will not be lost or skipped, nor ingested twice b. Notifications will not be lost or skipped, c.  Notifications are not sent more than once, d.  Product delivery records are not processed more than once, e.  The state of requests and granules at the time of the fault is recovered such that expensive ingest steps that were completed at the time of the fault will not be started again, such as file transfers, and checksum operations, and no ingest steps will be omitted, f.  No Data Pool ingest requests, nor any other ECS requests will fail or raise operator interventions just because of the fault recovery, g. Requests that were active at the time of the fault will be activated before any new work is started, h. Granule operations that were active at the time of the fault will be restarted before any new work is started, i. Granules that have not completed ingest at the time of the fault will not be visible to external users until their ingest is complete, j. The state of alerts and queues will be recovered, to the extent that they have not been changed by the operator during the outage caused by the fault, k. The state of operator interventions will be recovered to the extent that they have not been changed by the operator during the outage caused by the fault, l. The state of resources will be recovered to the extent that they have not been changed by the operator during the outage caused by the fault, m. No Data Pool insert actions are omitted and no granules are queued for Data Pool publication more than once.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18225	The Data Pool CI shall be able to complete recovery from a fault, including restarting ingest requests and granules that were active at the time of the fault in less than 15 minutes with at least 1,000 ingest requests and at least TBD granules currently queued or active at the time of the fault  [TBD by Integration Test Plan Review.] 	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18230	The Data Pool Ingest Service shall limit the number of concurrent transfers (excluding PDRD, PAN and PDR files) to the maximum configured by the operator for that ftp respectively scp host, or to the configured default values if no specific values are configured for that ftp/scp host (see S-DPL-16460).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18235	The Data Pool Ingest Service shall limit the number of concurrent local file transfers (excluding PDRD, PAN and PDR files) to the maximum configured by the operator (see S-DPL-16255).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18240	The Data Pool Ingest Service shall limit the number of concurrent checksum processes that it executes on an ECS host to a maximum configured by the operator for that host or to the default value if no specific value is configured for that host (see S-DPL-16460). [NOTE: That is, the limit applies regardless of which Data Pool service is requesting the checksum verification. The intent of the limit is to ensure checksum operations leave enough CPU resources for other activities which these hosts perform, and to prevent extreme variability in the amount of time it takes to execute these activities, i.e., make them more predictable.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18260	The Data Pool Ingest Service shall assign managed resources (i.e., file transfer, archiving, and checksumming slots) to active granules by priority, and within the same priority on a first-in first-out basis based on the time the corresponding request was originally created, such that the configured limitations on these resources are observed.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18265	The Data Pool Ingest Service shall minimize the amount of time managed resources are held by an ingest operation, e.g., release resources as soon as they are no longer needed, e.g., when a request is suspended or can no longer proceed. [NOTE: This requirement cannot be verified through testing.  It shall be verified during code inspection.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18270	The Data Pool Ingest Service shall activate queued ingest requests for processing by priority, and within the same priority on a first-in first-out basis based on the time each request was originally created, provided the requests meet the following conditions: a. Ingest is not suspended, b. There is no active request whose granules could be activated at this point, c. The provider of that ingest request is not suspended, d. At least one granule in the request could be activated (see S-DPL-18275). [NOTE: For example, a request may be the next one in line to be activated, but if it requires file transfers from an FTP host whose queue is backed up (i.e., which is deemed not available), it may not be the next request that is actually activated.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18272	The Data Pool Ingest Service shall not consider a queued ingest request eligible for activation if any of its granules requires a resource that is currently suspended by the operator or due to an alert, unless the operator explicitly relaxed this requirement (see S-DPL-17112 and S-DPL-16460). [NOTE: Such requests could not complete since some of their granules cannot be processed. Activating them nevertheless could result in a large number of active requests that cannot be completed at this time. However, if the granules that could be processed require a resource that is a bottleneck, then allowing them to be activated may be necessary to alleviate the bottleneck and speed up recovery. Note that as per requirement S-DPL-18265, such stuck requests may not block any resources, e.g., must not be counted against any system or provider limits.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18275	The Data Pool Ingest Service shall activate granules for active ingest requests by priority, and within the same priority on a first-in first-out basis based on the time each request was originally created, provided the following conditions are met: a. The number of active granules and their total size are below the configured (system) limits (see S-DPL-16460), b. The number of active granules for that provider and the total size of those granules are below the limit configured for that provider (see S-DPL-16110); or there are no other active or queued requests for other providers whose granules could be activated, c. if the granule is queued for retry, its retry delay has expired, d. the ingest request containing the granule is still active (e.g., not suspended or cancelled), e. the archive required by the granule is not suspended due to an alert, unless the DAAC configured Data Pool ingest to continue activation of granules in this situation  (see S-DPL-16460g), f. the archive required by the granule is not suspended by the operator, unless the request was active at the time the archive was suspended by the operator (i.e., when the operator suspends an archive, currently active requests will be allowed to complete in any case) or the DAAC configured Data Pool ingest to continue activation of granules in this situation (see S-DPL-16460g) or, g. the Data Pool file system required by the granule is not suspended due to an alert, h. the Data Pool file system required by the granule is not suspended by the operator, unless the request was activated before the time the file system was suspended by the operator (i.e., when the operator suspends a file system, currently active requests will be allowed to complete in any case, but granules in newly activated requests  if any, see S-DPL-17112  that require the file system will not be activated), i.  None of the other resources required by the granule are suspended by the operator or due to an alert, j. If the granule requires transferring: there is a suitable transfer slot available which the granule can use immediately (i.e., do not activate a granule that requires transferring but cannot be transferred at this time)	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18280	The Data Pool Ingest Service shall not assign resources that are currently suspended by the operator or due to an alert except where other requirements explicitly state differently. [NOTE: For example, if the operator suspends an archive, currently active requests will be allowed to complete, see S-DPL-16951, S-DPL-18275; and the operator/DAAC can elect to continue to activate ingest requests and granules that target a suspended archive, see S-DPL-16460.  However, in the case of automatic suspension, the activity that caused the suspension will be retried.]   	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18285	The Data Pool Ingest Service shall create an application log whose format is compatible with ECS application logs.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18290	The Data Pool Ingest Service shall roll over application log files when they exceed a configured maximum size	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18295	The Data Pool Ingest Service shall log Cancellation Requests, including the following information: a. success or failure b. if failure, the reason for the failure c. identification of the requester, if available	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18296	The Data Pool Ingest Service shall log Requests for priority changes, including the following information: a. success or failure b. if failure, the reason for the failure c. identification of the requester, if available	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18300	The Data Pool Ingest Service shall log Suspension Requests, including the following information: a. success or failure b. if failure, the reason for the failure, c. identification of the requester, if available.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18310	The Data Pool Ingest Service shall log Resumption Requests, including the following information: a. success or failure b. if failure, the reason for the failure, c. identification of the requester, if available.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18320	The Data Pool Ingest Service shall log all errors, including the following: a. Request identification, if applicable, b. Granule Identification, if applicable, c. File information, if applicable, d. Error Type, Severity, and Explanation, e. Data provider, if applicable.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18330	The Data Pool Ingest Service shall log alerts that it raises, including the following: a. Identifying information for the resource, b. Type of alert and explanation.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18335	The Data Pool Ingest Service shall log operator interventions that it requests, including the following: a. Request identification, b. Type of intervention and explanation.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18340	The Data Pool Ingest Service shall log suspension and resumption of queues and resources, including the following: a. Identification of the queue or resource.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18345	The Data Pool Ingest Service shall log the start and completion of PDR validation, including the following information: a. Data provider, b. Polling location c. PDR file name, d. Request identification if available, e. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18350	The Data Pool Ingest Service shall log the start and completion of file transfers, including the following information: a. Data provider, b. Source and Target locations c. File name, d. File size e. Request identification, f. Granule identification, g. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18360	The Data Pool Ingest Service shall log the start and completion of checksum calculations, including the following information: a. Data provider, b. File path name, c. File size, d. Type of checksum, calculated checksum and  if applicable  original checksum e. Request identification, f. Granule identification, g. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18365	The Data Pool Ingest Service shall log the start and completion of preprocessing operations such as pointer translation, including the following information: a. Data provider, b. Request identification, c. Granule identification, d. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18366	The Data Pool Ingest Service shall log the start and completion of archiving operations for granules, including the following information: a. Data provider, b. Request identification, c. ECS granule ID, d. archive, e. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18367	The Data Pool Ingest Service shall log the start and completion of archiving operations for files, including the following information: a. Data provider, b. Request identification, c. ECS granule ID, d. Source and target file name, e. archive, f. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18370	The Data Pool Ingest Service shall log the start and completion of SDSRV metadata inserts, including the following information: a. Data provider, b. Request identification, c. Granule identifications, including Data Pool granule ID, when available, d. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18375	The Data Pool Ingest Service shall log queuing Data Pool insert actions, including the following information: a. Data provider, b. Request identification, c. Granule identifications, including Data Pool granule ID, when available, d. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18380	The Data Pool Ingest Service shall log the start and completion of ingest operations for a granule, including the following information: a. Data provider, b. Request identification, c. Granule identifications, including Data Pool and ECS granule ID, when available, d. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18385	The Data Pool Ingest Service shall log the start and completion of ingest operations for a request, including the following information: a. Data provider, b. Request identification, c. Outcome.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18390	The Data Pool Ingest Service shall be able to generate a performance log compatible with the ECS performance log format to provide information about the frequency and duration of the following events: a. polling, separate by polling location b. file transfers, separate by source host c. PDR validation d. granule preprocessing e. granule metadata insert f. DELETED g. database transactions (e.g., stored procedure calls), separate by type of stored procedure h. mutex locks, separate by locked resource i. archive write operations, separate by archive j. ingest notification transfers, separate by target host	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18400	The Data Pool CI shall be able to ingest data distributed by another DAAC for cross-DAAC ingest.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18410	The Data Pool CI shall be able to accept the metadata of data distributed by another DAAC for cross-DAAC ingest in .met as well as XML file formats.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18420	The Data Pool CI shall verify the checksums of data it ingests from another DAAC.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18435	The Data Pool Ingest Service shall maintain request and granule states and information compatible with the INGST CI, except as required by S-DPL-18200 and S-DPL-18210.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18450	The DPL CI shall not remove ingested granules from the Data Pool until the corresponding ingest request completes. [NOTE: This includes cleanup request submitted by the OMS CI.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18455	The Data Pool Ingest Service shall remove ingested granules from the Data Pool after their ingest request completes, unless they are intended to be published in the Data Pool, reside in the public Data Pool, or are needed in fulfillment of orders, or their retention in the non-public area has not yet expired. [NOTE: Granules may be retained even after their ingest request completes to support orders, e.g., subscriptions.  Data Pool Ingest will rely on the Data Pool Insert Service and DlCleanup to clean up granules intended for publishing or published, and rely on OMS to clean up granules that are used for ordering purposes.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18460	The DPL CI shall remove the original versions of browse granules from the Data Pool after their ingest request completes, unless they are still needed in fulfillment of orders, or their retention in the non-public area has not yet expired, even if their jpeg representations need to be left in the public Data Pool.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18800	The Data Pool Insert Service shall archive all ingested granules in an ECS archive, doing so prior to registering these granules in the SDSRV inventory.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18810	The Data Pool Ingest Service shall copy ingested granules to the archive locations configured for the open volume groups to which the collection belongs. [NOTE: The primary and backup volume groups and the date for separating forward and reprocessing volume groups are defined in the STMGT database for each collection. The definitions take the form of target directories located in an archive cache file system. DAAC operations will use the DPL Ingest GUI to maintain that information, per NCR 44758.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18815	The Data Pool Ingest Service shall rename the files of a granule during archiving using the ECS granule ID that was pre-assigned to that granule and consistent with the SDSRV CI internal file naming convention. [NOTE: see S-DPL-18178 for the requirement for pre-assigning an ECS granule identifier.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18820	The Data Pool Ingest Service shall execute the archive write operations on the ECS Service Hosts configured for that purpose (see S-DPL-16460).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18825	The Data Pool Ingest Service shall observe the configured limit on the number of concurrent archive write operations for an ECS Service Host (see S-DPL-16460).	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18830	The Data Pool Ingest Service shall cancel an archive write operation if it does not complete within the time limit established in accordance with the configured time-out parameters, and retry the write operation until the configured number of maximum retries is exceeded, failing the archiving operation thereafter (see S-DPL-16460). [NOTE: Configuring the number of retries to zero would have the effect of failing the write operation without retry.  Note that N consecutive failures or timeouts of all current archive operations will cause an alert, as per S-DPL-16482.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18835	The Data Pool Ingest Service shall not dispatch archive write operations that require access to an archive that is suspended by the operator unless the corresponding ingest request was activated before the archive was suspended.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18840	The Data Pool Ingest Service shall suspend a granule whenever one of its write operations to one of its archive locations has encountered errors that could not be cleared by automatic retry, except when the error situation results in an operator alert.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18845	The Data Pool Ingest Service shall include the internal file information in the SDSRV metadata.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18850	The Data Pool Ingest Service shall record throughput statistics for archiving operations in the Data Pool Ingest database, as measured in terms of the number of granules and data volume per configured time interval (see S-DPL-16546): a. by archive, b. by Data Pool file system.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DPL-18855	The Data Pool Ingest Service shall obtain the cache status for archives in regular time intervals, as configured by the operator, and check the result against the configured alert thresholds.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DSS-72010	The SDSRV CI shall accept and process requests for the insertion of granule metadata into the ECS inventory. [NOTE: The insert is meant to include only the metadata; the insert request will not include granule files. This may require modifications to the SDSRV CI.]	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DSS-72011	The SDSRV CI shall accept and process requests for a pre-assigned ECS granule identifier, returning a unique ECS granule ID.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DSS-72013	The SDSRV CI shall accept a pre-assigned ECS granule ID and file metadata as part of the request for insertion of granule metadata into the ECS inventory.	
DP_S6_01	SIPS Ingest Into Data Pool	no data				S-DSS-72020	The SDSRV CI shall return a status indicating success or failure (including failure details) in response to a request for the insertion of granule metadata into the ECS inventory. [NOTE: The insert is meant to include only the metadata; the insert request will not include granule files.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25010	The Data Pool Archive GUI shall allow multiple operators to monitor and manage Data Pool archiving concurrently from different workstations.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25020	The Data Pool Archive Service shall support concurrent operation in multiple modes on the same and different hosts.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25030	The Data Pool Archive GUI shall support monitoring and managing Data Pool archiving in multiple modes concurrently on the same and different workstations. [NOTE: However, a single instance of the GUI will support one and only one mode.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25040	The Data Pool Archive GUI shall display the mode in which it is operating.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25050	The Data Pool Archive GUI shall be accessible via the web browsers that support the Data Pool Ingest GUI.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25060	It must be possible to protect the Data Pool Archive GUI against external access via appropriate configuration of the ECS firewall.  	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25080	The Data Pool Archive GUI shall use the same authorizations as the DPL Ingest GUI. [NOTE: This includes using a common login and applying the same authorization level for an operator to Data Pool archiving as to Data Pool ingest.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25099	The Data Pool Archive GUI shall be integrated with the Data Pool Ingest GUI in the sense that operators perceive the two as parts of the same GUI, with archiving and ingest information sharing the same screen where appropriate. [NOTE: This requirement will be verified by inspection during GUI reviews.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25100	The Data Pool Archive GUI shall allow authorized (ingest and archive tuning) operators to configure (i.e., define and edit) the following archiving policy parameters, separate for each volume group, as well as defaults to be used if no configuration information specific for a volume group exists: a. A data volume threshold for triggering archiving for the volume group in terms of data volume, b. A granule count threshold for triggering archiving for the volume group in terms of number of granules, c. A time threshold for triggering archiving for the volume group in terms of the time that expired since the last time the volume group was archived.  [NOTE: That threshold will be ignored if the volume group has accumulated less data than the configured minimum data threshold, see clause d.] d. A minimum data threshold for the minimum amount of data that must be waiting for archiving in a volume group before the volume group is considered eligible for archiving [NOTE: This will lead to a warning with request for confirmation if the operator attempts to activate the archiving of this volume group manually.] e. A maximum wait threshold in terms of the time that expired since the last time the volume group was archived which when exceeded, will cause the configured minimum data threshold (see clause d.) to be ignored. [NOTE: The primary and backup volume groups and the date for separating forward and reprocessing volume groups are defined in the STMGT database for each collection.  The definitions take the form of target directories located in an AMASS file system.  DAAC operations will continue to use the STMGT GUI to maintain that information. The Data Pool Archive GUI is used only to provide additional configuration information.  The mapping of the STMGT volume group directories to tape volume groups is defined in AMASS.  Throughout the requirements, the term volume group refers to tape volume groups unless explicitly specified otherwise.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25110	The Data Pool Archive GUI shall allow authorized (ingest and archive tuning) operators to configure (i.e., define and edit) the following resource management policy parameters to control the utilization of DAAC resources (the final set is  TBD by DDR ): a. Maximum number of volume groups that the Data Pool Archive Service may archive in parallel, separate for each archive [NOTE: This limit will be ignored but lead to a warning which the operator must acknowledge if the limit is exceeded by manual activation of volume groups], b. Maximum number of concurrent write operations to the archive cache per volume group, separately for each volume group, and a default value by archive to be used in the case that a separate value for a volume group has not been configured, c. The number of dirty cache blocks and the number of consumed F-nodes which when reached will trigger an operator alert, separate for each archive [ feasibility is TBD by PDR ], d.  The number of dirty cache blocks and the number of consumed F-nodes which when reached will trigger an operator alert and cause archiving for that archive to be suspended, separate for each archive [ feasibility is TBD by PDR ], e. A threshold which when underrun will clear the alerts referenced in c. and d., in terms of percent of the original threshold [ feasibility is TBD by PDR ], f. Parameters to calculate a time limit for cache write operations before assuming that they are hung, consisting of a minimum expected throughput and a time constant reflecting maximum expected fixed delays, separate for each archive [necessity is TBD by DDR], g. The number of consecutive archiving errors or hung copy operations that shall trigger an archive alert, independent of archive. [NOTE: The term archive refers to the silo, not the archive host.  Currently, there are archive hosts with more than one silo, and the future hardware architecture will evolve in that direction.  The archive hosts are defined in the STMGT database and DAAC operations will continue to use the STMGT GUI to maintain that information. The Data Pool Archive GUI is used only to provide additional configuration information]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25150	The Data Pool Archive GUI shall allow authorized (ingest and archive tuning) operators to configure the following Data Pool Archive Service cleanup parameters: a. the amount of time (in days) for which to retain information about completed archiving requests in the active database tables, b. the amount of time (in hours) for which to retain information about closed archiving interventions in the active database, c. the amount of time (in months) for which to retain information about completed archiving requests in the historic database tables, d. the amount of time (in months) for which to retain system monitoring information, e. the frequencies with which to perform the various cleanup operations. [NOTE: The cleanup parameters are meant to be distinct from those used by the Data Pool Ingest Service to cleanup its active requests, etc.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25160	The Data Pool Archive GUI shall allow authorized (ingest and archive tuning) operators to configure (i.e., define and edit) retry parameters (retry interval and maximum number of retries) for: a. retrying archive accesses, b. retrying Data Pool file system accesses [NOTE: This retry parameter is the same as that used by the Data Pool Ingest Service], c. retrying volume group archiving requests when they cannot be activated.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25170	The Data Pool Archive GUI shall allow authorized (ingest and archive tuning) operators to configure (i.e., define and edit) retry intervals for the following types of alert situations: a. an archive is suspended automatically and access to it needs to be retried, b. a Data Pool file system is suspended automatically and needs to be retried [NOTE: This retry parameter is the same as that used by the Data Pool Ingest Service.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25180	The Data Pool Archive GUI shall allow authorized (ingest and archive tuning) operators to configure (i.e., define and edit) the time interval for performing archive cache status checks.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25181	The Data Pool Archive GUI shall ask operators to confirm any changes to Data Pool archiving configuration parameters before saving them.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25185	The Data Pool Archive GUI shall allow all operators to view all Data Pool archiving configuration parameters.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25190	The Data Pool Archive Service shall make configuration changes effective within one minute after they were changed and saved via the Data Pool Archive GUI without requiring rebooting, with the exception of the following: a. A list of configuration parameters that require rebooting in order for their change to take effect is  TBD by DDR .   	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25200	The Data Pool Archive GUI shall allow operators to list the archive volume groups and display for each volume group: a. volume group host and path name(s) [ TBD by PDR  whether there can be more than one volume group path name], b. the number of granules and the total data volume currently in the Data Pool for that volume group but not yet archived, as well as the corresponding thresholds, c. the last time the volume group was archived, the elapsed time since then and the corresponding age threshold, d. status of the volume group, such as whether it is currently queued for archiving, in the process of being archived, or suspended, e. any resource management policy parameters configured for the volume group.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25210	The Data Pool Archive GUI shall allow operators to filter the list of archive volume groups by the following criteria: a. archive, b. status, c. one or several ESDT allocated to the volume group.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25220	The Data Pool Archive GUI shall allow operators to sort the list of archive volume groups by the following criteria: a. archive, b. status.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25230	The Data Pool Archive GUI shall allow authorized (ingest and archive control) operators to select one or several volume groups and suspend their archiving. [NOTE: Suspending a volume group will not affect archive cache write operations that are already in progress.  It will prevent any archiving request for the volume group from being activated; and if an archiving request for the volume group is currently active, no new archive cache write operations for it will be dispatched once the granules complete that are currently archiving.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25240	The Data Pool Archive GUI shall allow authorized (ingest and archive control) operators to resume the archiving of a suspended volume group. [NOTE: This makes the volume group eligible for being activated for archiving again, and will allow its archive write operations to be dispatched.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25250	The Data Pool Archive GUI shall allow authorized (ingest and archive control) operators to cancel an archiving request. [NOTE: This will cancel all write operations for the request that are already in progress and then terminate it. The granules whose write operations were canceled or were never dispatched will not be considered archived and will be archived the next time the corresponding volume group is dispatched.  If any granules failed, an operator intervention will be generated so the operator can disposition those.  In essence the request is interrupted and will appear as if the remaining granules (for which archiving was never attempted) had not been part of the request. Operations may employ this capability to halt archiving operations for a particular archive immediately (see also S-DPL-25400).]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25260	The Data Pool Archive GUI shall allow authorized (ingest and archive control) operators to select one or several volume groups that are currently not queued for archiving and queue archiving request for them.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25270	The Data Pool Archive GUI shall allow authorized  (ingest and archive control) operators to select one or several volume groups for which there are currently no active archiving requests and activate archiving requests for them (whether currently queued or not), provided that there is currently data for that volume group in the Data Pool that needs archiving.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25280	The Data Pool Archive GUI shall warn operators when they queue or activate an archiving request for a volume group that has less data to be archived than the configured minimum archiving threshold, or if the activation of these volume groups will cause the limit of volume groups that can be archived in parallel to be exceeded, or if the corresponding archive is suspended.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25290	The Data Pool Archive GUI shall ask the operator to confirm the activation of archiving for a volume group after displaying any related warnings.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25292	The Data Pool Archive GUI shall not permit the operator to activate the archiving of volume groups requiring an archive or a file system that is currently suspended.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25300	The Data Pool Archive GUI shall allow operators to list the archiving requests that are currently queued or active, listing the active ones first and sorting both list by archive and the queued ones within archive by current queue position, and display the following information for each archiving request: a. archive name, b. volume group host and path name(s) and volume group status (e.g., whether suspended), c. request status, i.e., queued or active, d. the number of granules and the total data volume to be written, e. resource management policy parameters configured for the volume group, and if the request is currently active, also the following: f. the number of granules and data volume written so far and current copy throughput (the meaning of current is  TBD by DDR ), g. whether at last check a drive was assigned to writing the volume group [ feasibility is TBD by PDR ]. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25301	The Data Pool Archive GUI shall precede the list of active and queued volume groups with information for each archive, 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25305	The Data Pool Archive GUI shall allow operators to filter the list of archive requests by: a. archive name, b. status (i.e., queued or active or both, c. any combination of a. or b.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25320	The Data Pool Archive GUI shall allow an operator to manually refresh the screen listing the archiving requests.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25330	The Data Pool Archive GUI shall permit operators to automatically refresh the screen listing archiving requests at an operator selected refresh interval of no less than N minutes. [NOTE: The value for N is  TBD by PDR .  It needs to be short enough to permit effective monitoring; and long enough to avoid overloading the data base when multiple monitoring stations are used by a DAAC concurrently.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25340	The Data Pool Archive GUI shall allow operators to display historic information about archiving requests performed by the DPL Archive Service, to: a. archive name, b. volume group host and path, c. start and completion date and time of the request, d. data volume in terms of amount of data and number of granules/files, e. final status, e.g., in terms of whether or not all granules were archived successfully, f. the number of granules not completed, g. average throughput achieved by that request [NOTE: Ideally, this would be the throughput achieved by its archive cache write operations and exclude dead time, e.g., while the request was suspended], h. indication whether the archiving request experienced suspension of resources, i. any operator annotations accumulated in interventions related to the volume group archiving request. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25345	The Data Pool Archive GUI shall allow operators to filter historic information about archiving requests performed by the DPL archive service by: a. archive, b. volume group, c. date/time period of start time or date/time period of completion time, d. final status, i.e., whether or not all granules were archived successfully, e. any combination of a. or b. with d. and e.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25350	The Data Pool Archive GUI shall allow operators to sort historic information about archiving requests performed by the DPL archive service by: a. start date/time, or b. completion date/time, or c. archive and volume group, or d. the number of granules that failed.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25360	The Data Pool Archive Service shall move information about completed archiving requests on a regular basis from the active to the historic database tables, leaving only information for the last configured number of days in the active database tables.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25362	The Data Pool Archive Service shall remove closed interventions on a regular basis, leaving only interventions for the last configured number of hours in the database.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25365	The Data Pool Archive Service shall remove historic information about completed archiving requests on a regular basis from the historic database tables, leaving only information for the last configured number of months in the database. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25370	The Data Pool Ingest Service shall remove any accumulated system monitoring information (e.g., alerts and throughput statistics) on a regular basis, leaving only system monitoring information for last configured number of months in the database.  	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25380	The Data Pool Archive GUI shall allow operators to display the Data Pool Archive Service status, to include: a. the list of archives in sequence of their name and status for each b. the list of Data Pool file systems in sequence of their name and status for each [NOTE: It is desirable to combine Data Pool Archive Service status with the corresponding archive / file system information displayed as part of the Data Pool Insert service status.] 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25390	The Data Pool Archive GUI shall include the following information as part of the archive status in the list of archives: a. archive name b. whether the archive is currently suspended, c. the number of Data Pool archive requests for it that are queued and active, d. the number of granules and the total data volume currently in the Data Pool destined for the archive but not yet archived e. number of dirty cache blocks, number of consumed F-nodes, as well as the corresponding thresholds [Feasibility is  TBD by PDR ], except if the archive is disk based.] [NOTE:  The term archive refers to a silo rather than archive host.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25400	The Data Pool Archive GUI shall allow authorized (ingest and archiving control) operators to suspend Data Pool archiving for an archive. [NOTE: Suspending an archive will not affect archiving requests that are already in progress (they will be allowed to complete), but it will prevent the activation of new archiving requests for that archive.  The purpose of suspending an archive is to permit operators to quiesce the archiving operations for an archive, e.g., in preparation for maintenance. To terminate the archiving operations for an archive immediately, the operator would first suspend the archive and then cancel any archiving requests for the archive that are still active.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25405	The Data Pool Archive GUI shall allow authorized (ingest and archiving control) operators to resume Data Pool archiving for an archive.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25410	The Data Pool Archive GUI shall include the following information as part of the file system status in the list of Data Pool file systems: a. status of the file system, e.g., whether the file system is full or suspended, b. status of the archiving operations for the file system, i.e., whether archiving operations for the file system are enabled or suspended, and whether archiving requests for volume groups that have data on the file system are currently active, c. the number of granules and the total data volume currently in that file system that need archiving.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25430	The Data Pool Archive GUI shall allow an operator to manually refresh the screen displaying the current status of Data Pool Archiving.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25435	The Data Pool Archive GUI shall permit operators to automatically refresh the screen displaying the current status of Data Pool Archiving at an operator selected refresh interval of no less than N minutes. [NOTE: The value for N is  TBD by PDR .  It needs to be short enough to permit effective monitoring; and long enough to avoid overloading the data base when multiple monitoring stations are used by a DAAC concurrently.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25440	The Data Pool Archive Service shall request an operator intervention for an archiving request whenever its archiving operation has encountered errors that could not be cleared by automatic retry, except in those cases explicitly excepted by other requirements or when the error situation generated an operator alert.  	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25445	The Data Pool Archive Service shall request an operator intervention for an archiving request if the archiving request terminates or was cancelled and at least one of the granules in the request for which archiving was attempted failed to archive despite retries.  	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25450	The Data Pool Archive Service shall not have more than one request for operator intervention for a given archiving request pending at the same time. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25455	The Data Pool Archive Service shall identify the granules that failed during archiving of a volume group, as well as the reason for each failure in terms of an intervention type (preliminary classification of failure causes is  TBD by PDR ) and error details.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25460	The Data Pool Archive Service shall not include suspended or failed granules in a volume group archiving request. [NOTE: This prevents suspended granules from being retried before the operator had a chance to make a disposition; and it prevents failed granules from being retried over and over again once the operator decided that they cannot be archived due to some permanent error.] 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25465	The Data Pool Archive Service shall include the following information in the notifications about operator interventions: a. volume group, number of suspended granules, and nature of the error (i.e., indicative of the type of error) that caused the intervention in the subject line, b. intervention detail that would be displayed on the intervention detail screen as part of the e-mail body, including a list of the failed granules and the cause for each failure. [NOTE: Refer to S-DPL-17255 in DP_S6_01.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25470	The Data Pool Archive Service shall add the information associated with interventions (e.g., annotations, outcome) to the request annotation when the interventions are closed.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25475	The DPL Archive GUI shall allow authorized (ingest and archiving admin) operators to configure an optional e-mail address to which notifications about operator interventions shall be sent. [NOTE: Refer to S-DPL-17250 in DP_S6_01.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25480	The Data Pool Archive GUI shall allow operators to monitor for operator interventions requested by the Data Pool Archive Service such that new interventions can be displayed within 20 seconds of them having been requested by the Data Pool Archive Service, e.g., by allowing operators to list new and open interventions and allowing the operator to refresh that list manually, as well as via automatic refresh as often as every 20 seconds.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25490	The Data Pool Archive GUI shall show on the screen that operators use to monitor for operator intervention requests, the following information for each archiving error intervention: a. time the intervention request was created, b. archive and volume group, c. type of the error causing the intervention [NOTE: The list of error types is  TBD by DDR .], d. if available, the identification of the operator currently working the intervention, e. if available, the time the intervention was acknowledged. [NOTE: If a request has several suspended granules, they may have failed for different reasons.  That is, multiple types of errors may be associated with that intervention.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25495	The Data Pool Archive GUI shall permit an operator to filter open operator intervention requests by a. archive, b. volume group, c. error type, d. any combination of (a. or b.) and c.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25500	The Data Pool Archive GUI shall permit an operator to sort open operator intervention requests in ascending or descending order of creation time, with descending order (i.e., latest first) being the default.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25510	The Data Pool Archive GUI shall permit an operator to select an open operator intervention request from the monitoring screen for viewing and disposition.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25515	The Data Pool Archive GUI shall permit an operator to select an open operator intervention request, acknowledge and annotate it. [NOTE: An intervention is considered acknowledged when it is viewed for the first time.  Thereafter, the intervention is considered open but not new.] [NOTE: The operator may annotate the intervention, for example, if s/he cannot resolve the problem and wants to leave a note for the next shift.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25520	The Data Pool Archive GUI shall permit an operator to select an open operator intervention and add an annotation.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25525	The Data Pool Archive GUI shall prefix each operator annotation with a time stamp (date and time) and the operator identification if known.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25530	The Data Pool Archive GUI shall display the accumulated operator annotations when displaying the intervention details.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25545	The Data Pool Ingest GUI shall list the suspended and failed granules that caused the intervention request when displaying the intervention details. [NOTE: It is undesirable to include in the list granules that are not suspended or were not failed by the operator]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25550	The Data Pool Ingest GUI shall include the following information in the list of granules displayed when viewing intervention details: a. ECS granule ID, b. data type name and version, c. granule status and type of the error [classification of errors is  TBD by DDR ], d. granule size.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25555	The Data Pool Ingest GUI shall permit an operator to view detailed information about a suspended granule shown as part of the intervention details, to include: a. number of files, b. the list of the pathnames of the files associated with the granule, c. detailed error information when available. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25560	The Data Pool Archive GUI shall permit an authorized (ingest and archiving control) operator to select one or several or all of the suspended granules shown as part of the intervention details and confirm the failure. [NOTE: The granules are considered failed by the operator thereafter.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25565	The Data Pool Archive GUI shall remove granules whose archiving operation was failed by the operator from the Data Pool and ECS inventories, but retain their files in the Data Pool for future inspection, and do so in such a fashion that these files will not be considered orphans.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25570	The Data Pool Archive GUI shall permit an authorized (ingest and archiving control) operator to request that the Data Pool Archive Service retry all suspended granules shown as part of the intervention details that were not failed by the operator. [NOTE: These granules will be included the next time the volume group is queued for archiving.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25575	The Data Pool Archive GUI shall permit an authorized (ingest and archiving control) operator to close an intervention once the operator failed or requested the retry of all suspended granules. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25580	The Data Pool Archive GUI shall record the following information when closing an operator intervention: a. date/time of closure, b. nature of the disposition (i.e., whether any granules were failed), c. if available, the identification of the operator. [NOTE: Closed interventions are no longer displayed in the intervention monitoring screen.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25585	The Data Pool Archive Service shall raise an alert for an archive when one of the following situations occur: a. the target archive host cannot be accessed, b. the agent on the archive host that performs the archiving operation cannot be contacted, c. the target archive file system cannot be accessed (i.e., is not mounted, indicating that the Archive COTS is not active), d. write operations to the archive cache for N different files failed consecutively on accessing the same archive, e. the write operations for N consecutive granules for the same archive were hung, f. the number of dirty cache blocks or the number of F-nodes exceeds a configured threshold (this condition will not suspend the archive), g. the number of dirty cache blocks or the number of F-nodes exceeds another configured threshold(this condition will suspend the archive). [NOTE: In some of the above cases, N-1 granules will already be suspended.  The value of N is configurable by the DAAC, S-DPL-25110.] [NOTE: The final list of alert situations is  TBD by DDR .]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25590	The DPL CI shall raise no more than one operator alert for a given archive. [NOTE: Archive alerts may also be raised by the DPL CI while inserting granules from the archive into the Data Pool.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25600	The Data Pool Archive Service shall suspend Data Pool archiving for an archive while an alert is currently pending for it unless other requirements explicitly specify otherwise, i.e., not activate any additional archiving request and not dispatch any more archive write operations for it.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25610	The Data Pool Archive Service shall automatically retry the operation whose failure caused an archive alert (e.g., connecting to the host and archiving agent, or re-copying a failed file) while the alert remains pending, using a globally configured retry time interval, and clear the alert and resume dispatching operations for that archive when a retry succeeds, unless Data Pool archiving for the archive was suspended by the operator. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25615	The Data Pool Archive Service shall clear the corresponding archive alert when it detects that the number of dirty cache blocks or consumed F-nodes for an archive has fallen below N% of the original threshold that caused the alert to be raised, where N is configured by the operator. [NOTE: If both parameters exceeded their threshold during the alert, the alert is only cleared after both parameters dropped below that lower threshold.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25620	The Data Pool Archive Service shall raise an operator alert if during an attempt to activate archiving for the volume group, it discovers that there is no tape space available in the archive for that volume group.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25625	The Data Pool Archive Service shall suspend Data Pool archiving for a volume group while an alert is pending for it, except where noted otherwise explicitly in S-DPL-25585.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25630	The Data Pool Archive Service shall automatically retry the check for available archive space for a volume group while the alert remains pending, using a globally configured retry time interval, and clear the alert and resume archiving for the volume group when a retried check succeeds, unless Data Pool archiving for the volume group was suspended by the operator.  	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25640	The Data Pool Archive Service shall raise an alert for a Data Pool file system when one of the following situations occur: a. the source Data Pool file system cannot be accessed (e.g., because it is not mounted), b. read operations for N different files failed consecutively on accessing the same source Data Pool file system, where N is configurable on a global basis (i.e., independent of source file system). [NOTE: In the latter case, the archiving of N-1 granules may already be considered failed.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25650	The DPL CI shall raise no more than one operator alert for a given Data Pool file system for suspension of archiving operations for that file system. [NOTE: File system alerts may also be raised by the DPL CI while inserting granules into the Data Pool.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25660	The Data Pool Archive Service shall suspend Data Pool archiving for a Data Pool file system while an alert is currently pending for it, except if the alert is due to the file system being full or nearly full.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25670	The Data Pool Archive Service shall automatically retry the operation whose failure caused a file system alert (e.g., re-copying a failed file) while that alert remains pending, using a globally configured retry time interval, and clear the alert and resume dispatching operations for that file system when a retry succeeds, unless Data Pool archiving for the file system was suspended by the operator. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25672	The Data Pool Archive Service shall automatically resume the granules that were suspended in the course of raising an alert because the error occurred for N granule consecutively (i.e., file system read error, archive write error, time out). [NOTE: However, this must not cause in infinite retry loop in case the same N granules experience the same problem again.] 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25675	The Data Pool Archive Service shall include the following information in the notifications about operator alerts: a. the resource that caused the alert (e.g., ftp host, data pool file system, ECS service), b. the type of alert [NOTE: a preliminary classification of alerts is  TBD by PDR ]. [NOTE: Refer to S-DPL-17700.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25680	The Data Pool Archive Service shall record the time an alert condition was closed as part of the information kept for the closed alert.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25685	The Data Pool GUI shall allow authorized (ingest and archiving admin) operators to configure an optional e-mail address to which notifications about alerts shall be sent. [NOTE: Refer to S-DPL-17690.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25690	The Data Pool Archive GUI shall display on the Data Pool Archive Service status page, whether there are any current alerts.  	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25695	The Data Pool Archive GUI shall allow operators to monitor for Data Pool Archive Service alerts such that new alerts can be displayed within 20 seconds of them having been requested by the Data Pool Archive Service, e.g., by allowing operators to list current alerts and allowing the operator to refresh that list manually, as well as via automatic refresh as often as every 20 seconds.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25700	The Data Pool Archive GUI shall show on the screen that operators use to monitor alerts, the following information for each alert: a. time the alert was created, b. the resource that caused the alert, c. the type of the alert indicative of the problem causing the alert [NOTE: A preliminary list of the types of alerts is  TBD by PDR .]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25710	The Data Pool Archive GUI shall permit an operator to filter operator alerts by a. resource, b. type of alert, c. a combination of both.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25715	The Data Pool Archive GUI shall permit an operator to sort alerts in ascending or descending order of creation time, with descending order (i.e., latest first) being the default.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25720	The Data Pool Archive GUI shall permit an operator to select an alert from the monitoring screen to view alert details, such as any detailed error information associated with it.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25725	The Data Pool Archive GUI shall permit an authorized (ingest and archiving control) operator to select an alert from the monitoring screen to close it.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25730	The Data Pool Archive GUI shall close an alert for a file system or archive after the operator manually suspended that archive or file system. [NOTE: Operators can manually suspend an archive or file system while an alert is pending.  If they do this, the alert is closed and the archive or file system is considered manually suspended.  Automatic retries will cease.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25735	The Data Pool Archive Service shall record the time an alert was closed.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25740	The Data Pool Archive Service shall queue an archiving request for volume group if the amount of data assigned to that volume group that is currently in the Data Pool exceeds the data volume or granule count threshold for that volume group.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25745	The Data Pool Archive Service shall queue an archiving request for volume group if the time that elapsed since the last time the volume group was archived exceeds the corresponding threshold.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25750	The Data Pool Archive Service shall queue an archiving request for a volume group if so requested by an operator via the Data Pool Archive GUI, as per S-DPL-25260.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25755	The Data Pool Archive Service shall not queue an archiving request for a volume group if that volume group is already queued for archiving or is currently being archived.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25760	The Data Pool Archive Service shall copy the granules of a volume group that require archiving to the appropriate path on the appropriate archive host, as configured in the database maintained by the STMGT CI. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25765	The Data Pool Archive Service shall copy the granules of a volume group to the ECS archive by ascending temporal coverage (beginning date time if different from ending date time), or Data Pool insert time if the granules do not have temporal coverage, except if the target archive is disk based. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25770	The Data Pool Archive Service shall rename the files of a granule during archiving, consistent with the SDSRV CI internal file naming convention. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25780	The Data Pool Archive Service shall update the SDSRV CI database after the archive operations for the primary volume group of a granule completed successfully to include the internal file and path information and the insert time in the corresponding SDSRV CI inventory tables. [NOTE: The insert time needs to match the time the granule was archived to ensure that upon future retrieval, the appropriate volume group from the volume group history will be accessed.  Additional information may have to be transferred to the ECS inventory file entries depending on what was originally stored in these tables during SDSRV metadata insert.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25790	The Data Pool Archive Service shall update the Data Pool inventory to record when a granule was archived successfully and the time the archiving was completed, recording multiple archiving completion times if the granule is assigned to multiple volume groups. [NOTE: If a granule is also assigned to a back-up volume group, it cannot be considered archived until both primary and backup archiving have occurred.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25800	The Data Pool Archive Service shall update the Data Pool ingest history to record the time that elapsed between the completion of the granule insertion into the Data Pool and ECS inventory and its archiving in the primary volume group as the TimeToArchive in the INGST table InRequestSummaryData.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25810	The Data Pool Archive Service shall update the Data Pool ingest history table InRequestSummaryHeader after the archiving operations for the primary volume group of all granules in a request complete to record as the TimeToArchive the time that elapsed since all granules completed their inserts into the Data Pool and ECS inventory.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25815	The Data Pool Archive Service shall record the following throughput statistics for archiving operations in the Data Pool database, as measured in terms of the number of granules and data volume per configured time interval: a. by archive, b. by Data Pool file system. [NOTE: The nature of the throughput statistics is  TBD during RTR .  Note that throughput statistics are kept as part of the history information for each archiving request.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25820	The Data Pool Archive Service shall recover after a fault such that: a. archiving of a granule/file will not be skipped and granules will be copied to the archive in the correct sequence, b. granules that completed all archiving steps successfully will not be archived again, c. archive copy operations will not be performed more than once if they completed successfully [NOTE: In a fault situation, it may not be possible or feasible to verify that a copy operation that appeared to be in progress at the time of the fault completed successfully; in that case, the copy operation must be repeated in order to meet the requirement in clause a.], d. no volume group archiving requests fail or raise operator interventions just because of the fault recovery, e. the state of volume groups is recovered correctly, f. volume group archiving requests that were in progress at the time of the fault will be restarted before any new work is started, g. the state of alerts and archiving request queues will be recovered to the extent that they have not been changed by the operator during the outage caused by the fault, h. the state of operator interventions will be recovered to the extent that they have not been changed by the operator during the outage caused by the fault, j. the state of resources will be recovered to the extent that they have not been changed by the operator during the outage caused by the fault.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25825	The Data Pool Archive Service shall be able to complete recovery from a fault, including restarting archiving operations that were active at the time of the fault in less than 15 minutes, with archiving operations for at least 8 volume groups being in progress at the time of the fault whose data volume to be archived encompasses the equivalent of at least 8,000 granules.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25830	The Data Pool Archive Service shall activate archiving requests for a volume group queued for the same archive in order of the time that elapsed since the last archiving for that volume group, followed by the amount of data in the Data Pool for that volume group and not yet archived (largest first), provided that the following conditions are met: a. archiving for the volume group is not suspended, b. the archive is not suspended for archiving purposes and the number of currently active archiving requests for the archive is below the configured limit, c. the data pool file systems that contain the data that need to be archived for the volume group are not suspended for archiving purposes (i.e., the nature of the suspension permits read access).	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25835	The Data Pool Archive Service shall ignore the configured limit on the number of volume groups that are being archived concurrently when archiving requests are activated manually by the operator.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25840	The Data Pool Archive Service shall observe the configured limit on the number of concurrent archive cache write operations when dispatching copy operations writing to the archive cache. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25845	The Data Pool Archive Service shall verify that tape space is available for the volume group in the archive before activating it, unless the target archive is disk based. [NOTE: Failure of the verification will cause an alert and suspension of archiving for that volume group, see S-DPL-25620.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25850	The Data Pool Archive Service shall not dispatch archive cache write operations for a volume group archiving request if the required resources are suspended. [NOTE: The volume group archiving request will remain active unless cancelled or suspended by the operator.] 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25855	The Data Pool Archive Service shall obtain archive cache status and drive information in regular time intervals, as configured by the operator, and check the result against the configured alert thresholds (except for disk based archives). [NOTE: The checks will require access to AMASS information based on the AMASS volume group ID.  The outcome of the checks may raise or clear corresponding alerts, see S-DPL-25585, S-DPL-25615.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25860	The Data Pool Archive Service shall cancel an operation writing to the archive cache if it does not complete within the time limit established in accordance with the configured time-out parameters, and retry the write operation until the configured number of maximum retries is exceeded, failing the archiving operation thereafter. [NOTE: Configuring the number of retries to zero would have the effect of failing the write operation without retry. The requirement also assumes that timeouts will be due to QuickServer, archive host, or AMASS problems and never due to StorNext file system problems.  Clarifying the assumptions and a reasonable setting for N is  TBD by DDR  via experiments in the PVC.  Note that N consecutive failures or timeouts of all current archive operations will cause an alert, as per S-DPL-25585.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25865	The Data Pool Archive Service shall maintain the following states for archiving requests: a.  Queued when an archiving request was queued, b. Active when a request was activated, c. Successful when a request completes successfully, d. Suspended when a request is suspended, requiring operator intervention to resume it; this includes the situation when all granules in a request are suspended, e. Partial_Failure when some but not all granules in a request were failed by the operator, f. Failed when all granules in a request were failed by the operator. [NOTE: An archive request is not created until it is queued, so Queued is the first state of a new archiving request.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25870	The Data Pool Archive Service shall maintain the following states for granules during archiving: a. Suspended when archiving for a granule was suspended, pending operator intervention b. ArcErr when archiving of the granule was failed by the operator [NOTE: Other granule states may be used but there are no specific requirements for their nomenclature.  Note that granules are flagged in the Data Pool inventory when they still need archiving and after they completed archiving for their primary respectively back-up volume group.]	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25880	The Data Pool Archive Service shall create an application log whose format is compatible with ECS application logs.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25885	The Data Pool Archive Service shall roll over application log files when they exceed a configured maximum size	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25890	The Data Pool Archive Service shall log the following events in the application log: a. start and completion of a volume group archiving request, including size and number of granules archived, b. start and completion of archiving for a granule, including outcome and granule size and number of files, c. start and completion of archiving for a file, including outcome and file size, d. queuing of a volume group for archiving, e. errors, f. suspensions and resumptions of volume groups and archives, g. cancellations.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25895	The Data Pool Archive Service shall include the following information in application log entries when applicable: a. archive request ID, b. volume group, c. ESDT and version, d. granule identification, e. file name, f. archive name, g. DPL file system, h. error details.	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25900	The Data Pool Archive Service shall be able to generate a performance log compatible with the ECS performance log format to allow the following information to be derived: a. frequency, duration and throughput of file copy operations by archive and volume group, b. frequency and duration of database transactions (e.g., stored procedure calls), by type of stored procedure, c. frequency and duration of mutex locks, by locked resource, d. frequency and duration of wait times, by type of event, e. frequency and duration of volume group sort operations. 	
DP_S6_02	Data Pool Archiving Service Cancelled. Superseded by DP_S6_01 Version 14	no data				S-DPL-25905	The Data Pool Archive Service shall be able to operate concurrently with the current STMGT CI.	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DMS-01200	The V0 Gateway shall be configurable by DAAC operators to submit integrated browse requests to the SDSRV or the Data Pool (DPL) CI. [NOTE: There shall be no impact on the existing ICD between ECS and Version 0, ESDIS Document 505-41-30.]	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DMS-01205	When so configured, the V0 Gateway shall submit a request for the browse granule referenced in an integrated browse request to the Data Pool (DPL) CI.	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DMS-01210	The V0 Gateway shall accept from the Data Pool (DPL) CI the response to the request for a browse granule, including the browse file itself.	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DMS-01215	The V0 Gateway shall include an appropriate error message to the user in the integrated browse result message if Data Pool (DPL) CI returns an error to the request for a browse granule.	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18500	The Data Pool (DPL) CI shall accept an integrated browse request from the V0 Gateway.	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18505	The Data Pool (DPL) CI shall retrieve the AIRS Summary Browse Product itself in response to an integrated browse request for the browse product associated with an AIRS Summary Browse Product	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18510	The Data Pool (DPL) CI shall return the browse file in its native format to the V0 Gateway in response to an integrated browse request .	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18515	The Data Pool (DPL) CI shall return an appropriate error status to the V0 Gateway if it cannot retrieve a requested browse granule. 	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18520	The Data Pool (DPL) CI shall return a browse granule requested by the V0 Gateway for integrated browse that is currently located in the Data Pool directly from the Data Pool, i.e., without retrieving it from its ECS archive location, if that browse granule is available in the Data Pool in its original format..	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18525	The Data Pool (DPL) CI shall retrieve a browse granule requested by the V0 Gateway for integrated browse from its ECS archive location if it is not located in the Data Pool, and do so without inserting it into the Data Pool inventory.	
DP_S6_03	Distribution of integrated browse products requested via the Version 0 Gateway	no data				S-DPL-18530	The Data Pool (DPL) CI shall obtain the location of a browse granule in the ECS archive from the volume group history information stored in the STMGT database.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00010	The Data Pool shall provide anonymous FTP service for accessing the data pool.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00020	The Data Pool service shall support FTP sessions in interactive mode.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00021	The Data Pool FTP service shall display a banner with the standard Government security warning containing the following text:           U.S. GOVERNMENT COMPUTER    If not authorized to access this system, disconnect now.YOU SHOULD HAVE NO        EXPECTATION OF PRIVACY    By continuing, you consent in your keystrokes and data content being monitored.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00022	The Data Pool FTP service shall allow the FTP  banner to be configurable by the operator.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00030	The Data Pool service shall support FTP sessions via script execution. 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00040	The Data Pool FTP service shall be accessible via the Data Pool web service.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00050	The Data Pool FTP service shall allow the operator to specify the default FTP home directory where all users are placed, upon their successful log-in.  	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00070	The Data Pool FTP service shall allow users to list the content of the data pool directories.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00071	In listing the directory content, the Data Pool FTP service shall make the actual file invisible to the user if it is associated with a file link. 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00080	The Data Pool FTP service shall allow users to traverse the data pool directory structure.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00090	The Data Pool FTP service shall allow users to transfer single or multiple data files from the data pool to a remote host. 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00110	The Data Pool FTP service shall prevent users from deleting any files or directories. 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00120	The Data Pool FTP service shall prevent users from renaming any files or directories.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00130	The Data Pool FTP service shall prevent users from modifying any files or directories.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00131	The Data Pool FTP service shall prevent users from creating a new directory in the data pool.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00132	The Data Pool FTP service shall prevent users from modifying access privileges on any files or directories in the data pool.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00140	The Data Pool FTP service shall prevent users from transferring a file into the data pool.  	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00150	The Data Pool FTP service shall prevent users from accessing any files or directories other than those included in the data pool. 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00160	The Data Pool FTP service shall provide an operator-configurable option for logging user events and errors.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00190	The Data Pool FTP service shall log user events and errors.	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00200	The Data Pool FTP service shall log the following for each FTP log-in event:  a.Time of log-in (Month, Day, Time of day)  b.user name (i.e. anonymous)  c.remote host name 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00205	The Data Pool FTP service shall log the following for each file transfer event. a.Time of access (Month, Day, and Time of day)  b.Identity of the retrieved object (path & filename)  c.File size (in bytes)  d.Service (i.e. ftpd) 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00220	The Data Pool FTP service shall terminate a user session upon detecting inactivity for a preconfigured timeout period. 	
DP_SY_01	Data Pool FTP Service	no data				S-DPL-00230	The Data Pool FTP service shall allow the operator to set the inactivity timeout period. 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05010	The Data Pool Service shall provide a Data Pool Web Access Service at each DAAC.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05020	The Data Pool Web Access Service shall be accessible by users outside a DAAC as well as within a DAAC	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05030	The Data Pool Web Access Service shall provide a home page that can serve as the starting point for access to the Data Pool via Web Browsers.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05040	The Data Pool Web Access Service shall include general information about the Data Pool on its home page. 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05050	The Data Pool Web Access Service shall include a link to the EDG with an appropriate explanation that ECS granules that are not available in the Data Pool can be located and ordered via the EDG. 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05060	The Data Pool Web Access Service shall include the standard Government security warning containing the following text:               U.S. GOVERNMENT COMPUTER    If not authorized to access this system, disconnect now.                YOU SHOULD HAVE NO EXPECTATION OF PRIVACY  By continuing, you consent in your keystrokes and data content being monitored.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05070	The Data Pool Web Access Service shall allow the user to navigate - starting from the Data Pool home page - through a series of navigational pages that offer various drill down choices to narrow the selection criteria for granules, until the user decides to view the list of granules itself.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05075	The Data Pool Web Access Service shall display on each page following a drill down the count of the remaining granules.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05080	The Data Pool Web Access Service shall support the following granule level metadata attributes for drill down:    a. DP Data Group  b. ESDT and version  c. Temporal coverage - Date  d. Temporal coverage - Time of Day  e. Spatial Coveragef. Day/Night Flag	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05090	The Data Pool Web Access Service shall present the list of possible values for drill down for the following attributes:  a. DP Data Groups,   b. ESDT and version,   c. Day/Night Flag..	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05100	The Data Pool Web Access Service shall support the following additional granule level metadata attributes for drill down:    a. Science QA Flag	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05105	The Data Pool Web Access Service shall present the list of possible values for drill down for the following additional attributes:    a. Science QA Flag	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05110	The Data Pool Web Access Service shall allow the user to drill down on Date by entering or selecting a date range.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05120	The Data Pool Web Access Service shall allow the user to drill down on Time of Day by entering or selecting a time range.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05130	The Data Pool Web Access Service shall allow the user to drill down on spatial coverage by entering the boundaries of a Latitude/Longitude Box (LLBOX).	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05132	The Data Pool Web Access Service shall allow the user to drill down on spatial coverage by drawing a polygon on a world map (assumed to be connected by great circle arcs).	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05134	The Data Pool Web Access Service shall allow the user to drill down on spatial coverage by picking a center point and drawing a circle on a world map.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05140	The Data Pool Web Access Service shall allow the user to drill down on spatial coverage by drawing a LLBOX on a world map.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05150	The Data Pool Web Access Service shall include explanatory information with each drill down choice, e.g., similar to what the EDG interface provides).	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05160	The Data Pool Web Access Service shall include links to additional helpful information such as: a glossary of terms and links to instrument team web pages.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05170	The Data Pool Web Access Service shall provide with each drill down choice, an indication regarding the amount of qualifying data (e.g., estimated or actual number of granules).	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05180	The Data Pool Web Access Service shall be able to query the Data Pool inventory to include the number of the granules remaining for a given drill down choice as an indication the amount of qualifying data.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05190	The Data Pool Web Access Service shall permit developers to configure for each drill down attribute whether the Data Pool inventory may be queried to obtain actual granule counts for each value.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05200	The Data Pool Web Access Service shall allow users to go back to a preceding level in the drill down and to resume drill down from that level.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05210	At the user's option as well as when all drill down choices are exhausted, the Data Pool Web Access Service shall display the list of resulting granule (via the results page). 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05220	The Data Pool Web Access Service shall segment the list of resulting granules for display purposes into display chunks whose size is selectable by the user. 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05225	The Data Pool Web Access Service shall allow operators to configure the default display chunk size. 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05230	The Data Pool Web Access Service shall initiate the display of the results page by displaying the first chunk.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05240	If there is more than one chunk, the Data Pool Web Access Service results page shall display links that can be used to display any of the chunks and indicates the chunk currently being displayed.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05250	The Data Pool Web Access Service results page shall display the actual number of granules in the Data Pool that match the selection criteria specified by the drill down.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05260	The Data Pool Web Access Service results page shall display with each granule a list of core metadata.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05270	The Data Pool Web Access Service shall permit a DAAC operator to configure the core inventory metadata to be displayed on the results page from the following list of candidate attributes:    a. ESDT and version  b. Temporal coverage - Date and Time of Day  c. Day/Night Flag  d. Science QA Flag  e. QA Percent Cloud Cover (if populated)  f. Size in Mbytes	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05280	The Data Pool Web Access Service results page shall display granules by default in sort order of Date and Time of the start time of temporal coverage, and then ESDT and version.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05285	The Data Pool Web Access Service shall allow the user to resort the list of resulting granules results page according to any of the other displayed core inventory metadata attributes.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05290	The Data Pool Web Access Service results page shall display with each granule a link for accessing and displaying its XML metadata file.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05295	The Data Pool Web Access Service shall allow the user to display the contents of the XML metadata file in a new browser window.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05300	When displaying the granule metadata, the Data Pool Web Access Service shall give the user an option to step forward to the next /last granule or return to the previous / first granule in the resulting granule list, without the user having to return to the results page itself.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05305	The Data Pool Web Access Service shall permit a user to save the XML file locally that is currently being displayed.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05310	The Data Pool Web Access Service results page shall display with each granule that has associated browse images in the Data Pool, a link for accessing and displaying each browse image.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05315	The Data Pool Web Access Service shall permit a user to save the browse image locally that is currently being displayed.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05320	The Data Pool Web Access Service results page shall display with each granule links that support the ftp download of the granule files.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05330	The Data Pool Web Access Service shall log all access to metadata files.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05340	The Data Pool Web Access Service shall log all access to browse files.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05350	The Data Pool Web Access Service shall log all access failures.	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05360	The Data Pool Web Access Service shall include in the access log the path name of the requested file, the date and time of day, and the ip address of the requester. 	
DP_SY_02	Data Pool Web Access	no data				S-DPL-05370	When recording file access failures, the Data Pool Web Access Service shall include in the log the error code, path name of the requested file, the date and time of day, and the ip address of the requester. 	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13010	The Data Pool Service shall include a Data Pool Cleanup Utility for removing granules from the data pool disks and inventory.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13020	Operators shall be able to run the Data Pool Cleanup Utility from the command line and in back ground.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13030	The Data Pool Cleanup Utility shall accept command line parameters specifying a date/time cut-off and a priority limit or the name of a granule ID file, and a no-prompt option.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13031	The Data Pool Cleanup Utility shall consider priority limit and date/time cut-off parameters as mutually exclusive to the granule ID file name parameter. 	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13032	The Data Pool Cleanup Utility shall validate the syntax of the command line parameters.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13034	If the command line parameters fail the syntax validation, the Data Pool Cleanup Utility shall display the error and the correct command line syntax.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13040	The Data Pool Cleanup Utility shall suppress all operator prompts if the no-prompt option is specified, assuming an affirmative response in these cases.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13042	The Data Pool Cleanup Utility shall suppress the display of all warning and error messages if the no-prompt option is specified but continue to log the errors and warnings to its log file.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13050	The Data Pool Cleanup Utility shall accept the date/time cut-off as an off-set from mid-night (24:00:00) of the previous day, expressed in hours.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13060	The Data Pool Cleanup Utility shall accept the cut-off  hours as a positive or negative number, including 0.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13065	The Data Pool Cleanup Utility shall consider the date/time cut-off parameter optional with a default value of 0.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13070	The Data Pool Cleanup Utility shall add the cut-off hours to mid-night of the previous day, resulting in a date and time previous to that if the number of hours is negative, and in a date and time after that if the number is positive, including possibly a date and time in the future.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13080	The Data Pool Cleanup Utility shall prompt the operator for confirmation of the date/time cut-off if it is in the future. 	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13091	The Data Pool Cleanup Utility shall accept the priority limit as a positive number between 1 and 255.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13093	If a priority limit is not specified, the Data Pool Cleanup Utility shall assume a configurable default priority limit.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13094	Data Pool Cleanup Utility shall accept a list of granule Ids of the granules to be cleaned up from the granule ID file specified in the granule ID file name parameter, formatted as one granule ID per line	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13100	The Data Pool Cleanup Utility shall qualify a science granule for clean-up if its priority is less than or equal to the priority limit and its expiration date/time is less than or equal to the cut-off date/time; or if its ID is listed in the granule ID file specified in the granule ID file name parameter.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13110	The Data Pool Cleanup Utility shall remove all science granules from the data pool inventory that qualify for clean-up, except where this would interfere with concurrent user access to the very same granule.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13120	The Data Pool Cleanup Utility shall remove the files - including metadata file - of all science granules that qualify for clean-up from the data pool disks, except where this would interfere with concurrent user access to the very same granule.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13125	The Data Pool Cleanup Utility shall remove any directories that have been emptied of files and link by the clean-up without causing concurrent Data Pool inserts to fail.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13130	The Data Pool Cleanup Utility shall remove all browse granules from the inventory that have been orphaned by the clean-up of science granules.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13140	The Data Pool Cleanup Utility shall remove the files belonging to cleaned up browse granules from the Data Pool disks.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13142	The Data Pool Cleanup Utility shall remove a link to a browse file from a Data Pool directory when all science granules referencing that browse in that directory are cleaned up.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13144	The Data Pool Cleanup Utility shall not leave any browse/science cross-reference entries in the Data Pool inventory once the browse granule has been removed from the inventory.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13160	If a clean-up is interrupted by a fault, it must be possible to restart the Data Pool Cleanup utility without affecting its ability to perform the remainder of the clean-up or its throughput.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13170	The Data Pool Cleanup Utility shall prevent concurrent executions of the utility if that could interfere with its error free and efficient operation.  (For example, the developer might prevent all parallel executions of the utility; or design the utility such that conflicts never occur, in which case it is not necessary to prevent concurrent runs at all)	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13180	The Data Pool Cleanup Utility must be able to operate concurrently with Data Pool web, ftp and any subscription distribution accesses and Data Pool insert operations.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13190	The Data Pool Cleanup Utility must not degrade concurrent Data Pool web and ftp access, distribution, inserts and distributions by more than 50% in terms of response time or throughput.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13200	The Data Pool Cleanup Utility must be able to cleanup at least 5,000 science and browse granules per hour (including clean-up of their metadata files and data pool inventory metadata) concurrent with the data pool insert and distribution loads  specified in Tickets DP_SY_04 and DP_SY_01	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13210	The Data Pool Cleanup Utility shall clear the 'NoFreeSpace' flag (that prevent Data Pool Inserts from dequeuing) if the amount of space it cleaned up exceeds an operator configurable limit.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13212	The Data Pool Cleanup Utility shall allow operators to configure the amount of space that - if freed up by a cleanup run - will cause the 'NoFreeSpace' flag to be cleared.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13220	The Data Pool Cleanup Utility shall log all cleanup attempts for a granule, including completion status to the cleanup log file.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13230	The Data Pool Cleanup Utility shall log the start of a cleanup run to the cleanup log file.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13240	The Data Pool Cleanup Utility shall log the completion of a cleanup run to the cleanup log file.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13260	The Data Pool Cleanup Utility shall log the total amount of space it cleaned up to the cleanup log file.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13270	The Data Pool Cleanup Utility log entries shall include the date and time of the cleanup log file entry (at least to the millisecond).	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13290	Where a cleanup log file entry is specific to a granule or file, the Data Pool Cleanup Utility log entries shall include the granule id or the file path name respectively in the log entry.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13300	The Data Pool Cleanup Utility shall generate a default name for the cleanup log file.  	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13310	The Data Pool Cleanup Utility shall append output to the cleanup log file if it already exists.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13320	The Data Pool Cleanup Utility shall create the cleanup log file if it does not exist.	
DP_SY_03	Data Pool Cleanup	no data				S-DPL-13330	The Data Pool Cleanup Utility shall create the cleanup log file if it does not exist.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20100	The Data Pool Insert Service shall allow configuration of a default retention period for all Data Pool Insert actions.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20150	The Data Pool Insert Service shall allow configuration of a default retention priority for all Data Pool Insert actions.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20200	The Data Pool Insert Service shall allow an operator to specify, as configuration items, the mapping of ESDTs to Data Pool Collection groups.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20350	The Data Pool Insert Service shall prevent the insertion of ineligible data types in the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20400	The Data Pool Insert Service shall allow an operator to specify, as configuration items, the shortname/versionids of ECS data types which are eligible only to have metadata for qualifying granules inserted into the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20450	The Data Pool Insert Service shall prevent the insertion of science files into the Data Pool for data types which are configured as eligible for metadata insert only.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20500	The Data Pool Insert Service  shall prevent duplicate insertion of an ECS granule into the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20600	The Data Pool Insert Service shall prevent the partial insertion of ECS granules into the Data Pool if there is insufficient free space remaining in the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20650	The Data Pool Insert Service shall allow an operator to suspend all Data Pool insert actions.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20660	The Data Pool Insert Service shall log the time (at least to the millisecond) at which Data Pool insert actions are suspended by the operator.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20670	The Data Pool Insert Service shall allow an operator to resume all Data Pool insert actions after they have been suspended.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20680	The Data Pool Insert Service shall log the time (at least to the millisecond) at which Data Pool insert actions are resumed by the operator.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20700	The Data Pool Insert Service shall allow the operator to control the number of  insert processes (so that Data Pool insert throughput can be tuned to demand and platform capacity).	
DP_SY_04	Data Pool Insert	no data				S-DPL-20740	The Data Pool Insert Service shall allow the operator to determine the number of insert processes running, and the status of each.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20750	The Data Pool Insert Service shall allow the operator to determine the number of pending Data Pool insert requests, and the subscription id, shortname/versionid, and dbid (granuleId or browseId) associated with each.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20760	The Data Pool Insert Service shall allow the operator to cancel a pending Data Pool insert request.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20770	The Data Pool Insert Service shall log the following information when the operator cancels a pending Data Pool insert request:    a. The time (at least to the millisecond) at which the request was cancelled.  b. The subscription id associated with the request  c. The shortname/versionid associated with the request  d. The dbid associated with the request.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20800	When a granule is inserted into ECS which qualifies for one or more Data Pool Insert subscriptions, the Data Pool Insert Service shall insert a metadata file into the Data Pool disks for that granule.	
DP_SY_04	Data Pool Insert	no data				S-DPL-20900	The metadata file shall contain all ECS granule level metadata for that granule.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21000	The Data Pool Insert Service shall insert the metadata file into the Data Pool disk directory structure in the lowest level directory, based on Data Pool Collection Group, shortname/versionid, and data acquisition time of the corresponding ECS granule.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21050	The Data Pool Insert Service shall create the appropriate lowest level directory if it does not exist.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21100	The Data Pool Insert Service shall insert the metadata file into the Data Pool disks in XML format, per the Granule-Level Metadata Document Type Definition (DTD) in Section A.3 of Appendix A, 'Bulk Metadata and Browse Export Capability for the ECS Project' (170-WP-023-011, 9/27/00).	
DP_SY_04	Data Pool Insert	no data				S-DPL-21200	The Data Pool Insert Service shall insert the metadata file into the Data Pool disks with an .xml extension.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21300	The Data Pool Insert Service shall insert the metadata file into the Data Pool disks with the same external file name as the corresponding .met file in ECS.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21400	When a granule is inserted into ECS which qualifies for one or more Data Pool Insert subscriptions, the Data Pool Insert Service shall insert metadata into the Data Pool database for that granule.   The metadata  shall contain at least the following information:    a. Shortname  b. Version id  c. Data acquisition time (RangeBeginningDate, RangeBeginningTime,    RangeEndingDate, RangeEndingTime)  d. Date/time of insert into ECS   e. Date/time of insert into the Data Pool  f. ECS Granule id (dbid)  g. DayNightFlag  h. Expiration Date/Time  i. Retention Priority  j. Subscription id(s) of all corresponding Data Pool Insert subscriptions  k. Granule size in MB  l. Spatial coverage (e.g., orbital information, polygon)  m. QA FlagNumber of files  n. File size(s)  o. File name(s)  p. Data Pool Collection Group 	
DP_SY_04	Data Pool Insert	no data				S-DPL-21500	The Data Pool Insert Service shall calculate the expiration date/time of a granule by adding the longest retention period of all  Data Pool Insert actions associated with the granule to the Data Pool insert date/time.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21600	The Data Pool Insert Service shall calculate the retention priority of a granule as the highest retention priority of all Data Pool Insert actions associated with the granule.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21700	When a granule is inserted into ECS which qualifies for one or more Data Pool Insert subscriptions, the Data Pool Insert Service shall insert all files containing science data for that granule into the Data Pool disks, unless the Insert Metadata Only option has been specified for all corresponding Data Pool Insert subscriptions.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21800	The Data Pool Insert Service shall insert the science data file(s) into the Data Pool disk directory structure in the lowest level directory, based on Data Pool collection group, shortname/versionid, and data acquisition time of the corresponding ECS granule.	
DP_SY_04	Data Pool Insert	no data				S-DPL-21900	The Data Pool Insert Service shall insert the science data file(s) into the Data Pool disks in the original ECS format.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22000	The Data Pool Insert Service shall insert the science data file(s) into the Data Pool disks with the same external file name(s) as the corresponding file(s) in ECS.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22100	The Data Pool Insert Service shall insert the science data file(s) into the Data Pool disks with the same external file name extension(s) as the corresponding file(s) in ECS.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22200	The Data Pool Insert Service shall insert into the Data Pool all Browse images associated with science granules residing in the Data Pool . 	
DP_SY_04	Data Pool Insert	no data				S-DPL-22300	The Data Pool Insert Service shall insert the Browse  image(s) into the Data Pool disk directory structure such that each Browse image is present only once on the Data Pool disks.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22350	The Data Pool Insert Service shall prevent the insertion of Browse images into the Data Pool if they are not associated with any Data Pool granules.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22400	The Data Pool Insert Service shall insert the Browse images into the Data Pool disks in jpeg format.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22500	The Data Pool Insert Service shall insert the Browse images into the Data Pool disks with a file name which includes the external file nameof the corresponding Browse filein ECS, and which includes an image sequence number	
DP_SY_04	Data Pool Insert	no data				S-DPL-22600	The Data Pool Insert Service shall insert the Browse images into the Data Pool disks with a .jpg file extension.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22700	The Data Pool Insert Service shall store a link to each Data Pool Browse imagefile in each lowest level Data Pool directory containing at least one related science and/or metadata file.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22800	The Data Pool Insert Service shall maintain cross reference information between each Browse image file and all corresponding science granules in the Data Pool database.	
DP_SY_04	Data Pool Insert	no data				S-DPL-22900	The concurrent insert action of a science granule and a related Browse granule into the Data Pool shall not result in incompatible Browse cross reference linkages.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23000	The Data Pool Insert Service shall log the following events as they occur to a Data Pool log file.    a. start of Data Pool insert  b. completion of Data Pool insert  c. start of a file transfer from the ECS archive to the Data Pool  d. completion of a file transfer from the ECS archive to the Data Poole.     retriable errors   f. non-retriable errors	
DP_SY_04	Data Pool Insert	no data				S-DPL-23200	The Data Pool Insert Service shall log the following information in the Data Pool database for each event, as applicable:    a. Unix Process ID  b. type of event  c. date and time of the event (at least to the millisecond)  d. shortname and version id of the associated granule  e. granule id (dbid)  f. associated subscription id(s)  g. file path name(s)  h. file size  i. description of error  j. fileincache status from AMASS (desired)	
DP_SY_04	Data Pool Insert	no data				S-DPL-23250	The Data Pool Insert Service shall generate a default name for the insert log file.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23260	The Data Pool Insert Service shall append output to the insert log file if it already exists.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23270	The Data Pool Insert Service shall create the insert log file if it does not exist.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23300	The Data Pool Insert Service shall set a 'No Free Space' flag in the Data Pool database if insertion of a file into the Data Pool disks fails because of insufficient free space.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23350	The Data Pool Insert Service shall not start further Data Pool Insert actions if the 'No Free Space' flag is set.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23355	The Data Pool Insert Service shall automatically resume processing of Data Pool Insert actions when the 'No Free Space' flag is cleared.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23360	The Data Pool Insert Service shall allow the operator to determine whether the 'No Free Space'flag is set.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23370	The Data Pool Insert Service shall allow the operator to reset the 'No Free Space' flag.	
DP_SY_04	Data Pool Insert	no data				S-DPL-23400	The Data Pool Insert Service shall return a retriable error for inserts which fail due to temporary error conditions (such as: insufficient free space available,  Data Pool disk temporarily unavailable, Data Pool directory does not exist, Data Pool database unavailable)	
DP_SY_04	Data Pool Insert	no data				S-DPL-23450	The Data Pool Insert Service shall return a fatal error for inserts which fail non-retriably (e.g., when the granule to be inserted is not found in ECS.)	
DP_SY_04	Data Pool Insert	no data				S-DPL-23500	The Data Pool Insert Service shall be able to operate in multiple modes concurrently.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08500	The Spatial Subscription Server(NSBRV) CI shall allow an operator to place a subscription with an action resulting in the insertion of an ECS granule into the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08510	The NSBRV CI shall allow a Data Pool Insert action to be associated with any subscription placed on an ECS Insert event.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08515	The NSBRV CI shall not allow a Data Pool Insert action to be associated with a subscription placed on ECS UpdateMetadata or Delete events.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08520	The NSBRV CI shall allow an operator to associate a retention period with each Data Pool Insert action.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08540	The NSBRV CI shall accept the retention period as a positive integer, representing the number of days for which granules associated with the subscription will be retained in the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08550	The NSBRV CI shall allow an operator to associate a retention priority with each Data Pool Insert subscription.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08560	The NSBRV CI shall accept the retention priority as a positive integer between 1 and 255.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08600	The NSBRV CI shall require that the InsertMetadataOnly option be associated with all actions for Data Pool insert where the shortname/versionid of the qualifying event has been configured as eligible only for metadata insert into the Data Pool.	
DP_SY_04	Data Pool Insert	no data				S-SSS-08650	The NSBRV CI shall issue a warning if the operator enters a retention period of less than 3 days on a DataPoolInsert subscription.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30010	The Data Pool Service shall include a Data Pool Update Expiration utility for updating the expiration date of individual science granules in the Data Pool inventory database.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30015	The Data Pool Update Expiration utility shall permit an operator to optionally update the cleanup priority of individual science granules in the Data Pool inventory database.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30020	Operators shall be able to run the Data Pool Update Expiration utility from the command line and in the background.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30025	The Data Pool Update Expiration utility shall accept command line parameters specifying:    a.either the name of a file containing a list of granule triplets, with each triplet consisting of the granule id (dbid), a new expiration date, and optionally a new cleanup priority; or a single triplet consisting of a granule id (dbid), a new expiration date, and optionally a new cleanup priority     b.a no-prompt option  c.a verbose confirmation option (available if the no-prompt option is not chosen)	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30030	The Data Pool Update Expiration utility shall accept the new expiration date as a date. 	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30032	The Data Pool Update Expiration utility shall accept the new cleanup priority as a positive integer between 1 and 255 inclusive.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30035	The Data Pool Update Expiration utility shall validate syntax (format of parameter values,range of parameter values, presence of required parameters,  validity of parameter keywords) of the command line parameters	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30040	If command line syntax validation fails, the Data Pool Update Expiration utility shall display an error message and the correct command line syntax, and shall not perform the requested update	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30060	The Data Pool Update Expiration utility shall display to the operator, before performing the update, the following confirmation information:    a.the number of granules which will be updated, and  b. the total size of all granules which will be updated.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30065	If the operator requests verbose confirmation information, the Data Pool Update Expiration utility shall additionally display to the operator, before performing the update, the list of granules which will be updated. For each granule in the list, the following information will be displayed:     a.shortname/versionid  b.granule id (dbid),  c.granule size,   d.current expiration date,  e.new expiration date,  f.current cleanup priority,   g. new cleanup priority (if applicable)	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30070	The Data Pool Update Expiration utility shall, by default, prompt the operator for confirmation after displaying the confirmation information.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30082	The Data Pool Update Expiration utility shall suppress the display of all operator prompts and confirmation information if the no-prompt option is specified, assuming an affirmative response to all prompts.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30085	The Data Pool Update Expiration utility shall suppress the display of all warning and error messages  if the no-prompt option is specified, but shall log the errors and warnings to its log file.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30090	The Data Pool Update Expiration utility shall perform the requested updates immediately after operator confirmation.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30110	The Data Pool Update Expiration utility shall display a warning message for any granule where the expiration date specified is less than or equal to today's date.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30115	If a warning message is displayed for any granule specified at the command line or in the input file, the Data Pool Update Expiration utility shall prompt the operator to confirm the entire update or exit.   If confirmation prompts and warning messages have been suppressed, the Data Pool Update Expiration utility shall write the warning message to its log and proceed with the update.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30140	The Data Pool Update Expiration utility shall log all updates. 	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30142	The Data Pool Update Expiration utility log entries shall include the date and time of the log entry (at least to the millisecond).	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30144	The Data Pool Update Expiration utility shall generate a default name for its log file.  	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30146	The Data Pool Update Expiration utility shall append output to its log file if it already exists.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30148	The Data Pool Update Expiration utility shall create its log file if it does not exist.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30150	The Data Pool Update Expiration utility shall log for each selected granule:     a.date and time  b.Unix id of the operator  c.shortname / versionid  d.granule id (dbid)  e.granule size  f.old expiration date  g.new expiration dateh. old cleanup priorityi. new cleanup priority (if cleanup   priority was changed), or 'unchanged'	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30160	The Data Pool Update Expiration utility shall log all update errors in the Update Expiration log file. 	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30170	The Data Pool Update Expiration utility shall log for each update error:    a.date and time  b.Unix id of the operator  c.nature of the error  d.granule id if the error is associated with a specific granule.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30180	The Data Pool Update Expiration utility shall handle situations where requested granule ids are not present in the Data Pool inventory database by logging an error and continuing the request for the remaining granule ids.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30185	The Data Pool Update Expiration utility shall handle situations where syntax errors are present on a line in the input file by logging the syntax error and continuing the request for the remaining triplets in the input file.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30190	The Data Pool Update Expiration utility shall perform update operations such that they can be restarted and completed successfully if interrupted by a fault.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30200	The Data Pool Update Expiration utility shall prevent database corruption due to conflicts with other Data Pool operations.	
DP_SY_06	Update Granule Expiration in Data Pool	no data				S-DPL-30210	The Data Pool Update Expiration utility shall be able to operate in multiple modes concurrently.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32010	The Data Pool Access Statistics Utility (DPASU) shall process the Data Pool Web Access Service log, extract or parse information on data accesses events from the logs and from other Data Pool databases, and write that summary information to the DPAL for use in reporting.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32020	The DPASU shall process the Data Pool FTP Server log, extract  or parse information on data accesses events from the logs and from other Data Pool databases, and write that summary information to the DPAL for use in reporting.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32030	The DPASU shall be able to concurrently process the FTP Server log and the Web Access Service log.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32040	The DPASU shall be configurable to permit automatic log processing, allowing the operator to specify:    a.Time of day at which roll-up processing should be initiated automatically each   day.    b.Start time of the 24 hour period for which roll-up results should be produced,   defaulting to start time of 0 hrs.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32050	When processing the Data Pool access logs, the DPASU shall produce parsed information sets from the as?yet?unprocessed data of the access logs, covering all of the specified period.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32060	The DPASU shall allow the initiation of parse processing of the FTP Server log and the Web Access Service log upon operator command.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32070	For operator initiated DPASU parse processing of the access logs, the operator shall be able to specify the date of the 24 hour period to be processed to produce parsed information, where the start time of that period is the same start time as is used for automatic parse processing.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32080	The DPASU shall prevent parse processing from occurring for given 24 hour period until the end time for that period has passed.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32090	When the DPASU processes the Data Pool access logs, the absence or unavailability of any of the logs or of a time range within a single log shall not prevent the processing of any of the remaining logs.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32100	The DPASU automatic access log processing capability shall be able to locate input log files with configured directory and file names where filename and directory specifications may include wildcards to allow the processing of sequences of regularly named items.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32110	The DPASU operator initiated access log processing capability shall accept operator input to identify input log files.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32120	The DPASU shall be able to access and read from input log files while they are opened and being used by the associated access utilities without causing errors or faults in those utilities.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32130	The DPASU shall provide an operator capability to delete or clean out parsed information from the DPAL that falls within an operator specified start-date and stop-date range.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32140	The DPASU shall provide an operator capability to copy all parsed information that falls within an operator specified start-date to stop-date range from the DPAL to an external file which may be stored or archived and subsequently restored to the DPAL as required.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32150	The DPASU shall not include duplicate entries of parsed information into the DPAL.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32160	The DPASU shall log to its error log when attempts are made to process previously processed time periods of the log files and add them to the DPAL.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32162	The DPASU shall issue a warning message to the operator in response to an operator command to process log files for a time period that has previously been processed. 	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32164	The DPASU shall permit operator initiated processing of log files for previously processed time periods if the operator directs that this should be done after the DPASU issues a warning message concerning this.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32170	The DPASU shall provide the capability to process log files representing 50,000 accesses and store the resulting parsed information to the DPAL within 1 hour.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32180	If syntax validation fails for any command line parameter, the DPASU capability shall notify the operator of the failure and display the correct syntax	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32190	The DPASU shall allow the operator to request suppression of confirmation prompts and warning/error messages via a command line parameter.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32200	If the operator requests that warning and error messages be suppressed, the DPASU shall write these messages to its error log.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32210	The DPASU shall log all errors.	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32220	The DPASU shall parse file access information from the logs and determine associated granule information from the Data Pool databases sufficient to record granule access information in the DPAL for granules that have been populated to the data pool by a subscription, including:    a.Granule ID  b.SubscriptionID  c.File Type (METADATA, BROWSE, SCIENCE)  d.Access size (bytes)  e.Date & time of access  f.Access Type (FTP, http)  g.Age of granule at access (i.e., number of days that the granule had been in   the Data Pool at the time of access)	
DP_SY_08	Compile & Examine Data Pool Access Statistics	no data				S-DPL-32230	The DPASU shall record information in the DPAL sufficient to uniquely identify each granule access.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00620	The DPL Ingest service shall allow the configuration, within the application configuration file, of a directory location for obtaining MCFs (Note: all MCFs will be stored within one directory).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00625	The DPL Ingest service shall allow the Operator to configure a directory location for storing granule metadata files that received warning messages during validation.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00630	The DPL Ingest GUI shall allow the operator to configure ESDTs to suppress the saving of metadata files when receiving validation warnings.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00635	The DPL Ingest service shall allow the configuration of a list of email addresses to be notified in the event of validation warnings.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00640	The DPL Ingest service shall, when ingesting a granule that contains a metadata file, use the AIM XML Validation Utility to validate the inventory metadata.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00645	The DPL Ingest service shall, when receiving validation warnings for a granule, continue processing of the granule and save the XML metadata file associated with the granule as well as the ODL metadata file received with the granule (if applicable) to the directory configured for storing metadata files with warnings.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00650	The DPL Ingest service shall suppress the saving of metadata files that receive validation warnings if the ESDT associated with the metadata file is configured to do so.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00655	The DPL Ingest service shall, when receiving the first validation warning return code for an ESDT within a calendar day or since startup of the DPL Ingest service,  send an email message to each email address configured to receive notification of validation warnings (unless the ESDT is configured to ignore validation warnings).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00660	The DPL Ingest service shall, when receiving a failure result from the AIM XVU, suspend the granule and create an Operator Intervention.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00665	The Data Pool Ingest Service shall, when encountering a Fatal or time-out error while attempting to validate a granule using the AIM XML Validation service, suspend the granule unless this is the N-th consecutive error or time-out (where N is configurable on a global basis (see S-DPL-16482-L).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00670	The Data Pool Ingest service shall, when the configured number of consecutive errors for the for the AIM XML Validation service is reached (where N is configurable on a global basis, see S-DPL-16482-L), raise an operator alert for the service.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00675	The Data Pool Ingest service shall, while there is an open alert on the AIM XML Validation service, suspend the submission of new requests to the service.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00680	The DataPool Ingest service shall, in the event that the AIM XML Validation service was suspended due to consecutive errors, automatically retry sending requests to the service using the alert retry time interval (which is configured on a global basis), and shall react as follows when a retry succeeds:  1. clear the corresponding alert condition and the alert as a whole if there are no other alert conditions for the service,  2. resume dispatching of the operations for that service that were suspended as a consequence of that alert condition.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00685	The DPL Ingest service shall store the granule metadata of each Science granule ingested in an XML file within the XML Archive.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00690	The DPL Ingest service shall, when ingesting a Science granule, name the associated XML file in the XML metadata archive using the convention: ShortName.VersionID.dbID.xml (where VersionID is zero padded to 3 characters).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00695	The DPL Ingest service shall determine the storage location for the XML metadata file associated with a granule based upon a configured base directory path plus the following metadata attributes: 1. ShortName  2. VersionID  3. the year and month of the time recorded for the RangeBeginningDate, or the CalendarDate, or the insertTime if RangeBeginningDate and CalendarDate are not available.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00700	The DPL Ingest service shall, when the directory location for storing an XML file does not exist, create the directory within the XML Archive.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00705	The DPL Ingest service shall, when creating a new directory within the XML Archive, use the AIM Inventory Insert Service to record the new directory location.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00710	The DPL Ingest service shall use the AIM Inventory Insert Service to record the Granule in the Inventory database after the metadata file and data files for the granule are successfully stored.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00715	The DPL Ingest service shall, when receiving a failure from the AIM Inventory Insert Service, suspend the granule and create an Operator Intervention.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00720	The Data Pool Ingest Service shall, when encountering a retry or time-out error on an attempt to insert science granule metadata using the AIM Inventory Insert service, suspend the granule unless this is the N-th consecutive error or time-out (where N is configurable on a global basis, see S-DPL-16482-L).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00725	The Data Pool Ingest service shall, when the configured number of consecutive errors for the AIM Inventory Insert service is reached (where N is configurable on a global basis, see S-DPL-16482-L), raise an operator alert for the service.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00730	The Data Pool Ingest service shall, while there is an open alert on the AIM Inventory Insert service, suspend the submission of new requests to the service.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00735	The DataPool Ingest service shall, in the event that the AIM Inventory Insert service was suspended due to consecutive errors, automatically retry sending requests to the service using the alert retry time interval (which is configured on a global basis), and shall react as follows when a retry succeeds:  1. clear the corresponding alert condition and the alert as a whole if there are no other alert conditions for the service,  2. resume dispatching of the operations for that service that were suspended as a consequence of that alert condition.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00740	The DPL Ingest service shall, during the transition period when SDSRV inserts are configured on, send a request to the SDSRV to validate the ODL granule metadata file.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00745	The DPL Ingest service shall, during a transition period following initial transition to release 7.21, send a request to the SDSRV CI to insert granule metadata only if configured to do so.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00750	The DPL Ingest service shall, during a transition period following initial transition to release 7.21, suppress the request to the SDSRV CI to insert granule metadata if configured to do so.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00755	The DPL Ingest service shall, when sending a request to the SDSRV CI to insert granule metadata, use the same granule identifier (dbID) used for identifying the granule in the Inventory database (note: the XML file information to be stored in the Inventory database is not processed by SDSRV, it is not present in the ODL metadata file, and will not be inserted into the SDSRV database).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00760	The DPL Ingest service shall, when receiving a validation error from SDSRV, suspend the granule and create an Operator Intervention.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00765	The DPL Ingest service shall, during the transition period when SDSRV inserts are configured on, mark the granule as deleted in the SDSRV database if the granule is cancelled, failed, or retried from start after the insertion of metadata to the SDSRV database.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00770	The DPL Ingest service shall, when ingesting a granule that contains active subscriptions, queue an event for the Spatial Subscription Service.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00775	The DPL Ingest service shall, when processing a Browse, Production History, or QA granule, use the AIM Inventory database to convert LocalGranuleID of the referenced Science granule to the information needed to link the Browse, Production History, or QA granule to its associated Science granule(s).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00780	The DPL Ingest service shall, when processing a Browse, Production History, or QA granule containing Science granule linkage information, add the reference to the Browse, Production History, or QA granule to the science granule XML metadata file in located in the XML Archive; if the XML metadata file already contains linkage information for the type of granule being processed, the existing linkage information should be removed (bad browse replacement).	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00785	The DPL Ingest service shall, when processing an AST_L1B granule that is linked to an AST_L1A Browse (by the IIU), add the Browse reference to the XML metadata file in located in the XML Archive.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00790	The DPL Ingest service shall, when processing a Non-SIPS ingest request, retrieve the required MCF for the ESDT from a configured location.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00795	The DPL Ingest GUI shall show the current operational status of the AIM XML Validation Utility and the AIM Inventory Insert Utility.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00800	The DPL Ingest GUI shall, during a transition period following initial transition to release 7.21, allow for the insertion of granule metadata by the SDSRV CI to be configured.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00805	The Data Pool Ingest GUI shall permit authorized ingest tuning operators to configure (i.e., enter and edit) the following set of Data Pool Ingest configuration parameters for access to the AIM Inventory Insert service: 1. the maximum number of allowable concurrent requests that can be sent to the service,   2. the maximum amount of time to wait before considering an insert service request timed out.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00810	The Data Pool Ingest GUI shall permit authorized ingest tuning operators to configure (i.e., enter and edit) the following set of Data Pool Ingest configuration parameters for access to the AIM XML Validation service: 1. the maximum number of allowable concurrent requests that can be sent to the service,   2. the maximum amount of time to wait before considering an insert service request timed out.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00820	The DPL Ingest GUI shall allow the operator to configure the number of allowable concurrent requests that can be sent to the XML Validation service.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00825	The DPL Ingest service shall dynamically identify configuration changes (not cause a server reboot) for the number of allowable concurrent requests to the Inventory Insert service and shall limit future requests to the service according to the new value.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00830	The DPL Ingest service shall dynamically identify configuration changes (not cause a server reboot) for the number of allowable concurrent requests to the XML Validation service and shall limit future requests to the service according to the new value.	
DS_7E_01	Removal of Science Data Server	no data				S-DPL-00835	The DPL Ingest service shall use the Volume Group information within the AIM Inventory database to determine the archive location for storing granule data files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-00995	The AIM Archive consistency check service shall provide the capability to verify that all science granule XML metadata files listed within the Inventory database are present within the Metadata archive directories specified.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01000	The AIM Archive consistency check service shall provide the capability to verify that all science granule files listed within the Inventory database are present within the Science data directories.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01010	The AIM Archive consistency check service shall provide the capability to identify files in the Science data directories that are not represented within the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01020	The AIM Archive consistency check service shall provide the capability to identify files in the XML metadata file directories that are not represented within the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01030	The AIM Archive consistency check service shall be able to accommodate multiple volume group history sets when checking the archive against the inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01040	The AIM CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01050	The AIM CI shall assume oriented polygon points are in a clockwise direction when inserting polygon metadata data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01060	The AIM CI shall maintain Granule Inventory Metadata for each stored data granule in accordance with the Release B data model.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01070	The AIM CI shall maintain Collection Metadata, for standard products, containing key organizations and personnel for all product-related DAACs, ADCs, and ODCs.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01980	The AIM CI shall have the ability to store product specific Metadata within the XML metadata files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01990	The AIM CI shall store and maintain Granule Inventory Metadata that references granule-related QA and validation Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-01995	The AIM CI shall store and maintain Granule Inventory Metadata that references granule-related Production History Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02050	The AIM CI shall restrict the capability to directly update XML metadata files in the XML Archive to the operations staff only.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02060	The AIM CI shall store and maintain Granule Inventory Metadata that references granule-related QA Statistics within the XML metadata files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02070	The AIM CI shall store and maintain metadata for granules that contain Navigation Data, including Spacecraft Orbit and Attitude Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02080	The AIM CI shall store and maintain metadata for granules that contain Ancillary Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02090	The AIM CI shall store and maintain metadata for granules that contain Calibration Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02100	The AIM CI shall store and maintain metadata for granules that contain Instrument Engineering Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02110	The AIM CI shall store and maintain Metadata that identifies the data production facility for the product within the descriptor file associated with the ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02120	The AIM CI shall accept polygons and process them using the assumption that points are ordered in a clockwise direction when viewed from above the earth.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02130	The AIM CI shall process polygons according to the Right Hand Inside rule.  This rule states that the inside of the polygon is to the right of each directed arc when viewed from above the earth's surface.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02140	The AIM CI shall be capable of storing an entire orbit of data as the spatial extent of a granule represented with the Gpolygon data type.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02150	The AIM CI shall be delivered with an MCF for each of the following data types: Browse, and Delivered Algorithm Package.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02160	The AIM ESDT Maintenance GUI shall allow the operator to add new data types (ESDTs) into the system.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02170	The AIM ESDT Maintenance GUI shall authenticate the operator before allowing any operations.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02180	The AIM ESDT Maintenance GUI shall provide operations staff with the ability to update ESDTs by adding collection metadata, inventory metadata, events and new qualifiers on existing events.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02190	The AIM ESDT Maintenance GUI shall provide the operations staff with the ability to update ESDTs by replacing non-restricted collection attributes.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02200	The AIM ESDT Maintenance GUI shall provide operations staff with the ability to update ESDTs by changing a mandatory attribute to optional or updating single-valued collection metadata, multi-valued collection metadata, inventory metadata, attributes of collection-related entities and service signatures	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02210	The AIM ESDT Maintenance GUI shall, when updating an ESDT, allow the addition of optional Inventory attributes.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02220	The AIM ESDT Maintenance GUI shall, when processing a request to update an ESDT, fail the request if the new descriptor file is missing any Inventory attribute defined in the installed version of the descriptor.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02230	The AIM ESDT Maintenance GUI shall reject attempts to update the following restricted attributes: ShortName and VersionID in the CollectionDescriptionClass Group, the  AdditionalAttributeType associated with each AdditionalAttributeName, and spatialSearchType.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02240	The AIM ESDT Maintenance GUI shall, when updating an ESDT, include a prompt to the Operator stating that changes take affect only after the Ingest service is restarted.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02250	The AIM ESDT Maintenance GUI shall allow operators to delete existing data types (products) providing that 1) the ESDT doesn't contain any granules in the Inventory, 2) the ESDT is not defined within the Data Pool, 3) the Spatial Subscription service doesn't contain subscriptions referencing the ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02260	The AIM ESDT Maintenance GUI shall require the operator to specify a descriptor file, in ODL format, to define an ESDT as part of the ESDT Install or Update.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02270	The AIM ESDT Maintenance GUI shall allow configuration, in the application configuration file, of a directory for storing descriptor files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02280	The AIM ESDT Maintenance GUI shall allow configuration, within the application configuration file, of a descriptor source directory to be used for identification of descriptor files to be processed.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02290	The AIM ESDT Maintenance GUI shall, when installing or updating an ESDT, generate and store the ESDT specific granule schema file in the configured descriptor file location; replacing the schema file if present.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02300	The AIM ESDT Maintenance service shall, when updating an ESDT, replace the current descriptor file associated with the ESDT with the descriptor file provided with the update request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02310	The AIM ESDT Maintenance GUI shall, when installing an ESDT, move the associated descriptor file from the installation source directory to the configured descriptor location.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02320	The AIM ESDT Maintenance GUI shall validate the descriptor file, included in the request to install an ESDT, to be consistent with the ECS Data Model.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02330	The AIM ESDT Maintenance GUI shall validate the descriptor file, included in the request to update an ESDT, to be consistent with the ECS Data Model.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02340	The ESDT Maintenance GUI shall display all errors and warnings found while validating the contents of the operator supplied descriptor file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02350	The AIM ESDT Maintenance GUI shall fail the installation of an ESDT if validation errors or warnings are found.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02360	The AIM ESDT Maintenance GUI shall validate that the definitions of Product Specific Attributes (PSAs) in the descriptor match existing definitions of PSAs defined within the Inventory DB.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02370	The AIM ESDT Maintenance GUI shall, when validating the collection level Bounding Rectangle component of a descriptor file, validate the spatial geometry (this is limited to checking that the North coordinate is greater than the South coordinate).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02380	The AIM ESDT Maintenance GUI shall add the definitions of Product Specific Attributes associated with the ESDT to the Inventory database if the definition is not already present.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02390	The AIM ESDT Maintenance GUI shall, when validating a descriptor file, verify that the ShortName and VersionID of the Collection Description within the Collection section of the descriptor matches the ShortName and VersionID specified in the Inventory section and the ShortName and VersionID within the file name.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02400	The AIM ESDT Maintenance GUI shall, when validating a descriptor file, verify that the granule metadata attributes listing in the Event section for Insert events match attributes listed in the Inventory section.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02410	The AIM ESDT Maintenance GUI shall, when validating a descriptor, obtain validation rules for non-PSA and non-keyword attributes from an XML schema delivered as part of the service.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02420	The AIM ESDT Maintenance GUI shall be deployed with an XML schema definition file to be used for validating descriptor files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02430	The AIM ESDT Maintenance GUI shall validate that the ECS keyword attributes in the descriptor match existing GCMD keyword hierarchies.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02440	The AIM ESDT Maintenance GUI shall be deployed with an XML schema file (Generic Inventory Schema) that contains the default rules for each element found in the Inventory section of the granule metadata file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02450	The AIM ESDT Maintenance GUI shall, when installing or updating an ESDT, generate an ESDT specific schema file that contain granule validation rules based upon the contents of the Inventory section of the Descriptor file and the default element rules.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02460	The AIM ESDT Maintenance GUI shall allow the operator to view a list of installed ESDTs.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02470	The AIM ESDT Maintenance GUI shall allow the operator to filter the list of installed ESDTs by providing a string to match against the ShortName / VersionID contained in list.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02480	The AIM ESDT Maintenance GUI shall allow the operator to view a list of descriptor files stored in the descriptor source location (awaiting installation or update).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02490	The AIM ESDT Maintenance GUI shall, when installing, updating, or deleting one or more descriptors, display processing totals for the number of descriptors processed successfully and the number of descriptors that failed.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02510	The AIM ESDT Maintenance GUI shall, when processing an Operator request to Install, Update, or Remove an ESDT, write to the application log the time of the request, Action requested, ShortName, VersionID, descriptor file name for the ESDT, and the result of the operation.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02520	The AIM ESDT Maintenance GUI shall, when processing an Operator request to generate an MCF or ESDT specific schema, write to the application log the time of the request, Action requested, ShortName, VersionID, descriptor file name for the ESDT, and the result of the operation.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02530	The AIM ESDT Maintenance GUI shall, when installing, or updating multiple ESDTs, abort ESDT Installation or Update of an individual ESDT if validation errors or warnings are encountered in the descriptor file and continue processing the remaining descriptor files selected by the operator.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02540	The AIM ESDT Maintenance GUI shall, when processing a batch of ESDTs, abort the batch if a database or file system is unavailable.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02550	The ESDT Maintenance GUI shall notify operations staff if there are no differences in a descriptor as part of the Update ESDT process.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02560	The ESDT Maintenance GUI shall, upon startup, display an error and shut down if another instance is detected within the same mode.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02570	The ESDT Maintenance GUI shall, upon startup, check for any incomplete requests from a previous run and query the operator for confirmation before recovering the failed requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02580	The ESDT Maintenance GUI shall, when recovering from a failed Update ESDT request, restore the previously installed version of the ESDT/descriptor.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02590	The ESDT Maintenance GUI shall allow configuration, within the application configuration file, the base directory within the small file archive to be used for creation of ESDT specific metadata directories.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02600	The ESDT Maintenance GUI shall, when installing an ESDT, create an ESDT specific metadata directory for the ESDT being installed within the configured base directory within the small file archive to be used for ESDT specific metadata directories.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02610	The AIM ESDT Maintenance GUI shall register insert events in the Spatial Subscription Server (EcNbDb) database when installing or updating an ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02620	The AIM ESDT Maintenance GUI shall, when installing or updating an ESDT, register all Spatial Subscription Server supported Insert event qualifers from the descriptor file into the Spatial Subscription Server database (Spatial Subscription Server supports only a subset of the Science granule metadata).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02630	The AIM ESDT Maintenance GUI shall, when installing or updating an ESDT, register the CSDT associated with ESDT in the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02640	The AIM ESDT Maintenance GUI shall, when installing an ESDT, shall populate the collection based tables identified in the Operations Concept of ticket DS_7E_01.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02650	The AIM ESDT Maintenance GUI shall, when updating an ESDT, replace the basic collection identification information (collection tables identified in Operations Concept of ticket DS_7E_01) in the AIM Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02660	The AIM ESDT Maintenance GUI shall, when processing an Install, Update, or Delete operation, allow the operator to select a group of ESDT descriptor files for the operation.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02670	The AIM ESDT Maintenance GUI shall, when processing an Install, Update, or Delete operation on a set of ESDT descriptor files, process all ESDT descriptor files selected.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02680	The AIM ESDT Maintenance GUI shall, when deleting an ESDT, remove 1. all of the ESDTs XML metadata file directories from the small file archive, 2. the MCF,  3. the ESDT specific schema file,  4. the Descriptor file,  5. the ESDTs collection information from the AIM Inventory database (including the removal of PSA definitions if the PSA is not used by other ESDTs),  6. the ESDTs event definitions and qualifiers from the Spatial Subscription Server database (provided that no cancelled subscriptions are present).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02690	The AIM ESDT Maintenance GUI shall provide the ability to view the descriptor file of an installed ESDT in either ODL or XML format.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02700	The AIM ESDT Maintenance GUI shall, when installing or updating an ESDT, generate an MCF and store it in the configured MCF location.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02710	The AIM ESDT Maintenance GUI shall provide the operator the ability to generate an MCF for any installed ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02720	The AIM ESDT Maintenance GUI shall allow configuration, in the application configuration file, of a directory for storing MCFs.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02730	The AIM ESDT Maintenance GUI shall provide the operator the ability to generate an ESDT specific schema for any installed ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02740	The AIM ESDT Maintenance GUI shall remove any partially inserted information if an error is encountered while installing an ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02750	The AIM ESDT Maintenance GUI shall recover from and process the resubmission of a partially completed ESDT update, install, or delete.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02760	The AIM ESDT Maintenance GUI shall restore the original version of the descriptor (including all steps of the update process) if a fatal error is encountered while updating an ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02770	The AIM ESDT Maintenance GUI shall, when validating a descriptor file, verify that the Product Specific attributes in the Inventory section match Product Specific attributes defined in the Collection section.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02780	The AIM ESDT Maintenance GUI shall, when validating a descriptor file, verify that the spatial attributes in the Inventory section are valid for the spatial search type identified at the top level of the descriptor.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02790	The AIM ESDT Maintenance GUI shall log all validation error messages pertaining to the validation of metadata elements to the application log file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02800	The AIM ESDT Maintenance GUI shall, when completing a successful install or update of an ESDT, or a successful restoration of a failed ESDT installation or update, remove all temporary files associated with the processing of the ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02810	The AIM ESDT Maintenance GUI shall, when processing an Install, Update, or Delete ESDT request, record the beginning of each step (RPC to a database, 1st access or processing of a file) of the request in the application log.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02820	The AIM Granule Deletion service shall be implemented as a set of command line utilities, one for each of the following operations: 1) Identify granules for deletion, 2) Mark granules as deleted or deleted from archive (DFA) (this restricts distribution of the granule and marking a granule as deleted makes it eligible for removal in the future,   3) Restore granules marked as deleted or deleted from archive to an active state,  4) Remove granules previously marked as deleted (removes the entries from the Inventory database and all constituent files).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02830	The AIM Granule Deletion service shall, when searching for science granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  inclusive temporal range for comparison to the start of the acquisition time (BeginningDateTime) of the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02840	The AIM Granule Deletion service shall, when searching for science granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  inclusive temporal range for comparison to the acquisition time range (BeginningDateTime, EndingDateTime) of the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02850	The AIM Granule Deletion service shall, when searching for science granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  a singe date specifying an open ended time range to be compared to the acquisition start time (return granules with the BeginningDateTime >= to the supplied value).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02860	The AIM Granule Deletion service shall, when searching for science granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  a singe date specifying an open starting time range for comparison to the acquisition start time of the granule (return granules with the BeginningDateTime <= to the supplied value).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02870	The AIM Granule Deletion service shall, when searching for science granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  a singe date specifying an open starting time range for comparison to the acquisition end time of the granule (return granules with the EndingDateTime <= to the supplied value).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02880	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  inclusive granule insert time range.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02890	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  a singe date specifying an open ended time range to be compared to the insert time (return granules with the insertTime >= to the supplied value).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02920	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): 1. ESDT short name,  2. ESDT version, and  3.  a singe date specifying an open starting time range for comparison to the insert time of the granule (return granules with the insertTime <= to the supplied value).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02930	The AIM Granule Deletion service shall, when searching for science granules to mark as deleted, permit an ECS operator to search for granules by providing (via command line parameters): a file containing: 1. ESDT short name, 2. ESDT version, and 3.  Local Granule ID values (one per line).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02940	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, provide a command line option to limit the search to only granules that are marked as delete from archive (can be used to verify the outcome of operation to mark granules or to create input to restore deleted from archive granules).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02950	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, provide a command line option to search only for granules that are already marked for deletion (can be used to verify the outcome of an operation to mark granules as deleted or to create input to restore granules marked as deleted).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02960	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, output a list ECS internal granule identifiers that match the input search constraints to a file (supplied by the operator as a command line argument).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02970	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, provide a command line parameter to limit the number of granules to output as the result of a search.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02980	The AIM Granule Deletion service shall, when searching for granules to mark as deleted, if applicable, limit the list of output granules to the granule limit specified on the command line (if the search contains a constraint on BeginningDateTime or insertTime, then output list shall be sorted by specified temporal attribute prior to limiting the output).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-02990	The AIM Granule Deletion service shall provide a mechanism to mark data as eligible for deletion.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03000	The AIM Granule Deletion service shall allow the operator to update the Granule Inventory Metadata to indicate that a data granule cannot be retrieved in the event of file corruption or unexpected file loss (mark as deleted from archive).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03380	The AIM Granule Deletion service shall permit an ECS operator to include the inventory database entry and XML metadata file when marking a granule for deletion, or exclude both from the deletion (i.e., cause a logical delete or delete from archive) via a command line parameter.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03390	The AIM Granule Deletion service shall, when marking granules as deleted or deleted from archive, process an input file (provided as a command line option) that contains ECS Internal granule identifiers (GeOIDs) formatted as one input line per granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03400	The AIM Granule Deletion service shall, when marking granules as deleted, by default mark any BROWSE, QA, and PH granules referenced by the science granule as deleted, if they are not referenced by any other granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03410	The AIM Granule Deletion service shall, when marking science granules as deleted, permit an ECS operator to suppress deletion of the BROWSE, QA, PH via command line option.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03420	The AIM Granule Deletion service shall, when completing a request to mark granules as deleted or deleted from archive, log the following information for each type of granule modified:  1.  the total number of science granules marked for deletion or DFA   2. the total number of Browse granules marked for deletion,  3. the total number of  PH granules marked for deletion,  4. the total number of QA granules marked for deletion,  5. the total number of Delivered Algorithm Package granules marked for deletion,  6) the total number of failures for each of the preceding granule types.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03430	The AIM Granule Deletion service shall, when marking granules as deleted or deleted from archive, allow the operator to specify a log file as a command line option.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03440	The AIM Granule Deletion service shall, in the event that a log file is not specified when marking granules as deleted or deleted from archive, create a log file in the standard log directory for the mode.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03450	The AIM Granule Deletion service shall, when encountering a request to mark a granule as deleted or deleted from archive that is already marked in the desired way, log an error message and continue processing the remaining granules within the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03460	The AIM Granule Deletion service shall identify and log errors encountered when marking a granule as deleted or deleted from archive.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03470	The AIM Granule Deletion service shall, when marking a granule as deleted or deleted from archive,  perform operations such that they can be restarted and completed successfully if they are interrupted by a fault.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03480	The AIM Granule Deletion service shall, when encountering an error marking a granule as deleted or deleted from archive, log an error and continue processing the remaining granules in the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03490	The AIM Granule Deletion service shall provide a mechanism to restore a granule that was marked deleted to an active (not marked for deletion) status.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03500	The AIM Granule Deletion service shall provide a mechanism to restore a science granule that was marked as deleted from the archive (DFA) to an active (not marked as DFA) status.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03510	The AIM Granule Deletion service shall, when restoring a granule marked as deleted or deleted from archive to an active status, process an input file (provided as a command line option) that contains ECS Internal granule identifiers (GeOIDs) formatted as one input line per granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03520	The AIM Granule Deletion service shall, when restoring a science granule marked as deleted to an active status, by default restore the BROWSE, QA, and PH granules referenced by the science granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03530	The AIM Granule Deletion service shall, when restoring a science granule marked as deleted to an active status, permit the operator to suppress restoring of the BROWSE, QA, PH via command line option.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03540	The AIM Granule Deletion service shall, when completing a request to restore granules previously marked as deleted or deleted from archive, log for each type of granule processed (Science, Browse, QA, PH, and DAP): 1. the total number of granules that were restored,  2. the total number of granules that failed to be restored.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03550	The AIM Granule Deletion service shall, when restoring granules marked as deleted or deleted from archive, allow the operator to specify a log file as a command line option.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03560	The AIM Granule Deletion service shall, in the event that a log file is not specified when restoring granules marked deleted or deleted from archive, create a log file in the standard log directory for the mode.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03570	The AIM Granule Deletion service shall handle a request to restore a granule that is not marked as deleted or deleted from archive by logging an error message and continuing to process the remaining granules within the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03580	The AIM Granule Deletion service shall identify and log errors encountered when restoring granules marked as deleted or deleted from archive.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03590	The AIM Granule Deletion service shall restore granules marked deleted or deleted from archive such the service can be restarted and completed successfully if interrupted by a fault.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03600	The AIM Granule Deletion service shall, when encountering an error restoring a granule marked as deleted or deleted from archive, log an error and continue processing the remaining granules in the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03610	The AIM Granule Deletion service shall process Data Delete Requests for the deletion of data and associated metadata.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03620	The AIM Granule Deletion service, when instructed to remove a granule  marked as deleted, shall remove: 1. the inventory entries for granule, 2. the metadata file for the granule from the XML Metadata archive (if processing a science granule), and 3. all data files associated with the granule from the Science file archives.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03630	The AIM Granule Deletion service, when instructed to remove a granule  marked as deleted from archive, shall remove all data files associated with the granule from the Science file archives and not delete the inventory entries or XML files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03640	The AIM Granule Deletion utility for removing (physically delete) granules marked as deleted shall require an ECS operator to specify a deletion lag time in days (retain granules marked for deletion within lag time days), including a lag time of 0 (zero is interpreted as a request to delete all granules marked for deletion).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03650	The AIM Granule Deletion service shall, when removing granules marked as deleted, remove granules that were marked for deletion before the current day minus the lag time days, and not remove granules that were marked as deleted within lag time days.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03660	The AIM Granule Deletion service shall, when removing granules marked as deleted, display the number of granules whose inventory entries and constituent files will be removed and prompt the operator for confirmation before performing the removal.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03670	The AIM Granule Deletion service shall, when removing science granules marked as deleted, log the start and end time of the process, the UNIX ID of the process, and log the ESDT short name,  ESDT version, granule ID, and local granule ID (if present) of each science granule removed.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03680	The AIM Granule Deletion  service shall, when removing non-science granules marked as deleted, log the start and end time of the process, the UNIX ID of the process, and the type (Browse, QA, PH, DAP) and granule ID for each non-science granule removed.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03690	The AIM Granule Deletion Service shall, when removing granules marked as deleted, log for each granule deletion error: the ESDT short name, ESDT version, granule ID of the affected granule, and the nature of the error.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03700	The AIM Granule Deletion service shall, when removing granules marked as deleted, prompt the operator for the name of a log file and create the log file or append to it if it already exists.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03710	The AIM Granule Deletion service shall, in the event that the operator fails to enter the name of a log file when removing granules marked as deleted, create or append to a log file with a default name in the default location.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03720	The AIM Granule Deletion service shall, when encountering an error removing the XML metadata file or the data files for a granule that is marked as deleted, log an error message and continue processing the remaining granules in the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03730	The AIM Granule Deletion service shall be capable of recovering from errors that may occur while removing granules marked as deleted, such that inventory entries or files for deleted granules can be correctly processed by subsequent executions of the utility, and incompletely processed inventory entries (if any) do not cause ECS faults.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03740	The AIM Granule Deletion service shall use the appropriate volume group history set to locate files when removing  a granule from the archive.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03840	The AIM Granule Deletion service, when recovering from a failed request to remove granules marked as deleted, shall display the number of granules that were not processed in the previous run and allow the operator to:  1. complete the removal of files from the previous run only,    2. start a new run and complete the previous run.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03850	The AIM Granule Deletion service shall record the following science or browse granule modifications and make the information available to the Bulk Metadata Generation Tool (BMGT):  1. marking granules as deleted,  2. marking science granules deleted from archive,  3. restoring deleted or deleted from archive granules to an active state.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03860	The AIM Granule Deletion service shall exit with an error message if it detects another instance of the service running concurrently within the same mode.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03870	The AIM Granule Deletion Service shall permit an ECS operator to perform granule deletions concurrently with other ECS functions.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03880	The AIM Granule Deletion service shall, when encountering a database deadlock, retry the database request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03890	The AIM Granule Deletion service shall abort processing if an database related access error is encountered.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03900	The AIM Inventory Insert service shall record the directory used for storing the XML metadata file in the Inventory database if it is not already recorded.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03910	The AIM Inventory Insert service shall receive and persistently store optional checksum type, checksum origin, and checksum value parameters from the DPL Ingest service for science granule inserts.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03920	The AIM Inventory Insert service shall populate all granule related tables (as defined in the Operations Concept of ticket DS-7E-01) in the AIM Inventory database with the metadata values contained in the XML file received in the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03930	The AIM Inventory Insert service shall, when inserting ASTER granule metadata, extract the Product Specific Attribute named RadiometricDBVersion and store it in the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03940	The AIM Inventory Insert service shall, when inserting ASTER granule metadata, extract the Product Specific Attribute named GeometricDBVersion and store it in the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03950	The AIM Inventory Insert service shall, when inserting ASTER granule metadata,  extract and store the values of the Product Specific Attributes named DAR_ID and store them in the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03960	The Inventory Insert Service shall be capable of receiving and recording the metadata of Browse granules, as requested by valid Data Insert Requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03970	The Inventory Insert service shall, when inserting an AST_L1B granule, link the Browse of the most recently inserted AST_L1A granule that matches the temporal range of the newly inserted AST_L1B granule to the AST_L1B granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-03980	The Inventory Insert service shall, when inserting a Browse granule that references an AST_L1B granule, link the most recently inserted AST_L1A granule that matches the temporal range of the referenced AST_L1B granule to the newly inserted Browse granule (replace a bad Browse that was ingested with the AST_L1A).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04040	The Inventory Insert service shall, when inserting a Browse granule that references an AST_L1A or AST_L1B granule, remove the existing associations of the AST_L1A and/or AST_L1B granules to other Browse granules.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04050	The Inventory Insert service shall, when inserting a Browse granule that references an AST_L1A granule, link the Browse to an AST_L1B granule and remove any existing link if an AST_L1B granule is found satisfying the following rules: 1) the AST_L1B is the most recently inserted AST_L1B granule that matches the temporal range of the referenced AST_L1A granule  2) the AST_L1B has an insertTime that is greater than that of the referenced AST_L1A granule (replace a bad Browse that was ingested with the AST_L1A).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04060	The AIM Inventory Insert service shall validate the set of NOSE track numbers and start/end block numbers associated with a granule at the time of insertion against the predefined orbit spatial extents defined within the AIM Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04070	The AIM Inventory Insert Service shall associate the BROWSE granule for an ASTER L1A granule with all ASTER L1B  products derived  from that L1A granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04080	The AIM Inventory Insert Service shall be capable of receiving and recording the metadata of Quality Assurance granules, as requested by valid Data Insert Requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04090	The AIM Inventory Insert Service shall be capable of receiving and recording the metadata of Production History granules, as requested by valid Data Insert Requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04100	The AIM Inventory Insert Service shall be capable of receiving and recording the metadata of Delivered Algorithm Packages, as requested by valid Data Insert Requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04110	The AIM Inventory Insert service shall support the association of inserted AMSR granules with predefined spatial extents by recording as metadata for the granule the set of track numbers and the set of block numbers of the spatial extents corresponding to the granules spatial region.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04120	The AIM Inventory Insert service shall support the association of inserted AMSR-E granules with predefined spatial extents by recording as metadata for the granule the set of track numbers and the set of block numbers of the spatial extents corresponding to the granules spatial region.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04130	The AIM Inventory Insert service shall support the association of inserted MISR granules with predefined spatial extents by recording as metadata for the granule the set of track numbers and the set of block numbers of the spatial extents corresponding to the granules spatial region.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04140	The AIM Inventory Insert service shall support the association of inserted GLAS granules with predefined spatial extents by recording as metadata for the granule the set of track numbers and the set of block numbers of the spatial extents corresponding to the granules spatial region.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04150	The AIM Inventory Insert service shall, when processing a granule with a spatialSearchType of Orbit, extract Orbit track numbers, start and stop block numbers from product specific attributes in the metadata file and store them in the AIM Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04160	The AIM Inventory Insert service shall use the Spatial Query Server to insert LLBOX and Gpolygon metadata attributes into the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04170	The AIM Inventory Insert service shall, when inserting a Browse, Production History, or QA granule that references Science granules, link the inserted granule to the referenced Science granules in the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04180	The AIM Inventory Insert service shall allow the configuration, within the application configuration file, the number of times to retry a database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04190	The AIM Inventory Insert Service shall, when encountering a database error, retry the insertion of granule information the configured number of times.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04200	The AIM Inventory Insert Service shall, when failing to insert the metadata of a granule into the Inventory database the configured number of times, return a failure result.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04210	The AIM Inventory Insert Service shall return a failure result if a required resource is unavailable.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04220	The AIM Inventory Insert Service shall remove metadata that is partially inserted into the Inventory database if a processing error or fault is encountered.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04230	The AIM Inventory Insert Service shall log all errors encountered in the processing of an insert request in the application log.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04240	The AIM Inventory Insert Service shall be capable of handling multiple concurrent insert requests from the DPL Ingest service.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04250	The AIM Inventory Insert service shall be able to operate in multiple modes concurrently.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04260	The AIM Inventory database shall maintain the following information for each stored science granule: a.  the unique Granule ID;  b.  the File Location for each of the granule's constituent file(s)  c. the date and time of storage d. all other metadata attributes, if present, that are assigned to tables identified in the Operational Concept of ticket DS_7E_01.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04270	The AIM Inventory Database shall  provide storage of polygonal (store Gpolygon) spatial extents.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04280	The AIM Inventory database shall store and maintain Granule Inventory Metadata that references granule-related Browse Data.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04290	The AIM Inventory database shall support the storage of spatial extents [LLBOX] defined as lines of constant latitude and longitude, up to and including whole Earth. (I.e., +90 degrees to -90 degrees latitude, +180 degrees to -180 degrees longitude).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04300	The AIM Inventory Database shall supply services to provide the name and location for each of the constituent files for granules associated with a data request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04310	The AIM Inventory database shall support predefined spatial extents for AMSR  data types that are characterized by a track number that corresponds to a pre-specified spacecraft orbit, and a block number that corresponds to a spatial extent along the track.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04320	The AIM Inventory database shall support predefined spatial extents for AMSR-E  data types that are characterized by a track number that corresponds to a pre-specified spacecraft orbit, and a block number that corresponds to a spatial extent along the track.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04330	The Inventory Insert service shall support predefined spatial extents for GLAS data types that are characterized by a track number that corresponds to a pre-specified spacecraft orbit, and a block number that corresponds to a spatial extent along the track.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04340	The AIM Inventory database shall support predefined valid ECS Keyword hierarchies.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04350	The Archive Inventory Management CI shall provide capabilities to populate the Inventory DsMdOrbitPolygons table with polygon definitions for an instrument and platform combination provided by the Science Instrument teams.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04355	The AIM Inventory database shall support predefined spatial extents that are associated with a specific instrument and platform.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-04357	The AIM Inventory database shall support the insertion of granules with metadata that matches existing granules within the Inventory (to facilitate the replacement of granules that are lost or reprocessed).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05010	The AIM Inventory database shall track QA flag updates	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05020	The AIM Inventory DB shall accept and persistently store optional checksum type, checksum origin, and checksum value parameters during a file insert.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05030	The AIM Inventory DB shall provide the capability to add or remove valid checksum types.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05040	The AIM Inventory Database shall provide storage for the valids used to produce the ECSMETV (export to ECHO).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05050	The Archive Inventory Management CI shall ensure that the following calendar transitions are handled completely and accurately:  a. New Year  b. New Decade  c. Leap Year. d. Daylight savings time	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05060	The AIM QA Update service shall accept and process Update Metadata Requests that request the update of the following QA Attributes for the specified data granules 1) Operational Quality Flag 2) Operational Quality Flag Explanation 3) Science Quality Flag  4) Science Quality Flag Explanation.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05070	The AIM QA Update service shall provide one utility that updates 1. the QA metadata attributes stored in XML files in the XML Archive,   2. The QA attributes stored in the Data Pool database,  3. the QA attributes stored in the XML metadata files within the Data Pool file systems for public granules that are not involved in a distribution request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05080	The AIM QA Update service shall provide an operator configurable mode-specific request directory where all QA update request files intended for that mode reside.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05090	The AIM QA Update service shall provide a DAAC configurable e-mail address at which the QA update requests are received.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05100	The AIM QA Update service shall maintain an operator  configurable list of valid Requester IDs corresponding to the sites and the ESDTs that can be updated by each site for the purpose of authenticating the QA update requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05140	The AIM QA Update service shall allow DAAC operations to configure, within the application configuration file, a directory location for the storage of completed request files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05150	The AIM QA Update service shall allow DAAC operations to configure, within the application configuration file, a directory location for the storage of failed request files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05160	The AIM QA Update service shall provide the following e-mail notification options that can be configured by the operator for each site.  a. Send e-mail notification upon successful completion of QA updates as well as non-retryable failure.  b. Send e-mail notification only upon non-retryable failure.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05170	The AIM QA Update service shall allow an operator to set up a list of internal DAAC e-mail addresses to which an e-mail notification is sent or copied upon completion of a QA update run.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05180	The AIM QA Update service shall allow an operator to configure a Reply-To: e-mail address for each site to which e-mail notifications are sent.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05190	The AIM QA Update service shall allow DAAC operations to configure the maximum number of granules to update within a single request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05200	The AIM QA Update service shall operate as a command line utility.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05210	The AIM QA Update service shall validate the command line parameters for correct syntax.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05220	The AIM QA Update service shall allow the operator to suppress the operator prompts and the display of all messages via a no-prompt command line option.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05230	The AIM QA Update service shall suppress all operator prompts if the no-prompt option is specified assuming an affirmative response in these cases.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05240	The AIM QA Update service shall be able to process an individual QA update request file provided via command line, (or) all update request files located in a configured request directory.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05250	Each AIM QA update request file name shall contain the following information as part of its name:  a. Operation mode   b. The site name that originated the request  c. Time tag of request accurate to second.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05260	The AIM QA Update service shall, as a command line option, provide the ability to process updates which failed in a previous run without starting any new updates.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05270	The AIM QA Update service shall, as a command line option, provide the ability to skip the processing of updates which failed in a previous run.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05280	The AIM QA Update service shall, as a command line option, provide the ability to remove any update requests marked as failed or investigate in a previous run before beginning a new run.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05290	The AIM QA Update service shall, as a command line option, provide the ability to modify update requests marked as investigate to indicate they don't require investigation, before beginning a new run.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05300	The AIM QA Update service shall require the QA update request to contain the following information:  a. Requester ID   b. QA Flag Type (Science or Operational)  c. QA metadata update request details.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05310	The Requester ID included in the request shall be provided in one of the following format:  a. a valid e-mail address   b. a text string identification for a site	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05320	The AIM QA Update service shall authenticate a QA update request by a. validating the Requester ID included in the request against a list of valid Requester IDs maintained at the DAAC (and) b. ensuring that the ESDT to be updated is allowed for the Requester ID.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05330	The AIM QA Update service shall provide the option to specify granules to be updated using one of the following formats within a request:   a. ESDT Short name, Version ID and Granule UR (or)   b. ESDT Short Name, Version ID and Local Granule ID (or)   c. ESDT Short Name, Version ID and a temporal window that defines the acquisition date and time range.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05340	The AIM QA Update service shall validate the syntax (format and valid range) of the QA Flag values included in the request before performing the updates.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05350	The AIM QA Update service shall, when an update request entry specifies the literal value ALL in place of a Parameter Name, update all measured parameters of the specified granules with the same set of QA flag and the explanation field values specified within the request entry.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05360	The AIM QA Update service shall append the date and time of update, accurate to the minute,  to the explanation fields provided in the request before storing them in the XML metadata files and Data Pool database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05370	The QA metadata update request specifying  ESDT and temporal window shall include the following information:  a. ESDT Short Name  b. Version ID  c. Temporal window characterized by the acquisition date and time range.  d. One or more triplets of  Measured Parameter name (or the literal ALL), QA Flag, and the corresponding explanation field.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05380	The temporal window for QA metadata update shall be specified as the inclusive time range bounded by the beginning acquisition date and time of the earliest granule and the beginning acquisition date and time of the latest granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05390	The QA metadata update request based on Local Granule IDs shall include the following information for each granule:  a. ESDT Short Name  b. Version ID  c. Local Granule ID (LGID)  d. One or more triplets of  Measured Parameter name (or the literal ALL), QA Flag and the corresponding explanation field.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05400	The QA metadata update request based on Granule URs shall include the following information for each granule:  a. ESDT Short Name  b. Version ID  c. Granule UR   d. One or more triplets of  Measured Parameter name (or the literal ALL), QA Flag and the corresponding explanation field.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05410	The AIM QA Update service shall be able to accept and update QA metadata for individual parameters, each with a different set of QA flag and explanation field values, if a Parameter Name is supplied in the request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05420	The AIM QA Update service shall, when processing multiple update request files in a request directory, process the requests originated from a particular site in order of the request time tag as indicated by the request file names.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05430	The AIM QA Update service shall, by default, display the number of granules to be updated and prompt the operator for confirmation before performing the updates.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05440	The AIM QA Update service shall, upon completion of the update to the XML file within the XML Archive, record the time of the update within the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05445	The AIM QA Update service shall, upon completion of the update to the XML file within the XML Archive, record the time of the update within the XML File.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05450	The AIM QA Update service shall record in a history file the granule ID (dbID) along with the measured parameters, the QA values, and the corresponding explanation fields before and after the update for each granule updated.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05460	The AIM QA Update service shall, in the event that a granule included in a QA Update request is published in the Data Pool and is not part of a distribution request, update the DataPool database and file system with the updated version of the QA attributes.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05470	The AIM QA Update service shall, upon completion of the update to the XML file within the DataPool and the DataPool database entries, record the time of the update within the DataPool database and within the XML file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05480	The AIM QA Update service shall, in the event that a granule included in the QA update request is made public in the DataPool after the start of the QA Update service, update the XML file and database entries in the DataPool with the new QA values.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05490	The AIM QA Update service shall, in the event that a granule included in the QA update request is being removed from the DataPool when the QA update service is attempting to process it, skip the DataPool update and proceed to the next granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05500	The AIM QA Update service shall, in the event that a state of granule included in the QA update request is being modified in the DataPool when the QA update service is attempting to process it, skip the DataPool update for the granule, proceed to the next granule in the request, and if the new state is still eligible for QA updates, retry the update of the granule in each future run  until the update is completed.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05510	The AIM QA Update service shall, when encountering an error processing an update request for a granule/parameter that is already marked as failed, update the request to indicate that investigation is required.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05520	The AIM QA Update service shall, by default, attempt to process all failed requests not marked as requiring investigation from previous runs in addition to all new update requests provided to the service (update requests marked as investigate must be modified to indicate the don't require investigation before they can be processed).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05530	The AIM QA Update service shall, when instructed to modify update requests marked as investigate, update all requests to indicate they don't require investigation before beginning a new run (in this case, all update requests known to the service will be processed).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05540	The AIM QA Update service shall, when instructed to recover failed requests only, attempt to process all failed requests from previous runs and not attempt to load any new update requests.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05550	The AIM QA Update service shall, when instructed to skip failed requests, update all failed requests to indicate that investigation is required before starting any new update requests (update requests marked as investigate are not processed).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05560	The AIM QA Update service shall, when instructed to remove any update requests marked as failed or investigate, remove any update requests marked as failed or investigate in a previous run before beginning a new run	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05570	The AIM QA Update service shall, upon completion of processing a request file, generate an e-mail notification including the following information as applicable:   a. The name of the request file being processed.  b. Total number of granules specified in the request c. Total number of granules updated d. A list of granules not updated along with specific error messages and reasons for failure.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05580	The AIM QA Update service shall, upon completion of processing a request file, send an e-mail notification to the requester using the Reply-To: e-mail address configured for the requesting site if available.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-05590	The AIM QA Update service shall, upon completion of processing a request file, send an e-mail notification to the From: e-mail address included in the request if the Reply -To address is not available.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06140	The AIM QA Update service shall, upon completion of processing a request file, allow the operator to view the following information:  a. A list of affected granules identified by ESDT Short Name, Version ID, LGID, dbID, along with the measured parameters and the updated QA flag values b. Total number of granules updated.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06150	The AIM QA Update Service shall, upon completion of processing a request file, move the request file to the completed request directory if all granules were processed or, in the event of an authentication error or the service is configured to exit on the first error, move the request file to the failed request directory.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06160	The AIM QA Update service shall abort with an error message if another instance is running in the same mode.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06170	The AIM QA Update service shall abort with an error message if the Data Pool Move Collection utility is running in the same mode.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06180	The AIM QA update service shall, in the event of an authentication error, send an e-mail notification to the requester indicating authentication failure	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06190	The AIM QA Update service shall reject a request and terminate with a non-retryable failure if the operation mode indicated by the request file name does not match the operation mode in which the service is being executed.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06200	The AIM QA update service shall, in the event of an authentication error, reject the entire request file and continue processing any remaining request files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06210	The AIM QA Update service shall, upon failure in validating the command line syntax, display an error message, the correct command line syntax, and terminate.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06220	The AIM QA Update service shall display a warning message if it detects that the number of granules to be updated exceeded a DAAC configurable maximum threshold.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06230	The AIM QA Update service shall, when encountering a duplicate Local Granule ID within the input request file, remove the duplicate and continue to process the request file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06240	The AIM QA Update service shall, when encountering a duplicate UR within the input request file, remove the duplicate and continue to process the request file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06250	The AIM QA Update service shall consider a reference to a Granule UR or a Local Granule ID that does not exist in the ECS inventory database a fatal error for the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06260	The AIM QA Update service shall, upon detecting a fatal error in processing a particular granule, a. log an error and continue with the rest of the granules in the request. (or)  b. log an error and terminate the entire request (default option), depending on the processing option set via command line.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06270	The AIM QA update service shall, when processing a request directory and encountering a fatal error on a single request file, continue processing the remaining request files within the directory.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06280	The AIM QA Update service shall consider a reference to a non-existent measured parameter name a fatal error for processing the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06290	The AIM QA Update service shall be able to recover from a failure while performing or recording its QA updates such that a correct record of the QA updates can be provided without error (e.g., by restarting the utility) and without incurring a performance penalty of more than 10 minutes.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06310	The AIM QA Update service shall use a standard name for its log file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06320	The AIM QA Update service shall create a log file if the log file does not already exist.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06330	DELETED.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06340	The AIM QA Update service shall include a time stamp and the process ID in all log messages.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06350	The AIM QA Update service shall log the name of the request file at the start of processing each request file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06360	The AIM QA Update service shall log all warning and error messages encountered during the run.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06370	The AIM QA Update service shall log the time, DPL granule ID, and DPL file name for each granule that it fails to update in the Data Pool.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06380	The AIM QA Update service shall log the following information at the end of a run  a. Total number of granules requested  b. Total number of granules updated  c. Run completion or Failure status	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06390	The AIM QA Update service shall be able to operate in multiple modes concurrently.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06400	The AIM QA Update service shall record the list of granules updated along with the new QA attribute values in the Inventory database (for use by BMGT).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06410	The AIM QA Update service shall not begin processing granule updates if the XML Archive file system is unavailable.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06420	The AIM QA Update service shall be capable of applying QA updates to metadata files in the XML Archive and the DataPool at a rate no less than 15,000 granules per hour.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06430	The AIM CI shall, upon transition to version 7.21, create a new Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06440	The AIM CI shall, upon transition to version to 7.21, copy the required tables (listed in the Operational Concept of ticket DS_7E_01) from the SDSRV and STMGT databases to the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06450	The AIM CI shall, upon transition to version 7.21, copy the PSA attributes RadiometricDBVersion, GeometricDBVersion, and DAR_ID from the Science Data Server database to the Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06460	The AIM CI shall, upon transition to version 7.21, insert a definition for the XML archive into the Ingest database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06470	The AIM CI shall, upon transition to version 7.21, store the association of each ESDT using the Nominal Orbit Spatial Extent (NOSE) search method to the correct set of Orbit Polygons based upon the Platform and Instrument metadata stored in the collection metadata for the ESDT.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06480	The AIM XML Validation service shall perform consistency and correctness checks for the metadata specified in the XML file of a validation request.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06490	The AIM XML Validation service shall be delivered with an XML schema file for each of the following data types: Browse, Production History, Quality Assurance, and Delivered Algorithm Package.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06500	The AIM Validation service shall be capable of validating granule metadata stored in an XML file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06510	The AIM XML Validation service shall, when validating a descriptor, verify that all elements conform to the rules specified in the schema for descriptor files.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06520	The AIM XML Validation service shall, when validating a descriptor, return a Success result if, and only if, all elements within the received descriptor file conform to the rules in the descriptor schema.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06530	The AIM XML Validation service shall, when validating a granule metadata file, verify that all mandatory elements conform to the rules specified in the ESDT specific schema associated with the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06540	The AIM XML Validation service shall, when validating granule metadata, return a Success result if, and only if, all elements within the received granule metadata file conform to the rules in ESDT specific schema associated with the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06550	The AIM XML Validation service shall, when validating a granule metadata file, return a warning result if, after the removal of invalid optional elements from the granule metadata file, all remaining elements conform to the rules in the ESDT specific schema associated with the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06560	The AIM XML Validation service shall, when validating a granule metadata file, return a fatal error result if any errors are encountered that prevent it from validating the XML file (including failed database operations after the configured number of retries).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06570	The AIM XML Validation service shall, when validating a granule metadata file, return a failure result if, after the removal of invalid optional elements from a granule metadata file (if present), any element doesn't conform to the rules specified in the ESDT specific schema associated with the granule.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06580	The AIM XVU shall, when validating granule metadata, allow a mandatory element to be missing if the immediate parent of the element is optional and also missing (the mandatory if applicable rule).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06590	The AIM XML Validation service shall, when validating a granule metadata file, validate the values of Product Specific Attributes using the definition of the Product Specific Attribute stored in the AIM Inventory database.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06620	The AIM Validation service shall validate the Spatial metadata of granules with a spatial search type not equal to Orbit / NOSE using the Spatial Query Server COTS.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06630	The AIM Validation service shall, when validating a granule with a spatial search type equal to Orbit, consider duplicate point values within the Gpolygon elements invalid.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06640	The AIM Validation service shall, when validating a granule metadata file, use the ESDT specific schema to determine if a non-PSA element is mandatory or optional.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06650	The AIM Validation service shall, when validating a granule metadata file, treat all PSA element as optional.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06660	The AIM Validation service shall, when detecting an invalid optional element, remove the element from the granule XML metadata file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06670	The AIM Validation service shall be capable of validating an element against a fixed domain of values.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06680	The AIM Validation service shall be capable of validating an element against a numeric range of values.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06690	The AIM Validation service shall be capable of validating an element against a fixed value.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06770	The AIM Validation service shall, when validating a granule metadata file, be capable of validating that metadata elements conform to rules stated within the ECS Data Model, with the exception of the Parameter Name element within the Measured Parameter Container which shall be allowed a length of up to 80 characters (NOTE: this attribute length is specified as 40 characters in the ECS Data Model).	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06780	The XML Validation service shall return a status indicating Pass, Fail, Warning, or Fatal to the DPL Ingest CI along with a list of any validation warnings or errors found while validating the granule metadata file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06790	The AIM XML Validation service shall return a Fatal return code if it encounters a fault or unavailable resource when validating a granule XML metadata file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06800	The AIM XML Validation service shall allow for configuration, within the application configuration file, the number of times to retry a database error.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06810	The AIM XML Validation service shall be capable of processing multiple granule validation requests from the DPL Ingest service concurrently.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06820	The AIM XML Validation service shall be capable of running in multiple modes concurrently.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06830	The AIM XML  Validation service shall log all validation warning messages and error messages pertaining to the validation of metadata elements to the application log file.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-06840	The AIM XML Validation service shall log information that is sufficient to identify the granule being validated along with the time associated with each metadata validation message it logs.	
DS_7E_01	Removal of Science Data Server	no data				S-DSS-0850	The AIM XML Validation service shall validate the set of NOSE track numbers and start/end block numbers associated with a granule against the predefined orbit spatial extents defined within the AIM Inventory database for the ESDT.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-BGT-01500	The BMGT shall use the MISR science and browse linkage information maintained in the AIM inventory database when exporting relationship of MISR science granules and MISBR granules to the external metadata clearinghouse.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DPL-00300	The Data Pool Ingest service shall be able to ingest 4,072 granules (combination between MISBR, MISR Level 1 and MISR Level 2) with an approximate volume of 0.4TB and publish them in Data Pool within 6 hours.  Note : The 24-hour behavior can be extrapolated from the 6-hour run.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DPL-00310	The DPL Insert service shall use the MISR science and browse linkage information maintained in the AIM inventory database when publishing MISR science and MISBR granules in Data Pool. [The linkage relationship is captured in Data Pool only if MISR science granules and MISBR granules are in public Data Pool]	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DPL-00315	The DPL Insert service shall automatically fix the error condition caused by the overwrite of the browse representation of an existing MISBR granule (by a newer MISBR granule with the same file name and acquisition date) by replacing the DPL MISBR Browse representation and updating all its corresponding AIM and DPL science links.   [Note:  the 7.20 behavior fails the insert of the browse representation of the new MISBR granule and expects the operator to manually repair the error and re-insert the new MISBR granule.]  	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45200	The Data Pool Ingest service shall provide a DAAC configurable option to turn on/off MISR data processing functionality.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45210	The AIM Inventory Insert Service shall maintain cross-reference information between single or multiple MISR Level 1 or Level 2 science granules with an associated MISBR granule in the AIM Inventory database.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45211	The AIM Inventory Insert Service shall capture the orbit number, path number, camera id and the product version for all configured MISR ESDTs.   [Note:  the MISR ESDTs that are not Level 1, Level 2 or MISBR must be added to the existing DsMdMisrProcessingCriteria table.  This is a new 7.21 ASDC requirement added in order to support the MISR Order Tool DUE.]  	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45220	The AIM Inventory Insert Service shall link a MISBR granule with MISR Level 1 science granule(s) in the AIM inventory database based upon the following matching attributes:  Matching SP_AM_MISR_ProductVersion product specific attribute value Matching orbit number and path number Matching cameraId. the MISR Level 1 granule(s) have not yet been linked to other MISBR granule(s)i   Note :  This requirement covers the situation when the MISBR granule is ingested after ingest of its associated MISR Level 1 granule(s).	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45230	The AIM Inventory Insert Service shall link a MISR Level 1 science granule with a MISBR granule in the AIM inventory database based upon the following matching attributes:  Matching SP_AM_MISR_ProductVersion product specific attribute value Matching orbit number and path number Matching cameraId.   Note :  This requirement covers the situation when the MISR Level 1 science granule is ingested after ingest of its associated MISBR granule.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45240	The AIM Inventory Insert Service shall link a MISBR granule with MISR Level 2 science granule(s) in the AIM inventory database based upon the following matching attributes:  Matching orbit number and path number the MISBR granule has a cameraId of 'AN' (the cameraId value of the MISR Level 2 granule is irrelevant) the MISR Level 2 granule(s) have not yet been linked to other MISBR granule(s)i   Note :  This requirement covers the situation when the MISBR granule is ingested after ingest of its associated MISR Level 2 granule(s).	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45250	The AIM Inventory Insert Service shall link a MISR Level 2 science granule with a MISBR granule in the AIM inventory database based upon the following matching attributes:  Matching orbit number and path number the MISBR granule has a cameraId of 'AN', regardless of the cameraId value of the MISR Level 2 granule   Note : This requirement covers the situation when the MISR Level 2 science granule is ingested after ingest of its associated MISBR granule.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45260	The AIM Inventory Insert Service shall link MISR Level 1 or Level 2 science granules with the most recently inserted MISBR granule in the event that multiple MISBR granules are identified using the specific linkage criteria defined for each type of MISR science granule.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45270	The AIM Inventory Insert Service shall be able to process concurrent insert of MISR Level 1, Level 2 science granules and MISBR granules and create correct linkage association. [This requirement ensures that the system will be able to adequately deal with the race conditions that may occur during concurrent insert]	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45300	A transition tool shall be developed to assist ASDC transition from Release 7.20 to Release 7.21 by capturing the MISR science and MISBR linkage associations for existing data, and recording the relationships in the AIM Inventory database. The transition tool shall also capture the orbit number, path number, camera id, and the product version for all MISR ESDTs in order to support the MISR Order Tool DUE.	
DS_7E_02	Support for MISR in Release 7.21	no data				S-DSS-45305	A MISR linkage transition tool shall capture the linkage association between the existing MISR Level 1 and Level 2 science granules and MISBR granules and record them in the AIM inventory database based on the following rules:  If a linkage association between a MISR science and MISBR granule exists in Data Pool, the same association will be captured in AIM inventory database. Otherwise, a linkage association will be created based on the rules described in L4 requirements 30, 40, 50, and 60.  [This is done to ensure that the granule linkage associations captured in the AIM inventory database will be synchronized with the existing associations captured in Data Pool]	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00010	The system shall be able to document the life cycles of reported software defects.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00020	The system shall be able to store at least the following information about each defect:  unique ID, status, description, affected hardware or software, problem solution, originator, and affected baseline.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00030	The system shall provide a Linux, Windows, or Web-based graphical user interface for submitting, browsing, editing, and printing defect reports and enhancement requests	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00040	The system shall permit access by users outside the local network on which it resides.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00050	The system shall be capable of assigning life cycle states to each defect report or enhancement request.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00060	The system shall be capable of categorizing defect reports and enhancement requests at least by type, class, project, urgency and priority.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00070	The system shall be capable of reassigning defects from one project and class to another.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00080	The system shall allow administrators to configure defect report or enhancement request data fields such that data entry is required.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00090	The system shall be capable of presenting lists of valid values to users while they create or edit defect reports and enhancement requests.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00100	The system shall have a state transition tracking mechanism that administrators can configure to enforce work flow through a defect resolution process tailored to ECS.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00110	The system shall allow tailoring of workflows according to defect type and project.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00120	The system shall be customizable, allowing administrators to alter and define additional life cycle states, defect report and enhancement request attributes, data entry screens, pick lists, and event-driven actions.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00130	The system shall allow entry of a defect report by any registered user of the system [as well as non-registered users].	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00140	The system shall regulate access to screens and fields according to permissions configurable by an administrator.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00150	The system shall be capable of automatically sending, to the defect reports originator and others as may be subscribed, an e-mail message that confirms submission of a defect report and enhancement request.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00160	The system shall be capable of sending, to the defect reports originator and others as may be subscribed, an e-mail message that documents each change made to a defect report and enhancement request.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00170	The system shall be capable of creating defect reports and enhancement requests from data it receives via e-mail.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00180	The system shall be capable of importing defect reports and enhancement requests from formatted data files	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00190	The system shall be capable of exporting user-selected defect reports and enhancement requests and fields as formatted data for use with other applications such as text editors and spreadsheets.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00200	The system shall provide a capability to search for historical and current defect reports by various criteria including keyword, user identity, and defect ID.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00210	The system shall allow users to run ad hoc and pre-defined queries to retrieve user-selected defect report and enhancement request data.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00220	The system shall be capable of searching for defects relating to the same resource (e.g., equipment).	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00230	The system shall be capable of producing ad hoc and pre-defined reports containing user-selected defect report and enhancement request data.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00240	The system shall produce reports, for users system-wide, which list the identity and disposition of defects against ECS baselines	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00250	The system shall make available, for users system-wide, the assignments, schedules, and status of tasks for correcting ECS defects.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00260	The system shall allow users to direct output of queries and reports to screen, file, or printer.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00270	The system shall maintain a historical record of each change made to a defect report and enhancement request, identifying the author, date/time, and description (or field name) of the change.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00280	The system shall be accompanied by documentation, to include user and administrator guides and installation instructions.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00290	The system shall be capable of forwarding defect reports from one collection to another to facilitate problem escalation.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00300	The system shall provide an API that supports entry of defect reports and enhancement requests by other applications.	
DT_72_01	Consolidated Defect Tracking System	no data				C-DTS-00310	The system shall allow sites to specify notification and escalation rules.	
EN_5B_01	Generate reports using IQ/SQR Cancelled per Contract Mod 10	C6003DD	IQ/SQR	COTS Report Writer deployment and configuration	Sep 27 1999 12:00AM	0-000-00001	Not applicable.  This L3 (SMC-8300) is being fulfilled completely by COTS. There are no new custom developed/integrated components required for fulfilling the criteria.	
EN_5X_01	PDS Distribution of New Media Types	no data				0-000-00004	L3 mapped directly to verification criteria. L4's are not needed to decompose PDS L3s into subsystem components. PDS L3's will be verified by inspection of the PDS systems operations. 	
EN_6A_01	Tape Ingest of IGS Browse data and Metadata Cancelled per Contract Mod 25	10023DT	IGS Browse Processing	The ability to ingest L7 IGS browse data via tape.	Jan 24 2000 12:00AM	S-DSS-06720	The SDSRV CI shall provide an automated procedure to perform insert processing of Landsat IGS Science data:    a. As a regular Science granule insert when Browse data is not provided.  b. As an integrated Browse insert when Science granule and Browse data is provided and the Science granule does not previously exist in the SDSRV Inventory.  c. As an update to the Science granule metadata and an insert of the Browse data when both Science and Browse are provided and the Browse does not previously exist.  d. Only an exact match of the following attributes will determine 'prior existence' of a Science granule within the SDSRV Inventory - Station ID, Starting path, and Subinterval Start time where a match is found if times match after truncating to the minute level.	
EN_6A_01	Tape Ingest of IGS Browse data and Metadata Cancelled per Contract Mod 25	10023IN	IGS Browse Processing	The ability to ingest L7 IGS browse data via tape.	Jan 24 2000 12:00AM	S-INS-00787	The INGST CI shall ingest Data, provided by the Landsat 7 International Ground Stations (IGSs), into the EDC DAAC on 8 mm cartridge tape.	
EN_6A_01	Tape Ingest of IGS Browse data and Metadata Cancelled per Contract Mod 25	10023IN	IGS Browse Processing	The ability to ingest L7 IGS browse data via tape.	Jan 24 2000 12:00AM	S-INS-00788	The INGST CI shall ingest browse and associated Metadata 0 data, provided by the Landsat 7 International Ground Stations (IGSs), into the EDC DAAC from 8 mm cartridge tape.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30431	The GTWAY CI shall always return a configurable set of attributes in the inventory search results that are required by the V0 client.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30432	The GTWAY CI shall accept requests for Inventory Search Results without spatial or temporal attributes using V0 protocols defined in the V0/ECS ICD.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30433	The GTWAY CI shall process requests for Inventory Search Requests against ECS collections containing granules without spatial or temporal metadata.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30434	The GTWAY CI shall accept requests specifying the granule level attributes to be included in the Inventory Search Results using V0 protocols defined in the V0/ECS ICD.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30435	The GTWAY CI shall accept requests specifying that the DEFAULT set of granule level attributes shall be included in the Inventory Search Results using V0 protocols defined in the V0/ECS ICD.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30436	The GTWAY CI shall accept requests specifying that the FULL set of granule level attributes shall be included in the Inventory Search Results using V0 protocols defined in the V0/ECS ICD.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30437	The GTWAY CI shall include the V0 core metadata in a search result to the extent that they are available and regardless of what other attribute selections the user made.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30438	The GTWAY CI shall process requests specifying that the DEFAULT set of granule level attributes shall be included in the Inventory Search Results.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30439	The GTWAY CI shall allow DAAC operators to configure the granule level attributes included in the default list.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30440	The GTWAY CI shall process requests specifying that the FULL set of granule level attributes shall be included in the Inventory Search Results. 	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30441	The GTWAY CI shall process requests specifying the set of granule level attributes that shall be included in the Inventory Search Results.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30442	The GTWAY CI shall process Inventory Search Requests against non-science collections.	
EN_6A_02	V0 Gateway Enhancements (non-science collections; result set attributes)	12002DM	V0 Gateway Enhancements (Access To Non-Science Collections)	Support the ability of the EDG client to search and order non-science collections; make available granules without spatial/temporal attributes as part of a search results set, or as the only results set returned; allow user to limit the attributes returned in a results set to a user-specified set of granule level attributes.	Feb 23 2000 12:00AM	S-DMS-30443	The GTWAY CI shall submit product orders for non-science data to the SDSRV CI.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DMS-31060	The GTWAY CI shall return an error to the user when it discovers that the granule identified in a user request does not exist in the SDSRV inventory. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01500	The SDSRV CI shall provide a command line utility for the deletion of granules.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01505	The SDSRV CI shall permit an ECS operator to perform granule deletions while it performs other requests concurrently. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01510	The SDSRV CI shall permit an ECS operator to select, via command line parameters, products for deletion by providing either of the following:  1. ESDT short name, ESDT version, and granule temporal coverage or granule insert time range; or  2. the name of a granule deletion input file listing the granules to be deleted.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01515	The SDSRV CI shall be able to process a granule deletion input file that contains either of the following formatted as one input line per granule:    1. ESDT short name, version and local granule Ids; or  2. SDSRV granule IDs(geoIDs).	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01520	The SDSRV CI shall permit an ECS operator to include the inventory metadata in the deletion, or exclude the metadata from the deletion (i.e., cause a physical delete or only a delete from archive) via a command line parameter. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01525	The SDSRV CI shall display to the ECS operator the number of granules which have been selected for deletion before performing the deletion. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01530	The SDSRV CI shall, by default, prompt the operator for confirmation after displaying the number of granules selected for deletion prior to performing the deletion. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01535	The SDSRV CI shall allow the operator to request suppression of confirmation prompts via a command line parameter. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01537	The SDSRV CI shall allow the operator to request via a command line parameter that the following information be listed for each of the selected granules, prior to the display of the total number of granules selected for deletion, and on a separate line for each:    1. SDSRV granule ID (geoIDs)  2. Local granule ID (if non-NULL)  	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01540	The SDSRV CI shall perform the requested granule deletion immediately after operator confirmation. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01542	The SDSRV CI shall make physically deleted granules inaccessible for normal SDSRV access commands.     	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01545	The SDSRV CI shall, by default, delete the BROWSE, QA, and PH granules referenced by a granule when performing a physical delete, if they are not referenced by any other granule. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01546	The SDSRV CI shall permit an ECS operator to suppress deletion of the BROWSE, QA, PH via command line option.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01550	The SDSRV CI shall, by default, not physically delete granules that are being referenced as inputs by other granules. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01552	The SDSRV CI shall permit an ECS operator to request via command line option that granules be included in a physical delete even if they are still referenced as inputs by other granules.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01555	The SDSRV CI shall allow the operator to specify on the command line the name of a separate granule deletion log file that is accessible to the deletion utility. 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01556	The SDSRV CI shall append output to the granule deletion log file if it already exists, or create it if it does not.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01560	The SDSRV CI shall log all deletion requests in the application log and in a separate granule deletion log file specified by the operator.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01565	The SDSRV CI shall log all delete errors in the application log and in a separate granule deletion log file specified by the operator.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01570	The SDSRV CI shall log for each deleted science granule:  1. Date and time  2. the (Unix- or MSS-) ID of the requesting user  3. the ESDT short name,  ESDT version and granule ID of the deleted granule  	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01575	The SDSRV CI shall log for each non-science granule being deleted:  1. Date and time  2. the (Unix- or MSS-) ID of the requesting user   3. the ESDT short name, ESDT version and granule ID of the deleted granule  	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01577	The SDSRV CI shall include in the log for each granule deletion error:     1. Date and time  2. the (Unix- or MSS-) ID of the requesting user   3. the ESDT short name, ESDT version and granule ID of the affected granule  4. nature of the error  	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01580	The SDSRV CI shall perform delete operations such that they can be restarted and completed successfully if they are interrupted by a fault.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01582	The SDSRV shall handle situations where it encounters an invalid granule or archive file reference, e.g.,  because a concurrent or previous deletion removed the granule from the inventory and/or archive, in a graceful manner by:    1. rejecting requests that reference non-existent granules; or  2. logging an error and terminating a request that encounters an invalid granule reference with an appropriate fatal response, if it is synchronous; or  3. logging an error and continuing a request that encounters an invalid granule reference for any other granules 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01585	The SDSRV CI shall provide a 'deletion cleanup' command line utility.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01588	The SDSRV CI deletion cleanup utility shall allow an operator to remove the inventory entries for granules that have been physically deleted and make their files as well as the files of granules that have been deleted from the archive eligible for removal from the archive.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01590	The SDSRV CI deletion cleanup utility shall require an ECS operator to specify via command line parameter a deletion lag time in days, including a lag time of 0 (zero). 	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01595	The SDSRV CI shall remove the inventory entries of granules whose physical deletion occurred before the lag time, and not remove the inventory entries of granules whose deletion occurred after the lag time.  	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01600	The SDSRV CI shall provide the list of files eligible for removal from the archive to the STMGT CI.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01603	The SDSRV CI shall include in the list of files eligible for removal from the archive the following information:  1. ESDT shortname  2. ESDT version ID  3. granule insert time  4. internal file name  5. effective date of deletion  	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01605	The SDSRV CI shall include in the list of files eligible for removal from the archive:  1. the files of granules whose inventory entries are being removed  2. the files of granules whose 'deletion from archive' occurred prior to the lag time   	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01610	The SDSRV CI shall create a separate error log recording all errors that occur while attempting to remove inventory entries for deleted granules, and write that error log to a new file or append it to an existing file whose name is specified by the operator via a command line parameter.    	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01615	The SDSRV CI shall display the number of granules whose inventory entries will be removed and the number of granules whose files will be made eligible for deletion from the archive, and then prompt the operator for confirmation before performing the removal.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-01620	The SDSRV CI shall be capable of recovering from errors that may occur while executing the deletion cleanup utility such that inventory entries or files for deleted granules can be correctly processed by subsequent executions of the utility, and incompletely processed inventory entries (if any) do not cause ECS faults.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-20700	The STMGT CI shall accept the list of files eligible for deletion from the SDSRV CI.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-20710	The STMGT CI shall provide an operator interface to remove the files that are eligible for deletion from the archive directories.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-20720	The STMGT CI shall display the number of files eligible for deletion from the archive to the operator, and then prompt the operator for confirmation before performing the removal.	
EN_6A_04	Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-20730	The STMGT CI shall allow operators to reclaim tape space that has been freed up due to the removal of files from the archive directory.	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DMS-33040	The GTWAY CI shall send a chunk size, as the number of data granules per chunk, to the SDSRV CI to be used in packaging the inventory search results. 	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DMS-33041	The GTWAY CI shall return an error message to the V0 EDG in V0 protocols upon failure in the SDSRV CI in providing the inventory search results.	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06750	The SDSRV CI shall provide a capability to return the inventory search results in one or more data chunks of a specified size.	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06752	The SDSRV CI shall provide a capability to accept a chunk size to be used in packaging the inventory search results into data chunks.	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06754	The chunk size used by the SDSRV CI in packaging the inventory search results shall be specified as the number of data granules per chunk. 	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06756	The SDSRV CI shall package the inventory search results using the default chunk size or the chunk size provided by the client, whichever is smaller. 	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06758	The SDSRV CI shall use a default chunk size in packaging the inventory search results if no chunk size is provided by the client.	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06760	The SDSRV CI shall allow the default chunk size to be a configurable parameter. 	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06764	In response to a request by a client application for the metadata of the first granule not contained in the current data chunk, the SDSRV CI shall return the next chunk of inventory search results populated with metadata.	
EN_6B_03	Results Set Chunking	12521DT	Results Set Chunking	SDSRV capability to return search results to the V0 Gateway in parts to improve overall throughput and reduce amount of time needed for client to receive some of the search results.	Jul 25 2000 12:00AM	S-DSS-06766	The SDSRV CI shall provide a capability to turn off inventory result-set chunking.	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022DT	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DMS-24080	The DDICT CI shall provide a capability to insert into the data dictionary database, the following optional attributes as part of the collection level metadata:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.     	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022DT	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DMS-24085	The DDICT CI shall provide a capability to update the following optional attributes as part of the collection level metadata in the data dictionary database:     (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.     	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022DT	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DMS-24090	The GTWAY CI shall provide a capability to retrieve the following optional attributes as part of the collection level metadata from the data dictionary database:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.      	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022DT	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DMS-24095	The GTWAY CI shall send the inventory search results to the Version 0 EDG Client. The search results shall include product information as well as the following optional information, if available, for the data set:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.     (6) DAAC-configurable disclaimer comment embedded by the GTWAY CI.    	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022IFF	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DSS-01625	The SDSRV CI shall provide a capability to insert into the inventory database, the following optional attributes as part of the collection level metadata:    (1) user's guide URL    (2) user's guide URL comment     (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.     .   	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022IFF	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DSS-01630	The SDSRV CI shall provide a capability to update the following optional attributes as part of the collection level metadata in the inventory database:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.     	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022IFF	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DSS-01635	The SDSRV CI shall provide a capability to retrieve the following optional attributes as part of the collection level metadata in the inventory database:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.     	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022IFF	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DSS-01640	The SDSRV CI shall send, as part of an insert collection to the DDICT CI, the following optional collection level metadata attributes:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL.  	
EN_BP_01	URLs for Data Set Disclaimer, User Guide, and Miscellaneous Information	02022IFF	URLs for data set user's guide, miscellaneous  information, and data set disclaimer	Capability to provide to V0 EDG client, the URL for data set user's guide and the associated comment for hypertext link;  the URL for miscellaneous data set specific information, and the associated comment for hypertext link; and the URL for the data set disclaimer and the associated comment, in response to an inventory search request.	May 24 2000 12:00AM	S-DSS-01645	The SDSRV CI shall send, as part of an update collection to the DDICT CI, the following optional collection level metadata attributes:    (1) user's guide URL    (2) user's guide URL comment    (3) miscellaneous information URL    (4) miscellaneous information URL comment    (5) disclaimer URL  	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75400	In response to a user registration request, the MCI user registration service shall return a status indicator using ECS protocols indicating success or error conditions.           	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75405	In response to a user password change request, the MCI user registration service shall return a status indicator using ECS protocols indicating success or error conditions.              	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75410	Upon successful user registration, the MCI user registration service shall trigger the transmittal of an e-mail message to the user indicating the request for user registration with basic search/order privileges has been successfully completed, and  they should contact their Home DAAC if they need additional data access privileges.                	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75415	Upon successful user registration, the MCI user registration service shall create a new user account with basic search and order privileges.            	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75420	Upon successful completion of granting additional data access privileges, the MCI user registration service shall trigger the transmittal of an e-mail message to the user, confirming the additional data access privileges.               	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75425	Upon successful completion of a user password reset, the MCI user registration service shall trigger the transmittal of an e-mail message to the user, confirming the password has been reset.           	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75430	The e-mail message, triggered by the MCI user registration service at the successful completion of a user password reset, shall contain a suggestion to the user to change their password as soon as possible for security reasons.      	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	C-MSS-75435	The MCI shall provide a capability to embed a DAAC-specific configurable preamble into the e-mail messages sent to the user.  	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-CLS-00500	The DESKT CI shall provide a capability to accept the ECS user registration message using protocols as defined in the ECS/V0 ICD.      	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-CLS-00505	The DESKT CI shall provide a capability to accept the ECS user password change message using protocols as defined in the ECS/V0 ICD.        	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-CLS-00510	The DESKT CI shall send the user registration message to the MCI user registration service using ECS protocols.      	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-CLS-00515	The DESKT CI shall send the user password change message to the MCI user registration service using ECS protocols.        	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-CLS-00520	The DESKT CI shall send the user registration result to the V0 EDG client using protocols as defined in the ECS/V0 ICD.      	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-CLS-00525	The DESKT CI shall send the user password change result to the V0 EDG client using protocols as defined in the ECS/V0 ICD.        	
EN_BP_02	Seamless User Registration Between ECS and V0	04507CL	Seamless User Interface	Single user interface and login step for both the EDG and ECS.	Jun 26 2000 12:00AM	S-DMS-24098	Upon successful validation of a product request, the GTWAY CI shall send a request to the MCI user registration service to update the user profiles using the information provided in the request.        	
EN_BP_02	Seamless User Registration Between ECS and V0	no data				C-MSS-75440	The MSS accountability management service shall provide the capability to maintain the following information for each registered user:          a.  Name of product shipping contact    b. Organization of product shipping contact    c.  Title of product shipping contact    d.  Name of billing contact    e.  Organization of billing contact    f.  Title of billing contact   	
EN_BP_02	Seamless User Registration Between ECS and V0	no data				C-MSS-75445	The MSS accountability management GUI shall provide the capability for an operator to maintain the following information for each registered user:     a.  Name of product shipping contact    b. Organization of product shipping contact    c.  Title of product shipping contact    d.  Name of billing contact    e.  Organization of billing contact    f.  Title of billing contact  	
EN_BP_03	Support for AIRS Summary Browse Products	12532DT	Support for AIRS Summary Browse	Provide a custom DLL for the integrated browse service for AIRS Summary Browse Products.	Dec  4 2000 12:00AM	S-DSS-07105	The SDSRV CI shall provide the capability for the integrated browse service of an AIRS Summary Browse Product to retrieve the SCIENCE granule containing the product itself. 	
ES_SY_01	External Subsetter Support	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75045	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	
ES_SY_01	External Subsetter Support	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75047	The MSS accountability management service shall support the following order/request states:  a. Pending  b. Operator Intervention  c. Staging  d. Transferring   e. Waiting for Shipment    f. Shipped  g. Aborted  h. Canceled  i. Terminated  j. Subsetting  k. Subsetting Staging  l. Prep for Distribution  m. SDSRV Staging  n. Queued  o. Waiting for data  p. Waiting for processing  q. Being processed  r. Completed processing  s. Expired  t. Awaiting L1B  u. L1B received  v. Null	
ES_SY_01	External Subsetter Support	no data				C-CSS-30700	The Registry Service shall be capable of storing subsetting options for any ECS collection.	
ES_SY_01	External Subsetter Support	no data				C-CSS-30710	The Registry Service shall be capable of storing subsetting options for ECS collections that support to the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001 and which conform to the Interface Control Document Between EOSDIS Core Systems (ECS) and the Version 0 System for Interoperability', ESDIS document number 505-41-30.	
ES_SY_01	External Subsetter Support	no data				C-CSS-30720	The Registry Service shall provide the capability to update subsetting options for an ECS Collection specified by shortname/version.	
ES_SY_01	External Subsetter Support	no data				C-CSS-30730	The Registry Service shall provide capabilities to retrieve subsetting options including subsetter location information for an ECS Collection by ESDT shortname/version. 	
ES_SY_01	External Subsetter Support	no data				C-CSS-30740	The Registry Service shall be capable of storing location information for each External Subsetter.	
ES_SY_01	External Subsetter Support	no data				C-CSS-30750	The Registry Service shall provide the capability to update location information for a specified external subsetter.	
ES_SY_01	External Subsetter Support	no data				C-CSS-30760	The Registry Service shall be capable of supporting 3 or more External Subsetters.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30368	The GTWAY CI shall have the capability to process V0 Inventory Search Requests.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30375	The GTWAY CI shall send inventory search results to the Version 0 Client using Version 0 protocols.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30392	The GTWAY CI shall receive inventory search requests from the Version 0 Client using Version 0 protocols.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30404	The GTWAY CI shall have the capability to process V0 Product Requests.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30406	The GTWAY CI shall receive Product Requests from the Version 0 IMS using Version 0 protocols.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30408	The GTWAY CI shall have the capability to send Product Request acknowledgements to the V0 Client using Version 0 system protocols.	
ES_SY_01	External Subsetter Support	no data				S-DMS-30890	The GTWAY CI shall  support multiple concurrent requests.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33300	The GTWAY CI shall retrieve subset options, including subsetter location information, from the Registry by shortname/version.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33320	The GTWAY CI shall construct inventory search result messages that include subset options constructed from the External Subsetter options for that shortname/version.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33330	The GTWAY CI shall construct subset options that contain references to metadata containing data set specific temporal extents. 	
ES_SY_01	External Subsetter Support	no data				S-DMS-33340	The GTWAY CI shall construct subset options that contain references to metadata containing data set specific spatial extents. 	
ES_SY_01	External Subsetter Support	no data				S-DMS-33350	The GTWAY CI shall process the line items of a Product Request that contain subset specifications to determine which entity, External Subsetter or SDSRV, the line item should be directed to.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33360	The GTWAY CI shall generate a new product request messages for each MSS request pertaining to an external subsetter.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33370	The GTWAY CI shall generate new MSS request objects consisting of a grouping of line items based on the following rules:    a.)The have a common destination , and  b.)They have common media options (Media Type, Media Format, Specialized            criteria), and  c.)They have common subset options.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33380	The GTWAY CI shall respond to a product request message in which subsetting is requested (except for Landsat 7 product subsetting) and physical media distribution is also requested with a product result message indicating product request message failure.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33390	The GTWAY CI shall assign the initial value of  'NULL' to the MSS request for subsetting product requests. 	
ES_SY_01	External Subsetter Support	no data				S-DMS-33400	The GTWAY CI shall include the MSS orderID/requestID in the product request message sent to the external subsetter.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33410	The GTWAY CI shall provide subsetting product request messages from users to External Subsetter systems in conformance with protocols defined 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33420	The GTWAY CI shall interface with the MSS Order server to update the request status with information returned by the External Subsetter in the product result message, translating status codes in the product result message as indicated in the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33430	The GTWAY CI shall consolidate into a single order status the statuses received in response to one or more requests that have been sent to ECS services, including external subsetters.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33440	The GTWAY CI shall provide the capability to receive Product Requests from External Subsetter systems, in conformance with protocols defined in 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33450	The GTWAY CI shall create an MSS Order and request object for Product Request submitted by External Subsetter.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33460	The GTWAY CI shall provide the capability to receive order status update messages from an External Subsetter system for a specified MSS requestID, in conformance with protocols defined in the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33470	The GTWAY CI shall interface with the MSS Order server to update the status associated with a specified MSS requestID in response to a corresponding order status update message from an External Subsetter system.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33480	The GTWAY CI shall send a order status acknowledgment message to the External Subsetter reflecting the success or failure of the requested order status update, in conformance with protocols defined in the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DMS-33490	The GTWAY CI shall be able to interface with three or more external subsetters. 	
ES_SY_01	External Subsetter Support	no data				S-DSS-31600	The External Product Dispatcher (EPD) shall be able to receive external subsetter product distribution requests from external subsetters which conform with the procedures defined in the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31610	The EPD shall poll configured directories to identify and retrieve product delivery record  (PDR) messages from external subsetters.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31620	The EPD shall validate the contents of PDR messages, and locate and confirm the existence of the files identified in the PDR in conformance with the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31625	The EPD shall validate the UserID and RequestID contained in the Product Request file.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31630	The EPD shall fail an external subsetter product distribution request if a product request file is not identified by the PDR received from the external subsetter or the file is not accessible for retrieval.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31640	The EPD shall construct a distribution request message for the external subsetter products identified in the PDR, using distribution information contained in the product request file, in conformance with the protocols defined in the 'Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs', ECS Project document number 209-CD-036-001.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31650	The EPD shall transfer distribution request messages via the DDIST Command Line Interface (DCLI) to DDIST for the distribution of external subsetter products.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31660	The EPD shall access MSS order tracking data to determine the status of orders that correspond to distribution requests submitted to DDIST by EPD.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31670	The EPD shall delete files received from external subsetters when the MSS order status for the distribution request corresponding to those files is 'Shipped'.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31680	The EPD shall be capable of supporting 3 or more External Subsetters concurrently to receive external subsetter product distribution requests.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31690	The EPD shall resubmit a distribution request a configurable number of times at a configurable interval if the DCLI returns a status indicating that the request has failed with a retryable error, and will fail the request if a non-retryable error is returned from DCLI.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31700	The EPD shall log all distribution requests submitted to DCLI.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31710	The EPD shall log all distribution requests status messages received from the DLCI, including successful, failed, or failed with retryable errors.	
ES_SY_01	External Subsetter Support	no data				S-DSS-31720	The EPD shall, if the validation fails for the information used from the Product Request File in generating the distribution request, fail the EPD request processing, log the failure to the EPD log indicating the type of error, and update the MSS status for the request to 'Operator Intervention'.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30140	The Process Framework Configuration File mechanism shall fetch parameters from the Registry Service.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30150	The Process Framework Configuration File mechanism shall read parameters from a .CFG file if present, otherwise parameters will be read from the Registry.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30400	The Registry Service shall maintain a collection of attribute-value pairs.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30410	The Registry Service shall support attributes of a hierarchical nature.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30420	The Registry Service shall allow a list of values to be associated with an attribute.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30430	The Registry Service shall support the string data type for values.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30440	The Registry Service shall support  multiple labeled Attribute Trees.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30450	The Registry Service shall allow a new attribute to be added to an Attribute Tree.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30460	The Registry Service shall allow a single mode to be associated with an Attribute Tree.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30470	The Registry Service shall allow an Attribute Tree to be copied to create a new Attribute Tree.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30480	The Registry Service shall provide access to the Registry via a mode-specific Registry Server.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30490	The Registry Service database shall be regularly backed up to disk and, in the event of its becoming corrupted, be able to be restored from that disk.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30495	The Registry Service shall allow multiple Registry Servers to run in a mode to provide redundancy of the Registry Service.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30510	The Registry Service shall allow a description to be associated with each attribute.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30520	The Registry Service shall allow a change description to be associated with each value. 	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30530	The Registry Service maintenance shall be performed via a GUI which communicates directly with the Registry database.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30540	The Registry Service shall allow an application to obtain the value or values for an attribute by supplying the attribute path.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30550	The Registry Service shall allow all attributes to be retrieved in a subtree by specifying a wildcard character as the last element in a path. 	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30560	The Registry shall allow indirect specification of a value by specifying an Attribute Path prefixed with an @ as the value of an attribute.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30570	The Registry Server shall accept the Registry Database SQL server name, username, password, and mode at startup.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30580	The Registry Service shall allow subtrees and individual attributes to be marked as privileged.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30590	The Registry Service shall have the capability to support multiple drops concurrently.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30600	The Registry Service shall allow any subtree of an Attribute Tree to be moved to another location within the same or another Attribute Tree.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30610	The Registry Service shall allow any tree node or attribute within an Attribute Tree to be renamed.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30620	The Registry Service shall allow any subtree of an Attribute Tree to be deleted.	
HA_5B_01	Configuration Registry	N5505ID	Configuration registry Database	Replacement of the custom configuration files with a config registry database (NCR 21239)	Sep 27 1999 12:00AM	C-CSS-30630	The Registry Service shall allow any subtree of an Attribute Tree to be replicated to another location within the same or another Attribute Tree.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00020	The HDF-EOS Format Conversion Tool shall be operable on an SGI IRIX 6.5 operating system.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00040	The HDF-EOS Format Conversion Tool shall allow HDF-EOS grid data to be converted to GeoTiff format, in accordance with the format definition in the GeoTIFF Revision 1.0 Specification (see www.remotesensing.org/geotiff/geotiff.html).	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00060	The HDF-EOS Format Conversion Tool shall allow HDF-EOS grid data to be converted to generic binary format, with an ASCII header, in accordance with the binary format defined in Appendix   of the HDF-EOS Format Conversion Tool User's Guide.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00065	When scaling factors are present in the HDF-EOS files, the HDF-EOS Format Conversion Tool shall include them in the output ASCII header file associated with generic binary output.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00070	The HDF-EOS Format Conversion Tool shall allow an HDF-EOS swath object to be converted to HDF-EOS grid format in the HDF-EOS Geographic projection, as defined in 'HDF-EOS Library Users Guide Volume 1 (170-TP-600)'.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00080	The HDF-EOS Format Conversion Tool shall allow HDF-EOS grid objects to be reprojected to the Universal Transverse Mercator (UTM) projection.  (as described in  U.S. Geological Survey Professional Paper 1395, 'Map Projections--A Working Manual',Snyder, John P.)	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00090	The HDF-EOS Format Conversion Tool shall allow HDF-EOS grid objects to be reprojected to the HDF-EOS Geographic projection, as defined in 'HDF-EOS Library Users Guide Volume 1 (170-TP-600)'.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00100	The HDF-EOS Format Conversion Tool shall allow HDF-EOS grid objects to be reprojected to the Space Oblique Mercator (SOM) projection. (as described in  U.S. Geological Survey Professional Paper 1395, 'Map Projections--A Working Manual',Snyder, John P.)	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00110	The HDF-EOS Format Conversion Tool shall allow HDF-EOS grid objects to be reprojected to a Polar Stereographic projection. (as described in  U.S. Geological Survey Professional Paper 1395, 'Map Projections--A Working Manual',Snyder, John P.)	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00120	The HDF-EOS Format Conversion Tool shall allow output data to be back-projected into its original projection to facilitate pixel by pixel error analysis and statistical summaries	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00130	The HDF-EOS Format Conversion Tool shall allow a user to subset an HDF-EOS swath object spatially, by specifying one of the following criteria:    a. LLBOX  	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00140	The HDF-EOS Format Conversion Tool shall allow a user to subset an HDF-EOS grid object spatially, by specifying one of the following criteria:    a. LLBOX	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00145	When spatially subsetting an HDF-EOS swath or grid object, the HDF-EOS Format Conversion Tool shall preserve the original ECS core attributes from the HDF-EOS input file  in the output file, and amend the values of the attributes as appropriate to reflect output file content. 	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00150	It is desirable that the HDF-EOS Format Conversion Tool allow a user to stitch together two or more HDF-EOS swathobjects, by track parameter (e.g., latitude).	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00160	It is desirable that the HDF-EOS Format Conversion Tool allow a user to stitch together two or more ASTER or MODIS HDF-EOS grid objects.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00165	It is desirable that the HDF-EOS Format Conversion Tool allow a user to spatially subset an output file containing stitched HDF-EOS objects.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00170	The HDF-EOS Format Conversion Tool shall be able to be invoked from a command line interface.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00180	The HDF-EOS Format Conversion Tool command line interface shall allow the user to specify:    a.the name of the HDF-EOS input file or files  b.the name of the object in the HDF-EOS input file on which to operate  c.the name of the output file  d.the location of the output file  e.the output file data format (GeoTiff, binary, HDF-EOS grid)  f.the output file data projection (if applicable)  g.the spatial subsetting parameters for the input file (if applicable)  h.the stitching specifications for the input files (if applicable)	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00190	The HDF-EOS Format Conversion Tool shall be downloadable to a user's workstation via ftp.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00200	The HDF-EOS Format Conversion Tool shall be able to be run via a web-based GUI.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00210	The HDF-EOS Format Conversion Tool web-based GUI shall provide a Help capability which allows a user to understand how to use the tool without reference to other documentation.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00220	The HDF-EOS Format Conversion Tool GUI shall allow the user to enter or choose:    a. the name of the HDF-EOS input file or files  b. the name of the object in the HDF-EOS input file on which to operate  c. the name of the output file  d. the location of the output file  e. the output file data format (GeoTiff, binary, HDF-EOS grid)  f. the output file data projection (if applicable)  g. the spatial subsetting parameters for the input file (if applicable)  h. the stitching specifications for the input files (if applicable)a. 	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00230	The HDF-EOS Format Conversion Tool GUI shall allow the user to browse a local file system and select input files from that file system.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00235	The HDF-EOS Format Conversion Tool GUI shall allow the user to configure the name of a default local file system.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00240	The HDF-EOS Format Conversion Tool GUI shall allow the user to list and view all objects (metadata in text attributes, local attributes, palettes, data tables and arrays, etc.) within HDF-EOS granules.	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00250	When converting an HDF-EOS swath object to an HDF-EOS grid object, the HDF-EOS Format Conversion Tool shall preserve the original ECS core attributes from the HDF-EOS input file  in the output file, and amend the values of the attributes as appropriate to reflect output file content. 	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00260	When reprojecting HDF-EOS grid objects, the HDF-EOS Format Conversion Tool shall allow a user to specify the resolution (i.e., grid dimensions) of the output file. 	
HD_SY_01	HDF-EOS Format Conversion Tool	no data				S-HEG-00280	The HDF-EOS Format Conversion Tool shall allow the user to compare two input files and write pixel by pixel differences to a user-specifiedoutput file.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00010	The ECS Bulk Metadata Generator Tool (BMGT) shall export metadata for an operator-configurable set of ESDT versions.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00020	The BMGT shall allow the operator to specify a date range to be processed.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00030	The BMGT shall allow the operator to specify a default date range of the previous day.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00040	The BMGT may be executed as a cron job.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00050	The BMGT may be executed at the discretion of the operator.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00060	The BMGT shall run in accordance to ECS mode conventions.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00070	The BMGT shall allow the operator to specify mappings between ESDT versions and groups.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00080	The BMGT shall allow the operator to specify a destination directory for the products that are created.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00090	The BMGT shall generate a Product Delivery Record (PDR) file to be used for the ingest of products generated via a single execution. The PDR file shall be generated in accordance to the ECS SIPS interface (423-41-57 section 4.5.3).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00100	The BMGT shall allow the operator to specify the name of a PDR file that conforms to the SIPS naming convention (423-41-57 section 4.5.2).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00110	The BMGT shall incur no more than 10 % performance degradation on the ECS Science Data Server Database under nominal operation load during data extraction.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00120	The ECS shall provide an ESDT (ECSMETC) that shall store products that contain an XML representation of ECS collection level metadata and the packaging options that may be used when ordering products from each collection.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00130	ECSMETC granules shall be created by data group.  Collection level metadata shall be grouped by instrument and mission. Metadata related to the MODIS instrument shall be grouped by mission and major discipline.   	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00140	Data group names and content  shall be configurable by the operator.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00150	The BMGT shall generate collection level metadata based on the temporal constraint.  Any collections that have been inserted,  or updated during that constraint shall be added to the product subject to all other specified constraints.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00160	The BMGT shall generate collection level metadata based on an ESDT version constraint. Any collections that apply to that constraint shall be added to the product subject to all other specified constraints.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00170	The BMGT shall generate collection level metadata for a specific collection only once per execution.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00180	Each ECSMETC product shall consist of a single XML file. There shall be one granule for each group.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00190	Each ECSMETC granule shall contain the metadata specified in document 170-WP-023-001 (section 2.2.1).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00200	The file naming convention of the ECSMETC XML files shall be in accordance of document 170-WP-023-001 (Section 2.2.2 Product Specification.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00210	Each ECSMETC product XML file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00220	The BMGT shall extract collection level metadata from the ECS Science Data Server Database at a rate of at least  25,000  collections per hour.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00230	The BMGT shall convert extracted collection level metadata to XML format at a rate of at least  25,000  collections per hour.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00240	The ECS shall provide an ESDT (ECSMETG) that shall store products that contain an XML representation of ECS granule level metadata.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00250	ECSMETG granules shall be created by data group.  Granule metadata shall be grouped by instrument and mission. Metadata related to the MODIS instrument shall be grouped by mission and major discipline. 	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00260	The BMGT shall generate products based on a temporal constraint.  Any granules that have been inserted, updated or deleted during that constraint shall be added to the product subject to all other specified constraints.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00270	The BMGT shall generate granule level metadata based on an ESDT version constraint. Any granules that apply to that constraint shall be added to the product subject to all other specified constraints.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00280	The BMGT shall generate granule level metadata for a specific granule only once per execution.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00290	The BMGT shall not generate granule level metadata for a granule that was both inserted and deleted within the temporal constraint.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00300	The BMGT shall generate a subset of granule level metadata for granules that have only been deleted within the temporal constraint. The subset is defined by the granule identifier and the deletion time.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00310	Each ECSMETG product shall consist of a single XML file. There shall be one product for each group.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00320	Each ECSMETG granule shall contain the metadata specified in document 170-WP-023-001 (section 2.2.1).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00330	The file naming convention of the ECSMETG XML files shall be in accordance of document 170-WP-023-001 (Section 2.2.2 Product Specification.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00340	Each ECSMETG product XML file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00350	The BMGT shall extract granule level metadata from the ECS Science Data Server Database at a rate of at least 25,000 granules per hour.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00360	The BMGT shall convert extracted granule level metadata to XML format at a rate of at least 25,000 granules per hour.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00370	ECS shall provide an ESDT (ECSMETV) that shall store products that contain an XML representation of ECS collection and granule valid values.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00380	The BMGT shall generate a single ECSMETV product per execution if one or more ECSMETC products were generated during that execution.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00390	Each ECSMETV product shall consist of a single XML file.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00400	Each ECSMETV granule shall contain the metadata specified in document 170-WP-023-001 (section 2.2.1).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00410	The file naming convention of the ECSMETV product XML files shall be in accordance of document 170-WP-023-001 ( Section 2.2.2 Product Specification).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00420	Each ECSMETV product XML file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00430	The ECS shall provide an ESDT (ECSBBR) that shall store products that contain an XML representation of ECS Bulk Browse products.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00440	The BMGT shall generate bulk browse metadata based on a temporal constraint. Any browse products that have been inserted, updated or deleted during that constraint shall be added to the product subject to all other specified constraints.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00450	The BMGT shall generate bulk browse metadata for a specific browse product only once per execution.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00460	The BMGT shall not generate bulk browse metadata for a browse product that was both inserted and deleted within the temporal constraint.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00480	Each ECSBBR product shall consist of a single XML file called the Browse Reference File (BRF).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00490	Each ECSBBR granule shall contain the metadata specified in document 170-WP-023-001 (section 3.2).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00500	The file naming convention of the BRF files shall be in accordance of document 170-WP-023-001 (p 13).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00510	Each BRF file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00520	The ECS shall provide a custom acquire service for acquiring the browse files associated with the generated bulk browse products.   For each ECSBBR granule in the acquire request, the custom acquire service will distribute the BRF from the ECSBBR granule, as well as all browse products referenced in the BRF (as if each browse product were another file in a multi-file granule.)	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00530	The BMGT shall extract browse cross-reference information from the ECS Science Data Server Database at a rate of at least 25,000 granules per hour.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00540	The BMGT shall convert extracted browse cross-reference information to XML format at a rate of at least25,000 granules per hour.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00550	The BMGT shall perform bulk metadata and bulk browse Generator operations such that they can be restarted and completed successfully if interrupted by a system fault.	
KC_BP_01	Bulk Metadata Generator Tool	no data				S-BGT-00604	The Ingest CSCI shall allow ingest of products of types ECSMETC, ECSMETG, ECSMETV, and ECSBBR through the SIPS interface.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40010	The MSS configuration management application service shall identify versions and variants of configuration controlled resources that comprise the site's operational baseline.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40110	The MSS configuration management application service shall maintain lists of configuration-controlled resources that comprise configuration items and their components.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40120	The MSS configuration management application service shall track the names and identifiers for:     a. ECS functional assemblies such as subsystems, and  configuration items;  b. Configured system and network device assemblies such as workstations,    servers, and firmware  c. ECS releases and baselines    d. Hardware and software resources deployed to sites. 	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40140	The MSS configuration management application service shall maintain, and make available system-wide, information identifying  sites at which each configuration controlled resource is deployed.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40150	The MSS configuration management application service shall maintain, and make available system-wide, records that identify the current and previous versions of ECS hardware and software resources deployed to the sites.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40190	MSS configuration management application service shall identify the change request that authorize each baseline change.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40200	The MSS configuration management application service shall maintain historical status records of the configuration changes to ECS hosts, subsystems, configuration items, and baselines, identifying for each:   a. current version;    b. component history   c. version history   d. effectivity period  	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40220	The MSS configuration management application service  shall maintain historical status records about ECS baseline changes to include:  a. sites affected;  b. hosts affected 	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40240	The MSS configuration management application service shall identify critical software items.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40270	The MSS configuration management application service  shall produce configuration reports identify the resources  baselined  for deployment to sites.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40280	The MSS configuration management application service shall characterize ECS-controlled resources as system-wide or site-specific.	
KS_XT_01	XRP Conversion to ClearCase - BLM	no data				C-MSS-40300	The MSS configuration management application service shall produce formatted data files containing baseline management data records.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-42200	The MSS License Management Service shall maintain information on product identification,  licensing provisions, numbers and types of users	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45010	The MSS Inventory/Logistics Management Service at the SMC shall maintain an on-line, system-wide catalog of non-expendable and consumable ECS resources.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45020	The MSS Inventory/Logistics Management Service at the SMC shall provide consolidated, system-wide views of ECS sites' inventory data.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45040	The MSS Inventory/Logistics Management Service at the SMC shall generate site and multi-site inventory reports for printout and display.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45050	The MSS Inventory/Logistics Management Service shall maintain inventory records of individual non-expendable ECS resources.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45060	The MSS Inventory/Logistics Management Service shall have the capability to update and track ECS resources status.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45070	The MSS Inventory/Logistics Management Service shall record attributes of inventoried resources.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45080	The MSS Inventory/Logistics Management Service shall distinguish between ECS resources and non-ECS resources in the inventory.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45090	The MSS Inventory/Logistics Management Service shall generate site inventory reports for printout and display.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45200	The MSS Logistics Management Service  shall provide the capability to input, store, update and view/print specified site's spare inventory information.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45210	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to produce individual site or consolidated sites spare related reports based on operator entered criteria.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45270	The MSS Inventory/Logistics Management Service shall provide the capability to generate site spare parts related reports based on operator entered criteria.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45350	The MSS Inventory/Logistics Management Service shall log at least the following information for transactions performed:  operation type, userid of initiator, and date time stamp.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-45360	The MSS Inventory/Logistics Management Service shall generate chronological reports of logged transactions associated with user selectable: time frames; operation types; and userids.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50010	The MSS  Maintenance Management Service  shall provide the capability to view specified site's corrective maintenance information.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50020	The MSS Maintenance Management Service shall provide the M&O staff the capability to produce corrective maintenance reports based on operator entered criteria.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50030	The MSS Maintenance Management Service at the SMC shall have the capability to receive specified site maintenance data for use in maintenance trends analysis.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50060	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print corrective maintenance performed (CMP) information.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50070	The MSS Maintenance Management Service shall have the capability, via M&O Staff entered criteria, to retrieve and display information relevant to corrective maintenance services previously performed.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50090	The MSS Maintenance Management Service shall have the capability to update repaired/replaced equipment component information in the database.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50100	The MSS Maintenance Management Service shall log at least the following information for transactions performed : operation type, userid of initiator, and date time stamp.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50110	The MSS Maintenance Management Service shall generate chronological reports of logged transactions associated with user selectable: time frames; operation types; and userids.	
KS_XT_02	XRP Conversion to Remedy - ILM	no data				C-MSS-50230	The MSS Maintenance Management Service  shall provide the capability to produce maintenance status reports.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00010	The Spatial Subscription Server (NSBRV) CI shall allow an operator to generate a standing order (hereinafter called 'subscription') for ECS standard products in the ECS archive holdings.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00015	The NSBRV CI shall store subscription information persistently. 	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00020	The NSBRV CI shall allow an operator to associate a subscription with any SDSRV event (SDSRV events for each ESDT are defined in that ESDT's descriptor).	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00030	The NSBRV CI shall not permit an operator to enter subscriptions for events that are not valid SDSRV events.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00040	The NSBRV CI shall require an operator to associate a valid ECS userid with a subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00050	The NSBRV CI shall allow an operator to associate an expiration date with a subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00065	The NSBRV CI shall assign a unique identification to each subscription.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00066	The NSBRV CI shall not evaluate subscriptions against ECS events which occur after the expiration date of the subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00070	The NSBRV CI shall allow the operator to qualify a subscription spatially by specifying one of the following criteria:    a. LLBOX  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00072	The NSBRV CI shall consider a granule to qualify spatially for a subscription if the granule's spatial coverage overlaps with the spatial qualification criterion.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00074	The NSBRV CI shall allow spatial qualification of a subscription where the underlying ESDT has a gpolygon spatial search type.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00076	The NSBRV CI shall allow spatial qualification of a subscription where the underlying ESDT has a bounding rectangle spatial search type.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00078	The NSBRV CI shall allow spatial qualification of a subscription where the underlying ESDT has an orbit spatial search type.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00079	The NSBRV CI shall not permit an operator to enter a spatial qualification criterion for an ESDT that does not have spatial coverage metadata.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00080	The NSBRV CI shall allow the operator to qualify a subscription temporally by specifying one of the following criteria:    a. date range    b. date and time range.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00082	The NSBRV CI shall consider a granule to qualify temporally for a subscription if the granule's temporal coverage overlaps with the temporal qualification criterion.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00084	The NSBRV CI shall not permit an operator to enter a temporal qualification criterion for an ESDT that does not have temporal coverage metadata.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00090	The NSBRV CI shall allow the operator to qualify a subscription by values of the following core attributes:    a. DayNightFlag    b. PGEVersion    c. Bandx_Available (for x = 1-3,3N, 4-14)    d. BeginningDateTime/EndingDateTime range  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00100	The NSBRV CI shall allow the operator to qualify a subscription by all product specific attribute values which correspond to the ESDT associated with the subscription event.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00110	The NSBRV CI shall allow the operator to qualify a subscription by values of the following measured parameter attributes:     a. QAPercentCloudCover  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00112	The NSBRV CI  shall accept a string value as a qualifier for core, product specific, or measured parameter attributes of type string. 	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00113	The NSBRV CI shall consider a granule to qualify by string attribute value for a subscription if the granule's metadata value for the string attribute is equal to the value of the string qualifier.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00114	The NSBRV CI shall accept a minimum and a maximum integer value as qualifiers for core, product specific, or measured parameter attributes of type integer.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00115	The NSBRV CI shall consider a granule to qualify by integer attribute value for a subscription if the granule's metadata value for the integer attribute is greater than or equal to the minimum integer qualifier and less than or equal to the maximum integer qualifier.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00116	The NSBRV CI shall accept a minimum and a maximum floating point value as qualifiers for core, product specific, or measured parameter attributes of type floating point.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00117	The NSBRV CI shall consider a granule to qualify by floating point attribute value for a subscription if the granule's metadata value for the floating point attribute is greater than or equal to the minimum floating point qualifier and less than or equal to the maximum floating point qualifier.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00120	The NSBRV CI shall not permit an operator to enter a qualification criterion for a product specific attribute that is not supported by the ESDT that is the target of the subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00122	The NSBRV CI shall not permit an operator to enter a qualification criterion for a measured parameter attribute that is not supported by the ESDT that is the target of the subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00124	The NSBRV CI shall permit an operator to enter up to 5 subscription qualifiers for core, product specific and measured parameter attributes of type string.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00126	The NSBRV CI shall permit an operator to enter up to 5 subscription qualifiers for core, product specific and measured parameter attributes of type integer, floating point, or datetime.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00130	The NSBRV shall consider a granule to qualify for a subscription if it meets all of the subscription's qualification criteria.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00160	The NSBRV CI shall allow an email notification action to be associated with a subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00162	The NSBRV CI shall require the operator to enter one 'to' address for the email notification action.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00164	The NSBRV CI shall provide the email address of the registered ECS user associated with the subscription as the default 'to' address for the email notification action.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00180	The NSBRV CI shall construct the subject text for each email notification per the ICD between ECS and the Science Investigator-Led Processing Systems (SIPS) (423-41-57).	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00185	The NSBRV CI shall construct the message text of each email notification per the ICD between ECS and the  Science Investigator-Led Processing Systems (SIPS) (423-41-57).	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00190	The NSBRV CI shall allow the operator to specify a userstring to be included in the message text for each email notification.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00200	The NSBRV CI shall allow the operator to include names and values for all metadata attributes in the ECS Earth Science Data Model (420-TP-022-002) in the email notification text.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00220	The NSBRV CI shall allow operators to only include names and values for the metadata attributes associated with the subscription qualifiers in the email notification text.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00230	The NSBRV CI shall embed all selected inventory metadata information in the email text, in parameter=value format, one parameter per line.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00235	The NSBRV CI shall not include the name or value of an operator-selected metadata attribute in email.notification text if the associated ESDT does not contain that attribute.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00260	The NSBRV CI shall allow a distribution action to be associated with a subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00270	The NSBRV CI shall require the operator to associate the userid of a registered ECS user with a distribution action.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00275	The NSBRV CI shall provide the userid of the registered ECS user associated with the subscription as the default userid for the distribution action.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00280	The NSBRV CI shall allow the operator to associate an email address with a distribution action.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00285	If the operator chooses to associate an email address with a distribution action, the NSBRV CI shall provide, as the default email address, the email address in the ECS user profile for the userid associated with the distribution action.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00290	The NSBRV CI shall allow the operator to associate a userstring with a distribution action.   (The userstring will be included in the Distribution Notice associated with the order.)	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00300	The NSBRV CI shall allow the operator to associate a distribution priority with a distribution action.   Valid distribution priorities shall be those accepted by ECS Data Distribution (DDIST).   	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00305	The NSBRV CI shall provide the distribution priority in the user profile of the userid associated with the subscription as the default distribution priority.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00310	The NSBRV CI shall allow the operator to select FtpPush distribution.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00320	If FtpPush distribution is selected, the NSBRV CI shall require the operator to enter or select values for the following FtpPush parameters:     a. media format    b. ftp userid    c. ftp password    d. ftp host name    e. ftp directory name  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00330	The NSBRV CI shall allow the operator to select FtpPull distribution.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00340	If FtpPull distribution is selected, the NSBRV CI shall require the operator to enter or select values for the following FtpPull parameters:     a. media format  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00380	The NSBRV CI shall use the Science Data Server Command Line Interface (SCLI) to submit all ECS distribution requests associated with distribution actions to the SDSRV.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00384	The NSBRV CI shall handle recoverable errors returned to it from the SCLI by retrying the distribution request, using the same tag passed to the SCLI for the original request.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00390	The NSBRV CI shall allow the operator to determine the number of pending email and distribution actions in the action queue, and the subscription id, status, userid, collection, version id, enqueue time, dequeue time, and action type (e.g.., email,distribution) associated with each.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00395	The NSBRV CI shall process the action queue in first-in, first-out order.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00440	The NSBRV CI shall retain information about completed actions, and the completion times associated with each, for an operator-configurable amount of time.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00443	The NSBRV CI shall process the event queue in first-in first-out order.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00444	The NSBRV CI shall retain information about processed events, and the time at which each finished subscription matching, for an operator-configurable amount of time.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00450	The NSBRV CI shall allow the operator to update the userid associated with a subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00455	The NSBRV CI shall allow the operator to update the expiration date associated with a subscription. 	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00460	The NSBRV CI shall allow the operator to add, modify,or delete qualifications associated with a subscription. 	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00470	The NSBRV CI shall allow the operator to add, modify, or delete actions associated with an existing subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00480	The NSBRV CI shall preserve the subscription id when a subscription is updated.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00490	The NSBRV CI shall allow the operator to suspend an individual subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00520	The NSBRV CI shall not evaluate a suspended subscription against ECS events which occur after the subscription is suspended.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00530	The NSBRV CI shall process normally any actions associated with a suspended subscription which were already queued at the time the subscription was suspended.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00540	The NSBRV CI shall allow the operator to resume a subscription which has been suspended.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00545	The NSBRV CI shall preserve the subscription id when a subscription is suspended or resumed.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00550	The NSBRV CI shall allow the operator to cancel an individual subscription.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00560	The NSBRV CI shall not evaluate a cancelled subscription against ECS events which occur after the subscription is cancelled.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00570	The NSBRV CI shall process normally any actions associated with a cancelled subscription which were already queued at the time the subscription was cancelled.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00590	The NSBRV CI shall allow the operator to display a list of subscriptions.   For each subscription in the list, the NSBRV CI shall display the subcription id, collection name, version id, event type, user id, expiration date, and current status.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00600	The NSBRV CI shall allow the operator to filter the subscription list by user id, collection name, and current status.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00610	The NSBRV CI shall allow the operator to sort the subscription list by subscription id, user id, collection name, expiration date, and current status.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00620	The NSBRV CI shall allow the operator to view all information about an individual subscription, including qualifier and action information, by selecting the subscription from the subscription list.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00630	The NSBRV CI shall provide the capability to persistently store information regarding which ECS events are valid for placing subscriptions.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00640	The NSBRV CI shall allow the operator to display the list of valid ECS events upon which subscriptions may be placed.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00650	The NSBRV CI shall allow the operator to filter the event list by collection name, version id, and event type.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00660	The NSBRV CI shall allow the operator to sort the event list by collection name, version id, and event type.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00680	The NSBRV CI shall automatically update its database of valid ECS events when an ESDT is installed in the SDSRV inventory.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00690	The NSBRV CI shall automatically update its database of valid ECS events when an ESDT is removed from the SDSRV inventory.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00700	The NSBRV CI shall automatically update its database of valid ECS events when an ESDT is updated in the SDSRV inventory and the list of valid events for that ESDT is changed.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00710	At startup time, the NSBRV CI shall allow the operator to specify the number of concurrently operating event handling processes to run.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00715	The NSBRV CI shall allow the operator to start additional event handling processes as needed.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00720	The NSBRV CI shall allow the operator to determine the number of event handling processes running, and the unix process id and the status of each.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00730	The NSBRV CI shall allow the graceful shutdown of an event handling process.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00740	The NSBRV CI shall allow the operator to list the following statistical information for each event in the event queue log:    a. collection name    b. version id    c. event type (e.g, INSERT, DELETE, UPDATEMETADATA)    d. total number of occurrences of the event     e. maximum time to insert metadata in the NSBRV database for these occurrences of the event    f. average time to insert metadata in the NSBRV database for these occurrences of the event    g. maximum time to evaluate all subscriptions associated with an occurrence of the event    h. average time to evaluate all subscriptions associated with an occurrence of the event  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00750	At startup time, the NSBRV CI shall allow the operator to specify the number of concurrently operating action handling processes to run.  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00755	The NSBRV CI shall allow the operator to start additional action handling processes as needed.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00760	The NSBRV CI shall allow the operator to determine the number of action handling processes running, and the unix process id and the status of each.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00770	The NSBRV CI shall allow the graceful shutdown of an action handling process.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00780	The NSBRV CI shall allow the operator to list the following statistical information for email notification actions in the action queue:    a. total number of email notification actions    b. maximum notification time (i.e., time from when the action was placed on the queue until the email was sent)  for all email notification actions    c. average notification time for an email notification action  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00785	The NSBRV CI shall allow the operator to list the following statistical information for distribution actions in the action queue:    a. total number of distribution actions    b. average processing time (i.e., time from when the distribution action was placed on the queue until the distribution request was submitted to the SCLI)    c. maximum processing time   	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00810	The NSBRV CI shall provide an interface such that externally-developed software can be substituted for the NSBRV GUI to insert subscriptions.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00830	The NSBRV CI shall support warm start after a fault such that no event, subscription, triggered event, or action is lost.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00835	The NSBRV CI shall retry an operation if it encounters a retriable error (such as database deadlock).	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00840	The NSBRV CI shall log the following information:    a. Receipt of event notification from SDSRV     b. Start of event processing    c. Completion of event processing    d. Start of action processing    e. Completion of action processing    f. Completion of metadata extraction  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00850	The NSBRV CI shall include the following information in each log entry, as applicable:    a. type of entry    b. date and time when logged (at least to the millisecond)    c. subscription id    d. action Id    e. Event Id    f. Userid associated with the subscription    g. Type of error and error details (for logged errors)  	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00860	The NSBRV CI event queue handling processes shall generate a default name for the event handling log file. 	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00865	he NSBRV CI action queue handling processes shall generate a default name for the action handling log file. 	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00870	The NSBRV CI shall append output to a log file if the log file already exists.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00880	The NSBRV CI shall create the log file if the log file does not already exist.	
NS_SY_01	Spatial Subscription Server	no data				S-SSS-00890	The NSBRV CI shall be able to operate in multiple modes concurrently.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-03441	The Order Management GUI shall allow an operator to list archived data distribution requests.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-03442	The Order Management GUI shall allow an operator to filter the list of archived distribution requests by one or several values of terminal request status and media type; or alternatively, by user name, or user e-mail address, or order identification, or request identification; an allow these filters to be combined with a creation time period.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-03443	The Order Management GUI shall allow an operator to sort the list of archived data distribution request by date/time of submission, or date/time of last status change, or request status, or user ID, or order identification, or request identification. 	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-03451	The Order Management GUI shall allow an operator to select a data distribution request from a list of archived requests and view it, as well as the order and user profile associated with that data distribution request.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-03452	The Order Management GUI shall allow an operator viewing an archived distribution request to list the granules ordered by the request.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-03453	The Order Management GUI shall identify failed granules in the list of granules.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06011	The OM GUI shall display the processing mode assigned to an archived request. [NOTE:  The processing mode may be blank if the request was terminated before it was assigned a processing mode.]	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06141	The OM GUI shall allow operators to AND the filter on request state and media type when filtering archived requests.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06151	The OM GUI shall display the capacity class to which a request was allocated in the request details of archived requests.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06176	The OM GUI shall display in the request details of archived FTP Push distribution requests, for each request its destination (Configured FTP Push Destination or FTP Push Target Host).	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06386	The OM GUI shall allow operators to filter the list of archived distribution requests by any combination of states, similar to the current DDIST GUI.	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06706	The OMS CI shall allow DAAC operators to archive OMS and MSS order tracking information for OMS orders that are past their expiration date (to include billing information). [NOTE: The capability can be a command line utility suitable for execution via cron.  The capability is not expected to clean up order tracking information for orders that did not go through OMS.] [Supersedes S-OMS-06705]	
OD_70_01	Persist Order Tracking Information	no data				S-OMS-06707	The OM GUI shall clearly indicate when it is displaying archived (i.e., historical) information.	
OD_71_01	OMS Assumes that Public Data Pool Granules Are Not Billable or Restricted	no data				S-OMS-06421	The OMS CI shall assume that pre-staged granules (i.e., granules in the public Data Pool) are not restricted and not billable. NOTE: This replaces S-OMS-06420 in Ticket OD_S4_01.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13200	The OM GUI shall permit operators to list the defined physical media devices and their configured attributes (e.g., tape devices and Rimage units), plus the following information: a. whether the device / unit is on-line or off-line, b. for non-Rimage devices, whether they are busy or free, and if busy, the mode in which they are being used, and if used by the same mode as that in which the GUI is operating, the request and volume to which they are allocated and the time of allocation, c. for Rimage units, their current actual and allocated workload, d. any explanation associated with the device e. an appropriate indication if a device is currently busy but was requested by the operator to go off-line once it frees up.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13210	The OM GUI shall permit an authorized operator to change the status of a device to free that is currently marked busy if it is used by a request operating in the mode in which the GUI is operating, except if the device is a production device currently allocated to a volume that is in the creating phase (i.e., Prepping, Prepped, Creating state) or verifying phase (i.e., Verifying state). [NOTE: The exceptions are intended to prevent operator mistakes. Testing this presumes an error in OMS device status maintenance and thus, it may not be possible to test this requirement during integration testing.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13220	The OMS CI shall allow DAAC operators to configure for each physical media type the following information: a. a default QC policy, to include the options to either verify by default all or none of the produced volumes, b. for tape media types that are activated automatically, the maximum number of devices that a request may use concurrently for media production while there are distribution requests pending or in media production that could use these devices, c. for any media type activated automatically, the maximum number of devices that a request may use concurrently for media verification while there are distribution requests waiting for QC activation or in QC that could use these devices.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13230	The OM GUI shall allow DAAC operators to list the configuration settings in S-OMS-10400, S-OMS-10402, S-OMS-10407, S-OMS-10410,  S-OMS-10420, and S-OMS-13220.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13240	The OM GUI shall allow an operator to monitor for the following request-related operator actions: a. to activate media creation manually, b. DELETED c. to collect the created media for QC, d. to assemble a distribution package for shipment, e. to activate media verification manually.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13250	The OM GUI shall allow an operator to monitor for the following request-related operator interventions: a. to handle media creation errors, b. to handle media verification errors, c. to handle the assignment of a physical media distribution request to Synergy III mode,	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13260	The OM GUI shall allow an operator to monitor for the following media device related actions: a. to assign a device to a volume, b. to confirm the mount of a volume on the assigned device, c. to confirm the dismount of a volume from the device to which it has been assigned.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13270	The OM GUI shall allow an operator to monitor for device related actions and request related actions concurrently on a single screen. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13280	The OM GUI shall allow an operator to filter the request related operator actions and interventions by type of action, respectively intervention.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13290	The OM GUI shall allow an operator to sort the request related operator actions and interventions by media type.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13300	The OM GUI shall organize the device related operator actions by media type.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13310	The OM GUI shall allow an operator to leave any of the request related operator actions / interventions related to OMS media creation, QC and shipment pending, optionally after providing an annotation.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13320	When displaying an action to assign a device for media production, the OM GUI shall offer the operator a list of volumes eligible to be produced on this device, i.e., the volumes of requests for that media type that have been activated for media creation, still require production, and have not yet been assigned to a device. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13330	When displaying an action to assign a device for media verification, the OM GUI shall offer the operator a list of volumes eligible to be verified on this device, i.e., the volumes of requests for that media type that have been activated for media verification, still require verification, and have not yet been assigned to a device. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13340	The OM GUI shall display the list of volumes offered for production or verification on a device grouped by request in ascending order of request ID and within the same request, in ascending order of volume identification. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13350	When displaying a list of volumes eligible to be verified on a device, the OM GUI shall identify volumes that were produced on that device. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13360	The OM GUI shall warn the operator when the operator assigns a device to the verification of a volume that was produced on that device, and accept that assignment only after the operator  has confirmed it. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13370	The OM GUI shall not allow an operator to assign a device unless the dismount of the volume previously mounted in that device had been confirmed before.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13380	When displaying an operator action to confirm the mount or dismount of media, the OM GUI shall display the following information: a. the identification of the request, b. the purpose of the mount or dismount (e.g., whether for media production or verification), c. the media type, d. the identification of the device, e. for media mounts and dismounts during QC, the ID of the volume that will be or was verified, f. for media mounts and dismounts during media creation, the ID of the volume that will be or was created.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13390	The OM GUI shall allow an authorized operator to disposition a request for operator action to dismount media by: a. confirming the successful completion of the requested action, or b. indicating that the requested action failed, optionally requesting that the device be set to off-line and associating an explanation with the off-line device. [NOTE: Failing a dismount will mark the corresponding media volume as failed.  It will also disassociate the volume from the device and the device will be assumed to be unassigned.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13400	When displaying the confirmation for dismounting a volume, the OM GUI shall indicate to the operator when the operation failed for which the volume was originally mounted.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13410	The OM GUI shall allow an operator to retry the failed operation of a volume without waiting for an operator intervention. [NOTE: Since there are no separate dismount actions for Rimage, operators will generally not know that a volume failed during Rimage production until OMS queues an operator intervention for the request.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13420	When displaying an operator action to activate media creation for tapes manually, the OM GUI shall: a. Display the due date of the request  (device selection removed), b. Display the number of volumes that need to be produced. [NOTE: If the media production of volumes is retried, the number of volumes to be produced may be less than the total number of volumes in that request.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13430	The OM GUI shall allow an authorized operator to complete an action for manually activating media creation for a request using Rimage for its media production: a. by selecting the offered default device, or b. by selecting any other offered device, or c. by failing the request, optionally after suppressing sending the DN.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13440	The OM GUI shall inform an operator who attempts to manually activate a request for media creation on a device other than Rimage if there is no device of the required type currently on-line which could be used in this operational mode, and not permit the operator to activate a request under that circumstance.  	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13450	The OM GUI shall allow an authorized operator to complete an action for manually activating media creation for tape: a. by activating the request, or b. by failing the request, optionally after suppressing sending the DN.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13460	The OMS CI shall generate a media creation error intervention for an active request that is in media creation if there is no on-line device of the required type which can be used by this processing mode. [NOTE: In this situation, any active requests that still require volumes to be created cannot proceed because their volumes can no longer be assigned to devices until a device is set on-line and/or made available to the mode.  The intervention will alert the operator to that fact and prevent the request from seemingly hanging indefinitely.  The operator can close the intervention by retrying the request.  This will requeue the request for activation.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13470	When displaying intervention details related to media creation errors, the OM GUI shall: a. display the nature of the media creation error, b. display the media type, c. list the media volumes, their status, the related production module, d. identify for each media volume, the device to which it was assigned, the time volume production was started, and whether the dismount of the volume needs to be confirmed, e. identify the volumes whose creation encountered an error, as well as the nature of the error, f. identify the request and allow the operator to access details related to the distribution request, g. in the case of tape distribution, ask the operator to confirm for those media volumes for which the dismount has not yet been confirmed that the media were removed from their respective production devices and the devices are now available for other requests, h. allow the operator to change the status of selected volumes, e.g., to indicate that volumes have been written successfully or were found to be defective.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13480	The OM GUI shall allow an authorized operator to complete an operator intervention related to physical media creation errors after any pending dismounts have been confirmed, by: a. retrying the media creation for the entire distribution request, optionally after failing granules that experienced media creation errors, or b. retrying the media creation for volumes that failed or were marked failed by the operator, optionally after failing granules that experienced media creation errors on those volumes, or c. failing the distribution request, optionally after suppressing sending the DN.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13490	When displaying a request for operator action to collect the created media for QC, the OM GUI shall: a. identify the distribution request and provide access to the request details, b. identify the media type, c. list the created media volumes and the related production module, d. identify for each media volume, the device on which it was produced, e. identify the media volumes currently selected for verification (e.g., by default or in case of a retry, because of a prior selection).	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13500	The OM GUI shall allow an authorized operator who is completing an action requesting collection of the created media for QC to change the current selection of the media volumes that are to be verified by: a. selecting all volumes for verification in a single operator action, b. selecting no volumes for verification in a single operator action, c. selecting individual volumes for verification, d. de-selecting individual volumes that are currently selected for verification. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13510	The OM GUI shall allow an authorized operator to complete an action requesting collection of the created media for QC by: a. acknowledging that the media have been collected and are ready for verification, or b. failing the action, e.g., because the media could not be collected or because the operator discovered a problem that prevents QC.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13520	When displaying an operator action to activate media verification manually, the OM GUI shall display: a. the due date of the request , b. the number of volumes that need to be verified.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13530	The OM GUI shall allow an authorized operator to complete an action for manually activating media verification: a. by activating the request, or b. by failing the action, thereby causing a QC error intervention.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13540	The OM GUI shall inform an operator who attempts to manually activate a request for media verification if there is no device of the required type currently on-line which could be used in this operational mode, and not permit the operator to activate a request under that circumstance.  	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13550	The OMS CI shall generate a media verification error intervention for an active request that is in media verification if there is no on-line device of the required type which can be used by this processing mode.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13560	When displaying an operator intervention related to media verification errors, the OM GUI shall: a. display the nature of the media verification error, b. display the media type, c. list the media volumes, d. identify for each volume the responsible production module, the device on which it was produced, (if applicable) the device used for verification and whether the dismount still requires confirmation, and its status, i.e., whether it failed verification, passed verification, or whether verification was skipped by the operator or not performed, e. change the selection of volumes to be verified (except for those volumes which are already verified), f. identify the request and allow the operator to access details related to the distribution request, g. allow the operator to change the status of a volume, e.g., to indicate that it is defective or passed, h. ask the operator to confirm for those media volumes for which the dismount has not yet been confirmed that the media were removed from their respective verification devices and the devices are now available for other requests, i. identify the printer to which the QC report was sent if one was generated, j. allow the operator to print a QC report.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13570	The OM GUI shall allow an authorized operator to complete an operator intervention related to media verification errors after any pending dismounts have been confirmed, by: a. retrying the media creation for the entire distribution request, optionally after failing granules that experienced media creation errors, or b. retrying the media creation only for volumes that failed or were marked failed by the operator, optionally after failing granules that experienced media creation errors on those volumes, or c. failing the distribution request, optionally after suppressing sending the DN, or d. requesting re-verification of volumes that failed or were marked failed by the operator if they are still flagged for verification, as well as the verification of volumes that are selected for verification and for which verification has not yet been performed.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13580	When displaying a request for operator action to assemble the final distribution package for shipment, the OM GUI shall: a. display request information, b. identify the media type, c. list the created media volumes, identify their status, the devices used for their production and verification, and the responsible production module, d. list the printed outputs and identify the printers where each is located, e. allow the operator to re-print any of the following (as applicable to the media type): shipping label, packing list, tape labels, jewel case inserts, and QC report. f. let the operator acknowledge the successful collection of all media volumes.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13590	The OM GUI shall allow an authorized operator to complete an operator action requesting assembly of the final distribution package for shipment by: a. acknowledging the successful assembly of the package, and confirming that the request can transitioned to the 'Shipped' state, optionally suppressing the DN, b. indicating that the distribution package could not be assembled successfully, thereby causing a QC error intervention, c. failing the request, optionally suppressing the DN.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13600	The OM GUI shall display the following additional information when displaying details for a physical media distribution request: a. Request Annotations, b. Identification of the tape production device or Rimage unit that was used for the request [NOTE: or the latest if more than one was used] and the time of allocation, c. List of media volumes created for the request in order of volume ID. d. Due Date.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13610	The OM GUI shall display the following information when listing media volumes: a. volume identification, b. volume status, i.e., one of the following:    NULL,   Prepping (volume is being prepared),    Prepared (volume was prepared but not yet created),    Creating (volume is being created,    Created (volume was created by not yet verified),    Verifying (volume is being verified),    Verified (volume was verified successfully),    Failed (volume failed the current operation, i.e., prepping, creating, or verifying),    QC Skipped by Ops (verification of volume was skipped by the operator).   c. associated production module, d. The time volume creation started if the volume is currently in the 'Creating' state (i.e., the time of last status change), e. The time volume verification started if the volume is currently in the 'Verifying' state (i.e., the time of last status change), f. for each volume, the devices used for production and verification, g. whether the dismount of the media volume still needs to be confirmed. [NOTE: The above ensures that the time the respective operation started as well as the device being used for a volume is displayed when the GUI offers the operator the option to stop this operation.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13620	The OM GUI shall display the list of volumes for a request when displaying historic request details.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13630	The OM GUI shall include the following information for each volume when displaying the volume list for historic requests: a. the final status of the volume (usually Verified or QC Skipped By Ops), b. the device on which the volume was created, c. the device on which the volume was verified (if it was verified).	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13640	The OM GUI shall allow authorized operators to stop the physical media verification for a physical media distribution request that is currently in the 'QC Hold' state, optionally for a specific volume. [NOTE: The OMS will cancel the execution of the current QC module and queue a QC error. The operator can handle any necessary actions in the resulting operator intervention.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13650	The OM GUI shall remind the operator who is canceling a request that any of its media volumes that are currently assigned to devices will be considered dismounted once the cancellation of the request has occurred.  	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13660	If the OMS CI is configured for automatic activation for a media type other than Rimage, the OMS CI shall dispatch requests for that media type for media creation while there is at least one device that is free, on-line, and supports the media type, if there is no request in media creation or verification that could use that device and whose device usage is below the configured maximum for media creation, respectively media verification. [NOTE: In other words, a device may be freed up because a volume of some other request completes production or verification.  However, if that request uses fewer devices than the configured limit permits and still has volumes that need to be verified or created, than that active request gets to use available devices first.] 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13670	The OMS CI shall be able to re-execute the physical media distribution steps for a request or a volume, re-assigning the same volume identifications to volumes that have been created before and are not being re-created. [NOTE: Re-dispatching may be needed after operator interventions. For example, a multi-volume job may encounter a device error after some media have been written; or some of the media failed verification. Note that in the case of Rimage, this implies that the OMS can distinguish between the response to a re-dispatch and the original dispatch.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13680	When automatically activating a request for media creation for a tape device, the OMS CI shall make its volume available for automatic device assignment.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13685	For media types configured for automatic activation, the OMS CI shall assign their devices to volumes of active requests for media creation automatically by priority and within the same priority in the order in which the requests were activated for media creation, and within the same request in sequence of volume ID, subject to the configured limits for concurrent device usage. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13690	When an operator action for activating a distribution request manually is completed successfully, the OMS CI shall make its volumes eligible for manual device assignment.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13700	After a volume was assigned to a device other than Rimage, the OMS CI shall generate an operator action to mount media for the volume into the assigned device.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13710	The OMS CI shall re-queue a volume for allocation to a different device if the mount action for its current device is failed and the media type is dispatched automatically. [NOTE: ECS tracks a single device for a distribution request. If a distribution request used several production devices, the tracking information will only show the most recent device that was used.]	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13720	The OMS CI shall generate an operator action for device assignment for a volume if its mount action is failed and the media type is dispatched manually.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13730	The OMS CI shall flag a volume as having failed its current media operation because of a failed dismount when the operator fails the action to dismount the volume and disassociate the volume from the device on which is was mounted. [NOTE: The volume is disassociated from the device so it can be retried if the copy that is currently in the device cannot be used.] 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13740	The OMS CI shall make a device available for another volume when it completes the physical media operation for the current volume (whether successfully or with an error), or the media operation is stopped, or the mount of the currently assigned volume is failed, provided that the device was not set off-line and that the operator confirms or fails the dismount of the previously mounted media, or acknowledges the dismount when the request is cancelled.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13750	The OMS CI shall no longer allocate a device to volumes if the operator requested that it be set off-line at a time when the device was busy, even if the device becomes free, until such time as the operator sets the device on-line again.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13760	If a production module returns an error the OMS CI shall indicate that the media creation for the affected volume failed.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13770	The OMS CI shall generate an operator intervention for a media creation error when it completes media creation for a request (i.e., all volumes are in a created or a failed state) if there are any volumes that have failed during media creation.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13780	The OMS CI shall fail the affected volumes when it cancels one or several production modules in response to the operator stopping the creation of the corresponding volume(s) or distribution request, indicating that the media creation for these volumes was stopped by the operator.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13790	The OMS CI shall fail the affected volumes when it cancels one or several media verification operation in response to the operator stopping media verification of the corresponding volume(s) or distribution request indicating that the media verification for these volumes was stopped by the operator.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13800	The OMS CI shall queue an action requesting the operator to collect the media for the distribution request for QC when it completes physical media production and any dismount actions for volumes of that request have been confirmed, if any of its media need verification.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13810	The OMS CI shall update the status of volumes that have not been  selected for verification to QC Skipped by Ops. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13820	The OMS CI shall queue distribution requests for which the operator acknowledged the successful collection of media for QC for automatic activation for media verification if the media type is configured for automatic activation and the request includes  volumes that require verification. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13830	The OMS CI shall automatically activate distribution requests for media verification in order of priority, and within the same priority, on a first-in first-out basis if the media type is configured for automatic activation. 	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13840	The OMS CI shall automatically activate distribution requests for media verification only while there is at least one device that is free, on-line, and could be used for QC by that request, provided there is no request in media verification that could use that device and whose device usage is below the configured maximum for media verification.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13860	The OMS CI shall generate a QC error intervention if a request is waiting for automatic activation for QC but there are no devices on-line that support QC of the required media type and are available to this mode (i.e., are not reserved for use by a different mode).	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13870	If the OMS CI is configured for automatic activation for a media type, it shall assign the volumes of distribution requests that were activated for verification to on-line free QC devices that support the requested media type by priority, and within the same priority in the order in which the requests were activated for QC, subject to the configured limits for concurrent device usage.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13880	The OMS CI shall not automatically assign a volume for QC to the device that was used to create that volume while there are other QC devices for that media type are on-line.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13890	The OMS CI shall give preference to QC over media creation when assigning devices to volumes automatically.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13900	The OMS CI shall fail the media verification for the affected volume if a media verification module returns an error.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13910	The OMS CI shall identify the media volumes that fail verification, but continue to verify the remaining media volumes designated for verification.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13920	The OMS CI shall queue an operator intervention for QC error when it completes media verification for a request (i.e., all volumes are in a verified or failed or QC skipped by operator state) if there are any media volumes that have failed verification.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13930	The OMS CI shall fail the media verification for the affected volume when a request that it created for a PC-attached QC device is not completed within an operator configurable time.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13940	The OMS CI shall queue an operator action for manual activation of QC for a distribution request once the operator acknowledges the successful collection of media for QC and the media type is configured for manual activation and there are volumes that need to be verified, and skip the media verification step if no volumes remain to be verified.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13960	When an operator action for manual activation of QC for a distribution request is completed successfully, the OMS CI shall make its volume eligible for manual QC device assignment.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13970	The OMS CI shall queue a request for operator action to assemble the distribution package, i.e., the printed output and the created media after the request completes QC for all volumes successfully and all dismount actions for that request have been confirmed.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13980	The OMS CI shall include the list of volumes associated with a physical media distribution request and the devices used to create and verify each volumes in the order tracking information that it archives.	
OD_71_02	OMS Enhancements for Managing Distribution Devices	no data				S-OMS-13990	The OMS CI shall maintain the following MSS order tracking information: a. media quantity b. identification of the device most recently assigned for the media production of a request [NOTE:  The MSS tables can track only one device per request.  For backwards compatibility, OMS will place the identification of the last device that was assigned to a request volume into that field.]	
OD_71_03	OMS Distribution of Browse Granules	no data				S-DPL-07110	In case of Data Pool insert requests queued by Data Pool subscriptions or the batch insert utility for granules that reside as order only in the Data Pool, the Data Pool insert service shall perform the additional insert processing steps necessary to make the granule fully visible to Data Pool users, including, if necessary, inserting any associated Browse that does not yet resides in the Data Pool. [NOTE: This replaces S-DPL-42480 in OD_S4_01, modifying the manner in which Browse is handled upon back-fill,  removing one of the backfill situations.  It does not change Data Pool Insert behavior otherwise, i.e., a separate test criterion is not needed.]	
OD_71_03	OMS Distribution of Browse Granules	no data				S-OMS-09010	The OMS CI shall copy browse granules from their ECS archive location into the hidden Data Pool area when processing an order for Browse granules, regardless of whether the Browse granule already resides in the Data Pool or not, and do so without registering it in the Data Pool inventory. [NOTE: This replaces S-DPL-42465 in OD_S4_01 and takes advantage of the fact that browse granules are archived on disk.]	
OD_71_03	OMS Distribution of Browse Granules	no data				S-OMS-09020	The OMS CI shall obtain the location of a browse granule in the ECS archive from the volume group history information stored in the STMGT database.	
OD_71_03	OMS Distribution of Browse Granules	no data				S-OMS-09030	The OMS CI shall remove the browse granules that are in the hidden Data Pool for order-only purposes after the configured cleanup delay if they are no longer referenced by distribution requests that are active (i.e., not in a terminal state) or by FTP Pull requests that are not yet expired. [NOTE: This replaces S-DPL-14512 in OD_S4_01.]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09100	The OMS CI shall permit DAAC operations to define the external production hosts available for DVD-ROM and CD-ROM generation, including: a. a unique label for that unit b. the OMS media type(s) supported by the unit c. a limit on the 'allocated workload' for the unit, i.e.,  a limit on the cumulative size of the requests (expressed in MB) allocated to this CDROM/DVD unit which when reached or exceeded causes the automatic activation of such requests to be halted temporarily until the cumulative size drops below that limit, e.g., because of request completions d. a limit on the 'actual workload' for the unit expressed in MB which must not be exceeded by the media production orders submitted to the unit, i.e., the creation and submission of media production order for that unit will be temporarily halted while this would cause the limit to be exceeded e. a descriptive text of at most 255 characters f. the directory used to communicate with the CDROM/DVD host g. optionally, indicate the mode for which the CDROM/DVD host is reserved (CDROM/DVD hosts not reserved for a specific mode are shared across all modes) [NOTE: Limits c. and d. may be different and are interpreted in a slightly different fashion. The first acts as a limit on activating work for CDROM/DVD media (though the limit can be ignored when activation is manual); the second acts as a limit on the amount of work that can actually be submitted to the CDROM/DVD host and this limit cannot be overridden by manual action.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09105	The OM GUI shall permit authorized operators to flag a tape device or external CDROM/DVD production host as on-line or off-line and when off-line, associate an explanation with the device of up to 255 characters that will be cleared when the device is returned to the on-line status.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09110	When displaying an operator action to activate media creation for an external CDROM/DVD production host manually, the OM GUI shall: a. Display the due date of the request. b. Indicate when all CDROM/DVD hosts are currently above their configured allocated workload limits, and c. offer a list of the available CDROM/DVD hosts for selection, displaying their allocated workload and the configured limit for each, and d. if there is at least one CDROM/DVD host whose allocated workload is below the limit, offer the one where the difference between workload and limit is the highest as the default choice, and if several qualify, select one randomly.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09115	If the OMS CI is configured for automatic activation for an CDROM/DVD media type, the OMS CI shall dispatch media creation for that media type while there is an external CDROM/DVD productionhost whose current allocated workload is less than its configured limit.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09120	When automatically activating media creation for an external CDROM/DVD production host, the OMS CI shall assign the distribution request to the CDROM/DVD host that is least busy based on current allocated workload, and update the assigned workload for that unit, making a random selection if more than one unit qualifies under that rule.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09125	The OMS CI shall be able to process media distribution requests that require multiple CDROM/DVD media volumes.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09130	The OMS CI production modules shall interface with Luminex for transferring the generated CD-ROM and DVD-ROM images to physical media and generating the media labels.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09135	The OMS CI shall not dispatch the media creation step for a media volume to be created by an external CDROM/DVD production host if the order would cause the configured workload limit for that CDROM/DVD host to be exceeded.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09140	The OMS CI production modules shall interface with Luminex in order to detect when a Luminex media creation completed	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09145	The OMS CI shall maintain the amount of work in progress for an external CDROM/DVD production host when the execution of a production module for CDROM/DVD media creation starts, completes or is terminated.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09150	The OMS CI shall generate a physical media distribution alert and set the corresponding external CDROM/DVD production host off-line when the Luminex unit is unreachable, or the Luminex server is unable to accept new jobs. [NOTE: Setting the external CDROM/DVD production host off-line will prevent its allocation to new requests.  It does not prevent requests that are already allocated to it from trying to use it.  To re-allocate existing requests, the operator would need to 'Stop' their media production operations (see S-OMS-11040).]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09155	The OMS CI shall clear any pending alert for an off-line external CDROM/DVD production host when the operator sets it on-line. [NOTE:  It is assumed that this is the normal operational scenario.  Operations will follow-up on the alert and set the unit back on-line once the fault has been resolved.  By that time, media operations for requests that are already allocated to the unit may already have restarted, see S-OMS-12444.]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09160	The OMS CI shall retry dispatching media creation operations for an external CDROM/DVD production host that is currently off-line because an alert is pending, and clear the alert and set the unit back on-line when a retried operation succeeds. [NOTE:  This ensures that production activities that were interrupted by the outage are resumed as soon as possible, perhaps even before the operator sets the unit back on-line.]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09165	When restarting after a fault, the OMS CI shall be able to recover the state of media productions that were in progress at the time of the fault such that no requests are lost, no media volumes are produced twice or not produced at all, no distribution steps are omitted, and steps that were completed or can continue despite the fault do not have to be redone or re-started, and such that the recovery does not place requests into operator intervention.  This includes: a. The OMS shall restart media preparations that were in progress at the time of the fault, and not redo as part of the recovery media preparation operations that already completed or had failed at the time of the fault. b. The OMS shall restart media creation for tape transfers that were aborted by the fault, and not redo as part of the recovery tape media creation operations that already completed or had failed at the time of the fault. c. The OMS shall recover media creation orders that were accepted by Luminex for processing (i.e., avoiding creation of duplicate volumes), and not resubmit as part of the recovery media creation orders that were already completed or had failed at the time of the fault. d. The OMS shall restart media verification operations that were aborted by the fault, and not redo as part of the recovery media verification operations for volumes that were already verified successfully at the time of the fault. e. The OMS shall recover media verification related requests that were submitted to PC platforms (i.e., avoid submitting them again), and not resubmit as part of the recovery verification related requests to PC platforms for volumes that already completed or had failed verification at the time of the fault. f. The OMS shall recover operator actions and interventions that were pending at the time of the fault and require their disposition before continuing the distribution of these requests.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09170	The OMS CI shall be able to perform media distribution concurrently in multiple modes. [NOTE: This is an extension of existing requirements to physical media creation. This may require reserving specific devices or external CDROM/DVD production hosts for specific modes, e.g., by not including them in the configuration of the modes that are not using them, or by setting them off-line in those modes.]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09175	The OM GUI shall permit operators to list the defined physical media devices and their configured attributes (e.g., tape devices and external CDROM/DVD production hosts), plus the following information: a. whether the device / unit is on-line or off-line, b. for non-CDROM/DVD devices, whether they are busy or free, and if busy, the mode in which they are being used, and if used by the same mode as that in which the GUI is operating, the request and volume to which they are allocated and the time of allocation, c. for CDROM/DVD units, their current actual and allocated workload, d. any explanation associated with the device e. an appropriate indication if a device is currently busy but was requested by the operator to go off-line once it frees up.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09180	The OM GUI shall allow an operator to retry the failed operation of a volume without waiting for an operator intervention. [NOTE: Since there are no separate dismount actions for external CDROM/DVD production hosts, operators will generally not know that a volume failed during CDROM/DVD production until OMS queues an operator intervention for the request.]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09185	The OM GUI shall allow an authorized operator to complete an action for manually activating media creation for a request using an external CDROM/DVD production host for its media production: a. by selecting the offered default device, or b. by selecting any other offered device, or c. by failing the request, optionally after suppressing sending the DN.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09190	The OM GUI shall inform an operator who attempts to manually activate a request for media creation on a device other than an external CDROM/DVD production host if there is no device of the required type currently on-line which could be used in this operational mode, and not permit the operator to activate a request under that circumstance.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09195	The OM GUI shall display the following additional information when displaying details for a physical media distribution request: a. Request Annotations, b. Identification of the tape production device or external CDROM/DVD production host that was used for the request [NOTE: or the latest if more than one was used] and the time of allocation, c. List of media volumes created for the request in order of volume ID. d. Due Date.	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09200	If the OMS CI is configured for automatic activation for a media type other than CDROM/DVD the OMS CI shall dispatch requests for that media type for media creation while there is at least one device that is free, on-line, and supports the media type, if there is no request in media creation or verification that could use that device and whose device usage is below the configured maximum for media creation, respectively media verification. [NOTE: In other words, a device may be freed up because a volume of some other request completes production or verification.  However, if that request uses fewer devices than the configured limit permits and still has volumes that need to be verified or created, than that active request gets to use available devices first.]	
OD_72_01	Physical Media Production with Luminex	no data				S-OMS-09205	After a volume was assigned to a device other than an external CDROM/DVD production host the OMS CI shall generate an operator action to mount media for the volume into the assigned device.	
OD_7B_01	Operational Updates to OMS	no data				S-DPL-60203	When performing orphan checking, the DPL CI Cleanup Utility shall not consider metadata files created as per S-OMS-14030 to be orphans.	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-12662	The OMS CI shall count a physical media distribution request once it has been activated against the High and Low Watermarks until it reaches a terminal state (i.e., shipped or canceled/failed. NOTE: This requirement replaces S-OMS-12660, as per DAAC request, see NCR 8047157.]  	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-13101	The OMS CI Command Line Interface shall provide an option to request that the distribution of metadata files with the order shall be suppressed. [This requirement expands S-OMS-13100 to ensure that this option is maintained through future releases.]  	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-14010	The OMS CI shall use as file names for distributed granules the local granule ID (if present) else the original file name regardless of the file names under which the granule is staged in the Data Pool, except if there is more than one granule in the same distribution request which would use the same file names (this is called a file name collision).	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-14020	In the presence of a file name collision, OMS shall deliver the files of the first granule using the rules in requirement S-OMS-14010 and for subsequent colliding granules, append a numerical suffix to the file names that were derived in accordance of requirement S-OMS-14010; the numerical suffix used shall be unique for each of the colliding granules and the same for all files of that granule.	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-14030	When distributing a granule with file names different from those under which the granule is staged in the Data Pool, the OMS CI shall create a copy of the metadata file (.met or .xml) using the names assigned for distribution and modify the metadata element DistributionFile to be consistent with the file names actually used for distribution.	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-14040	The OMS CI shall place any additional copies of metadata files created as per S-OMS-14030 in the hidden Data Pool in the same directory as the original metadata file or the link to the original metadata file if the granule is public, except if creating a copy of that metadata file in the FTP Pull directory for that distribution request.	
OD_7B_01	Operational Updates to OMS	no data				S-OMS-14050	When distributing a granule for FTP Pull with file names different from those under which the granule is staged in the Data Pool, the OMS CI shall create a copy of the granule files using the names assigned for distribution in the FTP Pull directory for that distribution request instead of creating links.	
OD_S3_01	Order Manager	no data				C-DMS-39010	The V0 Gateway shall submit all data distribution requests to the Order Management Service, except those that need to be routed to DORRAN and external subsetters, i.e., all data distribution requests currently submitted to the SDSRV or PDS.	
OD_S3_01	Order Manager	no data				C-DMS-39030	The V0 Gateway shall not retry submission of a request if the Order Management Service returns an error.	
OD_S3_01	Order Manager	no data				C-DMS-39040	The V0 Gateway shall forward errors returned by the Order Management Service to its clients, with explanatory comments that describe the corrective actions the user should take.	
OD_S3_01	Order Manager	no data				C-MSS-75924	The MSS CI shall accept the following new MSS request status values:  a. Partitioned	
OD_S3_01	Order Manager	no data				C-MSS-75925	The MSS CI shall allow operators to display and filter orders by the new MSS request status values.	
OD_S3_01	Order Manager	no data				C-MSS-75926	The MSS CI shall recognize the following new status values as indicating that the request has been terminated:  a. Partitioned	
OD_S3_01	Order Manager	no data				S-OMS-00010	The Order Management Service shall accept data distribution requests.	
OD_S3_01	Order Manager	no data				S-OMS-00100	The Order Management Service shall require that a data distribution request specify a set of distribution options.	
OD_S3_01	Order Manager	no data				S-OMS-00110	The Order Management Service shall accept any valid combination of electronic or physical media distribution options that are supported by ECS.	
OD_S3_01	Order Manager	no data				S-OMS-00120	The Order Management Service shall require that a data distribution request specify a single media type.	
OD_S3_01	Order Manager	no data				S-OMS-00130	The Order Management Service shall offer an interface that requires that a data distribution request specify a valid MSS order and a valid MSS request identifier.	
OD_S3_01	Order Manager	no data				S-OMS-00140	The Order Management Service shall accept an optional valid MSS user profile identifier (including ECSGuest) for a distribution request.	
OD_S3_01	Order Manager	no data				S-OMS-00150	The Order Management Service shall offer an interface that accepts a valid MSS order and request identifier as optional parameters, such that the order identifier can be omitted if the request identifier is omitted, as well. [That is, specifying a request ID but no order ID is invalid] 	
OD_S3_01	Order Manager	no data				S-OMS-00160	The Order Management Service shall verify that the MSS user profile, order and request identifiers - if specified for a distribution request - have corresponding associations in the MSS order tracking database.	
OD_S3_01	Order Manager	no data				S-OMS-00165	The Order Management shall create the missing MSS order and request tracking objects if the data distribution request does not specify an order or request ID, and return their identifiers to the calling application. [Note that this includes filling in the applicable MSS request attributes, including the ESDT shortname and version (or 'MULTIPLE').]	
OD_S3_01	Order Manager	no data				S-OMS-00170	The Order Management Service shall accept an optional UserString parameter of a maximum length of 255 characters for a distribution request.	
OD_S3_01	Order Manager	no data				S-OMS-00180	The Order Management Service shall accept an optional PRIORITY parameter for a distribution request that specifies one of the ECS priorities.	
OD_S3_01	Order Manager	no data				S-OMS-00190	The Order Management Service shall accept an optional DDISTNOTIFYTYPE parameter for a distribution request that specifies the ECS notification policy MAIL.	
OD_S3_01	Order Manager	no data				S-OMS-00200	The Order Management Service shall accept an optional NOTIFY parameter for a distribution request that specifies an e-mail address string of a maximum of (255) characters length.	
OD_S3_01	Order Manager	no data				S-OMS-00210	The Order Management Service shall require that a data distribution request specify the list of granules to be distributed by the request. 	
OD_S3_01	Order Manager	no data				S-OMS-00220	The Order Management Service shall require that the list of granules to be distributed include at least one granule. 	
OD_S3_01	Order Manager	no data				S-OMS-00230	The Order Management Service shall allow the list of granules to be distributed to include ECS granule UR strings. 	
OD_S3_01	Order Manager	no data				S-OMS-00240	The Order Management Service shall allow valid Landsat subsetting options to be associated with any granule in the granule list that is identified via an ECS granule UR string.	
OD_S3_01	Order Manager	no data				S-OMS-00250	The Order Management Service shall verify the information for a distribution request syntactically before accepting it by verifying:    a.that all information specified as mandatory in the requirements is present  b.each parameter value against the list of valid values as specified in the   requirements  c.that no parameter exceeds the maximum length as specified in the   requirements  d.[DESIRABLE] only valid combinations of parameter values are being used 	
OD_S3_01	Order Manager	no data				S-OMS-00260	The Order Management Service shall save the distribution request in the Order Management Database if it passes validation.	
OD_S3_01	Order Manager	no data				S-OMS-00270	The Order Management Service shall assign a value of 'Queued' to the request status attribute when saving a new distribution request in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-00280	The Order Management Service shall assign the current date and time to the request submission date/time and the last status change date/time attributes when saving a new distribution request in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-00285	The Order Management Service shall update the MSS status of a request to a value of 'Queued' when it is saved in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-00295	The Order Management shall provide client applications with the ability to resubmit requests, e.g., in case of failures, such that a request will be executed only once even if it is submitted more than once.	
OD_S3_01	Order Manager	no data				S-OMS-00300	When encountering an error, the Order Management Service shall return a detailed error status indicative of the specific error encountered, as well as an indication whether the error is retriable or fatal.	
OD_S3_01	Order Manager	no data				S-OMS-00310	The Order Management Service shall return a fatal error if a distribution request fails validation.	
OD_S3_01	Order Manager	no data				S-OMS-00320	The Order Management Service shall return a retriable error if a distribution request cannot be saved in the database.	
OD_S3_01	Order Manager	no data				S-OMS-00325	When used by an ECS server, the Order Management Service shall log all request submission errors and successful submissions to the log of that server.	
OD_S3_01	Order Manager	no data				S-OMS-00340	It shall be possible to run different instances of ECS applications that use the Order Management Service in different modes concurrently.	
OD_S3_01	Order Manager	no data				S-OMS-00350	The Order Management Service shall be multi-thread safe, capable of accepting distribution requests concurrently from multiple threads in the same client process.	
OD_S3_01	Order Manager	no data				S-OMS-01010	The Order Manager shall process new data distribution requests.	
OD_S3_01	Order Manager	no data				S-OMS-01020	The Order Manager shall process data distribution requests that were released from hold by the operator.	
OD_S3_01	Order Manager	no data				S-OMS-01030	The Order Manager shall normally process data distribution requests in priority order and within the same priority, on a first-in, first-out basis based on their original submission date and time. [Note: normally means 'when the number of actions in the database that are waiting to be queued is below an operator configurable limit.  When that number is above this limit, the Order Manager will start dispatching immediately while continuing to read actions form the database, to avoid idling resources.  For example, this would apply to a restart situation when the Order Manager may have to re-queue thousands of requests.  In such situations it is possible that the first few requests are not processed in the usual dispatch order.]  	
OD_S3_01	Order Manager	no data				S-OMS-01032	The Order Manager shall support pacing a set of distribution requests. [See requirement S-OMS-03082 for the purpose.]  	
OD_S3_01	Order Manager	no data				S-OMS-01033	The Order Manager shall process requests for user notifications by sending them to the email address (or list of email addresses) specified in the notification action, or else to the email address associated with the request.	
OD_S3_01	Order Manager	no data				S-OMS-01034	The Order Manager shall include in a user notification the data distribution request information of the request to which the notification pertains.	
OD_S3_01	Order Manager	no data				S-OMS-01035	If the user notification pertains to a failed request, the Order Manager shall include in a user notification the reason for the request failure and any provided operator annotation.	
OD_S3_01	Order Manager	no data				S-OMS-01036	If the user notification pertains to failed granules, the Order Manager shall include in a user notification the list of the failed granules with the reason for each failure, and any provided operator annotation.	
OD_S3_01	Order Manager	no data				S-OMS-01037	For distribution requests that had been routed through the DORRAN billing system, the Order Manager shall send a copy of any user notifications pertaining to the request to the DORRAN e-mail address.	
OD_S3_01	Order Manager	no data				S-OMS-01038	Operators shall be able to configure the DORRAN e-mail address.	
OD_S3_01	Order Manager	no data				S-OMS-01039	The Order Manager shall process requests for partitioning notices to DORRAN by sending e-mail to the e-mail address configured for DORRAN that includes the following information:  a.The order ID    b.The original request ID    c.Each new request ID    d.For each new request ID, the Ids of the granules included in this request in a format compatible with the granule ID format used by the V0 Gateway and Distribution Notifications sent to DORRAN.	
OD_S3_01	Order Manager	no data				S-OMS-01040	The Order Manager shall allow operators to suspend the queuing and dispatching of all requests.  [Note: meaning: no new requests are fetched from the database; and requests that are already queued in memory but not yet in progress are not dispatched]	
OD_S3_01	Order Manager	no data				S-OMS-01045	The Order Manager shall allow operators to suspend the dispatching of e-mail notification requests.  [Note: meaning: no new notification requests are fetched from the database; and requests that are already queued in memory but not yet in progress are not dispatched]	
OD_S3_01	Order Manager	no data				S-OMS-01050	The Order Manager shall allow operators to resume the queuing and dispatching of data distribution requests if it was suspended.	
OD_S3_01	Order Manager	no data				S-OMS-01055	The Order Manager shall allow operators to resume the queuing and dispatching of e-mail notification requests if it was suspended.	
OD_S3_01	Order Manager	no data				S-OMS-01060	The Order Manager shall validate the syntax of a request to the extent such validation did not take place during request submission before the request was accepted. [Note: The requirement is only applicable if the API does not perform sufficient syntactic validation. To be resolved during design]	
OD_S3_01	Order Manager	no data				S-OMS-01070	The Order Manager shall associate a fatal error with any request that has syntactic errors. [Note: The requirement is only applicable if the API does not perform sufficient syntactic validation. To be resolved during design]	
OD_S3_01	Order Manager	no data				S-OMS-01075	The Order Manager shall place on hold any request that encounters a fatal error. [Note: This means, the Order manager should never simply fail a request, but put such requests on hold so the operator can intervene and make a final disposition.]  	
OD_S3_01	Order Manager	no data				S-OMS-01080	The Order Manager shall validate the size of a request against request size limits in terms of number of granules.	
OD_S3_01	Order Manager	no data				S-OMS-01090	The Order Manager shall validate the size of a request against request size limits in terms of size in GB, unless the request specifies subsetting.	
OD_S3_01	Order Manager	no data				S-OMS-01100	The Order Manager shall allow operators to configure request size limits in GB by media type.	
OD_S3_01	Order Manager	no data				S-OMS-01110	The Order Manager shall allow operators to configure separate request granule count limits depending on whether the request involves subsetting or not independent of media type.  [Note:  I.e., whether the request involves Landsat fixed or floating scenes]	
OD_S3_01	Order Manager	no data				S-OMS-01120	The Order Manager shall place on hold, i.e., not continue to process, requests that exceed a request limit.	
OD_S3_01	Order Manager	no data				S-OMS-01130	The Order Manager shall validate the size of each granule in a distribution request against the capacity limits of the specified media, unless the granule is being subsetted.	
OD_S3_01	Order Manager	no data				S-OMS-01140	The Order Manager shall place on hold, i.e., not continue to process, requests containing granules that violated the media capacity limit.	
OD_S3_01	Order Manager	no data				S-OMS-01150	The Order Manager shall ignore all configured size limits when processing requests which have been flagged as exempt from limit checking. 	
OD_S3_01	Order Manager	no data				S-OMS-01160	The Order Manager shall determine for each granule in a request that is to be staged from the ECS archive whether the granule is inaccessible because the granule UR that was provided is invalid.	
OD_S3_01	Order Manager	no data				S-OMS-01170	The Order Manager shall determine for each granule in a request that is to be staged from the ECS archive whether the granule is inaccessible to the requesting user because of QA access constraints.	
OD_S3_01	Order Manager	no data				S-OMS-01180	The Order Manager shall determine for each granule in a request that is to be staged from the ECS archive whether the granule is inaccessible because it was flagged as deleted from archive or logically deleted.	
OD_S3_01	Order Manager	no data				S-OMS-01190	The Order Manager shall flag inaccessible granules as skipped and annotate them with the reason for skipping (i.e., invalid UR, restricted, deleted from archive).	
OD_S3_01	Order Manager	no data				S-OMS-01200	The Order Manager shall exclude from validation granules that have been flagged as failed.	
OD_S3_01	Order Manager	no data				S-OMS-01210	The Order Manager shall place a request on hold that contains granules that were skipped.	
OD_S3_01	Order Manager	no data				S-OMS-01220	The Order Manager shall request operator intervention when it places a request on hold.	
OD_S3_01	Order Manager	no data				S-OMS-01230	When placing a data distribution request on hold, the Order Manager shall update its status to a value of 'Operator Intervention', and its last status change date/time attributes to the current date/time.	
OD_S3_01	Order Manager	no data				S-OMS-01240	When placing a data distribution request on hold, the Order Manager shall update the MSS status of the request to a value of 'Operator Intervention'.	
OD_S3_01	Order Manager	no data				S-OMS-01250	When requesting operator intervention the Order Manager shall identify the nature of the intervention, including (the complete list of types of intervention requests is TBD during design):    a. request exceeds media capacity  b. request exceeds maximum size  c. request exceeds maximum granule count  d. request contains inaccessible granules	
OD_S3_01	Order Manager	no data				S-OMS-01260	For a data distribution request that specifies physical media, the Order Manager shall submit a corresponding physical media distribution request to the PDS, including in it all granules that were not failed.	
OD_S3_01	Order Manager	no data				S-OMS-01280	The Order Manager shall allow operators to suspend the submission of requests to the PDS in total as well as by media type.	
OD_S3_01	Order Manager	no data				S-OMS-01285	The Order Manager shall detect the unavailability of the PDSIS and suspend the submission of requests to it when that occurs until it detects that it is available again or resumption by the operator.	
OD_S3_01	Order Manager	no data				S-OMS-01290	The Order Manager shall allow operators to resume the submission of requests to the PDS (in total as well as media type) if it was suspended.	
OD_S3_01	Order Manager	no data				S-OMS-01300	For a data distribution request whose granules must be staged from the ECS archive and that specify electronic media, the Order Manager shall submit corresponding asynchronous ACQUIRE requests for electronic distribution to the SDSRV CI, including in it all granules that were not  failed. 	
OD_S3_01	Order Manager	no data				S-OMS-01320	The Order Manager shall allow operators to suspend the submission of requests to the SDSRV in total as well as by media type.	
OD_S3_01	Order Manager	no data				S-OMS-01325	The Order Manager shall detect the unavailability of the SDSRV and suspend the submission of requests to it when that occurs until it detects that it is available again or resumption by the operator.	
OD_S3_01	Order Manager	no data				S-OMS-01330	The Order Manager shall allow operators to resume the submission of requests to the SDSRV (in total as well as by media type) if it was suspended.	
OD_S3_01	Order Manager	no data				S-OMS-01340	The Order Manager shall be able to limit the number of requests it processes concurrently.	
OD_S3_01	Order Manager	no data				S-OMS-01350	The Order Manager shall be able to limit the number of requests it submits concurrently to any component external to the Order Manager independently for each external component.	
OD_S3_01	Order Manager	no data				S-OMS-01360	The Order Manager shall log the following events as they occur to the Order Manager log file:  a. Start and shut down of the Order Manager  b. Suspension and resumption of any activities  c. Queuing new data distribution requests from the Order Manager Database  d. Queuing data distribution requests from the Order Manager Database that          were resubmitted  e. Generation of operator intervention requests  f. Dispatching a data distribution request to another component  g. retriable errors  h. non-retriable errors	
OD_S3_01	Order Manager	no data				S-OMS-01370	The Order Manager shall log the following information in the log file for each event, as applicable:  a. Unix Process ID  b. Date and time of the event (at least to the millisecond)  c. Type of event  d. Request ID  e. User ID  f. Error / event details such as shortname, version id, and granule id of the granule associated with the event, or file path name(s) of the file associated with the event, or service to which the request is being dispatched  	
OD_S3_01	Order Manager	no data				S-OMS-01380	The Order Manager shall generate a default name for the log file compatible with ECS log file names.	
OD_S3_01	Order Manager	no data				S-OMS-01390	The Order Manager shall append output to the log file if it already exists.	
OD_S3_01	Order Manager	no data				S-OMS-01400	The Order Manager shall create the log file if it does not already exist.	
OD_S3_01	Order Manager	no data				S-OMS-01410	Different instances of the Order Manager shall be able to operate in different modes concurrently.	
OD_S3_01	Order Manager	no data				S-OMS-01420	The Order Manager startup scripts shall prevent the operation of more than one Order Manager on the same platform in the same mode.	
OD_S3_01	Order Manager	no data				S-OMS-01425	The Order Manager startup scripts shall prevent the operation of more than one Order Manager in the same mode within the same DAAC.	
OD_S3_01	Order Manager	no data				S-OMS-01430	The Order Manager shall provide client applications with the ability to resubmit requests, e.g., in case of failures, such that a request will be executed only once even if it is submitted more than once.	
OD_S3_01	Order Manager	no data				S-OMS-01440	The Order Manager shall allow an operator to shut it down.	
OD_S3_01	Order Manager	no data				S-OMS-01450	The Order Manager shall be able to warm restart after abnormal termination or operator shut down such that no requests are lost or left in an inconsistent or unknown state.	
OD_S3_01	Order Manager	no data				S-OMS-01460	Upon warm restart, the Order Manager shall resume requests that were being processed at the time of shut down or abnormal termination before processing new requests.	
OD_S3_01	Order Manager	no data				S-OMS-01470	Upon warm restart, the Order Manager shall reinstate any suspensions that are currently in force.	
OD_S3_01	Order Manager	no data				S-OMS-01480	Client applications shall be able to submit data distribution requests whether the Order Manager is currently operating or not.	
OD_S3_01	Order Manager	no data				S-OMS-01500	The Order Management Service shall include provisions for removing operator interventions and related information from the database whose completion date/time exceeds a maximum age.	
OD_S3_01	Order Manager	no data				S-OMS-01502	The Order Management Service shall include provisions for removing actions from the database whose completion date/time exceeds a maximum age.	
OD_S3_01	Order Manager	no data				S-OMS-01505	The Order Management Service shall include provisions for removing orders, data distribution requests and related information from the database when the corresponding MSS order tracking information is removed from the database.	
OD_S3_01	Order Manager	no data				S-OMS-01506	The Order Management Service shall include provisions for removing notifications from the database whose sent date/time exceeds a maximum age.	
OD_S3_01	Order Manager	no data				S-OMS-01510	DAAC operations shall be able to configure the maximum age that controls the removal of information from the Order Management Database. [Note: The maximum age typically would be at lest several days]	
OD_S3_01	Order Manager	no data				S-OMS-02010	The Order Management Service shall provide a command line utility for submitting data distribution requests. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-02015	The Order Management Service Command Line Utility shall accept MSS user ID, order ID and request ID as optional parameters. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-02020	The Order Management Service Command Line Utility shall save the distribution request in the Order Management Database. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-02025	The Order Management Service Command Line Utility shall retry saving a distribution request to the database for a specifiable number of times after a specifiable wait time if it encounters a retriable database error, with the default being 2 times and a wait time of 10 seconds. [OSS]  [Note: specifiable means that there are two optional command line parameters for this]	
OD_S3_01	Order Manager	no data				S-OMS-02030	The Order Management Service Command Line Utility shall return status information indicating success or the nature of the failure of a request submission. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-02040	The Order Management Service Command Line Utility shall include provisions for resubmitting the same request in case of a fault during submission such that the request will be processed only once. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-02070	It shall be possible to submit data distribution requests in multiple modes concurrently via the Order Management Service Command Line Utility. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-02080	It shall be possible to submit multiple data distribution requests in the same mode concurrently via the Order Management Service Command Line Utility. [OSS]	
OD_S3_01	Order Manager	no data				S-OMS-03010	The Order Management Service shall provide an Operator GUI.	
OD_S3_01	Order Manager	no data				S-OMS-03020	The Order Management Operator GUI shall be accessible via the web browsers in the ECS configuration baseline.	
OD_S3_01	Order Manager	no data				S-OMS-03030	The Order Management Operator GUI shall permit an operator to suspend and resume the processing of new data distribution requests.	
OD_S3_01	Order Manager	no data				S-OMS-03040	The Order Management Operator GUI shall permit an operator to suspend and resume the submission of requests by the Order Manager to the PDS, in total and by media type.	
OD_S3_01	Order Manager	no data				S-OMS-03050	The Order Management Operator GUI shall permit an operator to suspend and resume the submission of requests by the Order Manager to the SDSRV, in total and by media type.	
OD_S3_01	Order Manager	no data				S-OMS-03055	The Order Management Operator GUI shall permit an operator to suspend and resume the sending of e-mail notifications.	
OD_S3_01	Order Manager	no data				S-OMS-03060	The Order Management Operator GUI shall permit an operator to view the current setting of all suspension options.	
OD_S3_01	Order Manager	no data				S-OMS-03070	The Order Management Operator GUI shall permit an operator to monitor for pending or held operator interventions.	
OD_S3_01	Order Manager	no data				S-OMS-03080	The Order Management Operator GUI shall permit an operator to select and view a pending or held operator intervention.	
OD_S3_01	Order Manager	no data				S-OMS-03082	The Order Management Operator GUI shall permit an operator to select a pending operator intervention, annotate it and place it on hold.	
OD_S3_01	Order Manager	no data				S-OMS-03084	The Order Management Operator GUI shall permit an operator to select a held operator request, update its annotation, and retain it on hold.	
OD_S3_01	Order Manager	no data				S-OMS-03090	The Order Management Operator GUI shall permit an operator to select and view the data distribution request associated with an operator intervention, as well as the associated order and user profile.	
OD_S3_01	Order Manager	no data				S-OMS-03100	The Order Management Operator GUI shall permit an operator to resubmit a data distribution request without changing it, effectively requesting that the Order Manager retry it, thereby implicitly completing the intervention request and removing it from its pending state.	
OD_S3_01	Order Manager	no data				S-OMS-03110	For distribution requests that were placed on hold because they failed a check against request size or media capacity limits, the Order Management Operator GUI shall permit an operator to exempt the request from limit checking and then resubmit it, thereby implicitly completing the intervention request and removing it from its pending state (Note: this effectively requests that the Order Manager retry the request without limit checking)	
OD_S3_01	Order Manager	no data				S-OMS-03120	The Order Management Operator GUI shall permit an operator to fail a data distribution request that was placed on hold. 	
OD_S3_01	Order Manager	no data				S-OMS-03130	When the operator fails a data distribution request, the Order Management Operator GUI shall insert an action for user notification into the Order Management Database including an optional operator annotation and the reason for failure, unless the operator explicitly requests the suppression of the user notification.	
OD_S3_01	Order Manager	no data				S-OMS-03135	The Order Management GUI shall remove an operator intervention from its pending state after the corresponding data distribution request has been failed.	
OD_S3_01	Order Manager	no data				S-OMS-03140	The Order Management Operator GUI shall permit an operator to assign a request that was placed on hold to a different media type.	
OD_S3_01	Order Manager	no data				S-OMS-03145	The Order Management Operator GUI shall permit an operator to fail a granule that exceeded the capacity of the media type. 	
OD_S3_01	Order Manager	no data				S-OMS-03150	The Order Management Operator GUI shall permit an operator to request the automatic partitioning of a data distribution request that was placed on hold because it exceeded request limits.	
OD_S3_01	Order Manager	no data				S-OMS-03160	The Order Management Service shall be able to partition a data distribution request into partitions of approximately equal size that is less than a target partition size limit and target granule count limit and assign them to new requests. [Design decision was to handle this in a stored procedure]	
OD_S3_01	Order Manager	no data				S-OMS-03170	The operator shall be able to configure the target partition size limit by media type, but no smaller than the capacity of that media and no larger than the request size limit for that media type.	
OD_S3_01	Order Manager	no data				S-OMS-03180	The operator shall be able to configure a target granule count limit for requests with and without subsetting, independent of media type.	
OD_S3_01	Order Manager	no data				S-OMS-03182	The Order Management Operator GUI shall support the pacing of partitioned requests over an extended time period based on operator input.	
OD_S3_01	Order Manager	no data				S-OMS-03210	The Order Management Operator GUI shall save the new requests resulting from partitioning in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-03215	The Order Management Operator GUI shall remove the operator intervention request from its pending state after a request was partitioned.  [Note: In this particular case, the operator has the responsibility for sending an email to the user if a notification is deemed necessary.]	
OD_S3_01	Order Manager	no data				S-OMS-03216	After a request that was routed through DORRAN has been successfully partitioned, the Order Management Operator GUI shall queue a request for sending a partitioning notice to DORRAN. 	
OD_S3_01	Order Manager	no data				S-OMS-03220	When reviewing an operator intervention request regarding skipped granules, the Order Management Operator GUI shall permit an operator to view the granule information stored in the OMS database for the granules that were skipped	
OD_S3_01	Order Manager	no data				S-OMS-03240	The Order Management Operator GUI shall permit an operator to accept the granules that were skipped as failed.	
OD_S3_01	Order Manager	no data				S-OMS-03242	The Order Management Operator GUI shall permit an operator to update the granule identifier of any granules that was skipped because the granule was inaccessible, thereby clearing its 'Skipped' status.	
OD_S3_01	Order Manager	no data				S-OMS-03244	The Order Management GUI shall allow an operator to resubmit a data distribution request that contained skipped granules after the status of each skipped granule was either cleared or changed to failed.	
OD_S3_01	Order Manager	no data				S-OMS-03250	The Order Management GUI shall allow an operator to resubmit a data distribution request whose MSS request tracking status is 'Canceled' or 'Cancelled', 'Aborted' or 'Abort', or 'Shipped'.	
OD_S3_01	Order Manager	no data				S-OMS-03260	The Order Management GUI shall allow an operator to edit a data distribution request whose MSS request tracking status is 'Canceled' or 'Cancelled', 'Aborted' or 'Abort', or 'Shipped' in the following ways:  a. Modify Media type and/or media parameters (e.g., FTP Push information or    physical media shipping address),  b. Select one or several granules and mark them as failed,  c. Automatically partitioning the request,  d. Update the granule identifier of one or several granules.	
OD_S3_01	Order Manager	no data				S-OMS-03262	[DESIRABLE]  When displaying a distribution request that is in a status of 'Canceled', 'Cancelled', 'Aborted', 'Abort', or 'Shipped' to the operator for resubmission, the Order Management GUI shall display the status of granules that are marked failed in the DDIST database as 'Skipped'.	
OD_S3_01	Order Manager	no data				S-OMS-03264	[DESIRABLE]  When editing a distribution request that is in a status of 'Canceled', 'Cancelled', 'Aborted', 'Abort', or 'Shipped', the Order Management GUI shall permit the operator to change the status of granules that are marked as 'Skipped' to 'Failed', or clear the 'Skipped' status (causing the granules to be excluded or included in the resubmission).	
OD_S3_01	Order Manager	no data				S-OMS-03270	For requests that contain failed granules, the Order Management Operator GUI shall generate a request for user notification including any optional operator annotation. [Design decision was to handle this in the email notification driver of the OM.]	
OD_S3_01	Order Manager	no data				S-OMS-03280	The Order Manager shall be able to include operator configurable text into the e-mail notifications it generates, compatible with current handling by the DDIST CI.	
OD_S3_01	Order Manager	no data				S-OMS-03290	The e-mail notifications generated by the Order Manager shall be backwards compatible in contents and format with the Distribution Notices created by the DDIST CI.	
OD_S3_01	Order Manager	no data				S-OMS-03310	The Order Management Operator GUI shall update the status of a request released from hold or resubmitted to 'Queued', and its last status change date/time attribute to the current date/time.	
OD_S3_01	Order Manager	no data				S-OMS-03320	The Order Management GUI shall update the MSS order tracking status for requests released from hold to 'Queued'.	
OD_S3_01	Order Manager	no data				S-OMS-03330	When saving requests resulting from partitioning in the Order Management Database, the Order Management Operator GUI shall set their status to 'Queued', their submission date/time attribute to that of the original request, and the last status date/time attribute to the current date/time.	
OD_S3_01	Order Manager	no data				S-OMS-03340	The Order Management GUI shall generate MSS order tracking information for any new data distribution requests it generates, and link them to the same order to which the partitioned request is linked.	
OD_S3_01	Order Manager	no data				S-OMS-03350	The Order Management Operator GUI shall update the status of a partitioned request to 'Partitioned', and its last status change date/time attribute to the current date/time.	
OD_S3_01	Order Manager	no data				S-OMS-03360	The Order Management GUI shall update the MSS order tracking information for partitioned requests to reflect a terminal status of 'Partitioned'. (Note: The partitioned requests are considered complete and replaced by the new requests)	
OD_S3_01	Order Manager	no data				S-OMS-03370	The Order Management GUI shall update the status of a request failed by the operator to 'Canceled', and its last status change date/time attribute to the current date/time.	
OD_S3_01	Order Manager	no data				S-OMS-03380	The Order Management GUI shall update the MSS order tracking information for a request failed by the operator to a status of 'Canceled'. 	
OD_S3_01	Order Manager	no data				S-OMS-03390	The Order Management GUI shall record the date/time and the nature of the disposition of an operator intervention in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-03400	The Order Management GUI shall record the changes made to a data distribution request in association with an operator intervention in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-03410	The Order Management GUI shall record an operator intervention, as well as any changes made for a 'Canceled', 'Cancelled', 'Aborted', 'Abort', or 'Shipped' data distribution request that was resubmitted by the operator in the Order Management Database.	
OD_S3_01	Order Manager	no data				S-OMS-03420	The Order Management GUI shall allow an operator to list past operator interventions, filter the list by creation time period (using today as the default), and to sort the list by date/time when the intervention was requested, the type of intervention, and associated request ID, order ID and user ID (individually and in any combination). 	
OD_S3_01	Order Manager	no data				S-OMS-03430	The Order Management GUI shall allow an operator to select a past operator intervention and view it. 	
OD_S3_01	Order Manager	no data				S-OMS-03440	The Order Management GUI shall allow an operator to list data distribution request, filter the list by one or several values of request status, creation time period (using today as the default), user, order, and request identification (individually or in any combination), and to sort the list by date/time of submission or last status change, request status, user, order, and request identification (individually or in any combination). 	
OD_S3_01	Order Manager	no data				S-OMS-03450	The Order Management GUI shall allow an operator to select a data distribution request from a request list or an operator intervention and view it, as well as the order and user profile associated with that data distribution request. 	
OD_S3_01	Order Manager	no data				S-OMS-03460	The Order Management GUI shall allow an operator to display the number of requests received during the preceding, operator selectable time interval, and their granule counts and total size for:  a. newly submitted requests, total and by media type  b. requests submitted to other services, total and by service	
OD_S3_01	Order Manager	no data				S-OMS-03470	The Order Management GUI shall support concurrent operation in multiple modes.	
OD_S3_01	Order Manager	no data				S-OMS-03480	An instance of the Order Management GUI shall interface with a single mode designated by the operator, for example, based on the specific web address or port chosen to start the GUI. 	
OD_S3_01	Order Manager	no data				S-OMS-03485	The Order Management GUI shall display the mode in which it is operating. 	
OD_S3_01	Order Manager	no data				S-OMS-03490	The capabilities of the Order Management GUI shall be accessible to multiple operators on multiple platforms concurrently. 	
OD_S3_01	Order Manager	no data				S-OMS-03500	The Order Management GUI shall be accessible whether or not the Order Manager for that mode is operating or not.	
OD_S3_03	Media Distribution for Subscriptions	no data				C-MSS-75290	The MSS Accountability Service shall allow identification of an order as a standing bundling order. [Note: MSS already identifies standing orders and allows one-time orders and requests to reference the standing order - see C-MSS-75200ff. However, since these standing bundling orders are unrelated to ASTER on-demand processing, a new type of standing order likely is needed]	
OD_S3_03	Media Distribution for Subscriptions	no data				C-MSS-75291	The MSS Accountability Service shall allow identification of an order and a request as being for a standing bundling order. [Note: corresponds to C-MSS-75200]	
OD_S3_03	Media Distribution for Subscriptions	no data				C-MSS-75292	The MSS Accountability GUI shall allow operators to list the standing bundling orders. [Note: corresponds to C-MSS-75230]	
OD_S3_03	Media Distribution for Subscriptions	no data				C-MSS-75293	The MSS Accountability GUI shall display the original Order ID along with other order tracking information.  [Note: corresponds to C-MSS-75250; may not require code changes]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05010	The Order Management Operator GUI shall permit an operator who is viewing operator interventions or data distribution requests, to view and edit any associated bundling order and view any bundle associated with the bundling order. [Note the overlap with the NSBRV requirements for viewing and editing bundling orders]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05040	The Order Management Operator GUI shall permit an operator to list bundles, filter the list by user ID, ID of the bundling order, and media type; and sort the list by user ID, ID of the bundling order and media type.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05050	The Order Management Operator GUI shall permit an operator to select a bundle from a bundle list and view its current size, granule count, creation date, and list the contained granules, as well as the associated bundling order and user profile. [Note: as per requirement S-SSS-10260 above, the operator should then also be able to list the associated subscriptions and pick one for viewing and editing]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05110	The Order Management Service shall accept bundled data distribution requests.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05112	For all data distribution orders submitted by the Spatial Subscription Service, the Order Management Service shall set the order source in the MSS order tracking information to 'NSBRV'. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05210	The Order Manager shall be able to recognize when a data distribution request is bundled, i.e., references a bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05220	The Order Manager shall add the granules in a bundled data distribution request to the bundle for that order, if one exists, else initiate a new bundle and add the granules to it. [Note: NSBRV will submit single granule requests only; however, the design should not be limited to bundled requests containing a single granule.] 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05250	The Order Manager shall check a bundle against the completion criteria of the related bundling order when adding granules to a bundle. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05260	The Order Manager shall check a bundle against the completion criteria of the related bundling order on a regular basis, according to an operator configurable time interval. [Note: this time interval would typically be between 15 minutes and several hours]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05270	The Order Manager shall consider a bundle complete if the total size of the granules in the bundle exceed the minimum bundle size, or its granule count exceeds the minimum bundle granule count, or if the age of any granule in the bundle, calculated as the time since the granule was inserted into the bundle, exceeds the maximum bundle age.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05290	The Order Manager shall create a data distribution request for the granules to be distributed from a bundle using the distribution information from the bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05310	The Order Manager shall submit the data distribution request created from a bundle to the Order Management Service for processing and distribution.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05320	The Order Manager shall create MSS order and request tracking information for the data distribution request created from a bundle, such that the requests are linked to a new, one time order that references the original bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05330	Once a bundle has been turned into a distribution request, it shall not longer be considered an active bundle by the Order Manager.. [Note: in one of the design alternatives, the fact that a request is a bundle is indicated by the request state; the requirement would be satisfied if the request is disassociated from the bundling order and/or its state is changed so it no longer represents an active bundle.] 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05340	The Order Manager shall be able to recover upon restart after a fault or shut down, the state of bundled requests, bundles, and distribution requests generated from bundles such that no granules are lost or distributed more than once.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-OMS-05510	The Order Management Service Command Line Utility shall allow the submission of data distribution requests that reference bundling orders. [OSS]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-05205	The Order Manager shall set the status of an MSS order representing a bundling order to 'Expired' after the expiration date of the bundling order. [Note: This could be done with some delay, though a delay of more than two hours is undesirable.]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10010	The NSBRV CI shall allow operators to enter bundling orders.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10020	The NSBRV CI shall store bundling order information persistently. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10030	The NSBRV CI shall assign a unique identification to each bundling order and display the ID to the operator.  	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10040	The NSBRV CI shall require the operator to associate the userid of a registered ECS user with a bundling order. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10050	The NSBRV CI shall allow the operator to enter an expiration date for a bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10055	The NSBRV CI shall allow the operator to configure a default expiration period that shall be used to set the expiration date for a bundling order if the operator does not provide one.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10060	The NSBRV CI shall not evaluate a subscription against ECS events which occur after the expiration date of the bundling order referenced by that subscription. [Note: I.e., the subscription is considered expired when the Bundling Order expires.]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10070	The NSBRV CI shall allow the operator to associate a mandatory email address of a maximum length of 255 characters with a bundling order. (The email will be used for distribution notifications). 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10080	The NSBRV CI shall provide, as the default email address, the email address in the ECS user profile for the userid associated with the bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10090	The NSBRV CI shall allow the operator to associate a userstring of a maximum length of 255 characters with a bundling order. (The userstring will be included in the Distribution Notice associated with the order.)	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10100	The NSBRV CI shall allow the operator to associate a distribution priority with a bundling order.   Valid distribution priorities shall be those accepted by ECS Data Distribution (DDIST).   	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10110	The NSBRV CI shall provide the distribution priority in the user profile of the userid associated with the bundling order as the default distribution priority.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10120	The NSBRV CI shall allow the operator to select a valid ECS physical media type for the bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10125	The NSBRV CI shall allow the operator to select ftp push or ftp pull as media types for a bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10130	The NSBRV CI shall allow the operator to enter the distribution options that are valid for the selected media type into a bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10140	The NSBRV CI shall require the operator to enter all distribution options into a bundling order that are mandatory for the selected media type.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10150	The NSBRV CI shall allow the operator to enter bundle completion criteria for a bundling order, i.e., the conditions under which a bundle for that order will be considered complete.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10160	The NSBRV CI shall support bundle completion criteria that include a minimum bundle size, a minimum bundle granule count, and a maximum bundle age. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10170	The NSBRV CI shall allow operators to configure a default value for the maximum bundle age. [Note: the maximum bundle age normally would be between one day and one month.]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10175	The NSBRV CI shall allow operators to configure a default value for the minimum bundle granule count.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10180	The NSBRV CI shall allow operators to configure a default value for the minimum bundle size by media type.  [Note: typically, minimum bundle size will be roughly equivalent to media capacity].	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10190	The NSBRV CI shall warn the operator when the operator configures a default or enters a value for the minimum bundle size that exceeds the configured maximum request size for that media type.  [Note: The NSBRV will not prevent the operator to exceed request size limits on purpose.  Later, when the Order Manager distributes the bundle, it will be placed on hold for exceeding maximum request size and require operator intervention to be distributed unmodified.  The same holds true if a distributed bundle exceeds the maximum granule count for a request.] 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10195	The NSBRV CI shall warn the operator when the operator configures a default or enters a value for the minimum bundle granule count that exceeds the configured request granule count limit for non-subsetted requests.  [Note: same observation as above applies]. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10200	The NSBRV CI shall allow the operator to select a distribution option from a list of valid options where the distribution option has an enumerated list of valid values.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10210	The NSBRV CI shall create a standing MSS order for each bundling order and maintain the relationship between that order and the bundling order.  [Note: The initial state for a bundling order is 'Pending'.  Other valid states include 'Expired' and 'Canceled']	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10212	The NSBRV CI shall set the order source for the MSS orders it creates to 'SSS', and shall append to this '-' plus the subscription ID if the order is not bundled. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10220	The NSBRV CI shall allow an operator to list bundling orders, displaying the bundling order ID, the user ID, creation date, expiration date, media type, and current status for each.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10230	The NSBRV CI shall allow an operator to filter a list of bundling orders by user ID, media type, and current status.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10240	The NSBRV CI shall allow an operator to sort a list of bundling orders by order ID, user ID, creation date, expiration date, media type, and current status.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10250	The NSBRV CI shall allow an operator to view all information about an individual bundling order by selecting it from a displayed list of bundling orders.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10260	The NSBRV CI shall allow an operator to list the subscriptions associated with a bundling order, and select a subscription from that list for viewing and editing.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10270	The NSBRV CI shall allow an operator to select a bundling order from a displayed list of bundling orders for modification.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10280	The NSBRV CI shall allow the operator to update the userid associated with an existing bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10285	The NSBRV CI shall propagate an update to the userid of bundling order to all the subscriptions associated with that bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10290	The NSBRV CI shall allow the operator to update the expiration date associated with an existing bundling order. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10300	The NSBRV CI shall allow the operator to update the e-mail address associated with an existing bundling order. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10310	The NSBRV CI shall allow the operator to update the userstring associated with an existing bundling order. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10320	The NSBRV CI shall allow the operator to update the distribution priority associated with an existing bundling order. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10330	The NSBRV CI shall allow the operator to modify the media type and distribution options associated with an existing bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10340	The NSBRV CI shall allow the operator to modify the bundle completion criteria associated with an existing bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10345	The NSBRV CI shall ask the operator to confirm the modifications to a bundling order before saving them.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10350	The NSBRV CI shall preserve the id of a bundling order when it is updated.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10360	The NSBRV shall maintain the information in the MSS order that is redundant to the information kept with a bundling order when the bundling order is modified.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10370	The NSBRV CI shall allow the operator to cancel an individual bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10374	When an operator cancels a bundling order, the NSBRV CI shall set the MSS state of the MSS order representing the bundling order to 'Canceled'.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10380	The NSBRV CI shall consider all subscriptions associated with a cancelled bundling order as cancelled.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10390	When entering a subscription, the NSBRV CI shall allow an operator to select one of the bundling orders for the user ID specified in the subscription as the distribution action.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10391	The NSBRV CI shall not permit a subscription to include distribution actions that reference more than one bundling order, or the same bundling order more than once, or a mix of actions that reference and do not reference bundling orders. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10392	When updating a subscription, the NSBRV CI shall allow an operator to select one of the bundling orders for the user ID specified in the subscription as the distribution action (if none exists).	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10394	When updating a subscription, the NSBRV CI shall allow an operator to select one of the bundling orders for the user ID specified in the subscription as a substitution for an existing distribution action.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10395	When updating a subscription associated with a bundling order, the NSBRV CI shall not permit the operator to change the user ID specified in the subscription [Note: the user ID is considered associated with the bundling order and is changed via the bundling order - see S-SSS-10285].	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10400	The NSBRV CI shall submit all ECS data distribution requests to the Order Management Service.  [Note, currently the NSBRV uses the SCLI].	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10405	The NSBRV CI shall submit only one ECS data distribution request per granule and bundling order, even if more than one of the subscriptions that reference the bundling order qualify for an event. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10410	When a subscription referencing a bundling order qualifies for an event, the NSBRV CI shall submit an ECS data distribution request corresponding to the specifications in the bundling order. 	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10420	When submitting an ECS data distribution request that corresponds to a bundling order, the NSBRV CI shall provide the MSS order ID of the bundling order.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10430	The NSBRV CI command line interface shall permit the submission of media subscriptions. [Note: The details of the interface are TBD by design, e.g., whether a separate bundling order is generated each time a media subscription is submitted; or whether the utility accepts the reference to a previously submitted bundling order.]	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10440	The NSBRV CI command line interface shall permit the viewing of media subscriptions.	
OD_S3_03	Media Distribution for Subscriptions	no data				S-SSS-10450	The NSBRV CI command line interface shall permit the editing of media subscriptions.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05870	The Data Pool Web Access Service shall allow users to order the granules in the shopping cart for distribution via any of the physical media offered by ECS. [NOTE: this is not intended to extend to HEG orders.  They will continue to be available only via FTP.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05872	The Data Pool Web Access Service shall allow the user to include in or exclude from the order the XML metadata files for the granules in the shopping cart.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05874	The Data Pool Web Access Service shall require the user to enter an e-mail address of a maximum length of 128 characters for the order. [NOTE: The maximum length is dictated by PDS capabilities.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05876	The Data Pool Web Access Service shall allow the user to provide a contact address for the order, compatible with the corresponding MSS data elements.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05878	The Data Pool Web Access Service shall allow the user to provide a string of a maximum length of 255 characters as identification or characterization of the order. [NOTE: This will be used to fill the Userstring parameter that is available for each order, and will be included in the Distribution Notice associated with the order.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05880	The Data Pool Web Access Service shall assign a configurable distribution priority with a default value of NORMAL to the orders it submits. [NOTE: The priority is actually assigned by the OMS database during submission.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05882	The Data Pool Web Access Service shall allow the user to select a valid ECS physical media type for the order.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05884	The Data Pool Web Access Service shall require the user to provide the shipping information for the order, compatible with the corresponding MSS data elements.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05886	The Data Pool Web Access Service shall warn the user if the distribution request exceeds any of the configured request limits.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05888	The Data Pool Web Access Service shall make media types unavailable as choices if the contents of the shopping cart exceed one of their request limits (e.g., media too small or order exceeds maximum order size for that media type). [NOTE:  This could result in no media type being available if the order is too large.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05890	The Data Pool Web Access Service shall make media types unavailable as choices if the contents of the shopping cart are less than the minimum request size for that media type (i.e., request is too small). [NOTE: This could result in no media type being available if the order is too small. This also will require the addition of a 'Minimum Request Size' configuration parameter for each media type.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05892	The Data Pool Web Access Service shall verify that all granules in a shopping cart are still in the Data Pool before submitting the order, and not submit the order and return an appropriate error indication flagging the unavailable granule(s) if that is the case.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05894	The Data Pool Web Access Service shall submit a data distribution request for the ordered granules and files to the OMS Database. [NOTE: The interface must employ the OMS stored procedures for request submission.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05896	The Data Pool Web Access Service shall empty the shopping cart after the data distribution request was successfully submitted to the OMS Database.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05898	The Data Pool Web Access Service shall display the assigned MSS order ID and the order status to the user after the data distribution request was successfully submitted to the OMS Database.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05899	The Data Pool Web Access Service shall permit a user to obtain the current status of an order in a form that is meaningful to the user. [It was agreed that the user's request would need to provide an order Id and for verification purposes, a matching Email address to obtain the order status.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05900	The Data Pool Web Access Service shall permit a user to bookmark the page displaying the order ID and status such that the user can use the bookmark later to obtain a current status of the order.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05902	The Data Pool Web Access Service shall display a meaningful error message to the user if the submission of the order into the OMS Database failed. [NOTE: The error messages must be reviewed with the DAACs during detailed design]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05904	The Data Pool Web Access Service shall allow a user to resubmit an order for a shopping cart if the submission of the order to the OMS Database failed.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05906	When re-submitting a data distribution request, the Data Pool Web Access Service shall guard against duplicate order submission by employing the corresponding capability of the Order Management Service.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-05908	The Data Pool Web Access Service shall exclude order only data from all web drill down results. [NOTE:  The requirement is satisfied by virtue of not populating the Data Pool inventory data that are used by drill down searches during insert of order only data.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14500	The Data Pool Cleanup Utility shall not remove granules from the data pool that are referenced by distribution requests that are not yet complete.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14512	The Data Pool Cleanup Utility shall remove the browse granules that are in the Data Pool for order-only purposes when they are no longer referenced by a distribution request that is not active (i.e., not in a terminal state), or for FTP Push request that is not yet expired.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14515	The Data Pool Cleanup Utility shall log granules that are not removed because they are referenced by distribution requests that have not yet completed.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14520	At the conclusion of a cleanup run, the Data Pool Cleanup Utility shall log the total number of granules that were not cleaned up because they are referenced by incomplete distribution requests, as well as their total size.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14525	The Data Pool Cleanup Service shall be able to remove granules at an average rate of at least 15,000 granules per hour concurrent with normal Data Pool insert activity. [NOTE: verification is part of WL_S4_01]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14530	The Data Pool Cleanup Service shall be able to remove at least 90,000 granules per day. [NOTE: verification is part of WL_S4_01]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-14535	The Data Pool Validation Function shall ignore order-only granules. 	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-40410	The DPM GUI shall be able to support effective monitoring of at least 450 concurrently active Data Pool inserts.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-40420	The DPM GUI shall allow a full capability operator to configure the maximum number of tape mounts that may be dispatched concurrently for a distribution request (see S-DPL-42340 on the use of this parameter).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42300	The Data Pool Insert Service shall not dispatch Data Pool inserts requested solely by the OMS if one of the following conditions is true: a. staging for OMS is suspended b. the sole reason for insert is distribution staging for a granule that was failed c. the sole reason for insert is a distribution request that is in a terminal state.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42310	The Data Pool Insert Service shall not dispatch Data Pool inserts that require access to an archive for which staging is suspended. [NOTE: a requirement for not dispatching inserts for a suspended volume group is specified in ticket OP_S4_06.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42320	The Data Pool Insert Service shall dispatch Data Pool inserts from cache according to effective priority, and within the same priority, by age (oldest first), where the effective priority of a request is calculated in accordance with the configured request aging policy parameter. [NOTE: The request aging parameters used on this occasion may be different from those used to satisfy S-OMS-06490.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42330	The DPL CI shall allow operators to configure the following request aging parameters for each ECS priority level: a. an aging rate indicating the amount by which the priority of a request shall increase for every hour that the request has been waiting, in the range of 0 to 100 (including decimal fractions in increments of 0.1). b. the maximum priority a request can attain through aging. [NOTE: Configuration can be via a DPL configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators. Note that these are the aging parameters for requests that are in the staging state and are waiting for tape mounts.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42340	The Data Pool Insert Service shall dispatch Data Pool inserts from tape according to the following policy: a. Tape mounts needed by distribution requests that are not in the Staging state or that reference resources that are currently suspended (such as media type or FTP destination) are not considered when deciding which archive tape to mount next. b. Tape mounts needed by distribution requests are not considered at all when the OMS suspended the queuing and dispatching of all distribution requests. c. Tape mounts are dispatched in queue order to the next available drive regardless of high or low water mark considerations, unless the tape mount is solely for a distribution request for which the configured maximum number of concurrent tape mounts has been reached. d. If a tape mount cannot be dispatched after rules a. and b. have been applied, tape mounts are dispatched in queue order regardless of other restrictions. e. The queue of requests for tape mounts is considered ordered by effective priority and within the same priority, by age (oldest first), where the effective priority is calculated in accordance with the configured request aging policy parameters.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42350	Once a tape has been selected for mounting, the Data Pool Insert Service shall dispatch the Data Pool inserts for all the granules that reside on that tape and for which a Data Pool insert has been requested, or for which there exists an active order (even if not in the staging state), until the configured maximum number of concurrent Data Pool inserts from archive is reached; and continue to dispatch these inserts whenever the number of concurrent Data Pool inserts from archive falls below this maximum again.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42360	The Data Pool Insert Service shall notify the OMS of the completion of a Data Pool insert action originating from the OMS and provide its completion status (including status details).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42370	The Data Pool Insert Service shall suspend inserts from an archive (silo) if more than a configurable number of consecutive Data Pool inserts from the same archive fail, or a Data Pool insert failed due the failure of an archive service, such as: a. the archive host cannot be reached despite retries (e.g., quick server or AMASS host is down). b. access to the AMASS files system fails despite retries (e.g., AMASS is down).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42390	The Data Pool Insert Service shall notify the OMS if it suspends the Data Pool inserts into a Data Pool file system	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42400	The Data Pool Insert Service shall be able to insert at least 90,000 granules per day. [NOTE: verification is part of WL_S4_01]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42410	The Data Pool Insert Service shall be able to achieve a peak Data Pool insert rate of at least 5,000 granules per hour. [NOTE: verification is part of WL_S4_01]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42420	The Data Pool Insert Service shall be able to support at least 400 concurrently active inserts from tape.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42440	The Data Pool Insert Service shall flag granules inserted into the Data Pool solely for ordering purposes as  order only granules.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42450	The Data Pool Insert Service shall not populate then following Data Pool inventory information when inserting order only granules: a. Data Pool data warehouse information b. Spatial coverage and spatial coverage maps c. Measured parameter information	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42460	The Data Pool Insert Service shall skip browse insert processing for order only granules.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42465	The Data Pool Insert Service shall perform browse insert for order-only purposes to allow for the ordering of Browse granules, and do so even if there is no associated science granule in the Data Pool.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42470	The Data Pool insert service shall consider insert requests for order only granules as successfully completed without any further processing (other than what is necessary to track the completion of the insert) if that granule already resides in the Data Pool. [This guards against potential race conditions where the OMS or DPL Insert Service may fail to recognize that a granule is already in the Data Pool or already queued for insert.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-42480	In case of Data Pool insert requests queued by Data Pool subscriptions or batch for granules that reside as order only in the Data Pool, the Data Pool insert service shall perform the additional insert processing steps necessary to make the granule fully visible to Data Pool users, including, if necessary, converting any associated Browse that resides in the Data Pool for order-only purposes into a regular Data Pool Browse granule. [This guards against the possibility that an order only insert occurs first.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-DPL-70010	The Data Pool Most Recent Inserts Utility shall not include order only granules in the listings of recent Data Pool inserts.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06000	The OM GUI shall display the OMS processing mode. [NOTE: There is currently no intent to allow operators to change the OMS processing mode via GUI.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06010	The OM GUI shall display the processing mode of a request in a request list if it is different from the current OMS processing mode.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06015	The OMS CI shall allow operators to configure the exceptions that determine whether a distribution request must be processed according to Synergy III mode even if OMS is operating in Synergy IV mode (see S-OMS-06465), to include: a. a list of ECS collections that must be processed in Synergy III mode b. a list of media types that must be processed in Synergy III mode c. a list of the Configured FTP Destinations that must be processed in Synergy III mode. [NOTE: Configuration can be via an OMS configuration script. If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06020	The OMS CI shall allow operators to configure the following capacity classes based on archive resource demands: a. the number of tape mounts which when exceeded, classifies an order as EXPENSIVE. b. the number of tape mounts which when exceeded classifies an order that is not EXPENSIVE as MODERATE (all orders with fewer tape mounts than this will be considered CHEAP) c. an optional limit on the maximum number of distribution requests in each size category that may be in the Staging state concurrently. [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06025	The OMS CI shall allow operators to configure the following distribution staging policy parameters for each physical media type: a. A request high water mark (RHWM), specifying the desired maximum number of requests that may be in the Staging state, or that completed staging but are not in a terminal state (such as Shipped). b. A data volume high water mark (DHWM) specifying the desired maximum data volume that may be in staging or staged but not yet shipped; the assumption being that if the data volume and the number of requests in these states is above DHWM, respectively RHWM, the media devices have plenty of work to keep them busy. c. A request low water mark (RLWM), specifying the desired minimum number of requests that should be in staging or staged. d. A data volume low water mark (DLWM) specifying the desired minimum data volume that should be in staging or staged but not yet shipped; the assumption being that if the number of requests or data volume in these states falls below RLWM, respectively DLWM, the media devices may soon be idle. [NOTE: The low water marks are also used in preemptive staging decisions.] [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06030	The OMS CI shall allow operators to configure a RHWM, DHWM and DLWM value for each Configured FTP Push Destination, as well as the General FTP Push Destination Group of FTP Push target hosts that have not been configured explicitly: [NOTE: FTP Push requires no RLWM] [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06035	The OMS CI shall allow operators to configure the following distribution staging policy parameters for FTP Pull: a.  A request high water mark (RHWM), specifying the desired maximum number of requests that may be in the Staging state. b. A data volume high water mark (DHWM) specifying the desired maximum data volume that may be in staging or staged but not yet expired. c. A preemption priority, i.e., the priority level at which an FTP Pull distribution request becomes eligible for pre-emptive staging (i.e., to be staged even if the FTP Pull area is at or above the DHWM or the number of requests in staging is above RHWM). [NOTE: FTP Pull requires no RLWM or DLWM; their roles is replaced by the preemption priority] [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06040	The OMS CI shall allow operators to configure the following request aging parameters for each ECS priority level: a. an aging rate indicating the amount by which the priority of a request shall increase for every hour that the request has been waiting, in the range of 0 to 100 (including decimal fractions in increments of 0.1). b. the maximum priority a request can attain through aging. [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators. Note that these are the aging parameters for a request waiting to be promoted into staging and while waiting for its granules to be ftp pushed.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06045	The OMS CI shall allow operators to configure up to at least 64 FTP push destinations, each uniquely identified by the target ftp host and directory, as Configured FTP Push Destinations. [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06050	The OMS CI shall allow operators to configure the following FTP Push policy parameters for each Configured FTP Push Destination: a. The maximum number of concurrent FTP Push operations for that Configured FTP Push Destination (with a default of 1). b. Whether the FTP operations for the Configured FTP Push Destination shall be timed out, and if so, FTP time out parameters consisting of the minimum expected throughput in MB/second and an additional timeout value in seconds, to be used to identify stuck FTP push operations. c. Whether the Configured FTP Push Destination is subject to automated retry when suspended, and if so, the time interval (in minutes) between automatic retries. [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06055	The OMS CI shall allow operators to configure a maximum number of FTP Push operations that may be in progress concurrently for all Configured FTP Push Destinations together. [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06060	The OMS CI shall allow operators to configure the FTP Push policy parameters specified in S-OMS-06050 also for the General FTP Push Destination Group of FTP Push Target Hosts that are not part of a Configured FTP Push Destination. [NOTE: A ftp target host may offer a number of directories for ftp push.  It is conceivable, albeit unlikely, that some of them are part of Configured FTP Push Destination, and some are not.  A FTP Push request referencing a directory on that host referenced in a Configured FTP Push Destination is considered to be for that destination and subject to its dispatching rules; a FTP Push request referencing a directory on that host not mentioned in a Configured FTP Push Destination would be considered to belong to the General FTP Destination Group an would be subject to the policies in force for that group.] [NOTE: The OMS will allow at most one FTP connection for any destination in the General FTP Destination Group.] [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06065	The OMS CI shall allow operators to configure on a global basis (i.e., irrespective of destination) a maximum number of consecutive ftp transfer failures for a destination (Configured FTP Push Destination or FTP Push Target Host) which - when exceeded - shall lead to the suspension of that destination (Configured FTP Push Destination or the corresponding FTP Push Target Host). [NOTE: This also guards against getting an excessive number of operator interventions.] [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06070	The OM GUI shall allow full capability operators to configure a minimum request size of each media type.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06075	The OMS CI shall allow operators to configure the retention time period for MSS/OMS order tracking information according to: a. whether the order completed successfully or not b. for successful orders, the source of the order (V0 Gateway, SIPS Machine-to-Machine Gateway, Subscriptions, Data Pool Web Interface, others), and the type of media (FTP Pull, FTP Push, secure copy, or physical media) [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06080	The OM GUI shall allow full capability operators to suspend staging for the Synergy IV processing mode.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06085	The OM GUI shall allow full capability operators to suspend staging for the Synergy IV processing mode by archive (silo).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06090	The OM GUI shall allow full capability operators to resume suspended staging for the Synergy IV processing mode.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06095	The OM GUI shall allow full capability operators to resume staging for the Synergy IV processing mode for an archive (silo) for which staging is suspended.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06100	The OM GUI shall indicate on its queue status monitoring screen whether staging is suspended for the Synergy IV processing mode.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06105	The OM GUI shall indicate on its queue status monitoring screen whether staging is suspended in the Synergy IV processing mode for a specific archive (silo).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06110	The OM GUI shall allow operators to display the overall distribution staging status for the Synergy IV processing mode, to include the total amount (number, MB) of ordered granules that are currently: a. waiting for staging, b. in staging, c. staged to the Data Pool but not yet shipped, d. staged and shipped, but still in the Data Pool[NOTE: this excludes data that were inserted into the Data Pool also for other reasons, such as when granules are ordered for FTP Push but are also inserted into the Data Pool via Data Pool insert subscriptions].	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06115	The OM GUI shall list the Data Pool file systems for which staging is suspended on its queue status monitoring screen.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06120	The OM GUI shall allow operators to display the overall distribution staging status for the Synergy IV processing mode by media type, and for FTP Push by Configured FTP Push Destination, and on the same display page, the corresponding staging policy parameter, such as disk low and high watermarks. [NOTE: DAAC operations indicated during the review that displaying request low/high watermarks would not be useful to them and just consume extra screen real estate.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06125	The OM GUI shall allow operators to display the number of Synergy IV OMS distribution requests that are currently in staging.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06130	The OM GUI shall allow operators to display the number of Synergy IV OMS distribution requests that are currently in staging by media type, and for FTP Push, by Configured FTP Push Destination as well as the General FTP Push Destination Group.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06135	The OM GUI shall allow operators to filter the distribution request list so it shows only the distribution requests in specific states, such as those that: a. are currently in the staging state, b. are in the staging state but no granules have been staged for them as yet, c. are in the staging state and have begun but not yet completed staging, d. have completed staging (i.e., all granules are staged) but are yet shipped, e. (for FTP Push requests) have begun FTP Push, f. have been submitted to PDS. (i.e., are no longer managed by OMS), g. have shipped. [NOTE: The lists of states shall be completed during preliminary design.  It is desirable to use the existing MSS states to characterize the state of a request.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06140	The OM GUI shall allow operators to AND the filter on request state and media type when filtering requests.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06145	The OM GUI shall allow operators to display in the list of requests, for each request the number of granules that have been staged.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06150	The OM GUI shall display the capacity class to which a request was allocated in the list of requests.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06155	The OM GUI shall allow operators to sort the list of requests by the capacity class to which each was allocated.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06160	The OM GUI shall allow operators to display in the list of granules for a given request, the staging status of each granule.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06165	The OM GUI shall allow operators to sort the list of granules for a given request by their staging status.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06170	The OM GUI shall allow operators to display the number of FTP Push operations in progress. [NOTE: An FTP push operation is the process of transferring a granule via FTP to its FTP destination.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06175	The OM GUI shall allow operators to display in the list of FTP Push distribution requests, for each request its destination (Configured FTP Push Destination or FTP Push Target Host) and the number of granules that have been pushed.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06180	The OM GUI shall allow operators to sort the list of FTP Push requests by destination (Configured FTP Push Destination or FTP Push Target Host).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06185	The OM GUI shall allow operators to display in the list of granules for a given FTP Push request, its FTP Push status (e.g., whether the granule completed push or not).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06190	The OM GUI shall allow operators to sort the list of granules for a given FTP Push distribution request by their FTP Push status. [NOTE: This is only significant if the request has begun but not yet completed FTP Push.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06195	The OM GUI shall allow full capability operators to suspend the dispatching of FTP Push operations for any destination (i.e., Configured FTP Push Destination or FTP Push Target Host).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06200	The OM GUI shall allow operators to display a list of the suspended FTP Push destinations (i.e., Configured FTP Push Destination or FTP Push Target Host), including when they were suspended, whether they were suspended automatically by the system or manually by the operator, and the amount of data (number of granules, MB) queued for each.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06205	The OM GUI shall allow operators to view details about a suspended destination (i.e., Configured FTP Push Destination or FTP Push Target Host), to include the list of FTP Push operations that caused the suspension and the list of the FTP Push requests that are associated with the destination and are not in a terminal state.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06210	The OM GUI shall allow full capability operators to resume dispatching of FTP Push operations to a suspended destination (i.e., Configured FTP Push Destination or FTP Push Target Host).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06220	The OMS GUI shall allow full capability operators to configure the time period for which granules for FTP Pull requests shall be retained, as well as the retention priority they shall be assigned. [NOTE:  The retention period shall apply to all FTP Pull requests which have not yet completed staging (i.e., their expiration time has not yet been updated by the OMS).]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06225	The OM GUI shall allow operators to view operator interventions related to staging (i.e., failed Data Pool inserts) and FTP Push (i.e., failed ftp push operations that did not cause the destination to be suspended).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06230	The OMS shall allow operators to configure an optional e-mail address to which notifications about alerts and interventions shall be sent. [NOTE: Configuration can be via an OMS configuration script.  If it is via GUI, the capability to change these values must be restricted to full capability operators.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06235	The OMS CI shall send an e-mail containing the information regarding an alert or an operator intervention to the configured email address, if such an email address was configured.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06240	The OM GUI shall allow full capability operators to disposition interventions related to staging and FTP Push by having the staging/ftp push operation retried, failing the corresponding granule, or failing the distribution request. [NOTE: See corresponding requirements for the Data Pool Insert Service to react to request cancellations.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06245	The OM GUI shall allow operators to monitor for operator alerts. [NOTE:  The list of alerts includes suspension of the following due to errors: a/ FTP destination; b/ archive; c/ Data Pool file system; d/ PDS submissions; e/  SDSRV submissions.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06250	The OM GUI shall allow operators to view FTP Push operator alerts.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06255	The OM GUI shall display the current status of the FTP Push destination (i.e., Configured FTP Push Destination or FTP Push Target Host) when displaying an FTP Push alert. 	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06260	The OM GUI shall allow full capability operators to list the FTP Push distribution requests associated with the destination (i.e., Configured FTP Push Destination or FTP Push Target Host) that is the subject of the FTP Push alert being viewed. [NOTE: This is the same list as if the operators had selected the destination from a list.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06262	The OM GUI shall allow full capability operators to resume dispatching to the destination (i.e., Configured FTP Push Destination or FTP Push Target Host) that is the subject of the FTP Push alert they are viewing.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06265	The OM GUI shall allow full capability operators to edit the FTP Push parameters of a request for a suspended destination (i.e., Configured FTP Push Destination or FTP Push Target Host). [NOTE: This would allow operators to correct failures due to a changed password or ip address. If host or directory is updated, the request might now match a destination group that is different from the one to which it was assigned originally.  If that occurs, the OMS is not required to reallocate the request to that new group and recompute staging and ftp push policy limits.  Rather, the request is allowed to run to completion in the FTP Push destination group to which it is currently allocated..]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06270	The OM GUI shall allow operators to apply the updates to the FTP Push parameters of a request mentioned in S-OMS-06265 to all FTP Push requests for that destination (i.e., Configured FTP Push Destination or FTP Push Target Host) that are not yet in a terminal state. [NOTE: As a result, these requests may now be allocated to a different destination group.  OMS is not required to apply this change to any requests that are currently in progress, i.e., no longer 'Queued'.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06275	The OM GUI shall generate an operator intervention for all updates to request information made by the operator, and allow operators to identify the person who made the change and the reason for the change.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06280	The OM GUI shall allow full capability operators to alter the status of an automatically suspended destination (i.e., Configured FTP Push Destination or FTP Push Target Host) from automatic resumption to manual resumption. [NOTE: This means that the OMS will not continue to retry resuming the FTP Push operation to the destination.  Instead, the destination must be resumed by the operator.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06285	The OM GUI shall identify the archive affected by an archive related operator alert when listing alerts. 	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06290	The OM GUI shall allow operators to view operator alerts regarding archives. 	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06295	The OM GUI shall identify the Data Pool file system affected by an operator alert related to Data Pool file system when listing alerts.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06300	The OM GUI shall allow operators to view operator alerts regarding Data Pool file systems. [NOTE: the details of the information to be displayed should be determined in cooperation with the DAACs during preliminary design. Resumption of Data Pool inserts to a specific Data Pool file system is the subject of Data Pool Maintenance GUI requirements, see ticket OP_S4_06]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06305	The OM GUI shall allow full capability operators to alter the priority of a distribution request while granules for the request still need to be staged.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06310	The OM GUI shall allow full capability operators to alter the priority of a FTP Push requests while granules for the request still need to be pushed.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06315	The OM GUI shall allow full capability operators to suspend a distribution request while granules for the request still need to be staged (i.e., not all granules have completed staging or have been otherwise dispositioned).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06320	The OM GUI shall allow full capability operators to suspend a FTP Push requests while granules for the request still need to be pushed.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06325	The OM GUI shall allow full capability operators to resume a distribution request that was suspended by the OM GUI operator. 	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06330	The OM GUI shall allow full capability operators to suspend the processing of new requests by the OMS. [NOTE: This is mean to emulate the 'suspend all new requests' function of DDIST and is different from S-OMS-01040 in OD_S3_01, since it places the individual requests into Operator Intervention and does not affect the processing and dispatching of requests that are not 'new'.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06335	The OM GUI shall allow full capability operators to resume an individual request while the processing of new requests by the OMS is suspended.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06340	The OM GUI shall allow full capability operators to resume the processing of new requests by the OMS if it has been suspended by the OM GUI operator.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06345	The OM GUI shall allow full capability operators to cancel a distribution request that is not in a terminal state and while granules for the request still need to be staged	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06350	The OM GUI shall allow full capability operators to cancel a FTP Push distribution request that is not in a terminal state and while granules for the request still need to be pushed.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06355	The OM GUI shall generate an operator intervention for all request cancellations and allow operators to identify the person who cancelled the request and the reason for cancellation.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06360	The OM GUI shall require operators to confirm the cancellation of a distribution request.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06365	The OM GUI shall provide access to its ability to cancel, suspend and resume distribution requests for any eligible request appearing in a request list, or while such a request is being viewed by an operator. [NOTE: The intent of this requirement is to ensure that the ability to cancel, suspend and resume requests that are under OMS control is available from all screens this list requests, e.g., in response to alerts, filters, etc.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06370	The OM GUI shall update the MSS status of a distribution request to 'Operator Intervention' when it is suspended by the operator. [NOTE: the status update may actually be performed by an OMS database procedure.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06375	The OM GUI shall update the MSS status of a suspended distribution request to the state it had before the request was suspended. [NOTE: The status update may actually be performed by an OMS database procedure.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06380	The OM GUI shall update the MSS status of a distribution request to 'Cancelled' when it is cancelled by the operator. [NOTE: the status update may actually be performed by an OMS database procedure.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06385	The OM GUI shall allow operators to filter the list of distribution requests by any combination of states, similar to the current DDIST GUI.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06390	The OM GUI shall not display an OMS Server Summary Statistics page. [NOTE: This rescinds S-OMS-03460, based on DAAC input that these summary statistics are not used operationally.  This obviates the need to update the page with statistics for the OMS processing threads that are new to Synergy IV.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06395	The OMS CI shall accept data distribution requests for pre-staged data that specify a list of granules containing identifiers other than an ECS granule UR, and for each granule, a list of the files to be distributed for that granule, including their absolute path names. [NOTE: the files must be accessible at that location from the platforms performing the distribution]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06405	The OMS CI shall accept data distribution requests that specify for all granules either a valid list of ECS granule UR, or a list of ECS granule id or a list of Data Pool granule Id.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06415	When validating the size of an order against established limits, the OMS CI shall use for pre-staged granules, their sizes as specified in the OMS database rather than looking the size up in the ECS inventory.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06420	The OMS CI shall assume that pre-staged granules are not restricted.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06425	The OMS CI shall assign and return a MSS order ID to requests that are submitted to the OMS and do not provide one. [NOTE: required to support the interface to the Data Pool web GUI for order submission].	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06430	The OMS CI shall assign and return a MSS request ID to requests that are submitted to the OMS and do not provide one. [NOTE: required to support the interface to the Data Pool web GUI for order submission].	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06435	The OMS CI shall send an e-mail containing the order information to the user as order confirmation after the data distribution request was successfully submitted to the OMS Database.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06440	The OMS CI shall include a DAAC configurable preamble in the email message sent according to S-OMS-06435.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06442	The OMS CI shall include in the e-mail confirmation the URL via which the user can obtain the status for this order.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06445	The OMS CI shall support two processing modes: a. Synergy III ('old') processing mode. b. Synergy IV ('new') processing mode.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06450	The OMS CI shall allow DAAC operations to switch from one processing mode into the other, e.g., via a utility, while the OMS is not operating but while orders are queued and/or in process.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06455	The OMS CI shall submit physical media distribution requests from the Data Pool Web GUI to the PDS, including the absolute path for each file and the relevant size information, regardless of processing mode. [NOTE: this requirement applies regardless of the processing mode in which the OMS operates.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06460	When operating in Synergy III mode, the OMS CI shall process all requests except those submitted via the Data Pool Web GUI according to Synergy III system flows, i.e.: a. Physical media distribution requests shall be submitted to the PDS. b. Electronic media distribution requests shall be submitted to the SDSRV. c. The OMS CI shall not queue granules for insertion into the Data Pool.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06465	When operating in Synergy IV mode, the OMS CI shall process the following requests according to Synergy III mode unless their granules are pre-staged: a. Requests that were routed through the DORRAN billing system. b. Requests that contain restricted granules. c. Requests that contain granules belonging to a list of ECS collections that is configurable by DAAC operations. d. Requests containing granules whose collections are not configured and enabled for Data Pool insert or configured for metadata-only inserts. e. Requests for distribution on media types configured for processing via Synergy III ops mode. [NOTE: We plan to handle secure FTP in this fashion.] f. FTP Push requests for  Configured FTP Push Destinations that were configured for processing via the Synergy III ops mode.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06470	When processing a distribution request in Synergy IV mode, the OMS CI shall classify a request as CHEAP, MODERATE, or EXPENSIVE in accordance with the configured size classification parameters, substituting suitable default values if none have been configured by the operator.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06475	When processing a distribution request in Synergy IV mode, the OMS CI shall determine whether any of its granules that are not identified as pre-staged do reside in the Data Pool or in an archive cache or on an archive tape.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06480	When processing a request in Synergy IV mode, the OMS CI shall queue Data Pool insert actions for any granules that do not reside in the Data Pool but are in an archive cache, unless the granule is marked failed or the request is in a terminal state (e.g., was cancelled by the operator). [NOTE: This would include staging the files for a granule that currently only has its metadata in the Data Pool.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06485	When processing a request in Synergy IV mode, the OMS CI shall queue distribution requests that require granules from an archive tape for promotion into the Staging state, unless the granule is marked failed or the request is in a terminal state (e.g., was cancelled by the operator). [NOTE: Requests that are suspended or terminated are no longer considered to be in the Queued state.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06490	The OMS CI shall promote distribution requests that are queued for promotion into the staging state according to the following policy (see  S-OMS-06020 to S-OMS-06040) for the meaning of the various configuration parameters referenced here), unless the queuing and dispatching of all requests is suspended or they reference a resource (such as archive., Data Pool file system. Media type, and Configured FTP Push Destination or FTP Push Target Host) that is currently suspended: a. Distribution requests shall be promoted to the Staging state in queue order (i.e., by effective priority and within the same priority by age) as long as the requests are at a position in the queue that would be below the low watermarks for the respective media type or corresponding FTP destination (i.e., Configured FTP Push Destination or General FTP Push Destination Group), or above the configured preemptive dispatch priority for FTP Pull. b. Distribution requests for each physical media type or FTP Push shall be promoted into the Staging state in queue order as long as the number of requests and data volume for that media type are below the corresponding configured RHWM and DHWM. c. However, requests in a size category for which the maximum number of distribution requests currently in the staging state is at or above the configured limit for that size category will not be promoted into the Staging state. d. The effective priority of a request is calculated in accordance with the configured request aging policy parameters. [NOTE: This would include staging the files for a granule that currently only has its metadata in the Data Pool.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06495	The OMS CI shall promote the next distribution request (in queue order) into the staging state regardless of the rules a., b., c., and d. specified in S-OMS-06490 that references only granules from archives that have tape drives available, yet for which there are no requests in the Staging state that still require granules from those archives. [NOTE: This guards against idling archives, but also against overloading other archive queues just because one is underutilized.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06500	The OMS CI shall request Data Pool insert actions for granules that need to be retrieved from archive tapes. [NOTE: The rules for dispatching Data Pool insert actions are specified in requirements S-DPL-42300 through S-DPL-42350.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06505	The OMS CI shall derive a Data Pool insert dispatch priority from the distribution request priority according to the existing priority translation table, and assign that priority to the Data Pool insert actions it queues.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06510	The OMS CI shall assign a Data Pool retention period of 0 and priority of 1 to the Data Pool insert actions it queues. [NOTE: For FTP Pull distribution requests, this will be updated again before the request is marked Shipped.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06515	The OMS CI shall identify itself as the request source in the Data Pool insert actions it queues.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06520	The OMS CI shall accept notifications from the DPL CI that signal the completion status of a Data Pool insert action requested by the OMS CI.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06525	The OMS CI shall propagate the Data Pool insert completion status (including detailed status) of a granule to the corresponding granule entries in the requests that reference the granule.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06530	The OMS CI shall queue an operator intervention for a request when one of its granules failed staging, i.e., failed Data Pool insert.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06535	The OMS CI shall maintain a record of the staging throughput statistics in the OMS database on the basis of 15 minute time intervals, to include the total amount (number, MB) of ordered granules that were: a. found in the Data Pool, b. submitted for staging (differentiated between staging from cache and from tape), c. completed staging to the Data Pool successfully (differentiating between what was staged from cache versus read from tape), d. returned with staging error (differentiating between cache v. tape).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06538	The OMS CI shall assume that an archive failure occurred when more than a configurable number of consecutive Data Pool inserts from the same archive fail.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06539	TThe OMS CI shall recognize the failure of an archive service, such as: a. the archive host cannot be reached despite retries (e.g., quick server or AMASS host is down). b. access to AMASS fails despite retries (e.g., AMASS is down).	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06540	The OMS CI shall suspend staging for an archive and queue a corresponding operator alert if it recognizes or is supposed to assume the occurrence of an archive failure.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06545	The OMS CI shall queue a corresponding operator alert if the response from the Data Pool insert service indicates a failure with a Data Pool file system.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06550	When processing a physical media distribution request in Synergy IV mode, the OMS CI shall queue the request for submission to the PDS once all of its granules are available in the Data Pool or have been dispositioned by operators.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06555	The OMS CI shall include the XML metadata file associated with each granule in the submission of a request to the PDS unless the distribution request specifies otherwise.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06560	The OMS CI shall accept notifications regarding the rejection(i.e., cancellation) by a PDS operator of Synergy 4 distribution requests that it submitted to the PDS.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06565	When operating in Synergy IV mode, the OMS CI shall queue the granules that belong to FTP Push distribution requests for FTP push as soon as each granule becomes available in the Data Pool, unless the request is in a terminal state (e.g., if the request was cancelled in the mean time) or still waiting to be promoted into the Staging state, or once all granules are in the Data Pool or otherwise dispositioned. [NOTE: The latter would be the case if the request never needs to go into the Staging state.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06570	The OMS CI shall be able to dispatch FTP Push operations in accordance with the operator configured FTP Push policy parameters, and within the limitations of this policy in effective priority order and within the same priority on a first in first out basis, where the effective priority of a request is calculated in accordance with the configured request aging policy parameters.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06575	The OMS CI shall not dispatch FTP Push operations for granules that are marked failed or for requests that are in a terminal state (e.g., cancelled by the operator) or are suspended, or if the FTP Push destination (i.e., Configured FTP Push Destination or FTP Push Target Host) is currently suspended, or if the dispatching of all distribution requests is currently suspended. [NOTE: the OMS FTP Push service will not remove files from a target host that have already been pushed and are part of a failed granule; the DN needs to contain adequate information to allow the user to identify the file(s) that represent an incomplete granule.].	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06580	The OMS CI shall use the FTP parameters specified in the distribution request to perform the FTP Push operations for its granules.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06585	The OMS CI shall include the XML metadata file associated with a granule in the FTP Push operation unless the request specifies otherwise.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06590	The OMS CI shall not dispatch more concurrent FTP Push operations for a Configured FTP Push Destination than the maximum permitted by the corresponding configuration parameter.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06595	The OMS CI shall not dispatch more than one concurrent FTP Push operation for a destination in the General FTP Push Destination Group.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06600	The OMS CI shall not dispatch more concurrent FTP Push operation for destinations belonging to the General FTP Push Destination Group (i.e., for destinations not explicitly configured) than the limit configured for this group.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06605	The OMS CI shall not dispatch more concurrent FTP Push operation for all Configured FTP Push Destinations together than the configured overall limit.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06610	The OMS CI shall push the metadata and science files for single file granules over the same FTP push connection. [Note: To be verified by code inspection.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06615	The OMS CI shall maintain a record of FTP Push throughput by destination (i.e., Configured FTP Push Destination or FTP Push Target Host) in the database.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06620	The OMS CI shall consider an FTP Push operation failed and cancel it if it exceeds its maximum allowed execution time as calculated from the corresponding configuration parameters, provided that they have been configured for that FTP destination. 	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06625	The OMS CI shall suspend the dispatching of FTP Push operations for a destination if an FTP Push operation to that destination fails for one of the following reasons: a. An FTP Push operation exceeded its maximum allowed time. b. The connection with the target FTP host could not be established. c. The ftp login to the destination failed. d. There is insufficient space on the target host. e. There are N consecutive transfer failures for the same destination, where N is configurable by operations on a global basis (i.e., not specific to a destination). [NOTE: The suspension does not affect concurrently ongoing FTP Push operations to that destination.  They are likely to fail as well, or may succeed but in that case would not alter the state of the destination.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06630	The OMS CI shall queue an operator alert when it suspends the dispatching of FTP Push operations for a destination. [NOTE: This is different from request specific interventions.  When an FTP push request fails, the destination is suspended and the operator is notified of the suspension, but the granules remain queued for FTP Push distribution.  They will be retried automatically once the destination is resumed.  Since the OMS resumes FTP Push operations automatically if a retry to the destination is successful, the destination may be already back in operation by the time the operator may be ready to resume it manually.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06635	If multiple concurrent FTP Push operations fail for the same FTP destination, the operator shall be alerted only once.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06640	The OMS CI shall retry FTP Push to an automatically suspended destination on a periodic basis in accordance with the FTP Push policy, unless the suspension has been changed by the operator to require manual resumption.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06645	The OMS CI shall resume dispatching of FTP Push operations to a suspended destination if the periodic retry of FTP Push to that destination succeeds.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06650	The OMS CI shall mark a pending operator alert about a suspended FTP destination as completed when it resumes dispatching to that destination.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06655	The OMS CI shall queue an action for sending a Distribution Notice (DN) after all granules for an FTP Push request have either been pushed successfully or otherwise dispositioned by the operator.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06660	The OMS CI shall queue an action for sending a DN after all granules for an FTP Pull request have completed insertion into the Data Pool successfully or been otherwise dispositioned by the operator.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06662	The OMS CI shall log an error when the mail submission for a DN fails (e.g., because it was rejected by the mail server) and forward the DN with an appropriate error indication to a DAAC configurable e-mail address. [NOTE: This can be the same e-mail address that is used as Reply To address for DNs.  If the forwarding of the DN fails, e.g., because the e-mail address is not configured or configured incorrectly, this should be considered as an additional error and logged, but there is no need to try additional alternate e-mail addresses.]  	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06665	The OMS CI shall create a directory for the FTP Pull request (similar to the STMGT Pull Monitor) and populate it with links that point to the files for that request and have the same names as the files.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06666	The OMS CI shall remove the directories for FTP Pull requests after the requests expired and shall do so no later than midnight (24:00 hours) of the day following their expiration. [NOTE: The manner in which this is accomplished is left to the implementation.  It is assumed that the OMS CI will update the current high watermark for FTP Pull on this occasion, as well.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06670	The OMS CI shall update the Data Pool expiration time and retention priority of any granule that is referenced by an FTP Pull request before marking the request as complete in accordance with the corresponding FTP Pull configuration parameters, unless the result would be lower than the corresponding current values of that granule.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06673	The OMS CI shall send DN that are backwards compatible with the DN currently sent by DDIST, however, the DN shall list the failed granules and their failure reasons.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06675	The OMS CI shall update the MSS status of a request to 'Staging' when it is promoted into the Staging state.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06680	The OMS CI shall update the MSS status of a FTP Push request to 'Transferring' once all granules have been staged or otherwise dispositioned and at least one granule has been dispatched for FTP Push. [NOTE:  Backwards compatible with DDIST.  Note that granules may be pushed while others are still staging, i.e., while the request is still in the Staging state.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06685	The OMS CI shall update the MSS status of a FTP Push request to 'Shipped' once all granules have been pushed or otherwise dispositioned and the DN has been sent.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06690	The OMS CI shall update the MSS status of a FTP Pull request to 'Shipped' once all granules have been staged or otherwise dispositioned and the DN has been sent. [NOTE:  Backwards compatible with DDIST.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06695	The OMS CI shall use the DAAC configured retention time period to determine when the order tracking information for an order is considered expired.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06700	The OMS CI shall consider the expiration date of an order to be the completion date of the order plus the retention time period, and for FTP Pull orders, plus the FTP Pull expiration time in effect for that order.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06705	The OMS CI shall allow DAAC operators to remove order tracking information for orders that are past their expiration date. [NOTE:  The capability can be a command line utility suitable for execution via cron.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06710	The OMS CI shall log the following events: a. Errors b. Submission of a granule for staging. c. Completion of the staging of a granule d. Start of an FTP Push operation e. Completion of the FTP Push operation f. Suspension of an FTP Push destination g. Resumption of an FTP Push destination h. Sending of a DN i. Cancellation of an FTP Push operation	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06715	The OMS CI shall log the following information with each logged event as applicable and available: a. priority, identification and description of the error b. request ID c. granule ID and/or file path name, d. size of a granule or file e. media type, and for FTP Push, the destination	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06720	The OMS CI shall support performance logging. [NOTE: The types of events to be included in performance logging would be TBR during detailed design.]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06725	The OMS CI shall generate alerts when it suspends the submission of requests automatically.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-OMS-06730	The Order Management Service Command Line Interface shall accept data distribution requests for pre-staged data that specify a list of granules containing identifiers other than an ECS granule UR, and for each granule, a list of the files to be distributed for that granule including their absolute path names, as well as the size of each granule or file. [NOTE: To be resolved by preliminary design.  Non ECS UR might be a DPL granule ID or a Local Granule ID]	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00010	The PDSIS shall accept physical media distribution requests for pre-staged granules from the OMS.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00020	The PDSIS shall format data distribution requests for pre-staged data into granule packages and save them for processing by the PDS.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00030	The PDSIS shall not submit staging requests to ECS for pre-staged data.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00040	The PDSIS shall not remove pre-staged granules from disk.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00050	The PDS shall distribute pre-staged granules from their staging locations.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00060	The PDS shall accept metadata files in XML format, as well as allow for distribution of granules without metadata files.	
OD_S4_01	Improve Distribution to End Users through Data Pool	no data				S-PDS-00070	The PDS shall notify the OMS CI when the PDS operator rejects (i.e., cancels)  distribution requests for pre-staged granules that it received form the OMS.	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				C-CSS-51010	The MTMGW CI shall support a new configuration parameter that specifies the manner of order submission to be either to the Order Management Service (OMS) or the ECS Science Data Server (SDSRV), and submit orders to the OMS or SDSRV in accordance with the setting of this configuration parameter.	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				C-CSS-51020	When configured to submit orders to the OMS, the MTMGW shall translate a product request into the form required by the OMS interfaces and interface with the OMS software (i.e., stored procedures) as necessary to save it in the OMS database and queue an action for the Order Manager.	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				C-CSS-51030	When configured to submit orders to the OMS, the MTMGW CI shall return any new types of responses it may receive from the OMS when submitting orders and return them to its client in accordance with C-CSS-50450 and 50460 in Ticket RM_6A_05.	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				C-CSS-51040	When configured to submit orders to the OMS, the MTMGW CI shall retry saving a product request to the database for a specifiable number of times after a specifiable wait time if it encounters a retriable database error, with the default being 2 times and a wait time of 10 seconds.	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				C-CSS-51050	When configured to submit orders to the OMS, the MTMGW CI shall use the provisions in the OMS for resubmitting a request safely in case of faults (i.e., for submitting a request with the same external request ID and from the same external client as a product request received earlier) such that the request will be processed only once [Note this requirement supercedes C-CSS-50476 to 50478 when submitting product requests to the OMS].	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				C-CSS-51060	When configured to submit orders to the OMS, the MTMGW CI shall set the order source for the MSS orders it creates to 'MTMGW'.	
OD_S4_02	Interface the Machine-to-Machine Gateway with Order Management	no data				S-OMS-03025	The Order Management Operator GUI shall display the external request ID in the screens displaying request and order details.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-DPL-07010	The Data Pool Insert Service shall support the insert of order-only granules into the Data Pool for all ECS collections, including:    AP   DAP   FAILPGE   PGEEXE   PH   QA   SSAPC    [NOTE:  These data types would currently be distributed in Synergy III mode and hence continue to require the PDS for physical media distribution.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10010	The OMS CI shall submit requests for physical media distribution for a given media type to the PDS ('PDS media creation') or handle media creation internally within the OMS ('OMS media creation') based on DAAC configuration (by media type).	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10020	Unless a request was confirmed for Synergy III processing by the operator, the OMS CI shall generate an operator intervention for any physical media distribution request that it classifies for Synergy III mode processing if a. the media type is configured for OMS media creation, or b. OMS is configured to generate an intervention in this case, [NOTE: The intent is to allow the DAAC to prevent such requests from being submitted to the PDS by accident; and to detect the occurrence of such requests during the transition phase, before the PDS is decommissioned.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10030	The OMS CI shall allow a DAAC to configure the OMS to generate an operator intervention when it classifies a physical media request for Synergy III processing.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10100	The OMS CI shall permit EMD Development to configure the available production modules, and for each, the location of the text and image files to be used when printing jewel case inserts. [NOTE: The available production modules are subject to EMD configuration management and cannot simply be modified by a DAAC.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10102	The OMS CI shall permit DAAC operations to specify a default production module.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10104	The OMS CI shall permit DAAC operations to define the production module to be used for an ECS collection. [NOTE: Unless otherwise defined, the default production module will be used for a collection; and if there is only one production module defined, it will be the default module.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10130	The OMS CI shall allow DAAC operations to edit the configuration information for a production module.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10200	The OMS CI shall permit DAAC operations to configure a printer for printing shipping labels.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10210	The OMS CI shall permit DAAC operations to configure a printer for printing tape labels.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10220	The OMS CI shall permit DAAC operations to configure a printer for printing jewel case inserts.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10230	The OMS CI shall permit DAAC operations to configure a printer for printing packing lists.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10232	The OMS CI shall permit DAAC operations to configure OMS to print packing lists by default: a. always b. never	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10234	The OMS CI shall permit DAAC operations to configure a printer for printing QC reports.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10236	The OMS CI shall permit DAAC operations to configure OMS to print QC reports by default: a. always b. never c. only if there was a QC error	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10240	The OM GUI shall permit DAAC operations to list the printer configuration.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10300	The OMS CI shall permit DAAC operations to define the devices available for tape media creation and verification (i.e., 8 mm and DLT),and the CDROM/DVD devices used for verification, including: a. a unique label for the device, b. for Unix devices, the Unix device path name, c. for PC attached devices, the path name of the directory used to communicate with its controlling software and an indication that the device is attached to a PC platform, d. the OMS media type(s) supported by the device, e. a descriptive text of at most 255 characters,  f. the purpose for which the device can be used (media creation, media verification, or both). [NOTE: CDROM/DVD devices other than Rimage can be used only for verification], and g. optionally, indicate the operational mode for which the device is reserved (devices not reserved for a specific mode are shared across all modes).	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10310	The OMS CI shall permit DAAC operations to define the Rimage units available for DVD-ROM and CD-ROM generation, including: a. a unique label for that unit b. the OMS media type(s) supported by the unit c. a limit on the 'allocated workload' for the unit, i.e.,  a limit on the cumulative size of the requests (expressed in MB) allocated to this Rimage unit which when reached or exceeded causes the automatic activation of such requests to be halted temporarily until the cumulative size drops below that limit, e.g., because of request completions d. a limit on the 'actual workload' for the unit expressed in MB which must not be exceeded by the media production orders submitted to the unit, i.e., the creation and submission of media production order for that unit will be temporarily halted while this would cause the limit to be exceeded e. a descriptive text of at most 255 characters f. the directory used to communicate with Rimage g. optionally, indicate the mode for which the Rimage unit is reserved (Rimage units not reserved for a specific mode are shared across all modes) [NOTE: Limits c. and d. may be different and are interpreted in a slightly different fashion. The first acts as a limit on activating work for Rimage media (though the limit can be ignored when activation is manual); the second acts as a limit on the amount of work that can actually be submitted to the Rimage unit, and this limit cannot be overridden by manual action.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10320	The OMS CI shall allow DAAC operations to edit any of the attributes associated with a physical media device.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10330	The OM GUI shall permit authorized operators to flag a tape device or Rimage unit as on-line or off-line and when off-line, associate an explanation with the device of up to 255 characters that will be cleared when the device is returned to the on-line status.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10340	The OM GUI shall permit operators to list the defined physical media devices and their configured attributes (e.g., tape devices and Rimage units), plus the following information: a. whether the device / unit is on-line or off-line, b. for non-Rimage devices, whether they are busy or free, and if busy, the mode in which they are being used, and if used by the same mode as that in which the GUI is operating, the request to which they are allocated and the time of allocation, c. for Rimage units, their current actual and allocated workload, d. any explanation associated with the device e. an appropriate indication if a device is currently busy but was requested by the operator to go off-line once it frees up.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10350	The OM GUI shall permit operators to sort and filter the list of defined physical media devices by the OMS media type they support.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10360	The OM GUI shall permit an authorized operator to change the status of a device to free that is currently marked busy if it is used by a request operating in the mode in which the GUI is operating, except if the device is a production device currently allocated to a request that is in the Transferring state, or if the device is a QC device currently allocated to a request in the QC Hold state. [NOTE: The exceptions are intended to prevent operator mistakes.  Testing this presumes an error in OMS device status maintenance and thus, it may not be possible to test this requirement during integration testing.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10400	The OMS CI shall allow DAAC operators to configure a media type for PDS or OMS media creation. [NOTE: This is meant to support transition to Synergy 5.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10402	The OMS CI shall allow DAAC operators to configure for each physical media type, whether it shall be activated manually or automatically.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10407	The OMS CI shall allow DAAC operators to configure an optional email address for notifications regarding operator actions.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10408	The OM GUI shall allow DAAC operators to list the configuration settings in S-OMS-10400, S-OMS-10402, S-OMS-10407, S-OMS-10410, and S-OMS-10420.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10410	The OMS CI shall allow DAAC operations to configure a maximum time interval in minutes within which a Rimage order is expected to be pulled by Rimage after it was created by OMS.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10420	The OMS CI shall allow DAAC operations to configure a time interval in days to be added to the time when a request completes staging to establish a Due Date for the request.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10500	The OM GUI shall allow an operator to disposition  an intervention indicating that a physical media distribution request was classified as a Synergy 3 mode request in one of the following manners: a. confirm the assignment of a request to the Synergy 3 processing mode, optionally changing the media type to a different physical media type. b. change the media type to FTP Pull or FTP Push, and in the latter case, add the required distribution options, c. fail the request. d. resubmit the request without change e. resubmit the request in Synergy 4 mode [NOTE: The ability to manually change the processing mode for a request is currently the subject of Synergy 4 NCR 40501.  This requirement adds the capability to confirm the processing mode that was assigned by the OMS and supports transition from PDS to OMS.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10510	The OM GUI shall allow an operator to monitor for the following requests for operator interventions and actions: a. to activate media creation manually, b. to load media into a device, c. to collect the created media for QC, d. to assemble a distribution package for shipment, e. to handle media creation errors, f. to handle media verification errors, g. to handle the assignment of a physical media distribution request to Synergy III mode, h. to activate media verification manually.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10512	The OM GUI shall allow an operator to filter the requests for operator action / intervention by type of action, respectively intervention.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10520	The OM GUI shall allow an operator to sort the requests for operator action / intervention by media type.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10525	The OM GUI shall allow an operator to select a request for operator action / intervention for viewing and disposition.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10530	The OM GUI shall allow an operator to leave any of the requests for operator action / intervention related to OMS media creation, QC and shipment pending, optionally after providing an annotation.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10540	When displaying requests for operator action to mount media, the OM GUI shall display the following information: a. the identification of the request, b. the purpose of the mount (e.g., whether for media production or verification), c. the media type, d. the identification of the device, e. for media mounts during QC, media volume ID, f. for media mounts during media creation, the ID of the volume that will be created.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10550	The OM GUI shall allow an authorized operator to disposition a request for operator action to mount media by: a. confirming the successful completion of the requested action, or b. indicating that the requested action failed, optionally requesting that the device be set to off-line and associating an explanation with the off-line device.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10560	When displaying an operator action to activate media creation for tapes manually, the OM GUI shall: a. Display the due date of the request b. Indicate when there are currently no devices available for allocation, or c. Offer a list of the available devices for selection and one of those devices as the default choice	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10562	When displaying an operator action to activate media creation for Rimage manually, the OM GUI shall: a. Display the due date of the request. b. Indicate when all Rimage units are currently above their configured allocated workload limits, and c. offer a list of the available Rimage units for selection, displaying their allocated workload and the configured limit for each, and d. if there is at least one Rimage unit whose allocated workload is below the limit, offer the one where the difference between workload and limit is the highest as the default choice, and if several qualify, select one randomly.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10566	The OM GUI shall allow an authorized operator to complete an action for manually activating media creation: a. by selecting the offered default device, or b. by selecting any other offered device, c. plus for tape, acknowledging that blank media is already mounted, or d. by failing the request, optionally after suppressing sending the DN.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10590	When displaying intervention details related to media creation errors, the OM GUI shall: a. display the nature of the media creation error, b. display the media type c. identify the tape device or Rimage unit to which the request was allocated and the time of allocation, d. list the media volumes, their status, and the related production module e. identify the volumes whose creation encountered an error, as well as the nature of the error f. identify the request and allow the operator to access details related to the distribution request g. allow the operator to indicate that the media was removed from the allocated device and the device is now available for other requests, h. update the status of selected volumes, e.g., to indicate that volumes have been  written successfully or were found to be defective	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10592	The OM GUI shall identify in the granule list for a physical media request: a. the granules for which the physical media creation encountered an error or was not completed, b. the media volume to which a granule was written, c. the granule status [NOTE: The states of a granule during physical media creation and verification is implied by the state of the media volume to which it is allocated.  For example, if the volume state is Created, the granule was written to the media.  Granules that are Failed and whose failure was confirmed by the operator are not allocated to media volumes and their state is Failed.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10610	The OM GUI shall allow an authorized operator to complete an operator intervention related to physical media creation errors by: a. retrying the media creation for the entire distribution request, optionally after failing granules that experienced media creation errors, or b. retrying the media creation for volumes that failed or were marked failed by the operator, optionally after failing granules that experienced media creation errors on those volumes, or c. failing the distribution request, optionally after suppressing sending the DN.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10620	The OM GUI shall allow an operator to monitor for physical media distribution alerts. [NOTE:  For an example of an alert, see S-OMS-12440]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10630	The OM GUI shall allow an operator to view alerts related to physical media distribution.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10682	When displaying a request for operator action to collect the created media for QC, the OM GUI shall: a. identify the distribution request and provide access to the request details, b. identify the media type, c. list the created media volumes, d. identify the device to which the request was allocated e. in the case of tape distribution, ask the operator to confirm that the last media was dismounted from the production device.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10684	The OM GUI shall allow an authorized operator to complete an action requesting collection of the created media for QC by: a. acknowledging that the last media volume was dismounted from the production device and that the media have been collected and are ready for verification, or b. failing the action, e.g., because the media could not be collected or because the operator discovered a problem that prevents QC, plus optionally setting the device off-line and associating an explanation for this with the device.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10685	When displaying an operator action to activate media verification manually, the OM GUI shall: a. Display the due date of the request and the volume that needs to be mounted for verification b. Indicate when there are currently no eligible devices available for allocation, or c. Offer a list of the available eligible devices for selection and one of those devices as the default choice [NOTE: The device used in request production is considered ineligible for verifying the media volumes of this request.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10686	The OM GUI shall allow an authorized operator to complete an action for manually activating media verification: a. by selecting the offered default device, or b. by selecting any other offered device, c. plus acknowledging that the requested media is already mounted, or d. by failing the request, optionally after suppressing sending the DN	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10690	When displaying an operator intervention related to media verification errors, the OM GUI shall: a. display the nature of the media verification error, b. display the media type, c. identify the device to which the verification was allocated, d. list the created media volumes, e. identify for each volume the responsible production module, and whether it failed verification, passed verification, or whether verification was not performed, f. identify the request and allow the operator to access details related to the distribution request, g. allow the operator to change the status of a volume, e.g., to indicate that it is defective or passed, h. allow the operator to indicate that the media was removed from the allocated device and the device is now available for other requests, i. identify the printer to which the QC report was sent if one was generated, j. allow the operator to print a QC report.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10692	The OM GUI shall allow an authorized operator to complete an operator intervention related to media verification errors by: a. retrying the media creation for the entire distribution request, optionally after failing granules that experienced media creation errors, or b. retrying the media creation only for volumes that failed or were marked failed by the operator, optionally after failing granules that experienced media creation errors on those volumes, or c. failing the distribution request, optionally after suppressing sending the DN, or d. requesting re-verification of volumes that failed or were marked failed by the operator,	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10700	When displaying a request for operator action to assemble the final distribution package for shipment, the OM GUI shall: a. display request information, b. identify the media type, c. list the created media volumes, identify their status and the responsible production module, d. list the printed outputs and identify the printers where each is located, e. allow the operator to re-print any of the following (as applicable to the media type): shipping label, packing list, tape labels, jewel case inserts, and QC report. f. let the operator acknowledge the dismount of the last media volume from the QC device.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10702	The OM GUI shall allow an authorized operator to complete an operator action requesting assembly of the final distribution package for shipment by: a. acknowledging the dismount of the last media volume from the QC device, successful assembly of the package, and confirming that the request can transitioned to the 'Shipped' state, optionally suppressing the DN, b. indicating that the distribution package could not be assembled successfully, optionally setting the device off-line and associating an explanation for this with the device, c. failing the request, optionally suppressing the DN.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10710	The OM GUI shall update the state of an open operator action to 'Closed' once the action has been completed. [NOTE:  This extends S-OMS-03215 in OD_S3_01 to operator actions.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10720	The Order Management GUI shall record the date/time and the nature of the disposition of an operator action in the Order Management Database. [NOTE:  This extends S-OMS-03390 in OD_S3_01 to operator actions.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10740	The Order Management GUI shall allow an operator to list past operator actions, filter the list by creation time period (using today as the default), and to sort the list by date/time when the operator action was requested, the type of operator action, and associated request ID, order ID and user ID. [NOTE:  This extends S-OMS-03420 in OD_S3_01 to operator actions.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10750	The Order Management GUI shall allow an operator to select a past operator action and view it. [NOTE:  This extends S-OMS-03430 in OD_S3_01 to operator actions.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10760	The OMS CI shall apply the configured maximum age that controls the removal of interventions from the Order Management Database to the removal of operator actions. [NOTE:  This extends S-OMS-01510 in OD_S3_01 to operator actions.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10800	The OM GUI shall display the following additional information when displaying a list of distribution requests that are not in a terminal state: a. Request Priority	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10810	The OM GUI shall allow an operator to sort the list of distribution requests that are not in a terminal state by the following additional attributes: a. Request Priority	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10850	The OM GUI shall display the following additional information when displaying details for a physical media distribution requests: a. Request Annotations, b. Identification of the tape production device or Rimage unit that was used for the request [NOTE: or the latest if more than one was used] and the time of allocation, c. List of media volumes created for the request. d. Due Date.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10860	The OM GUI shall allow an authorized operator to edit the following additional information for a physical media distribution request that is not shipped: a. any of the addresses associated with the request	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10870	The OM GUI shall display the following information when listing media volumes: a. volume identification b. volume status, i.e., one of the following:    NULL   Prepping (volume is being prepared)   Prepared (volume was prepared but not yet created)   Creating (volume is being created   Created (volume was created by not yet verified)   Verifying (volume is being verified)   Verified (volume was verified successfully)   Failed (volume failed the current operation, i.e., prepping, creating, or verifying)    c. associated production module d. The time volume creation started if the volume is currently in the 'Creating' state (i.e., the time of last status change). e. The time volume verification started if the volume is currently in the 'Verifying' state (i.e., the time of last status change). [NOTE: The above ensures that the time the respective operation started for a volume is displayed when the GUI offers the operator the option to stop this operation.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10930	The OM GUI shall display the following additional information in the granule list of a physical media distribution request: a. the identification of the media volume to which the granule was written	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-10932	The OM GUI shall be able to display in the granule list of a physical media distribution request, any new failure explanations that may apply.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11010	The OM GUI shall allow an authorized operator to annotate a distribution request or change its existing annotation, up to a total annotation size of at least 2,000 characters.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11040	The OM GUI shall allow authorized operators to stop the physical media creation for a physical media distribution request that is currently in the 'Transferring' state, optionally for a specific volume. [NOTE: The OMS will cancel the execution of the corresponding production module(s) and queue a media creation error.  The operator can handle any necessary actions in the resulting operator intervention.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11050	The OM GUI shall allow authorized operators to stop the physical media verification for a physical media distribution request that is currently in the 'QC Hold' state. [NOTE: The OMS will cancel the execution of the current QC module and queue a QC error. The operator can handle any necessary actions in the resulting operator intervention.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11070	The OM GUI shall allow an authorized operator also to cancel a physical media distribution request that is not in a terminal state and while granules for the request still need to be transferred to media (i.e., the request cannot be in a 'QC Hold' or 'Waiting for Shipment' state). [NOTE:  This extends the requirement for cancellation in Ticket OD_S4_01, S-OMS-06345 for physical media distribution requests.  Note the applicability of related requirements from Ticket OD_S4_01, such as S-OMS-06355, S-OMS-06360, S-OMS-06365.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11080	The OM GUI shall allow authorized operators to suspend a physical media distribution request also while it is pending media production, if it is for a media type that is activated automatically. [NOTE: This extends suspension requirements in Ticket OD_S4_01, S-OMS-06315, for physical media requests. The request for suspension may be rejected if the request has already been allocated to a device.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11100	The OM GUI shall allow authorized operators to alter the priority of a physical media distribution request also while it is pending media production. NOTE:  This extends requirement S-OMS-06305 in Ticket OD_S4_01 for physical media distribution requests.  The priority change will affect only the automatic activation of requests.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11130	The OM GUI shall allow multiple operators to monitor physical media distribution concurrently from different workstations.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11140	The OM GUI shall support concurrent physical media distribution in multiple modes. [NOTE: This is an extension of existing requirements to physical media creation.  Separate modes will require separate web browser windows.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-11200	The OM GUI shall allow an operator to view current physical media distribution information, including the: a. number of devices of each media type that are currently off-line, or on-line and if applicable, busy vs. free; b. number of physical media requests of each media type currently pending media production; c. total amount of data in MB in physical media distribution requests pending media production for each media type.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12010	The OMS CI shall queue a physical media distribution request for media creation after all its granules are available in the Data Pool or were otherwise dispositioned and the media type is configured for OMS media creation.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12020	The OMS CI shall establish a Due Date for a physical media request that is a DAAC configurable number of days from the time the request completed staging.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12050	The OMS CI shall assign the MSS state of 'Pending Media Prod' to a distribution request when it queues the request for media creation.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12070	The OMS CI shall not automatically activate media creation for a media type whose queue is suspended.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12072	The OMS CI shall not automatically activate media creation for a distribution request that is currently suspended.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12078	The OMS CI shall activate media creation automatically by priority and within the same priority on a first-in first-out basis.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12080	If the OMS CI is configured for automatic activation for a media type other than Rimage, the OMS CI shall dispatch media creation for that media type while there is a device that is free and on-line and supports the media type.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12082	If the OMS CI is configured for automatic activation for an Rimage media type, the OMS CI shall dispatch media creation for that media type while there is a Rimage unit whose current allocated workload is less than its configured limit.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12090	When automatically activating media creation for a tape device, the OMS CI shall assign the distribution request to one of the free devices that are on-line and mark the device as busy.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12100	When automatically activating media creation for an Rimage unit, the OMS CI shall assign the distribution request to the Rimage unit that is least busy based on current allocated workload, and update the assigned workload for that unit, making a random selection if more than one unit qualifies under that rule.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12120	When queuing a physical media distribution request for media types that are configured for manual activation, the OMS CI shall request an operator action to dispatch the distribution request manually.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12150	When an operator action for activating a distribution request manually is completed successfully, the OMS CI shall dispatch the media creation steps for the corresponding distribution request.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12152	The OMS CI shall be able to re-execute the physical media distribution steps for a request or a portion of a request (such as a specific volume or all remaining granules), re-assigning the same volume identifications to volumes that have been created before and are not being re-created. [NOTE: Re-dispatching may be needed after operator interventions.  For example, a multi-volume job may encounter a device error after some media have been written; or some of the media failed verification.  Note that in the case of Rimage, this implies that the OMS can distinguish between the response to a re-dispatch and the original dispatch.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12160	The OMS CI shall exclude from the media creation process any granules flagged as failed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12170	The OMS CI shall update the MSS status of a request to 'Transferring' when it activates the media creation for that request.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12200	The OMS CI shall include the production modules supported by PDS, altered as necessary for execution within the OMS CI. [NOTE: The intent is to re-use the existing production modules and adapt them for operation within the OMS CI.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12205	The OMS CI shall determine the applicable production module for each granule in a request that needs to be written to physical media in a fashion compatible with the existing PDS.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12210	The OMS CI shall perform media creation using the required production modules, grouping granules by production module if the request requires the execution of more than one module.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12220	The OMS CI shall be able to execute production modules on a DAAC configured target platform other than the one on which the OM server is executing. [NOTE:  For Synergy 5, the intent is to execute the production modules on the current PDS platform.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12240	The OMS CI production modules shall be able to retrieve the data to be written to physical media from the Data Pool SAN for transfer to physical media devices or device handling software.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12250	The OMS CI production modules shall transfer the distributed granules to tape media volumes such that the resulting tapes are backwards compatible in format with those created by the PDS.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12251	The OMS CI production modules shall create and transfer an Order Summary to each media reflecting the contents of this media volume.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12252	The OMS CI shall be able to process tape media distribution requests that require multiple tape volumes.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12254	The OMS CI production modules shall generate tape media labels backwards compatible with the PDS [NOTE: The intent is to re-use the existing production modules and adapt them for operation within the OMS CI.  Since unit numbering restarts with each volume, unit numbers on the label have become superfluous.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12256	For multi-volume requests, the OMS CI shall be able to overlap the media preparation step for one volume with the media creation step of another volume. [NOTE: The requirement shall be verified via inspection during Code Review.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12260	The OMS CI shall be able to process media distribution requests that require multiple Rimage media volumes.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12270	The OMS CI production modules shall create CD-ROM and DVD-ROM images for the distributed granules such that the resulting CD/DVD media are backwards compatible in format with those created by the PDS.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12280	The OMS CI production modules shall interface with R-Image for transferring the generated CD-ROM and DVD-ROM images to physical media and generating the media labels. [Note: Media labels may differ in detailed content from those produced by the PDS because of changes in unit numbering and the format of volume labels.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12290	The OMS CI shall not dispatch the media creation step for a media volume to be created by Rimage if the order would cause the configured workload limit for that Rimage unit to be exceeded.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12300	The OMS CI production modules shall interface with R-Image in order to detect when an Rimage media creation completed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12330	The OMS CI production modules shall return a status indicating success or an appropriate error indication and the failure status of each granule that encountered an error.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12340	The OMS CI production modules shall generate logs containing the information that is recorded in the current PDS media production logs.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12380	The OMS CI shall generate requests for operator actions for mounting media: a. when ready to create the first tape of a distribution request unless the request was dispatched manually and the operator indicated that blank media is already loaded, b. after completing creation of a tape (other than the last one) for a multi-volume distribution request, c. when ready to verify the first media volume for a distribution request unless media verification is dispatched manually and the operator indicated that the required media volume is already loaded, d. after completing verification of a media volume (other than the last one) for a multi-volume verification.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12384	During media creation, the OMS CI shall re-queue a distribution request for allocation to a different device if the first mount action for its current device is failed and the media type is dispatched automatically. [NOTE: ECS tracks a single device for a distribution request.  If a distribution request used several production devices, the tracking information will only show the most recent device that was used.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12388	During media creation, the OMS CI shall generate an operator intervention for a media creation error if any but the first mount action for the device used by the request is failed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12400	During media verification, the OMS CI shall generate an operator intervention for a QC error if a media mount action is failed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12402	The OMS CI shall make a device available for another distribution request unless the operator requested that it be set off-line, if the operator: a. acknowledges the dismount of the last media for a request, b. indicates that the drive is available for other request during an intervention.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12404	The OMS CI shall no longer allocate a device to requests if the operator requested that it be set off-line at a time when the device was busy, even if the device becomes free, until such time as the operator sets the device on-line again.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12410	The OMS CI shall maintain the amount of work in progress for an Rimage unit when the execution of a production module for Rimage media creation starts, completes or is terminated.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12420	The OMS CI shall delete all temporary files used in the course of physical media distribution automatically after they are no longer needed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12430	The OMS CI shall generate an operator intervention for a media creation error if a production module returns an error.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12432	The OMS CI shall provide an indication of the nature of the media creation error in the media creation error intervention that it generates.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12434	The OMS CI shall generate an operator intervention for a media creation error when it cancels one or several production modules in response to the operator stopping the creation of the corresponding volume(s) or distribution request, indicating that the media creation for these volumes was stopped by the operator.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12436	The OMS CI shall generate an operator intervention for a QC error when it cancels a media verification operation in response to the operator stopping media verification for a request.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12440	The OMS CI shall generate a physical media distribution alert when the physical media platform or the OMS agent running on that platform is down or cannot be reached, and suspend dispatching of activities to that platform. [NOTE:  Synergy 5 assumes that all physical media distribution will be via a single platform, currently dig06. No alert conditions are intended for PC host platforms because the number of attached devices is small, and the subsequent QC error intervention will alert operations, as well as block the device for use by other requests until the operator dispositioned the error.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12441	The OMS CI shall generate a physical media distribution alert and set the corresponding Rimage unit off-line when a media order that it created for Rimage is not pulled by Rimage within an operator configurable time. [NOTE: Setting the Rimage unit off-line will prevent its allocation to new requests.  It does not prevent requests that are already allocated to it from trying to use it.  To re-allocate existing requests, the operator would need to 'Stop' their media production operations (see S-OMS-11040).]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12442	The OMS CI shall retry dispatching of activities to the physical media distribution platform while an alert is pending for it, and if a retry succeeds, clear any pending physical media distribution alert for that platform and resume dispatching physical media distribution activities to it.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12443	The OMS CI shall clear any pending alert for an off-line Rimage unit when the operator sets it on-line. [NOTE:  It is assumes that this is the normal operational scenario.  Operations will follow-up on the alert and set the unit back on-line once the fault has been resolved.  By that time, media operations for requests that are already allocated to the unit may already have restarted, see S-OMS-12444.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12444	The OMS CI shall retry dispatching media creation operations for an Rimage unit that is currently off-line because an alert is pending, and clear the alert and set the unit back on-line when a retried operation succeeds. [NOTE:  This ensures that production activities that were interrupted by the outage are resumed as soon as possible, perhaps even before the operator sets the unit back on-line.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12459	The OMS CI shall update the status of a request to 'QC Hold' when the operator acknowledges that collection of the media for QC was completed successfully and any of its media need verification.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12461	The OMS CI shall queue an action requesting the operator to collect the media for the distribution request for QC when it completes physical media production and any of its media need verification.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12462	The OMS CI shall queue an intervention for a media creation error if the request for collecting the media for a distribution request for QC is failed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12463	The OMS CI shall queue a distribution request for automatic assignment of a QC device (different from the one used for media creation) if the operator acknowledges the collection of media for QC and the media type is configured for automatic activation.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12464	If the OMS CI is configured for automatic activation for a media type, it shall assign a distribution request for verification to one of the on-line free QC devices that support the requested media type by priority, and within the same priority on a first-in, first-out basis and mark the device as busy.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12465	The OMS CI shall give preference to QC over media creation when assigning devices to a distribution request automatically.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12466	The OMS CI shall invoke media verification for each of the media volumes that were determined to need verification by executing a media verification module on the DAAC configured media production platform.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12467	The OMS CI shall identify the media volumes that fail verification, but continue to verify the remaining media volumes designated for verification.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12468	The OMS CI shall queue an operator intervention for QC error when media volumes for a request fail verification.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12469	The OMS CI shall generate a QC error intervention when a request that it created for a PC-attached QC device is not completed within an operator configurable time.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12470	The OMS CI verification modules shall by able to interface with QC devices attached to the SGI media distribution platform. [NOTE:  This is only testable to the extent such devices are available in the PVC.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12472	The OMS CI verification modules shall be able to interface with DVD/CDROM QC devices attached to PC platforms. [NOTE:  This is only testable to the extent such devices are available in the PVC.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12473	The OMS CI verification modules shall generate a QC Report for a volume that is backwards compatible with the PDS.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12474	The OMS CI shall print a QC Report for a request backwards compatible with the PDS when it queues an operator intervention for QC error for the request, if configured to print a QC report by default always or only when a QC error occurs.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12475	The OMS CI shall queue an operator action for manual activation of QC for a distribution request once the operator acknowledges the collection of media for QC and the media type is configured for manual activation.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12476	When an operator action for manual activation of QC for a distribution request is completed successfully, the OMS CI shall dispatch the media verification steps for the corresponding distribution request.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12500	The OMS CI shall print shipping labels backwards compatible with the PDS for physical media distribution requests after the request completed QC for all volumes successfully.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12510	The OMS CI shall print jewel case inserts backwards compatible with the PDS for CD-ROM/DVD-ROM distribution requests after the request completed QC for all volumes successfully.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12520	The OMS CI shall print a Packing List for a physical media distribution request backwards compatible with the PDS after it completed QC for all volumes successfully, if the DAAC configured OMS to print Packing Lists by default always. 	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12522	The OMS CI shall print a QC Report for a physical media distribution request backwards compatible with the PDS after it completed QC for all volumes successfully, if the DAAC configured OMS to print QC Reports by default always.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12530	The OMS CI shall update the MSS status of a request to 'Waiting for Shipment' after it completes QC for all volumes successfully.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12540	The OMS CI shall queue a request for operator action to assemble the distribution package, i.e., the printed output and the created media after the request completes QC for all volumes successfully.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12545	The OMS CI shall queue an operator intervention for QC error if the request to assemble the distribution package for shipment is failed.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12610	The OMS CI shall queue a Distribution Notice (DN) when a physical media distribution request completed or failed, unless the operator requested suppression of the DN. [NOTE: Listing the failed granules and the reason for failure in the DN is already an existing requirement, but there may be new failure reasons.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12620	The OMS CI shall generate Distribution Notices (DN) for physical media distribution requests that are compatible with the ICD 423-41-57, 'ICD Between ECS and the Science Investigator-led Processing Systems (SIPS)'. [NOTE:  Changes will need to be agreed with the DAACs and will require approval of CCRs  to the ICDs that include or reference them.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12630	The OMS CI shall queue a DN for DORRAN when a physical media distribution request completed or failed that was routed via the DORRAN billing system. [NOTE: This notice needs to be sent even if the operator suppressed the DN.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12640	The OMS CI shall generate Distribution Notices for DORRAN for physical media requests that are compatible with the ICD 423-41-58 Interface Control Document Between EOSDIS Core System (ECS) and the Land Processes Distributed Active Archive Center (LP DAAC).	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12650	The OMS CI shall update the MSS status of a physical media distribution request to 'Shipped' when the operator confirms that the package was assembled and the request can be marked shipped, once its DN creation has been queued.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12660	The OMS CI shall no longer count a physical media distribution request against the High and Low Watermarks when it is waiting for shipment or is suspended or canceled/failed, or in operator intervention (not including interventions representing operator actions normally occurring in the course of media distribution).	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12690	The OMS CI shall send e-mail notifications for actions to the configured e-mail address if such an address is configured, and include the following information as part of the e-mail: a. The nature of the action and the identification of the affected request as part of the subject line. b. Any additional information that the OM GUI would display for the action, as part of the message body.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12710	The OMS CI shall log the following events: a. Start and completion of media preparation for individual media volumes  (to the extent this occurs under OMS control), b. Start and completion of media preparation for a distribution request  (to the extent this occurs under OMS control), c. DELETED d. Start and completion of media creation for individual media volumes (or the formatted media volume files in the case of CD-ROM and DVD-ROM) (to the extent this occurs under OMS control), e. Start and completion of media generation for a distribution request, f. Start and completion of media verification for a media volume (to the extent this occurs under OMS control), g. Start and completion of media verification for an individual distribution request, h. Errors, i. Devices or device handling software going off-line / on-line, j. Alerts, k. Queuing of interventions and actions (to the extent these are initiated by the server), l. Suspensions and resumptions.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12720	The OMS CI shall log the following information as applicable: a. File name and size, b. granule ID and granule number, c. request ID, d. volume ID, e. device identification, f. Error type, severity, explanation, g. Nature of alert or intervention.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12730	The OMS CI shall provide the capability to remove  production module log information and QC reports after a time period that is operator configurable by type of log information. [NOTE: This is meant to match the PDS Cleanup requirements.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12740	The OMS CI shall provide the capability to archive production module log information and QC reports that is no longer retained to a DAAC configurable location. [NOTE:  This is meant to match the PDSIS 'archive_root' configuration parameter.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12745	The OMS CI shall provide the capability to archive order tracking information for physical media requests after their retention time has expired. [NOTE:  This extends S-OMS-06705 in OD_S4_01 and NCR 39889 to physical media types.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12750	The OMS CI shall include provisions for removing operator actions and related information from the database whose completion date/time exceeds a maximum age. [NOTE:  This extends S-OMS-01500 in OD_S3_01 to operator actions.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12810	When restarting after a fault, the OMS CI shall be able to recover the state of media productions that were in progress at the time of the fault such that no requests are lost, no media volumes are produced twice or not produced at all, no distribution steps are omitted, and steps that were completed or can continue despite the fault do not have to be redone or re-started, and such that the recovery does not place requests into operator intervention.  This includes: a. The OMS shall restart media preparations that were in progress at the time of the fault, and not redo as part of the recovery media preparation operations that already completed or had failed at the time of the fault. b. The OMS shall restart media creation for tape transfers that were aborted by the fault, and not redo as part of the recovery tape media creation operations that already completed or had failed at the time of the fault. c. The OMS shall recover media creation orders that were accepted by Rimage for processing (i.e., avoiding creation of duplicate volumes), and not resubmit as part of the recovery media creation orders that were already completed or had failed at the time of the fault. d. The OMS shall restart media verification operations that were aborted by the fault, and not redo as part of the recovery media verification operations for volumes that were already verified successfully at the time of the fault. e. The OMS shall recover media verification related requests that were submitted to PC platforms (i.e., avoid submitting them again), and not resubmit as part of the recovery verification related requests to PC platforms for volumes that already completed or had failed verification at the time of the fault. f. The OMS shall recover operator actions and interventions that were pending at the time of the fault and require their disposition before continuing the distribution of these requests.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12910	The OMS CI shall be able to perform media distribution concurrently in multiple modes. [NOTE: This is an extension of existing requirements to physical media creation. This may require reserving specific devices or Rimage units for specific modes, e.g., by not including them in the configuration of the modes that are not using them, or by setting them off-line in those modes.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12915	The OMS CI shall be able to perform media distribution in a test mode concurrently with PDS operating in another mode. [NOTE: This is intended to support transition.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12920	The OMS CI shall share media devices and maintain their status across modes. [NOTE:  That is, a defined media device is available to all ECS modes, and its status and attributes are mode independent.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12922	The OMS CI shall be able to allocate devices automatically for production across modes if they support a media type that is dispatched automatically.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-12924	The OMS CI shall be able to allocate devices automatically for QC across modes.	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-13000	The OMS CI shall be able to perform physical media distribution for granules whose collections are being moved concurrently, or that are being replaced concurrently by a reprocessed granule, or that are being made publicly visible by a concurrent Data Pool insert when they were originally inserted for order-only purposes. [NOTE: This extends existing requirement to the physical media distribution by OMS.  Examples of acceptable behavior include recognizing and automatically correcting the problem (e.g., by substituting the correct path name for the original one); generating an operator intervention which allows the operator to update and/or resubmit the request such that it will succeed without failing any granules.]	
OD_S5_01	Integrate Physical Media Distribution Into OMS	no data				S-OMS-13020	The OMS CI shall maintain the following MSS order tracking information: a. media quantity b. identification of the device used for the media production	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06400	The Data Pool web application service shall not permit a user to submit a shopping cart to the OMS when the number of granules in the shopping cart that require HEG processing exceeds the configured OMS limit for the number of granules in a subsetting request.	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06405	The Data Pool web application service shall warn a user about the limit placed on the number of granules in a shopping cart for which HEG processing can be requested. [NOTE: Preferably, the warning is not displayed until the user starts to enter HEG processing instructions.]	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06410	The Data Pool web application service shall submit requests that require HEG processing services to the OMS by saving them in the OMS database in accordance with the format specified by the DPL-OMS HEG request interface specification. [NOTE: Data Pool web application will submit the HEG processing instructions for each granule input file as a single processing instruction in XML format compatible the HEG Service interface specifications.  Also note that currently, all granules that can be processed by the HEG have only one file.]	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06440	The Data Pool web application service shall return to the user the status of the placement of a request with the OMS, including a meaningful message. [NOTE: This modifies S-DPL-06110 in WD_S3_01.]	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06450	Users shall be able to bookmark the order status page for a HEG request that involves HEG processing and obtain the status of the HEG order by reloading the bookmark. [NOTE: this extends the general web order status capabilities to HEG orders]	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06460	Users shall be able to request the distribution of the results of a request involving HEG processing via any media type configured by DAAC operations for Data Pool Web orders. [NOTE: The configured media types are available for all orders submitted via the Data Pool web application. The default media type for distribution is FTP Pull.]	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06470	The Data Pool web application service shall inform users when upon submitting a request involving HEG processing, the OMS returns a status indicating that submission of HEG requests is stopped.	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06480	The Data Pool web application service shall display an optional DAAC provided announcement text of up to four lines of 30 characters on the Data Pool home page. [NOTE:  The DAAC can use this to announce upcoming service outages, e.g., of HEG processing.] 	
OD_S5_02	Managing HEG Orders	no data				S-DPL-06485	The Data Pool Cleanup Utility shall not remove granules needed as input for HEG processing even if they are expired, until they are no longer needed as inputs.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08300	In the e-mail message sent to a user after acceptance of an order, the OMS CI shall include also the following information for each granule that requires  HEG processing: a. the input granule ID b. the conversion actions requested by the user [NOTE: This replaces S-DPL-06012 in WD_S3_01 and extends S-OMS-06435 in OD_S4_01.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08310	The OMS CI shall validate requests that require HEG processing like subsetting requests, i.e. validate the total request against the normal request limits (including granule count limit), plus the number of granules that require HEG processing against the granule count limit established for subsetting requests. [NOTE:  See ticket OD_S3_01, S-OMS-01090, S-OMS-01110, S-OMS-01130.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08315	The OMS CI shall generate an operator intervention if any of the granules referenced by a HEG processing order no longer reside in the Data Pool and cannot be staged, flagging these granules as inaccessible due to unavailability in the Data Pool. [NOTE: Normal submission from the Data Pool web application ensures that the referenced granules are in the Data Pool.  However, when an operator resubmits a shipped or otherwise terminated HEG processing orders, granules referenced by the order may have been cleaned up. The operator intervention should be treated otherwise like those for unavailable / inaccessible granules. See also S-OMS-01190 and related requirements in OD_S3_01.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08350	The OMS CI shall activate requests for HEG processing (i.e., start dispatching granules that require HEG processing to the HEG Service) by priority, and within the same priority, on a first-in first-out basis, as HEG processing slots can no longer be filled by requests that are currently active. [NOTE: the granules for HEG orders are staged in the Data Pool and hence, staging policy considerations do not apply.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08360	The OMS CI shall not activate requests for FTP Pull that require HEG processing if the FTP Pull DHWM has been reached or exceeded, unless the priority of the request is equal to or higher than the FTP Pull pre-emptive dispatch priority. [NOTE: Requests that are already active will continue to be processed (to prevent deadlocks). ]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08370	The OMS CI shall queue the granules of a request for HEG processing once the request has been activated.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08380	The OMS CI shall dispatch the granules queued for HEG processing in accordance with the configured HEG dispatch policy.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08390	The OMS CI shall not activate requests for HEG processing nor dispatch HEG processing for them if they are canceled, or in operator intervention, or suspended.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08400	After dispatching a granule for HEG processing, the OMS CI shall submit the processing instructions for that granule to the HEG services in accordance with the HEG service interface specified in Synergy 5 ticket OG_S5_01.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08410	The OMS CI shall comply with the HEG service interface specifications for resubmissions in case of faults.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08420	The OMS CI shall accept a completion status from the HEG execution indicating success or failure, in accordance with the HEG service interface specified in Synergy 5 ticket OG_S5_01.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08460	If a request is resubmitted, the OMS CI shall not include the subsetting outputs of any failed granules. [NOTE: This means that if an operator resubmits a request after failing a granule, any outputs of that granule that may already have been produced must not be included in the distribution and can be removed from the request.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08470	The OMS CI shall generate an operator intervention for a HEG processing error if the HEG execution response indicates an error and suspend the corresponding HEG order. [NOTE: This replaces S-DPL-06116 in WD_S3_01.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08480	The OMS CI shall include in the operator intervention for a HEG processing error, the reason for the failure (if available).	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08490	The OMS CI shall be able to create and send Distribution Failure Notices for requests or granules that were failed by the operator while handling a HEG processing error intervention, at the discretion of the operator. [NOTE: This extends S-OMS-03280, S-OMS-03290 in OD_S3_01.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08500	The OMS CI shall generate an operator alert and suspend the dispatching of HEG processing if one of the following errors occur: a. It cannot communicate with the HEG processing service (e.g., HEG processing platform is down, the service is not up, communication is interrupted).	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08510	The OMS CI shall retry submission to the HEG service while an alert is pending and the queue was not suspended by the operator, as specified in the dispatch policy.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08520	The OMS CI shall clear the pending operator alert and resume the queue if retrying submission to the HEG service succeeds.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08530	The OMS CI shall stop activation of requests for HEG processing and the dispatching of HEG service requests while the HEG request queue is suspended. [NOTE: It is OK to complete a granule before stopping the dispatching of HEG executions.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08540	The OMS CI shall submit a cancel request to the HEG service when an operator cancels the HEG processing for a currently executing granule.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08542	The OMS CI shall submit a cancel requests to the HEG service when an operator cancels a distribution request to cancel granules from that request that are currently executing.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08550	The OMS CI shall queue a DN for a request specifying FTP Pull and involving HEG processing after all its granules have been processed or otherwise dispositioned.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08560	After all the granules for a request involving HEG processing and specifying physical media distribution have been processed or otherwise dispositioned, the OMS CI shall validate the results against the minimum and maximum request size and media capacity limits for that media type, and queue an operator intervention if the validation fails. [NOTE:  The intent is to let the operator disposition this intervention like the interventions for the same limit violations normally detected during initial request validation except for partitioning.]   	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08562	After the processing for a request is complete, the OMS CI shall update the request size in the MSS order tracking table to contain the total size of the granules that are distributed, i.e., for granules involving HEG processing, the OMS CI shall use the size of the outputs rather than the input size to calculate the request size for this purpose.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08570	The OMS CI shall queue the output of a request involving HEG processing and specifying FTP Push or physical media distribution for final distribution after all its granules have been processed or otherwise dispositioned.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08580	The OMS CI shall be able to distribute HEG outputs via any of the media types it supports.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08590	The OMS CI shall include in the Distribution Notices (DN) sent for requests that involve HEG processing, for each granule that required HEG processing and failed, any error detail provided by the HEG. [NOTE: This modifies S-DPL-06114 in WD_S3_01.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08595	The OMS CI shall support the following packaging options for FTP Pull downloads: a. gzip.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08600	The OMS CI shall include in the DN for a request specifying FTP Pull distribution, URL links for each of the output packaging options that are supported for downloading, including the XML files of the input granules, if so configured by the DAAC.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08605	The OMS CI shall allow a DAAC to configure whether a DN for FTP Pull will offer packaging options or not.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08610	The OMS CI shall remove HEG service order files related to HEG processing once they are no longer needed.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08630	The OMS CI shall remove outputs from HEG processing once they are no longer needed for distribution. [NOTE: Outputs of failed or canceled granules or left incomplete due to faults are removed by the HEG service, see OG_S5_01.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08650	The OMS CI shall log the follow HEG processing events: a. Dispatching of HEG processing for a granule b. Completion of HEG processing for a granule c. Starting work on a request involving HEG processing d. Completing work on a request involving HEG processing e. Sending a DN for a request involving HEG processing f. Errors. g. HEG related operator interventions and alerts h. HEG Queue suspension and resumption i. Stopping and resuming acceptance of HEG orders.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08660	The OMS CI shall format its application log entries compliant with the current ECS log format (e.g., they contain time and severity), and include the following information for HEG related log entries, as applicable: a. Request ID b. Granule ID c. File name and file size d. Error/event identification and explanation e.  HEG service assigned HEG process identifier f.  OMS assigned HEG service request identifier	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08670	The OMS CI shall include steps related to HEG processing in the performance log.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08680	While executing a request involving HEG processing, the OMS CI shall maintain the order tracking status of the request in MSS as follows: a. While a request is queued for HEG processing, its state shall be 'Waiting for Processing'. b. Once a request has been activated and until all its HEG granules completed processing or are dispositioned otherwise, its state shall be 'Processing'. c. After all granules for a FTP Push request completed HEG processing or were otherwise dispositioned, and until the first FTP Push operation for the request is started, the state of the request shall be 'Staged'. [NOTE:  FTP Pull requests are complete at this time, and physical media requests are 'Pending Media Prod.']	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08690	The OMS CI shall maintain the status of each granule requiring HEG processing as follows. a. While a granule is queued for HEG processing, its state shall be 'Waiting for Processing'. b. Once the HEG processing for a granule is dispatched, its state shall be 'Processing'. c. After HEG processing for a granule completed, its state shall be 'Completed Processing', until such time as the granule state is changed by subsequent distribution activities.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08692	The OMS CI shall not re-perform HEG processing when operators disposition interventions resulting from errors during electronic or physical media distribution steps.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08700	The OM GUI shall allow appropriately authorized operators to configure a dispatch policy for HEG processing which includes: a. the maximum number of HEG Service requests that may be processed concurrently. b. the maximum number of HEG Service requests that may be processed concurrently for a single request c. retry interval for automatic retry in case the queue is suspended automatically.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08710	The OMS CI shall allow DAAC operations to configure the host and port for the HEG service. 	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08740	When displaying operator interventions related to HEG processing, the OM GUI shall identify the type of the intervention (i.e., HEG processing error) and display status detail information if returned by HEG.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08750	The OM GUI shall allow an appropriately authorized operator to disposition an operator intervention for a HEG processing error by: a. failing the request b. failing the granule(s) that caused the error and resubmitting the request. c. deleted d. resubmitting the request, requesting reprocessing of the failed granule(s).	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08752	When displaying the details of an intervention caused by HEG request outputs violating one of the configured size limits, the OM GUI shall display the output size of the HEG request, respectively of any granule whose outputs exceed media capacity. [NOTE: Normally, the OM GUI displays the input granules and their size.  However, on this occasion, the operator needs to know the output size of the HEG.  See also S-OMS-08560]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08754	When displaying the details of an intervention caused by HEG processing, the OM GUI shall allow operators to display the processing instructions for the granule that caused a processing error.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08760	The OM GUI shall not generate a request for user notification when the operator elects to fail granules while handling a HEG processing error intervention, unless instructed otherwise by the operator. [NOTE: The final DN tells the user which granules failed, so this notification is normally superfluous.  This augments S-OMS-03130, S-OMS-03270 in OD_S3_01 for HEG requests.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08770	The OM GUI shall allow the operator to request suppression of the failed DN when the operator elects to fail a request while handling a HEG processing error intervention. [NOTE: By default, a failed DN is sent and tells the user that the request failed, but the operator can suppress this, e.g., if the operator intends to resubmit the request.  This augments S-OMS-03130, S-OMS-03270 in OD_S3_01 for HEG requests.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08780	The OM GUI shall allow operators to view alerts for HEG processing.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08790	The OM GUI shall allow operators to view the following information for the HEG processor: a. the current state of the queue for the HEG (suspended or active and whether suspended by operator or automatically) b. the number of distribution requests and granules currently queued for HEG processing, as well as the total amount of input data. c. whether the acceptance of HEG processing requests is stopped.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08792	The OM GUI shall allow operators to list the HEG granules that are currently pending with the HEG processing service in order of their submission time, and display for each item in the list: a. the request ID, as a link to the request details page b. the ESDT, version and ID of the input granule c. a link to display the corresponding HEG processing instructions d. the time the granule was submitted to the HEG service e. the identification returned by the HEG service (e.g., the pid).	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08794	The OM GUI shall allow operators to cancel any of the HEG granules that are currently pending with the HEG processing service.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08800	The OM GUI shall allow appropriately authorized operators to edit the configuration information for the HEG processor.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08810	The OM GUI shall allow appropriately authorized operators to suspend the dispatching of HEG processing if this is currently not suspended.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08820	The OM GUI shall allow appropriately authorized operators to resume the dispatching of HEG processing if it is currently suspended. [NOTE: Resumption will cause any pending alert to be cleared.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08830	The OM GUI shall allow appropriately authorized operators to stop the acceptance of distribution requests involving HEG processing.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08840	The OM GUI shall allow appropriately authorized operators to resume  the acceptance of distribution requests involving HEG processing if it is currently stopped.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08850	The OMS CI shall return an appropriate error to submissions of distribution requests involving HEG processing while the acceptance of such requests is stopped.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08860	The OM GUI OMS status page shall indicate whether any processing/subsetting queues are currently suspended or not. [NOTE: This is to ensure that there is an indication of the queue status on the OMS status page even if there is a separate status page for the HEG queue (see S-OMS-08790). The requirement has been formulated in general terms: when other subsetting/processing queues are added, the OMS status page is supposed to show only a summary status of all queues.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08870	The OM GUI OMS status page shall indicate whether the acceptance of any processing/subsetting requests is currently stopped  or not. [NOTE: This is to ensure that there is an indication of the queue status on the OMS status page even if there is a separate status page for the HEG queue (see S-OMS-08790). The requirement has been formulated in general terms: when other subsetting/processing queues are added, the OMS status page is supposed to show only a summary status of all queues.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08880	The OM GUI shall be able to filter the request list so it displays only requests involving HEG processing.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08882	The OM GUI shall be able to filter the list of archived requests so it displays only requests involving HEG processing.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08890	The OM GUI shall indicate requests that involve HEG processing when listing requests.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08892	The OM GUI shall indicate requests that involve HEG processing when listing archived requests.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08900	The OM GUI shall provide request editing, cancellation, suspension, resubmission, etc. capabilities for requests involving HEG processing similar to other distribution requests to appropriately authorized operators.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08908	When displaying a granule list for a request that involves HEG processing, the OM GUI shall display the original input granule. [NOTE: The OMS design may elect to represent the processing outputs as output granules.  However, from an operator perspective, it is more meaningful to display the granule that is the basis for the processing and is the one originally specified by the user.]	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08910	The OM GUI shall allow an operator to display the HEG processing instructions for each granule that requires HEG processing.	
OD_S5_02	Managing HEG Orders	no data				S-OMS-08920	The OM GUI shall include order tracking information for requests involving HEG processing when archiving order tracking information. [NOTE: See NCR 39889 for details regarding the archiving of order tracking information.]	
OD_S5_02	Managing HEG Orders	no data				S-PDS-10040	The PDS CI shall distribute physical media distribution requests that include HEG processing outputs.	
OD_S5_05	Interface SCLI With OMS	no data				S-OMS-13100	The OMS CI shall provide a command line interface that is backwards compatible with the SDSRV command line interface (SCLI) in terms of interface functionality and behavior, but which submits data requests to the OMS rather than the SDSRV.  [NOTE: This interface does not need to support the submission of Landsat subsetting requests.]	
OD_S5_05	Interface SCLI With OMS	no data				S-OMS-13110	The OMS CI version of the SCLI shall be configurable to submit data requests to the OMS or the SDSRV.	
OD_S5_05	Interface SCLI With OMS	no data				S-OMS-13120	The OMS CI version of the SCLI shall provide a backwards compatible interface to obtain MCF files from the SDSRV.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06200	The Data Pool shall use secret names for the collection group and collection directories in the hidden directory structure that are derived from the corresponding public name by appending a random string of no less than eight (8) characters. [NOTE: The purpose of this requirement is to ensure that the directory names cannot be easily guessed and not easily produced even if the encryption algorithm and key are known.  The method for deriving the secret directory names cannot be verified during integration testing, but must be verified during code inspection]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06210	The Data Pool shall allow Development to select from the following two choices via configuration during deployment: a. The hidden directories for all collections will be located on a specified file system reserved for order-only granules. b. The hidden directories for all collections will be located on the same file system as the public directories of a collection. [NOTE: The purpose of this requirement is not to allow the DAAC to change this via configuration, but to defer the final choice until deployment planning.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06220	When creating files or directories in the hidden directory structure, the Data Pool insert service shall apply the Unix permissions to these files and directories that are required to achieve the intended data hiding. [NOTE: As per design instructions, the required masks must be established during  preliminary design. ]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06230	The Data Pool shall provide a utility to create and save the hidden directory names during transition.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06240	The Data Pool shall provide a utility which a DAAC can employ during Data Pool and OMS downtime to create new names for the hidden directories, save these names, rename the existing hidden directories, and update existing FTP Pull links that point to the previous hidden directories to point to the corresponding renamed directory. [NOTE:  TBD during unit testing  - Evidence must be provided during unit testing that the FTP Pull links can be renamed at a rate of no less than 10 links per second.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06250	The Data Pool Maintenance GUI shall create a secret name for a collection and collection group when a new collection or collection group is defined.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06260	The Data Pool Insert Service shall allow the insertion of order-only granules into the Data Pool regardless of whether a collection is enabled for Data Pool insert or not, and regardless of whether the insert is normally restricted to metadata only. [NOTE:  These restrictions are only meaningful for inserts into the public Data Pool.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06262	The Data Pool Insert Service shall generate links in the hidden directories when processing an insert of a granule for ordering purposes into the Data Pool for any granule files that are already in the public Data Pool.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06264	The Data Pool Web Service shall not provide access to the science files of any granules belonging to collections whose public Data Pool inserts are restricted to metadata only even if these are available in the hidden directories for ordering purposes.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06266	The Data Pool Most Recent Inserts Utility shall not list the science files of any granules belonging to collections whose public Data Pool inserts are restricted to metadata only even if these were inserted into the hidden directories for ordering purposes.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06270	The Data Pool Insert Service shall generate hidden directories based on the names saved in the Data Pool inventory when these directories do not yet exist.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06280	The Data Pool Insert Service shall convert an order-only granule into a normal Data Pool granule in accordance with S-DPL-42480 in Ticket OD_S4_01, without restaging the granule files from the archive and without causing ftp pull operations for granules ordered for FTP Pull to fail. [NOTE: This will require some measures to maintain the integrity of the ftp pull links.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06290	The Data Pool ftp service shall hide the names and contents of all hidden directories, with the possible exception of the top-level directory. [NOTE: The directory structures must be accessible via anonymous ftp, but their names and contents must not be returned to ftp clients, e.g., via ftp ls commands.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06300	The Data Pool ftp log analyzer shall send an e-mail to a configured e-mail address when it detects direct accesses to hidden directories, i.e., external accesses that did not use the FTP Pull links but hidden directory names in an FTP protocol command, and include the following information in that e-mail for each unique combination of external address and directory: a. external address b. identification of the collection that was accessed c. number of accesses d. first time this access was detected in the log e. last time this access was detected in the log	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06310	The Data Pool collection remap utility must also remap the hidden directory for a collection that is being remapped to a different collection group. [NOTE: The integrity of existing pathnames and links must be maintained, e.g., as used by OMS or FTP Pull.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-DPL-06320	The Data Pool collection move utility must also move the hidden directory for a collection when the collection is being moved to a new file system and the Data Pool is configured for keeping public and hidden directories for a collection on the same file system, and not perform such a move if a separate file system has been configured for the order-only granules. [NOTE: The integrity of existing pathnames and links must be maintained, e.g., as used by OMS or FTP Pull.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-OMS-08200	The OMS CI shall be configurable to support the processing of orders for restricted data in Synergy IV mode. [NOTE: Changing this configuration may require rebooting the OMS server.  This configuration parameter removes the automatic routing of such orders according to Synergy III rules.  Allowing this data to be stored in the Data Pool in a 'hidden' fashion is the responsibility of the Data Pool services.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-OMS-08210	The OMS CI shall be configurable to support the processing of orders for billable data in Synergy IV mode. [NOTE: Changing this configuration may require rebooting the OMS server.  This configuration parameter removes the automatic routing of such orders according to Synergy III rules.  Allowing this data to be stored in the Data Pool in a 'hidden' fashion is the responsibility of the Data Pool services.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-OMS-08220	The OM GUI shall be able to display whether OMS is configured to process orders that include billable, respectively restricted data, in Synergy 3 mode.	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-OMS-08222	The OMS CI shall generate links in the hidden directories when discovering that the science and metadata files for an ordered granule are already in the public Data Pool but the links are not yet in the hidden directories. [NOTE: A granule belonging to a collection enabled for metadata only insert may be in the public Data Pool, but its science files are not and hence, the granule needs to be inserted for ordering purposes.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-OMS-08230	The OMS CI shall be able to remove order-only granules that are no longer required for order fulfillment from the hidden directories, as well as the public directories. [NOTE: Order-only granules may reside in public directories during a transition time period.  Cleanup of order-only granules will be performed by a new OMS function.]	
OD_S5_06	Hiding Order-Only Granules In The Data Pool	no data				S-OMS-08240	The OMS CI shall not classify orders for Synergy III mode processing just because they reference granules from collections that are not enabled for Data Pool insert or are enabled for metadata insert only. [NOTE:  These restrictions are only meaningful for inserts into the public Data Pool.]	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-DPL-00450	The Data Pool FTP service shall give users an option to download metadata in .met file format rather than XML file format, generating the .met files on the fly. [NOTE: These .met files cannot include collection level metadata since they will be generated on the fly form the XML files in the Data Pool which do not contain this type of metadata.]	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00400	The OM GUI shall allow DAAC operators to configure a list of Email addresses of .met-file recipients, i.e., users that need to receive metadata in .met file format.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00405	The OMS CI shall by default provide metadata in XML format for all orders.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00410	The OMS CI shall distribute metadata files in ODL .met file format if the Email address for the Distribution Notice matches the Email address of a .met-file recipient.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00415	The OMS CI shall distribute metadata files in the format specified by the operator regardless of the Email address for the Distribution Notice if the operator changed the format during request resubmission.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00420	When the OMS CI distributes metadata files in ODL .met file format, the metadata files shall be identical in format and content to current .met files, to include collection level metadata.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00425	The OMS CI shall include the format used for metadata distribution for a request in the archived order tracking information.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00430	The OMS CI shall include .met files in its cleanup of distribution requests.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00435	When displaying request details, the OM GUI shall display the format for metadata distribution that the OMS will use for the request.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00440	When displaying request details for archived requests, the OM GUI shall display the format for metadata distribution that the OMS used for the request.	
OD_S6_01	Distribution Of Metadata in Either XML or .met Format	no data				S-OMS-00445	The OM GUI shall allow operators to update the metadata format to be used for distribution when resubmitting a request that is in a terminal state.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04010	The OMS CI shall provide a secure distribution service.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04015	The OMS CI shall allow DAAC operations to configure whether secure distributions shall be processed in Synergy III or Synergy IV mode.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04030	The OMS CI shall allow operators to configure scp destinations, analogous to the manner in which operators can configure ftp destinations.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04040	The OMS CI shall allow operators to configure the same staging policy parameters for scp destinations as for ftp destinations.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04070	The OMS CI shall be able to execute multiple secure distribution operations to the same as well as different scp destinations concurrently.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04080	The OMS CI shall suspend dispatching of scp operations to a destination and generate an operator alert under the following conditions: a.  the scp operation exceeded its maximum  allowed time, b. a connection to the target host could not be established, c. scp login fails, d. the destination directory does not exist, e. the permission to write to the destination directory is denied, f. the maximum number of consecutive errors has been exceeded g. the destination directory is not a directory (e.g., secure copy is capable of detecting this condition and returning it in an error code) h. protocol mismatch (e.g., secure copy is capable of detecting this condition and returning it in an error code) [NOTE:  This extends requirement S-OMS-06625 in Ticket OD_S4_01 to scp, adding items f through h for scp to those already being tested for ftp push.]	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04090	The OM GUI shall provide capabilities for viewing and handling operator alerts resulting from secure copy operations that match those for ftp push.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04100	The OM GUI shall provide capabilities for viewing and handling operator interventions resulting from secure copy operations that match those for ftp push.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04110	The OMS CI shall schedule staging and secure distribution operations for secure distribution requests in accordance with the configured staging and push policy parameters, similar to the current handling of ftp push operations.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04120	When listing or displaying destinations, the OM GUI shall identify those that are designated for secure distribution.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04130	The OMS CI shall transfer the DN for successful secure distribution requests to the user via scp rather than via e-mail, using file formats and file naming conventions that are the same as those used by NCR 41991 and are compliant with ESDIS document number 423-41-57, 'Interface Control Document between the EOSDIS Core System (ECS) and the Science-Investigator-led Processing System (SIPS), Volume 0, Interface Mechanisms.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04132	The OMS CI shall place a secure copy request into operator intervention under the following circumstances: a. A granule associated with the request fails to stage successfully (e.g., failed Data Pool inserts) b. The operator has chosen to cancel the request [NOTE: The legacy behavior is described in requirements OMS-06530 & OMS-06355].	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04133	In the event of an unsuccessful secure copy transfer of the distribution notice for a secure copy request, the OMS CI shall do the following: a.Send the distribution notice to the user via the email address associated with the request. Send an email to the OMS operator indicating the secure copy notice failure, the associated request ID, and the email address to which the secure copy distribution notice will be sent.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04135	The OMS CI shall transfer the DN for failed secure distribution requests to the user via e-mail, using file formats and file naming conventions that are the same as those used by NCR 41991 and are compliant with ESDIS document number 423-41-57, 'Interface Control Document between the EOSDIS Core System (ECS) and the Science-Investigator-led Processing System (SIPS), Volume 0, Interface Mechanisms.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04150	The OMS CI shall queue scp operations for DNs for a destination along with the scp operations for files, and apply any limits on the maximum number of concurrent operations to their combined number of scp operations.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04160	The OM GUI shall treat secure distribution as a separate media type, e.g., from the perspective of queue suspension and resumption, and displaying statistics and summary information, for example, as specified in OD_S4_01, S-OMS-06120 and S-OMS-06130.	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04170	The OM GUI shall treat secure distribution destinations like ftp push destinations, e.g., from the perspective of displaying statistics and summary information (e.g., as specified in OD_S4_01, S-OMS-06120, S-OMS-06130, S-OMS-06170) or handling suspension, resumption and similar destination management functions (e.g., as specified in OD_S4_01, S-OMS-06195, S-OMS-06200, S-OMS-06205, S-OMS-06210).	
OD_S6_02	OMS Distribution of Data via scp	no data				S-OMS-04180	The OM GUI shall treat secure distribution requests similar to ftp push requests, e.g., from the perspective of list, sort, and filter capabilities (e.g., as specified in OD_S4_01, S-OMS-06135, S-OMS-06140, S-OMS-06145, S-OMS-06175, S-OMS-06180, S-OMS-06185, S-OMS-06190), and request editing capabilities (e.g., OD_S4_01, S-OMS-06265, S-OMS-06270, S-OMS-06310, S-OMS-06320, S-OMS-06350).	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DMS-01150	The GTWAY CI shall register requests for external subsetting with the OMS. NOTE: This modifies S-DMS-33350 in Ticket ES_SY_01.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DMS-01155	The GTWAY CI shall identify the external subsetter that needs to process an external subsetting request when registering such a request to the OMS. [NOTE: The GTWAY will update the status of the MSS requests object based on the response from the external subsetter, see the related L4. Specifically, the status will be updated to Pending if the external processing service accepted the request, and to Aborted if the external processing service rejected the request.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DMS-01165	The GTWAY CI shall accept error responses from the OMS for registration errors and include the appropriate error information in the product result message, in accordance with the Interface Control Document for ECS Interfaces That Support External Subsetters Located at DAACs, ESDIS Document 423-41-66. [NOTE: A request that cannot be registered with OMS will be rejected.  Errors that prevent registration include invalid ESDT reference, invalid granule ID, and OMS database errors.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DSS-22310	The EPD shall cause the distribution of the outputs from external subsetters and processing systems via the OMS CI.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DSS-22315	The EPD shall be able to accept and distribute output granules from external processing systems for collections other than SBSTDATA, and do so for one or several granules that belong to different collections. [NOTE: This requirement cannot be integration testing since the subsetters available for testing do not generate the required outputs.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DSS-22330	The EPD shall transfer the outputs of an external processing request that are identified in the PDR to a directory structure in the Data Pool SAN that is hidden from anonymous user access.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DSS-22340	The EPD shall notify OMS of the arrival and location of the outputs it ingested, as well as the request ID of the corresponding external processing request.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-DSS-22350	The EPD shall retry notifying OMS indefinitely at the configured retry interval when such notification attempts fail. [NOTE: OMS is responsible for handling the remaining distribution steps, including cleanup of the ingested files.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02210	The OMS CI shall provide an interface to accept registrations of external processing requests from the GTWAY CI and save them in the OMS database, including for each request the designated external subsetter for this request. [NOTE: The size of the ODL string may be quite large since a single subsetting request can span many granules. A size allowance of 3 MB is adequate and in line with DAAC feedback during RTR regarding expected request sizes.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02220	The OMS CI shall return an appropriate error to the V0 Gateway for user requests that require a processing service for which the acceptance of requests is stopped. [NOTE: See also the analogous requirement S-OMS-08850 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02225	If an external processor has been configured in OMS, it shall use its configured name for its identification and the identification passed in by the V0 Gateway otherwise. [NOTE: Requests that reference external subsetters which were not configured in OMS will not be rejected, but their subsetter identifications may have a different look when displayed in the OM GUI, e.g., they may be host+port information rather than a name.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02230	The OMS CI shall be able to identify requests for external processing inputs and the external processing system that originated them based on the unique DN Email address used by that external processing system, if the corresponding information has been configured in OMS. [NOTE:  The external processing must use this feature if it expects to use any OMS capabilities that depend on the ability to identify the source of input requests.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02240	For external processing requests that requested distribution via FTP Pull, the OMS CI shall make the outputs available for FTP Pull and queue a DN after the outputs were ingested successfully. [NOTE:  Sending the DN for other media types after distribution is complete is covered by existing requirements.  This is analogous to requirement S-OMS-08550 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02245	The OMS CI shall not include the list of input granules nor their status in the Distribution Notices sent for external processing requests, but instead include the external processing outputs, as well as additional preamble text that can be configured by the DAAC separately for each configured subsetter.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02255	The OMS CI shall update the request size in the MSS order tracking table for external processing requests after their outputs have been ingested to contain the total size of the granules that are distributed, i.e., for granules involving processing, the OMS CI shall use the size of the outputs rather than the input size. [NOTE: This is analogous to requirement S-OMS-08562 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02260	The OMS CI shall update the number of files in the MSS order tracking table for external processing requests after their outputs have been ingested to contain the total number of the files that are distributed, i.e., for granules involving external processing, the OMS CI shall use the number of the output files rather than the number of input files. [NOTE: This is analogous to requirement S-OMS-08562 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02265	The OMS CI shall queue the outputs of a user request that involves external processing and specifies FTP Push for final distribution after the outputs have been ingested and the request passed any subsequent validations. [NOTE: This is analogous to requirement S-OMS-08570 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02270	The OMS CI shall be able to distribute external processing outputs via any of the electronic media types it supports.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02280	The OMS CI shall include in the DN for a user request specifying FTP Pull distribution, URL links for each of the output packaging options that are supported for downloading, including the metadata files of the input granules, if so configured by the DAAC. [NOTE: This is a duplicate of S-OMS-08595 in Ticket OD_S5_02, as a reminder that these options must be available for external processing outputs, as well.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02285	The OMS CI shall remove processing outputs received from external processing services from the Data Pool when they are no longer needed for distribution. [NOTE: This augments S-DSS-31670 in Ticket ES_SY_01 and is analogous to S-OMS-08630 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02290	The OMS CI shall remove input granules staged for external processing when they are expired and are no longer needed for distribution or by another user request.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02300	If the DN Email address and FTP Pull expiration for an external processing system has been configured in OMS, the OMS CI shall use that FTP Pull expiration time for FTP Pull requests received from that external processing system.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02305	The OMS CI shall remove any temporary files it created in support of external processing once they are no longer needed. [NOTE: The requirement is analogous to S-OMS-08610 Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02310	The OMS CI shall log the following events related to external processing: a. Receipt of the external processing outputs. b. Errors related to the receipt of external processing outputs c. Events that are normally logged during distribution.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02320	The OMS CI shall format its application log entries compliant with the current ECS log format (e.g., they contain time and severity), and include the following information for log entries related to the receipt and distribution of external processing outputs, as applicable: a. Request ID b. Granule ID c. file name and file size d. error/event identification and explanation e. message types and identifications [NOTE: The requirement is analogous to S-OMS-08660 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02325	The OMS CI shall include order-tracking information for user requests involving external processing when archiving order tracking information, excluding the processing instructions. [NOTE: See also the analogous requirement S-OMS-08920 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02330	The OMS CI shall remove and not archive order-tracking information for user requests involving external processing that are in the NULL state at the time they normally would be archived if they were completed requests. [NOTE: In line with DAAC feedback during RTR, the OMS will not remove Aborted requests from the OMS database when the V0 Gateway updates the state to Aborted.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02335	The OM GUI shall allow authorized operators to specify the following information for each external processing service: a. the unique name (i.e., an operator assigned label) for the external processing service, b. the DN Email address used by that external processing service, and if that information has been provided, also the following: c. Deleted, d. Optional text of up to 255 characters to include as part of the preamble in any Distribution Notices (DN) sent to users after completing the distribution of requests for this subsetter, e. an FTP Pull expiration time, not to exceed the FTP Pull expiration for normal FTP Pull orders. f. the host and port of that external processing service, as configured in the ECS registry. [NOTE: The V0 Gateway passes the host and port to the OMS during the registration, allowing the OMS to associate the request with the applicable configuration entry.] [NOTE: Configuring an external processing service in OMS is optional.  However, some OMS capabilities are only available to external processing services that have been configured.  This is spelled out in the corresponding requirements.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02340	The OM GUI shall allow operators to delete an external processing service for which no requests are currently pending and for which request acceptance has been stopped, requesting confirmation from the operator before performing the deletion.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02345	The OM GUI shall allow operators to view a list of external processing services, including for each: a. its configured identification, b. its DN Email address and other properties as per S-OMS-02335, c. the number of requests and granules currently queued, as well as the total amount of input data, and d. whether the acceptance of requests for that processing service is stopped.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02350	The OM GUI shall allow appropriately authorized operators to edit the configuration information for any of the listed external processing services.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02355	The OM GUI shall allow appropriately authorized operators to stop the acceptance of requests for an external processing service. [NOTE: See also the analogous requirement S-OMS-08830 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02360	The OM GUI shall allow appropriately authorized operators to resume the acceptance of requests for an external processing service if this is currently stopped. [NOTE: See also the analogous requirement S-OMS-08840 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02365	The OM GUI OMS status page shall indicate whether the acceptance of processing requests for any processing service is currently stopped or not. [NOTE: See also the analogous requirement S-OMS-08870 in Ticket OD_S5_02.  The intention is to have a single indicator for the status of all processing queues, including the HEG processing queue.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02370	The OM GUI shall be able to filter the user requests so it displays only requests for a specific processing service. [NOTE: See also the analogous requirement S-OMS-08880 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02375	The OM GUI shall provide the same filter and sort capabilities for request and granule lists that show external processing requests as for the general list of distribution requests and their granule lists.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02380	The OM GUI shall be able to filter the list of archived user requests so it displays only requests for a specific processing service. [NOTE: See also the analogous requirement S-OMS-08882 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02385	The OM GUI shall provide the same filter and sort capabilities for lists of archived requests that show external processing requests as for the general list of archived distribution requests and their granule lists.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02390	The OM GUI shall identify requests that involve external processing when listing requests. [NOTE: See also the analogous requirement S-OMS-08890 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02395	The OM GUI shall identify requests that involve external processing when listing archived requests. [NOTE: See also the analogous requirement S-OMS-08892 in Ticket OD_S5_02.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02400	The OM GUI shall provide request cancellation, and suspension capabilities for distribution requests involving external processing while they are under OMS control, i.e., after their outputs have been ingested.	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02405	The OM GUI shall not permit an operator to resubmit an external processing request that is in a terminal state (e.g., shipped, aborted, cancelled). [NOTE: The OMS has no interface with the external processing service and hence cannot submit such requests.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02410	When displaying a granule list for a request that involves external processing, the OM GUI shall include the outputs once they have been ingested. [NOTE: During final distribution, the input granules are irrelevant; any errors will be related to the outputs, which are not related to any specific input granule.]	
OD_S6_03	OMS Distribution of Externally Subsetted Products Requested via V0GWY	no data				S-OMS-02415	The OM GUI shall allow an operator to display the external processing instructions for a request (excluding historic requests), and save them in a locally accessible file. [NOTE: HEG processing instructions and external processing instructions may be stored in different formats.]	
OD_S6_04	Distribution of Bulk Browse Products	no data				S-DPL-18600	The DPL CI shall not permit the ECSBBR collection to be enabled for insertion into the public Data Pool.	
OD_S6_04	Distribution of Bulk Browse Products	no data				S-OMS-02500	The OMS CI shall be able to distribute bulk browse products, i.e., granules of the ECSBBR collection together with the browse files they reference, in their original format, in Synergy IV processing mode.	
OD_S6_04	Distribution of Bulk Browse Products	no data				S-OMS-02510	The OMS CI shall include ECSBBR granules and their files in the cleanup of distribution requests.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30000	The Web Order Status Interface shall be compatible with the EMD baseline versions of web browsers and operating systems in accordance with Technical Document 910-TDA-042-Rev01, EMD Browsers Baseline.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30010	The Web Order Status Interface shall be accessible to external users through the ECS firewall.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30020	The Web Order Status Interface shall be accessible to local users inside the ECS firewall.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30030	The Web Order Status Interface shall support DAAC-configurable headers and footers on each web page.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30040	The Web Order Status Interface shall be compliant with federal laws defined in Section 508 of the Rehabilitation Act.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30050	The Web Order Status Interface shall allow a user to request the status of a single order by specifying the following information: a.  Order Id b.  User contact email address	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30060	The Web Order Status Interface shall allow a user to request a history of all orders submitted over a date range by specifying the following information: a.  Beginning and ending dates b.  User contact email address c.  Order Id of any order submitted by the user 	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30070	The Web Order Status Interface shall allow a user to request a history of all orders submitted over a date range by specifying the following information: a.  Previous number of days b.  User contact email address c.  Order Id of any order submitted by the user [NOTE:  Previous number of days may be selected from a pick list (e.g., last 30 days, last 60 days) rather than entered by the user.]	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30080	The Web Order Status Interface shall retrieve information from both the OMS operational and archive database tables, if necessary, to fulfill a request for order history. 	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30090	The Web Order Status Interface shall return an error message and not display any order status if the requested date range exceeds the DAAC-configurable limit on the number of days of order history that can be requested.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30100	The Web Order Status Interface shall display the following status information for each qualifying order: a.  Order Id b.  Submission date/time c.  Order state, translating ECS status values into status terms generally understandable to an end user d.  Order completion date/time (if order is in a completed state) e.  List of requests associated with the order	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30110	The Web Order Status Interface shall display the following status information for each request associated with an order: a.  Request Id b.  Request state, translating ECS status values into status terms generally understandable to an end user c.  Media type d.  Number of granules e.  Request completion date/time (if request is in a completed state) f.  An indication whether more detailed information is available or not	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30120	The Web Order Status Interface shall segment order and request status information based on a user-selectable number of items per page.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30130	The Web Order Status Interface shall by default sort order status by order submission date/time. 	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30140	The Web Order Status Interface shall display the following detailed request information when requested by the user and if it is available: a.  Request Id b.  List of granules associated with the request c. Processing description [NOTE: A granule processed by the external subsetter will have its processing description associated with the request in which it was contained.  Even though granule processing recipes used by HEG and HEW may be stored in different internal formats, the external processing descriptions provided to the user should be made as uniform and understandable as possible. ]	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30150	The Web Order Status Interface shall display the following information for each granule associated with a request, if it is available: a.  Granule Id b.  Collection short name c.  Collection version id d.  Granule size in megabytes e.  Granule state, translating ECS status values into status terms generally understandable to an end user f.  Granule processing description [NOTE:  A granule that was processed by the HEG will have an associated granule processing description at the granule level, which contains an explanation of the processing that was performed by HEG.  Even though granule processing recipes used by HEG and HEW may be stored in different internal formats, the external processing descriptions provided to the user should be made as uniform and understandable as possible.]	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30155	The Web Order Status interface shall not be required to display granule level status information for output granules.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30160	The Web Order Status Interface shall segment granule status information based on a user-configurable number of granules per page.	
OD_S6_05	Web Accessible Order Status and History	no data				S-CLS-30170	The Web Order Status Interface shall return the first segment of order status information within 10 seconds when running under a normal DAAC workload with an order, request, and granule segment size less than or equal to 25 and a total of at least 25,000 orders in the active orders database table and at least 50,000 requests in the active requests database table.	
OD_S6_05	Web Accessible Order Status and History	no data				S-OMS-04310	The OMS CI shall provide a DAAC-configurable limit on the number of days of order history that can be requested.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20310	The HEG Converters shall provide  support for the following MODIS Aqua HDF-EOS data types: a. MYD09A1.004; b. MYD11A1.004; c. MYD13A1.004; d.MYD13A2.004; e. MYD13Q1.004. Support for these data types must include the ability to:   convert from HDF-EOS to GeoTiff format  reproject to supported HEG projections  subset spatially by bounding box  	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20335	The HEG Converters shall allow the production of external metadata files associated with GeoTiff converter output to be optional.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20340	The HEG CI shall provide a standard  synchronous interface for all HEG conversion requests.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20350	The standard HEG interface shall be callable from java and C++ applications.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20360	The standard HEG interface shall accept the following input parameters from its clients for a HEG conversion request:   Requestor / client name (e.g., OMS, W*S, DOWS Converter)  A unique identifier for the request (optional, unless client indicates it will attempt to reconnect if interrupted by a fault; see (o) below.)  Input file path and file name (DESIRABLE:  multiple input file names to support stitching)  Whether the input file is compressed  Decompression algorithm for input file (if applicable)  Output file format  Output file projection  Output file projection parameters (if they were supplied by end user) (Note:  if projection parameters are not supplied by the end user, the HEG converter executables will supply defaults)  Output file subset type (optional)- e.g., spatial, band, field  Output file subsetting parameters (optional)  e.g., bounding rectangle corner coordinates, object names, field names, band names, band values, 4th dimension names, 4th dimension values  Output file name(s) (optional)  Output file directory name  Whether metadata files (e.g., .tif.met, .hdf.met) should be produced with the converter output  Whether a request summary file (i.e., ConverterSynopsis.txt) should be produced for the request  Whether all output GeoTiffs produced by the HEG converters should be combined in a single multi-band GeoTiff  That the client will not reconnect to a pre-submitted HEG service request if the request is interrupted by a fault  (NOTE:  this does not imply that the standard HEG interface will or can recover a request interrupted by a fault and allow a client to reconnect to it).  	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20365	The standard HEG interface shall be able to run in debug mode.    When running in debug mode, the HEG interface shall instruct the HEG converters not to remove temporary files created during the conversion process; when not running in debug mode, the HEG interface shall instruct the HEG converters to remove temporary files at the completion of the conversion process.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20370	The standard HEG interface shall accept and carry out requests to cancel a HEG service request (i.e., an execution of a HEG converter executable.)   When the request is cancelled, no permanent or temporary output files shall remain. (NOTE:  For Synergy V, only the C++ client will require this service).	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20375	The standard HEG interface shall produce a request summary file (ConverterSynopsis.txt) and place it in the client-specified output directory, if requested to do so by the client.   (Note:   This file is currently produced by the HEG Front End/WebAccess packager).	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20380	The standard HEG interface shall return a completion status code to its clients.   (the set of valid completion codes is TBD by design). 	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20390	The standard HEG interface shall return to its clients the process id of the HEG converter process that was started on behalf of the clients HEG service request. (NOTE:  For Synergy V, only the C++ client will require this service).	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20400	The standard HEG interface shall return to its clients the names of all output files produced by the HEG converters.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20410	The standard HEG interface shall decompress compressed-format input files before making them available to the HEG converters for conversion, using the decompression algorithm provided by the client.  If no decompression algorithm is provided, the standard HEG interface shall use a standard decompression algorithm which corresponds to the compressed-format suffix of the input file, if possible.  Ref: Ticket DP_S4_07: Support Compression on Data Pool Insert, requirement S-DPL-75135: The HEG Front End shall decompress files which were compressed at insert time before converting them, using the decompression algorithm provided by the DAAC.  If no decompression algorithm is provided, the HEG Front End shall assume that decompression is not necessary.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20420	The standard HEG interface shall gracefully handle termination of the client-side connection.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20430	The standard HEG interface shall be able to gracefully handle resubmission of a request by its client; i.e., resubmission of a request by a client shall not result in file creation errors nor failure to return a completion status to the client.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20440	The standard HEG interface shall successfully handle a configurable number of concurrent requests from multiple clients.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20450	Different instances of the standard HEG interface shall be able to execute in different EMD operation modes concurrently and independently.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20460	The standard HEG interface shall be able to log the following information and/or events at the applicable debug levels  (TBD by detailed design which information and/or events should be logged at which debug levels):   start up  mode of operation (if applicable)  c. receipt of data conversion request  input parameters received from client  submission of request to converter  process id of converter request  command line content for converter request submission  content of parameter file sent to converter  completion of converter request  results of converter request  error conditions (input file not found, client no longer communicating, resubmission of request)  shut down  All log entries shall be date/time stamped to the nearest millisecond.	
OG_S5_01	HEG Extensions for OWS	no data				S-HEG-20470	The standard HEG interface shall create the appropriate parameter file and call the appropriate HEG converter executable (i.e, gdtif, swtif, resample, etc.) based on the HDFEOS objects within the input data set and on the requested output conversion options.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01400	The GSCT prototype shall chain an OWS compliant WCS+ (version 1.0.20).	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01410	The GSCT prototype shall chain an OWS compliant WCTS prototype based on HEG functionality according to the results of the IH4DS thread.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01420	The GSCT prototype shall chain an external OWS compliant WCTS according to the results of the IH4DS thread.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01430	The GSCT prototype shall chain an external OWS compliant WICS according to the results of the IH4DS thread.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01460	The GSCT prototype shall return a successful completion document once the execution of the chaining service is done. The user can download the processed data via the url embedded in the completion document.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01470	The GSCT prototype shall return an exception document once the execution of a service has failed. The exception document shall contain the service failure reason (such as no data found).	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01480	The GSCT prototype shall log the chain execution and make the log available to the user.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01490	The GSCT prototype shall allow the user to populate a chain template and deploy a service chain.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01500	The GSCT prototype shall have a web GUI so that a user can access the GSCT prototype via a http web address.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01510	The GSCT prototype shall provide the user a list of 4 defined chains for the purpose of allowing the user to select one.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01520	The GSCT prototype shall contain several different chain templates	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01530	The WCTS prototype shall provide a service that conforms to the WCTS 0.0.20 Implementation Specification with the following constraints/exceptions: a. The WCTS prototype shall support a single HTTP URL as the input data component of a Transform request. b. The WCTS prototype shall support a single HTTP URL as the output data component of a Transform response c. The WCTS prototype shall support the following processing capabilities provided by the HEG:    Projections: Geographic, UTM   Input Formats: HDF-EOS   Output Formats: HDF-EOS, GeoTIFF   Interpolation Methods: Nearest neighbor   	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01540	The WCTS prototype shall have valid WSDL so it can be chained in a BPEL process.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01550	The WCTS prototype shall store resultant products locally.  This local disk can be accessed via HTTP remotely by other services or external end users.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01560	The administrator of the WCTS prototype shall be able to delete products off the server after an expiration time is reached. The expiration time shall be configurable.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01570	The WCTS prototype shall accept requests through HTTP GET and POST bindings.	
OG_S5_02	Image Processing Services for Decision Support	no data				S-OWS-01580	The WCTS prototype shall store input data for a Transform request locally.  The input data shall remain on disk until the Transform request is processed.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01720	The DOWS shall support version 1.0 of the Open Geospatial Consortium Web Coverage Services specification. http://www.opengeospatial.org/specs/?page=baseline s document Web Coverage Service Version 1.0 (03-065r6) dated 2003-10-16with the following exceptions:   The WCS shall, at a minimum, support WGS 84 coordinate reference system.  Of the above, the WCS shall, at a minimum, support those projections supported by the HEG tool.  c) The WCS shall, at a minimum, support GeoTIFF and HDF-EOS formats on input and output.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01730	The DOWS shall support version 1.1.1 of the Open Geospatial Consortium (OGC) Mapping Services specification. http://www.opengeospatial.org/specs/?page=baseline  document Web Mapping Service Version 1.1.1 (01-068r2) dated 2001-12-07	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01740	The DOWS shall support a Coverage Portrayal Service (CPS) that conforms to the OGC CPS Discussion Paper. http://www.opengeospatial.org/specs/?page=baseline document Coverage Portrayal Service (02-019r)  dated 2002-02-28	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01745	The DOWS shall support a WMS+SLD service that conforms to version 1.0.0 of the OGC SLD specification.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01750	The DOWS shall provide OWS access for up to 10 new Earth Science Data Types.   MOD13A2  MYD13A2  MOD13Q1  MYD13Q1  MOD13A1  MYD13A1  MOD11A1  MYD11A1  MOD09A1  MYD09A1  	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01770	The DOWS shall be able to store and manage up to 50000 pieces of inventory via OWS. [Note : the definition of an individual piece of inventory is the collection of GeoTIFFs created from a single hdf-eos granule]	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01780	The OWS Vendor shall support the following services on supported data types and as supported by HEG:  Format conversion  Spatial subsetting  Varying output resolution  Re-projections contained in WGS84  	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01830	The DOWS shall support the conversion to GeoTIFF of 16 bit HDF-EOS data.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01860	The DOWS shall provide a system that will be operationally stable whilst inserting and deleting granules and/or geoTIFFs at a rate of at least 5000 daily	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01870	The DOWS shall provide a system that will provide client visibility to new inventory at a rate of 1 update per two-second period.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01900	The Data Pool Maintenance GUI shall allow the 'full access' operator to create references to arbitrary groups of granules belonging to the same ECS Earth Science Data Type (ESDT) suitable for OGC web services. Those groupings will be referred to as OWS themes.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01910	The Data Pool Maintenance GUI shall allow the 'full access' operator to associate an OWS theme with a WMS layer.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01915	The DOWS shall associate a granule that belongs to a WMS theme with a unique WMS layer.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01920	The DOWS shall allow the operator to associate an OWS theme with a WCS coverage offering.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01925	The DOWS shall associate a granule that belongs to a WCS theme with a unique WCS coverage.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01930	The Data Pool Maintenance GUI shall allow the 'full access' operator to specify whether an OWS themes associated granules should be pre-converted to GeoTIFF files.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01940	The Spatial Subscription GUI shall allow the 'full access' operator to define OWS enabled data via a number of metadata constraints, such that only newly-inserted inventory, that corresponds to those constraints, is enabled. Those constraints may consist of one or more of the following,   Spatial  Temporal  Collection  	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01950	The DOWS shall allow the full access operator to add OWS themes to the system.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01970	The DOWS  Data Conversion Utility shall automatically convert HDF-EOS granules that,   Are inventory desired for OWS. This is defined as inventory that has been inserted during a specified time constraint.  Belong to an OWS theme that is marked for pre-conversion.   The conversion will be to one or more GeoTIFF files.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01980	The DOWS Data Conversion Utility shall place the GeoTIFF files in a location configurable by a full access operator if the datapool has sufficient space within the cache to accommodate this action. If there is insufficient space the GeoTIFFs will not be created and the synchronization utility will be informed. [Note: The Conversion Utility will leverage existing datapool functionality to determine this]	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01990	The DOWS Data Conversion Utility shall register the generated GeoTIFF files in the Data Pool Database as children of the originating HDF-EOS granule.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01995	The DOWS Data Conversion Utility shall add GeoTIFFs to the Data Pool inventory in a manner that will allow existing Data Pool clean up capabilities to remove them when their parent inventory is removed.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-01997	The Data Pool Cleanup Utility shall support the maintenance of the DOWS directories.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02000	The DOWS Data Conversion Utility shall only produce GeoTIFF files that are defined by the operator for the specific ESDT the HDF-EOS file belongs to.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02015	The DOWS Data Conversion Utility shall allow operators to specify a time range as an input parameter. This time range defines the bounds of desired OWS inventory based on Data Pool insert time.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02020	The DOWS  Data Conversion Utility shall run in previous time mode such that it will run over a previous unit of time (e.g., year, month, day, hour, minute) with respect to the current time. This time range defines the bounds of desired OWS inventory based on Data Pool insert time.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02030	The DOWS Data Conversion Utility shall allow operators to specify a time range at a granularity of one minute.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02040	The DOWS Inventory Synchronization Utility shall propagate OWS metadata to the W*S indexer via an API.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02060	The DOWS Inventory Synchronization Utility shall allow operators to specify a time range as an input parameter. This time range defines the bounds of desired OWS inventory based on Data Pool insert time.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02070	The DOWS  Inventory Synchronization Utility shall run in previous time mode such that it will run over a previous unit of time (e.g., year, month, day, hour, minute) with respect to the current time. This time range defines the bounds of desired OWS inventory based on Data Pool insert time.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02080	The DOWS Inventory Synchronization Utility shall allow operators to specify a time range at a granularity of one minute.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02090	The DOWS Inventory Synchronization Utility shall only propagate metadata that obeys the following constraints, a) Desired OWS inventory validated by a supplied time range. AND b) Inventory that belongs to an OWS theme.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02120	The DOWS shall allow the custom addition and removal of arbitrary WCS metadata, exposed by a DescribeCoverage request, for WCS inventory exported to the indexer.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02130	The DOWS Inventory Synchronization Utility shall allow the custom addition and removal of arbitrary WMS metadata, exposed by a DescribeLayer request, for WMS inventory exported to the indexer.	
OG_S5_06	Deploy OGC Web Services	no data				S-OWS-02135	The DOWS Inventory Synchronization Utility shall label, within the Data Pool database, all inventory that has been successfully synchronized	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00260	The OEA shall support version 2 of the Open GIS Catalogue Services Specification for the Z39.50 binding only.  (http://portal.opengis.org/files/?artifact_id=5929&version=1 )	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00270	The OEA shall support Version 6.0 of the ECHO application programming interface specification.  (http://api.echo.eos.nasa.gov/echo/About.jsp) 	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00280	The OEA shall support the following Z39.50 Version 3  (http://lcweb.loc.gov/z3950/agency/document.html ) requests,   a)  Initiate Session  b)  Terminate Session  c)  Search  d)  Present  e)  Status  f)  Cancel  	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00290	The OEA shall support the Geo profile, with respect to Z39.50.  (http://www.blueangeltech.com/Standards/GeoProfile/geo22.htm)	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00300	The OEA shall support the TCP transport mechanism for OGC Catalogue service requests and responses.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00310	The OEA shall accept Basic Encoding Rules (BER) TCP requests and transmit BER responses.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00320	The OEA shall receive TCP requests and transmit TCP responses as specified in  IETF RFC 1729: Using the Z39.50 Information Retrieval Protocol in the Internet Environment. 	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00340	The OEA shall be registered as a NSDI Clearing House node with the NSDI registry.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00360	The OEA shall support the Z39.50 Type I query language.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00370	The OEA shall be stateful with respect to client interaction. [Note: the definition of stateful corresponds to the definition supplied by the OGC Catalogue Services Specification for the Z39.50 binding.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00380	The OEA shall be able to process multiple sessions, concurrently.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00390	The OEA shall be able to process a configurable number of sessions at any given time. [Note: a change in the number of sessions will occur when the OEA is restarted]	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00410	The OEA shall log information pertaining to initialization and termination for a particular session.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00420	The OEA shall log information related to requests for a particular session.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00430	The OEA shall preserve the link between a Z39.50 session and its corresponding ECHO session.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00440	The OEA shall support the OGC Catalogue services Initiate session request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00450	The OEA shall support the OGC Catalogue services Terminate session request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00460	The OEA shall support the OGC Catalogue services Status request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00470	The OEA shall support the OGC Catalogue services Cancel request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00480	The OEA shall terminate the pending request described by any OGC Catalogue services Cancel request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00490	The OEA shall support the OGC Catalogue services Present request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00500	The OEA shall render an OGC Catalogue services Search request into an ECHO API call.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00510	The OEA shall render an OGC Catalogue services Present request into ECHO API calls to retrieve both metadata and service information.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00520	The OEA shall return an OGC Catalogue services Initiate session response when presented with an OGC Catalogue services Initiate session request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00530	The OEA shall return an OGC Catalogue services Terminate session response when presented with an OGC Catalogue services Terminate session request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00540	The OEA shall return an OGC Catalogue services Status response when presented with an OGC Catalogue services Status request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00550	The OEA shall return an OGC Catalogue services Cancel response when presented with an OGC Catalogue services Cancel request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00560	The OEA shall return an OGC Catalogue services Search response when presented with an OGC Catalogue services Search request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00570	The OEA shall return an OGC Catalogue services Present response when presented with an OGC Catalogue services Present request.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00580	The OEA shall render ECHO result set xml into FGDC-compliant xml when formulating an OGC Catalogue services Present response. The xml will conform to the FGDC's GEO profile.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00590	The OEA shall render Z39.50 Type I queries into ECHO-compliant alternative queries(IIMSAQL)	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00600	The OEA shall translate a Z39.50 Search request into an ECHO Search request within 0.5 seconds.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00610	The OEA shall translate an ECHO Search response for a single piece of inventory into a Z39.50 Search Response within 1 second.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00620	The OEA shall translate a Z39.50 Present request into an ECHO Present request within 0.5 seconds.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00630	The OEA shall translate an ECHO Present response for a single piece of inventory into a Z39.50 Present Response within 0.1 seconds.	
OG_S5_07	OGC Interface to ECHO	no data				S-OWS-00640	The OEA shall allow sessions to remain dormant for a configurable amount of time. If no subsequent requests are received during that time the session will be terminated.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70510	The DPM GUI shall distinguish between read-only and full capability operators in a secure fashion (e.g., using encrypted operator login protected and encrypted passwords).	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70520	The DPL shall allow DAAC operations to maintain independently for each mode, the information that identifies which capability an individual DAAC operators has when using the DPM GUI, and allow DAAC operations to restrict who can maintain that information.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70530	The DPM GUI shall retain the capability level of an individual operator -once it has been established - for the duration of the GUI session.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70535	The DPM shall time out an operator session if the last activity in that session is  a time out value that can be configured by DAAC operations. [NOTE: The time out value would be measured in minutes.  It would be the same for all GUI session, i.e., not operator specific.]	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70540	The DPM GUI shall provide the following functionality only to full capability operators: a. On the DPM Home page, the ability to update the free space flag or suspend/resume Data Pool inserts; b. On the DPM List Insert Queue page, the ability to cancel an insert; c. On DPM Configuration page, the ability to change a configuration parameter; d. On the DPM Manage Collection Group page, the ability to add or modify a collection group; e. On the List of Collections pages, the ability to add or modify a collection; and f. On the Detailed List of Themes page, the ability to add or modify a theme.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70550	When used by read-only operators, the DPM GUI shall disable all screen elements that are related only to functionality that is not available to read-only operators.  For example, the Manage Collection Group page shall disable the links that offer access to the add/modify capability (i.e., such that these links cannot be invoked).	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-DPL-70560	The DPM GUI shall make the following pages only accessible to full capability operators: a. Adding a collection group; b. Modifying a collection group; c. Adding an ECS collection; d. Adding a non-ECS collection; e. Modifying an ECS collection; f. Modifying a non-ECS collection g. Adding a Theme; and h. Modifying a Theme.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07010	The OM GUI shall distinguish between read-only and full capability operators in a secure fashion, as was approved by the ARB (e.g., via login and encrypted passwords).	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07020	The OMS shall allow DAAC operations to maintain independently for each mode, the information that identifies which capability an individual DAAC operators has when using the OM GUI, and allow DAAC operations to restrict who can maintain that information.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07030	The OM GUI shall retain the capability level of an individual operator - once it has been established - for the duration of the GUI session.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07035	The OMS  shall time out an operator session if the last activity in that session is a time out value that can be configured by DAAC operations. [NOTE: The time out value would be measured in minutes.  It would be the same for all GUI session, i.e., not operator specific.]	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07040	The OM GUI shall provide the following functionality only to full capability operators: a. On the OM Server Queue Status page, the ability to change the state of queue; b. On the OM Configuration pages, the ability to change a configuration parameter; c. On the OM Intervention for Request pages, the ability to enter or override the current worker, change the dbid or fail a granule, or change the request level disposition or parameters or modify or enter operator notes; d. On the OM Distribution Request List page, the ability to resubmit a request; and e. On the OM Distribution Request Details page, the ability to resubmit the request.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07050	When used by read-only operators, the OM GUI shall disable all screen elements that are related only to functionality that is not available to read-only operators.  For example, the OM Configuration page shall disable in that case the ability to type into the data entry boxes intended for updating configuration parameters.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-OMS-07060	The OM GUI shall make the following pages only accessible to full capability operators: a. All intervention confirmation pages.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12010	The NSBRV GUI shall distinguish between read-only and full capability operators in a secure fashion (e.g., using encrypted operator login protected and encrypted passwords).	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12020	The NSBRV shall allow DAAC operations to maintain independently for each mode, the information that identifies which capability an individual DAAC operators has when using the NSBRV GUI, and allow DAAC operations to restrict who can maintain that information.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12030	The NSBRV GUI shall retain the capability level of an individual operator -once it has been established - for the duration of the GUI session.	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12035	The NSBRV shall time out an operator session if the last activity in that session is a time out value that can be configured by DAAC operations. [NOTE: The time out value would be measured in minutes.  It would be the same for all GUI session, i.e., not operator specific.]	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12040	The NSBRV GUI shall provide the following functionality only to full capability operators: a. On the Manage Subscriptions page, the ability to add, update or delete a subscription; b. On the pages listing subscriptions, the ability to update, cancel, or suspend/resume subscriptions; c. On the Manage Bundling Orders page, the ability to add, update or cancel a bundling order or change the bundling order defaults;	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12050	The NSBRV GUI shall disable all screen elements that provide only access to functions that are not available to read-only operators.  For example, on pages listing subscriptions, the links providing access to the update, cancel, and suspend/resume capability shall be disabled (i.e., such that they cannot be invoked).	
OP_S4_01	Add Security Features to Synergy Operator GUIs	no data				S-SSS-12060	The NSBRV GUI shall make the following pages only accessible to full capability operators: a. The pages used to enter the information for a new subscription or modify the information associated with an existing one; b. The page used to change the bundling order defaults; c. The pages used to enter bundling order information; d. The pages used to update a bundling order; and e. All pages for confirming creations, updates, cancellations, or deletions.	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32805	The Data Pool FTP Log Parsing script shall extract all information required in Ticket DP_SY_08, Requirement S-DPL-32220 from the proxy firewall ftp log.	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32810	The Data Pool FTP Log Parsing script shall extract the following additional information from the proxy firewall ftp log for each ftp access of a Data Pool file, and store it in the Data Pool database: a. Transfer time of the access (in seconds) b. The value of the special-action-flag(s) c. IP address of remote host	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32815	For each ftp access of a Data Pool file, the Data Pool Access Statistics Utility shall derive the domain name of the remote host from the ip address of the remote host, and shall store the domain name in the Data Pool database.	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32820	The Data Pool FTP Log Parsing script shall filter out incomplete ftp transfers of Data Pool files  from its access statistics.	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32830	The Data Pool Web Access Service shall include in its access log the ip address of the external user. (Refer to requirement S-DPL-05369 in Ticket DP_SY_02, which states: &quot; The Data Pool Web Access Service shall include in the access log the path name of the requested file, the date and time of day, and the ip address of the requester.&quot;  Note that the Data Pool Web Access Service currently places the firewall ip address in its log as the &quot;ip address of the requester&quot;.  This Synergy IV Ticket requires specifically that the external user's ip address be logged as the &quot;ip address of the requester&quot;)	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32835	The Data Pool Access Statistics Utility shall extract the ip address of the external user from the Data Pool Web Access Service log for each http access of a Data Pool metadata or browse file, and store this information with the http access statistics in the Data Pool database. (Note that this is a specific instance of existing requirement S-DPL-32010 in Ticket DP_SY_08, which states: &quot;The Data Pool Access Statistics Utility (DPASU) shall process the Data Pool Web Access Service log, extract or parse information on data accesses events from the logs and from other Data Pool databases, and write that summary information to the DPAL for use in reporting.&quot;)  	
OP_S4_02	Enhance Data Pool Log Processing	no data				S-DPL-32840	The Data Pool FTP Log Parsing script shall support the  operational and user interface requirements defined in ticket DP_SY_08 (Compile and Examine Data Pool Access Statistics) when parsing the proxy firewall ftp log:  S-DPL-32040, S-DPL-32050, S-DPL-32060, S-DPL-32070, S-DPL-32080, S-DPL-32090, S-DPL-32100, S-DPL-32110, S-DPL-32150, S-DPL-32160, S-DPL-32162, S-DPL-32164, S-DPL-32170, S-DPL-32180, S-DPL-32190, S-DPL-32200, S-DPL-32210.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45010	The DPM GUI shall allow full capability operators to define the file systems available for use by the Data Pool, including the root path information for the file system.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45020	The DPL CI shall install an entry for the existing Data Pool file system during transition.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45030	The DPM GUI shall allow full capability operators to select the file system to be used for a Data Pool collection from the list of available Data Pool file systems when they define a new collection.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45032	The DPM GUI shall use the single Data Pool file system as the default file system for a collection until more than one Data Pool file system has been defined.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45034	The DPL shall allocate existing collections to the existing Data Pool file system during transition.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45040	The DPM GUI shall allow full capability operators to update the file system to be used for a Data Pool collection as part of the screen used to update collection information if and only if the collection is empty and not enabled for insert.  [Note: a separate utility is provided to allow operators to move an existing collection that is not empty].	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45050	The DPM GUI shall display the file system to which a Data Pool collection is allocated on the screens operators use to view/update collection information.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45060	The DPM GUI shall allow operators to monitor the 'no free space' flag of each Data Pool file system.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45070	The DPM GUI shall allow full capability operators to change the 'no free space' flag for a specific Data Pool file system.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45080	The DPM GUI shall allow operators to list the Data Pool collections that are allocated to a specific Data Pool file system.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45085	The DPM GUI shall allow operators to filter the list of queued Data Pool insert actions by file system.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45090	The DPM GUI shall allow full capability operators to configure the amount of space that must be freed to clear the free space flag separately for each file system. [Note: This extends S-DPL-13212 in DP_SY_03, which contains the equivalent requirement for a single file system].	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45100	The DPM GUI shall allow full capability operators to mark an available file system as unavailable. [Note: Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45105	The DPM GUI shall allow full capability operators to mark an unavailable file system as available. [Note: Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45110	The Data Pool CI shall provide a utility that allows operators to move a Data Pool collection from one file system to another in a recoverable fashion[Development and integration test cannot occur until Synergy 5.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45111	The Data Pool utility that moves a Data Pool collection from one file system to another shall allow an operator to not complete a previously interrupted move operation if at the time of interruption the original collection directory contents were still intact. [NOTE:  This means, for example, that once files were deleted from the original directory, the move needs to be completed.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45112	The Data Pool utility that moves a Data Pool collection from one file system to another shall verify that the target file system has sufficient free space to hold the collection to be moved before performing the move operation.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45113	The Data Pool utility that moves a Data Pool collection from one file system to another shall prompt the operator for confirmation prior to a move when used in OPS mode.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45115	The Data Pool utility that moves a Data Pool collection from one file system to another shall create a link pointing from the old collection location to the new collection directory. [NOTE: This is a single link for a collection.  DAACs can remove the link when they believe that it is no longer needed.  Otherwise, the link will only be removed (by the Data Pool Cleanup Utility) if the collection becomes empty.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45120	Moving a Data Pool collection between file systems shall not involve mass updates to the Data Pool inventory. [To be verified by inspection during code and unit test review.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45210	The Data Pool Web Drill Down GUI shall prevent drill down on a collection if web access to the granules in the collection during the move would result in an error. [Note: Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45220	The Data Pool Web Drill Down GUI shall be able to support the fact that different Data Pool collections may reside on different file systems transparently to users. [Note: Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45310	The Data Pool Insert Service shall insert files into the configured file system in accordance with the root path configured for the file system on which the collection resides, but otherwise apply the existing Data Pool directory and file naming rules.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45320	The Data Pool Insert Service shall set the 'no free space flag' for a file system if insertion of a file into that Data Pool file system fails because of insufficient free space. [Note this extends S-DPL-23300 in DP_SY_04 to multiple file systems].	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45330	The Data Pool Insert Service shall not start further Data Pool Insert actions targeted for a file system whose 'no free space' flag is set or that is marked 'unavailable'. [Note: this extends S-DPL-23350 in DP_SY_04  to multiple file systems.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45340	The Data Pool Insert Service shall automatically resume processing insert actions targeted for file system whose 'no free space' flag is updated to indicate that free space is available (unless it is marked as unavailable). [Note: this extends S-DPL-23355 in DP_SY_04  to multiple file systems.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45350	The Data Pool Insert Service shall automatically resume processing insert actions targeted for file system whose 'unavailable' flag is updated to indicate that it is available again (unless its 'no free space flag' is set). [Note: this extends S-DPL-23355 in DP_SY_04  to multiple file systems.  Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45410	The Data Pool Cleanup Utility shall clear the 'no free space' flag for a file system if the amount of space that was cleaned up exceeds the operator configured limit for that file system. [Note: This extends requirement S-DPL-13210 in DP_SY_03 to multiple file systems.].	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45420	The Data Pool Cleanup Utility shall be able to support the fact that different Data Pool collections may reside on different file systems transparently to operators. [Note: Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45430	The Data Pool Cleanup Utility shall skip the cleanup of granules for collections that reside on a file system marked unavailable.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45440	The Data Pool Cleanup Utility shall log the collections skipped during cleanup because they reside on a file system marked unavailable.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45445	The Data Pool Cleanup Utility shall remove any links established by the Data Pool Collection Move Utility when removing collection directories.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45450	The Data Pool Validation Utility shall be able to support the fact that different Data Pool collections may reside on different file systems transparently to operators. [Note: Integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45460	The Data Pool Validation Utility shall skip the validation of collections that reside on a file system marked unavailable.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45470	The Data Pool Validation Utility shall log the collections skipped during validation because they reside on a file system marked unavailable.	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45610	The Data Pool FTP log analyzer shall be able to support the fact that different Data Pool collections may reside on different file systems transparently to operators. [Note: Testing cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45710	The Data Pool web log analyzer shall be able to support the fact that different Data Pool collections may reside on different file systems transparently to operators. [Note: Testing cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45810	The Data Pool FTP Service must provide anonymous FTP access to all public Data Pool directories, which may reside on several different File systems, but must not permit access to any other directories. [Development and integration test cannot occur until Synergy V.]	
OP_S4_06	Support Multiple Data Pool File Systems	no data				S-DPL-45820	[DESIRABLE] The Data Pool FTP Service shall offer to anonymous FTP users a directory structure that is backwards compatible with that of Synergy III. Note:  This requirement has dependencies on the capability to extend the data pool collection group identifier to 12 characters:  if it is decided that the DAACs would maintain links between the chosen long names and the actual collection group directories, then the DAACs would also need to take responsibility for maintaining the shadow directory links. [To be resolved by Synergy V DDR. Development and integration cannot occur until Synergy V.]	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKD-01700	The SDP Toolkit shall provide a thread-safe version which has functions that are callable from any thread in a multi-threaded application. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKD-01705	The SDP Toolkit shall provide a thread-safe version which operates as specified in the SDP Toolkit Users Guide. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKD-01710	The SDP Toolkit shall provide a thread-safe version and a non-thread-safe version of the SDP Toolkit.  	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKD-01715	The SDP Toolkit shall provide a thread-safe version which complies with the POSIX standard, i.e. POSIX.1c threads (pthreads) will be supported. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKD-01720	The SDP Toolkit shall provide a thread-safe version which locks and unlocks calls to non-thread-safe COTS libraries included with the Toolkit software. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKD-01730	The SDP Toolkit shall provide a thread-safe version which is supported on the SGI platform. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01700	The SDP Toolkit shall provide a thread-safe version which has functions that are callable from any thread in a multi-threaded application. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01705	The SDP Toolkit shall provide a thread-safe version which operates as specified in the SDP Toolkit Users Guide. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01710	The SDP Toolkit shall provide the capability for a user to install a thread-safe version or the non-thread-safe version.  	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01715	The SDP Toolkit shall provide a thread-safe version which complies with the POSIX standard, i.e. POSIX.1c threads (pthreads) will be supported. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01720	The SDP Toolkit shall provide a thread-safe version which locks and unlocks calls to non-thread-safe COTS libraries included with the Toolkit software. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01725	The SDP Toolkit shall provide a thread-safe version which is supported on the SUN platform. 	
RH_5B_01	Processing Toolkit Upgrades to Support Concurrency	11500TK	Threadsafe Toolkit		Aug 11 1999 12:00AM	S-TKS-01730	The SDP Toolkit shall provide a thread-safe version which is supported on the SGI platform. 	
RH_5B_02	C++ SDP Toolkit	11501TK	Toolkit Support for C++		Aug 11 1999 12:00AM	S-TKD-00116	The SDP Toolkit shall provide bindings to source code written in the C++ Programming Language.	
RH_5B_02	C++ SDP Toolkit	11501TK	Toolkit Support for C++		Aug 11 1999 12:00AM	S-TKS-00116	The SDP Toolkit shall provide bindings to source code written in the C++ Programming Language.	
RH_5B_03	Closest Granule Production Rules	00967DP	AM-1 Production Rules (Closest Granule, Spatial Pad)	DPS (SSIT) support for specifying the Closest Granule Production Rule	Aug 11 1999 12:00AM	S-DPS-46000	The AITTL CI shall validate the following new parameters that define and describe the closest granule production rule:  a. Direction of search (forward/backward)  b. The Query interval/offset period  c. The maximum number of queries	
RH_5B_03	Closest Granule Production Rules	00967DP	AM-1 Production Rules (Closest Granule, Spatial Pad)	DPS (SSIT) support for specifying the Closest Granule Production Rule	Aug 11 1999 12:00AM	S-DPS-46010	The AITTL CI shall be able to register PGEs that exercise the closest granule production rule.	
RH_5B_03	Closest Granule Production Rules	00967PL	AM-1 Production Rules (Closest Granule, Spatial Pad)	Upon processing a PGE that uses the closest granule production rule the software will identify the search direction (backwards or forwards). It will then search in that direction until it finds an input granule that matches the request. It does this by successively expanding the query interval. Note that the number of times it expands the search and the length of the time interval are both user configurable parameters.	Dec  2 1999 12:00AM	S-PLS-00412	The PLANG CI shall have the capability to determine input granules, which have data collection times closest to the time of the related DPR.	
RH_5B_03	Closest Granule Production Rules	00967PL	AM-1 Production Rules (Closest Granule, Spatial Pad)	Upon processing a PGE that uses the closest granule production rule the software will identify the search direction (backwards or forwards). It will then search in that direction until it finds an input granule that matches the request. It does this by successively expanding the query interval. Note that the number of times it expands the search and the length of the time interval are both user configurable parameters.	Dec  2 1999 12:00AM	S-PLS-00414	The PLANG CI shall have the capability to specify the direction of search (forward or backwards) when searching for the closest granule to the time of the related DPR.	
RH_5B_04	Spatial Pad Production Rules	00964DP	AM-1 Production Rules (Closest Granule, Spatial Pad)	DPS (SSIT) support for specifying the Spatial Pad Production Rule	Aug 11 1999 12:00AM	S-DPS-46020	The AITTL CI shall validate the following new parameter that defines and describes the spatial pad production:  the distance in kilometers by which the spatial query should be extended.	
RH_5B_04	Spatial Pad Production Rules	00964DP	AM-1 Production Rules (Closest Granule, Spatial Pad)	DPS (SSIT) support for specifying the Spatial Pad Production Rule	Aug 11 1999 12:00AM	S-DPS-46030	The AITTL CI shall be able to register PGEs that exercise the spatial pad production rule.	
RH_5B_04	Spatial Pad Production Rules	00964PL	AM-1 Production Rules (Closest Granule, Spatial Pad)	This capability involves retrieving the polygon from a SDSRV granule and expanding it's area by a given amount.   This will allow the PRE to find more granules than it normally would.	Aug 11 1999 12:00AM	S-PLS-00410	The PLANG CI shall have the capability to extend the spatial extent of an ASTER granule by a specified amount in distance units when determining the input granules within it.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-21010	The PRONG CI shall be able to compute the orbit number (counting from the start of the day) and provide that as a runtime parameter to the PGE.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-21012	The PRONG CI shall be able to compute the granule number (counting from the start of the orbit) and provide that as a runtime parameter to the PGE.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-21014	The PRONG CI shall be able to compute the year of the data collection time and provide that as a runtime parameter to the PGE.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-21016	The PRONG CI shall be able to compute the month of the year of the data collection time and provide that as a runtime parameter to the PGE.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-21018	The PRONG CI shall be able to compute the day of the month of the data collection time and provide that as a runtime parameter to the PGE.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46040	The AITTL CI shall be able to register PGEs that exercise the "PM-1 Orbit number within the day" prodcution rule.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46050	The AITTL CI shall be able to register PGEs that exercise the "PM-1 Granule number within the orbit" production rule.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46060	The AITTL CI shall be be able to register PGEs which require the year of the data collection time as a run time parameter.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46070	The AITTL CI shall be able to register PGEs which require the month of the year of the data collection time as a run time parameter.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46080	The AITTL CI shall be able to register PGEs which require the day of the month of the data collection time as  a runtime parameter.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46090	The AITTL CI shall validate the new parameter(s) that define and describe the "PM-1 Orbit number within the day" production rule.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46100	The AITTL CI shall validate the new parameter(s) that define and describe the "PM-1 Granule number within the orbit" production rule.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46110	The AITTL CI shall validate the new parameter(s) that define and describe the "Year of the Data collection time" production rule.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46120	The AITTL CI shall validate the new parameter(s) that define and describe the "Month of the Year of the Data collection time" production rule.	
RH_5B_05	Orbit Processing Runtime Parameters Production Rules	10500DP	PM-1 Production Rules And Preprocessing	DPS (SSIT) support for currently uknown production rules specific to PM-1.  Assumes 1 advanced rule (200 SLOC) and 3 basic rules (70 SLOC each).	Aug 11 1999 12:00AM	S-DPS-46130	The AITTL CI shall validate the new parameter(s) that define and describe the "Day of the month of the Data collection time" production rule.	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30005	The PRONG CI shall process FDS Definitive Orbit data for the EOS PM-1 spacecraft (received in the FDF 2800-byte block, binary EPHEM format) to reformat the received data into the format used by the SDP Toolkit.	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30010	The PRONG CI shall process one day of FDS Definitive Orbit Data per mission day and store to the archive the output as a single day definitive orbit file.	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30015	The Prong CI shall produce output definitive orbit data in both HDF EOS and native formats as required by SDP Toolkit.	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30035	The PRONG CI shall produce output granules of definitive orbit data for PM1 such that the time range begins at the first point at or after 0Z and ends at the last point which occurs before 0Z of the next day	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30036	The PRONG CI shall handle leap seconds in the definitive PM1 orbit ephemeris data.	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30037	The PRONG CI shall produce definitive PM1 orbit ephemeris with intervals between data points equivalent to the input data.	
RH_5B_06	DPREP Processing for PM-1	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30041	The PRONG CI shall set data quality flags if gaps are found in the data received	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKD-00201	The SDP Toolkit shall contain tools to read Consultative Committee on Space Data Systems (CCSDS)-format packetized data for EOS PM-1 GIRD format packets from Level 0 data files. Data is assumed to be made available to the Toolkit in the native format of the computing platform the Toolkit is instantiated on.	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKD-00221	The SDP Toolkit shall include the capability to provide the first CCSDS packet after a given time for EOS PM-1 GIRD format packets.	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKD-00226	The SDP Toolkit shall return the number of Level 0 packets read to reach the Level 0 packet with the correct start time for EOS PM-1 GIRD format packets	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKD-01171	The SDP Toolkit shall provide tools to transform time among the six following systems:     a. Coordinated Universal Time (UTC) (Date and ASCII formats)  b. UT1 (binary and Julian Date formats)  c. International Atomic Time (TAI) (binary and Julian Date formats)  d. Julian Date (floating point format, in units of days)  e. spacecraft clock represented in the GIRD format  f. Global Positioning System (GPS)  	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKS-00201	The SDP Toolkit shall contain tools to read Consultative Committee on Space Data Systems (CCSDS)-format packetized data for EOS PM-1 GIRD format packets from Level 0 data files. Data is assumed to be made available to the Toolkit in the native format of the computing platform the Toolkit is instantiated on.	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKS-00221	The SDP Toolkit shall include the capability to provide the first CCSDS packet after a given time for EOS PM-1 GIRD format packets.	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKS-00226	The SDP Toolkit shall return the number of Level 0 packets read to reach the Level 0 packet with the correct start time for EOS PM-1 GIRD format packets.	
RH_5B_07	SDP Toolkit Support for EOS PM-1 (Aqua)	11506TK	Toolkit Support for PM-1	Implementation of Toolkit support for access to PM-1 format data packets.	Mar  6 2000 12:00AM	S-TKS-01171	The SDP Toolkit shall provide tools to transform time among the six following systems:     a. Coordinated Universal Time (UTC) (Date and ASCII formats)  b. UT1 (binary and Julian Date formats)  c. International Atomic Time (TAI) (binary and Julian Date formats)  d. Julian Date (floating point format, in units of days)  e. spacecraft clock represented in the GIRD format  f. Global Positioning System (GPS)  	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30400	The PRONG CI shall process FDS definitive orbit data for the Aura spacecraft (received in the FDS 2800-byte block, binary EPHEM format) to reformat the received data into the format used by the SDP Toolkit.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30405	The PRONG CI shall process each day FDS definitive orbit data for the AURA mission covering the period from 12:00 UTC of the previous day to 12:00 UTC of the current day, and store the output to the archive as a single file granule of definitive orbit covering the same time period.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30410	The PRONG CI shall produce output definitive orbit data in both HDF and native formats as required by SDP Toolkit.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30415	The PRONG CI shall produce output granules of definitive orbit data for Aura such that the time range begins at the first point at or after 12:00 UTC and ends at the last point which occurs before 12:00 UTC of the next day.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30420	The PRONG CI shall handle leap seconds in the definitive Aura ephemeris data.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30425	The PRONG CI shall produce definitive Aura ephemeris with intervals between data points equivalent to the data point spacing of the input data.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30430	The PRONG CI shall set data quality flags in the output ephemeris data if gaps are found in the FDS ephemeris data.	
RH_6B_01	DPREP Ephemeris Processing for Aura	11001DP	DPREP changes to step up to AURA	AURA Production Rules and Preprocessing	Jun 25 2001 12:00AM	S-DPS-30435	The PRONG CI shall define as a configurable parameter the Orbit Point Spacing parameter, which is the nominal time spacing between sequential orbit data points in the received FDS ephemeris data and the DPREP generated ephemeris data produced from it.	
RH_6B_02	Ingest of DAS Data Types	10022IN	Ingest Tailoring For DAS Data Types	Support for ingest of DAO data	Oct 30 2000 12:00AM	S-INS-00558	The Ingest CI shall ingest and insert into the SDSRV at the GSFC DAAC the DAO data in the HDF-EOS format as follows: DREAPCHM, DREAPCLD, DREAPMIS, DREAPMOM, DREAPMST, DREAPTMP, DREAPTRP, DREAXCHM, DREAXCLD, DREAXENG, DREAXLSM, DREAXMIS, DREAXSTR.	
RH_6B_03	Ingest of 6B Aura and SORCE Instrument Data Types	00030IN	Ingest Tailoring For Aura and SORCE Instrument Data Types	Support for ingest of Aura SORCE Instrument data	Jun 25 2001 12:00AM	S-INS-00600	The Ingest CI shall ingest and insert into the SDSRV at the GSFC DAAC the MLS SIPS data as follows:    ML1ENG  ML1LOG  ML1OA    ML1RADD  ML1RADF  ML2BRO    ML2CLO  ML2CO  ML2DGG    ML2DGM  ML2Z  ML2H2O    ML2HCL  ML2HCN  ML2HNO3    ML2HO2  ML2HOCL  ML2ICE    ML2LOG  ML2N2O  ML2O3    ML2OH  ML2OTH  ML2RHI    ML2SO2  ML2T  ML3DCLO    ML3DCO  ML3DZ  ML3DH2O    ML3DHCL  ML3DHCN  ML3DHNO3    ML3DICE  ML3DN2O  ML3DO3    ML3DOH  ML3DRHI  ML3DT    ML3DZMD  ML3DZMS  ML3LOG    ML3MMAPD  ML3MZMD  ML3MZMS      ML3MMAPS   	
RH_6B_03	Ingest of 6B Aura and SORCE Instrument Data Types	00030IN	Ingest Tailoring For Aura and SORCE Instrument Data Types	Support for ingest of Aura SORCE Instrument data	Jun 25 2001 12:00AM	S-INS-00601	The Ingest CI shall ingest and insert into the SDSRV at the LaRC DAAC the TES SIPS data as follows:    TL1BL  TL1BN  TL2ATMTL    TL2ATMTN  TL2CH4L  TL2CH4N    TL2COL  TL2CON  TL2H2OL    TL2H2ON  TL2HNO3L  TL2NO2L    TL2NOL  TL2O3L  TL2O3N    TL3ATMTL  TL3ATMTN  TL3CH4L    TL3CH4N  TL3COL  TL3CON    TL3H2OL  TL3H2ON  TL3HNO3L    TL3NO2L  TL3NOL  TL3O3L    TL3O3N       	
RH_6B_03	Ingest of 6B Aura and SORCE Instrument Data Types	00030IN	Ingest Tailoring For Aura and SORCE Instrument Data Types	Support for ingest of Aura SORCE Instrument data	Jun 25 2001 12:00AM	S-INS-00602	The Ingest CI shall ingest and insert into the SDSRV at the GSFC DAAC the HIRDLS SIPS data as follows:    HIR1DRV  HIR2APR  HIR2BRWS    HIR2CFG  HIR2CLDS  HIR2CLIM    HIR2CTRL  HIR2INST  HIR2LOG    HIR2QA  HIR2TRA  HIR3CFG    HIRDLS1  HIRDLS2  HIRDLS3   	
RH_6B_03	Ingest of 6B Aura and SORCE Instrument Data Types	00030IN	Ingest Tailoring For Aura and SORCE Instrument Data Types	Support for ingest of Aura SORCE Instrument data	Jun 25 2001 12:00AM	S-INS-00603	The Ingest CI shall ingest and insert into the SDSRV at the GSFC DAAC the SORCE spacecraft SIPS data as follows:    SORL0TLM  SOR3TSID  SOR3TSI6  SOR3SSID  SOR3SSI6  SOR41NMD  SOR41NM6  	
RH_BP_01	L7 Pricing Algorithm Update Cancelled per Contract Mod 25	02024DM	Enhanced Landsat-7 Pricing Algorithm		May 17 2000 12:00AM	S-DMS-30379	The GTWAY CI shall calculate the Price Estimate for Landsat 7 0R full subintervals in the same manner as for floating scenes but making use of different operator configurable costing parameters than are used in the floating scene calculation.	
RH_BP_01	L7 Pricing Algorithm Update Cancelled per Contract Mod 25	02024DM	Enhanced Landsat-7 Pricing Algorithm		May 17 2000 12:00AM	S-DMS-30380	The GTWAY CI shall be capable of receiving and responding to a price estimate request from the V0 client that explicitly identifies a full subinterval product, i.e., not indirectly via corner point values for the subinterval.	
RH_BP_01	L7 Pricing Algorithm Update Cancelled per Contract Mod 25	02024DM	Enhanced Landsat-7 Pricing Algorithm		May 17 2000 12:00AM	S-DMS-30382	The GTWAY CI shall reduce the Price Estimate for L0R floating scenes and full subinterval products by a percentage of the total cost (not including media costs) for each band not included in the product, where the operator configurable percentage reduction will be unique for each band.	
RH_BP_01	L7 Pricing Algorithm Update Cancelled per Contract Mod 25	02024DM	Enhanced Landsat-7 Pricing Algorithm		May 17 2000 12:00AM	S-DMS-30383	The GTWAY CI shall generate a Price Estimate for non-image data products, which are defined in the L7 to ECS ICD, that is an operator configurable price fixed for all non-image data products.	
RH_BP_01	L7 Pricing Algorithm Update Cancelled per Contract Mod 25	02024DM	Enhanced Landsat-7 Pricing Algorithm		May 17 2000 12:00AM	S-DMS-30385	The GTWAY CI shall include in the total order Price Estimate for the following applicable product types:    a. Floating Scenes    b. Full Sub-interval    c. Non-image products    a cost for the physical media distribution option selected with the order, which is an operator configurable value for each supported media type and does not depend on the number of physical media units (e.g., tapes) required to distribute the order.	
RH_BP_01	L7 Pricing Algorithm Update Cancelled per Contract Mod 25	02024DM	Enhanced Landsat-7 Pricing Algorithm		May 17 2000 12:00AM	S-DMS-30386	The GTWAY CI shall be able to produce Price Estimates for physical media distribution costs for any of the media distribution options supported at the DAAC.	
RH_BP_02	NCEP AVN Product Ingest	10026IN	NCEP AVN Ingest	Ingest of NCEP 1-Degree Aviation Model (AVN)	Jul 25 2000 12:00AM	S-INS-00550	The Ingest CI shall insert to the SDSRV NCEP AVN data in the GRIB format.	
RH_BP_02	NCEP AVN Product Ingest	10026IN	NCEP AVN Ingest	Ingest of NCEP 1-Degree Aviation Model (AVN)	Jul 25 2000 12:00AM	S-INS-00551	The Ingest CI shall convert NCEP AVN data from the GRIB format in which it is received into the HDF-EOS grid format.	
RH_BP_02	NCEP AVN Product Ingest	10026IN	NCEP AVN Ingest	Ingest of NCEP 1-Degree Aviation Model (AVN)	Jul 25 2000 12:00AM	S-INS-00552	The Ingest CI shall insert to the SDSRV the NCEP AVN data after conversion to the HDF-EOS format.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30050	The PRONG CI shall provide the capability to process EMOS-generated carry-out files containing Aqua GBAD data from APID channels 959 and 957 to extract and process spacecraft attitude data into the format used by the SDP Toolkit.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30052	The PRONG CI shall time tag the refined attitude points using the body-rate-time field from GBAD 957 (as inserted into the carry-out file).	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30054	The PRONG CI shall evaluate the value of the GNCC Status Word 2, which is time tagged with the packet time, for the purpose of determining the quality of the received attitude data.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30056	The PRONG CI shall provide parameterized access to the contents of the carry-out file so that the implementation of the carry-out file processing is not dependent on specific field names in the carry-out file.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30058	The PRONG CI shall produce output Aqua spacecraft attitude data in both HDF and native formats.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30062	The PRONG CI shall produce Aqua spacecraft refined attitude data using definitive Aqua ephemeris data and carry-out file data.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30064	The PRONG CI shall be capable when processing carry-out files containing Aqua GBAD data, of distinguishing between the following states or values for the GNCC status word:  Status word value indicating good attitude: 'Fine Pointing' (110);  Status word values indicating bad attitude: all other values including 'Earth Point' (001), 'Sun Point' (101), 'Sun Hold' (010), 'Mode 0' (000), 'Attitude Hold' (100).  	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30066	The PRONG CI shall determine, for the purpose of quality flagging the Aqua refined attitude data, the presence or absences, and if present the value of the GNCC Status Word that is to appear in the GBAD APID channel at a rate of once per 8 seconds.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30068	The PRONG CI shall set quality flags in the output refined attitude data indicating 'good attitude data' when all GNCC status word values within 8 seconds before or after the target attitude point are evaluated as being set to a Fine Pointing (110) state.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30070	The PRONG CI shall set quality flags in the output refined attitude data indicating 'missing status word' when one or more GNCC status word values within 8 seconds before or after the target attitude point are unavailable.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30072	The PRONG CI shall set quality flags in the output refined attitude data indicating 'bad attitude data' when any GNCC status word value within 8 seconds before or after the target attitude point are evaluated as a value other than Fine Pointing (110) state.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30074	The PRONG CI shall be capable of processing a target interval of carry-out files containing Aqua GBAD data with or without the presence of other data sets (orbit or attitude data) for adjacent time intervals.	
RH_BP_04	DPREP Processing of Carry-Out File Data for Aqua	11002DP	PM-1 Production Rules And Preprocessing	DPREP processing the L0 attitude and ephemerous data from the PM-1 platform.	Jul 17 2000 12:00AM	S-DPS-30076	The PRONG CI shall identify gaps in the output Aqua attitude data by setting flags in the data used for this purpose.	
RH_BP_05	NCEP PREPQC Data Ingest	10025IN	NCEP PREPQC Ingest	Ingest of NCEP PREPQC Ancillary Data	Aug 10 2000 12:00AM	S-INS-00555	The Ingest CI shall ingest and store to the SDSRV NCEP PREPQC data in the BUFR format into the GSFC DAAC.	
RH_BP_06	NCEP PREPQC Data Conversion	10025DP	NCEP PREPQC Conversion	Conversion of NCEP PREPQC Ancillary Data to HDF-EOS	Aug 10 2000 12:00AM	S-DPS-30100	The PRONG CI PREPQC conversion PGE shall convert NCEP PREPQC data from the BUFR format in which it is received into the HDF-EOS Point format.	
RH_BP_06	NCEP PREPQC Data Conversion	10025DP	NCEP PREPQC Conversion	Conversion of NCEP PREPQC Ancillary Data to HDF-EOS	Aug 10 2000 12:00AM	S-DPS-30110	The PRONG CI PREPQC conversion PGE shall store to the SDSRV the NCEP PREPQC data after conversion to the HDF-EOS Point format.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00186	The SDSRV shall support the definition of predefined spatial extents to aid in spatial searching.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00187	The SDSRV shall provide capabilities to populate the SDSRV DsMdOrbitPolygons table with polygon definitions for an instrument.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00188	The SDSRV shall support predefined spatial extents that are associated with a specific instrument and platform.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00189	The SDSRV shall support predefined spatial extents for GLAS data types that are characterized by a track number that corresponds to a prespecified spacecraft orbit, and a block number that corresponds to a spatial extent along the track.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00190	The SDSRV shall support predefined spatial extents for AMSR data types that are characterized by a track number that corresponds to a prespecified spacecraft orbit, and a block number that corresponds to a spatial extent along the track.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00192	The SDSRV shall support the association of inserted GLAS granules with predefined spatial extents by recording as metadata for the granule the set of track numbers and the set of block numbers of the spatial extents corresponding to the granules spatial region.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00193	The SDSRV shall support the association of inserted AMSR granules with predefined spatial extents by recording as metadata for the granule the set of track numbers and the set of block numbers of the spatial extents corresponding to the granules spatial region	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00194	The SDSRV shall validate the set of NOSE track numbers and start/end block numbers associated with a granule at the time of insertion against the predefined values defined within SDSRV for spatial extent definitions.	
RH_BP_07	GLAS and AMSR NOSE Support	no data				S-DSS-00195	The SDSRV shall for spatial searching for those instruments for which predefined spatial extents are defined, provide the capability to support the translation of user specified spatial search regions into one or more prespecified instrument standard spatial extents.	
RH_XT_01	Modify Aura Orbit DPREP Software	no data				D-DPS-30440	The PRONG CI, when processing FDS definitive orbit data for the Aura spacecraft to produce output definitive orbit data, shall extract the following orbital elements parameters from each FDS file:    &nbsp;&nbsp;1. epoch of the elements.    &nbsp;&nbsp;2. semi-major axis (m);    &nbsp;&nbsp;3. orbital eccentricity;    &nbsp;&nbsp;4. inclination (radians);    &nbsp;&nbsp;5. right ascension of ascending node (radians);    &nbsp;&nbsp;6. argument of the perigee (radians);    &nbsp;&nbsp;7. mean anomaly at epoch (radians)	
RH_XT_01	Modify Aura Orbit DPREP Software	no data				D-DPS-30445	The PRONG CI shall store each orbital element parameter as ASCII numeric PSA metadata with the output definitive orbit data product when it is stored.	
RH_XT_01	Modify Aura Orbit DPREP Software	no data				D-DPS-30450	The PRONG CI shall store orbital element parameter PSAs with both the HDF format and the native format output definitive orbit data product that is stored.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032IN	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:22PM	S-INS-00790	The INGST CI shall ingest data, received on physical media from the ASTER GDS, into the EDC DAAC.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032IN	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:22PM	S-INS-03111	Implement Requirement S-INS-03110 	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032IN	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:22PM	S-INS-03116	Implement Requirement S-INS-03115 	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-00155	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-03002	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-03292	The SDSRV CI shall provide the capability to process Data Insert Requests for the storage of the metadata and data (if any), for the data types specified in the Data Type Services Matrix.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-03305	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-03308	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-20000	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-21357	The STMGT CI shall have the capability to transfer data from DTF-2 tape	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-21374	The STMGT CI shall transfer data from ingest media as directed by the INGST CI.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-21384	The STMGT CI shall provide operations staff the capability to manually mount media on stand alone data input/output devices used for media ingest and distribution.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	00032ST	Sony DTF Ingest 	Transition from ASTER D3 Ingest to Sony DTF Ingest.   	May  9 2002 12:26PM	S-DSS-21386	The STMGT CI shall provide operations staff the capability to manually unmount media from stand alone data input/output devices used for media ingest and distribution.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	no data						
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	no data				S-DSS-21492	The STMGT CI shall provide APIs to support the retrieval of data from devices used for the ingest of data from physical media.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	no data				S-INS-00130	The INGST CI shall interactively accept Hard Media Ingest Requests from operations staff for data to be ingested from hard media.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	no data				S-INS-00140	The INGST CI shall check the Hard Media Ingest Request to verify that the Media Type is a type supported by the INGST CI.	
RH_ZZ_01	ASTER Ingest Via Sony DTF-2	no data				S-INS-00150	The INGST CI shall verify that the External Data Provider specified in a Hard Media Ingest Request is an authorized provider of hard media to be ingested.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30440	The PRONG CI shall provide the capability to process EMOS-generated carry-out files containing Aura GBAD data.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30445	The PRONG CI shall produce Aura spacecraft attitude data using Aura ephemeris data and Aura GBAD.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30450	The PRONG CI shall process Aura GBAD quaternion representation attitude data into Euler angle representation attitude data. 	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30455	The PRONG CI shall be able to calculate the magnitude of the quaternion unit vector, test whether this magnitude value is in the range of 1  1E-07, and set appropriate values in the quality flags.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30460	The PRONG CI shall identify gaps in the output Aura attitude data by setting flags in the data used for this purpose.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30465	The PRONG CI shall produce an output attitude record for each input attitude report contained in the Aura GBAD carry-out file.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30470	The PRONG CI shall time tag the Aura attitude records using the body-rate-time field extracted from the GBAD carry-out file reports.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30475	The PRONG CI shall during Aura GBAD processing evaluate the value of the GNCC Status Word 2, which is time tagged with the packet time, for the purpose of determining the quality of the received attitude data as defined in Ticket RH_ZZ_02.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30480	The PRONG CI shall, during Aura GBAD processing, save the GNCC Status Word 2 value in the quality flags field of the output attitude date records, as defined in Ticket RH_ZZ_02. 	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30485	The PRONG CI shall, during Aura GBAD processing, determine the Status Word Transition Value from the GNCC Status Word 2 value, as defined in Ticket RH_ZZ_02.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30490	The PRONG CI shall, during Aura GBAD processing, save the Status Word Transition Value in the quality flags field of the output attitude date records, as defined in Ticket RH_ZZ_02.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30495	The PRONG CI shall during Aura GBAD processing be capable of identifying missing or invalid GNCC Status Word 2 values, as defined in Ticket RH_ZZ_02.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30500	The PRONG CI shall, during Aura GBAD processing, set flags in the quality flags field of the output attitude date records indicating missing or invalid GNCC Status Word 2 values, as defined in Ticket RH_ZZ_02	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30505	The PRONG CI shall be capable of processing a carry-out file containing Aura GBAD data with or without the presence of other orbit or attitude data files for adjacent time intervals.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30510	The PRONG CI shall produce output Aura spacecraft attitude data in the native system file format used by the SDP Toolkit.	
RH_ZZ_02	DPREP Attitude Processing for Aura	no data				S-DPS-30515	The PRONG CI shall produce output Aura spacecraft attitude data in HDF formats.	
RM_5B_01	LLBox and Oriented Polygon	00964DT	AM-1 Production Rules (Closest Granule, Spatial Pad)		Aug 11 1999 12:00AM	S-DSS-00177	The SDSRV CI shall assume orient polygon points are in a clockwise direction when inserting and distributing polygon metadata data.	
RM_5B_01	LLBox and Oriented Polygon	12501DT	SQS LLBox Support	The SDSRV shall provide the capability to utilize the SQS LLBOX Datatype in place of the exising Rectangle Datatype.	Aug 11 1999 12:00AM	S-DSS-00181	The SDSRV CI shall provide spatial search constraints based upon LLBOX spatial extents.	
RM_5B_01	LLBox and Oriented Polygon	12501DT	SQS LLBox Support	The SDSRV shall provide the capability to utilize the SQS LLBOX Datatype in place of the exising Rectangle Datatype.	Aug 11 1999 12:00AM	S-DSS-00182	The SDSRV CI shall support spatial extents [LLBOX] defined as lines of constant latitude and longitude, up to and including whole Earth. (I.e., +90 degrees to -90 degrees latitude, +180 degrees to -180 degrees longitude).	
RM_5B_01	LLBox and Oriented Polygon	12501DT	SQS LLBox Support	The SDSRV shall provide the capability to utilize the SQS LLBOX Datatype in place of the exising Rectangle Datatype.	Aug 11 1999 12:00AM	S-DSS-00183	The SDSRV CI shall provide storage of LLBOX spatial extents.	
RM_5B_01	LLBox and Oriented Polygon	12501DT	SQS LLBox Support	The SDSRV shall provide the capability to utilize the SQS LLBOX Datatype in place of the exising Rectangle Datatype.	Aug 11 1999 12:00AM	S-DSS-00184	The SDSRV CI shall support LLBOX search constraints that cross the +180 degrees to -180 degrees longitude discontinuity.	
RM_5B_01	LLBox and Oriented Polygon	12501DT	SQS LLBox Support	The SDSRV shall provide the capability to utilize the SQS LLBOX Datatype in place of the exising Rectangle Datatype.	Aug 11 1999 12:00AM	S-DSS-00185	The SDSRV CI shall support LLBOX interpretation of existing Metadata stored with the BoundingRectangle datatype.	
RM_5B_01	LLBox and Oriented Polygon	12504DT	SQS Oriented Polygons (Allow Polygon Searches Greater Than Half The Globe)	The SDSRV shall provide the capability to utilize the SQS with Oriented Gpolygon. Convert SDSRV storage and interpretation of ECS Gpolygon to utilize SQS SDT Oriented Gpolygon.	Aug 11 1999 12:00AM	S-DSS-00171	The SDSRV CI shall provide spatial searching with polygonal search areas.	
RM_5B_01	LLBox and Oriented Polygon	12504DT	SQS Oriented Polygons (Allow Polygon Searches Greater Than Half The Globe)	The SDSRV shall provide the capability to utilize the SQS with Oriented Gpolygon. Convert SDSRV storage and interpretation of ECS Gpolygon to utilize SQS SDT Oriented Gpolygon.	Aug 11 1999 12:00AM	S-DSS-00172	The SDSRV CI shall  provide storage of polygonal (store Gpolygon) spatial extents.	
RM_5B_01	LLBox and Oriented Polygon	12504DT	SQS Oriented Polygons (Allow Polygon Searches Greater Than Half The Globe)	The SDSRV shall provide the capability to utilize the SQS with Oriented Gpolygon. Convert SDSRV storage and interpretation of ECS Gpolygon to utilize SQS SDT Oriented Gpolygon.	Aug 11 1999 12:00AM	S-DSS-00173	The SDSRV CI shall accept polygons and process them using the assumption that points are ordered in a clockwise direction when viewed from above the earth.	
RM_5B_01	LLBox and Oriented Polygon	12504DT	SQS Oriented Polygons (Allow Polygon Searches Greater Than Half The Globe)	The SDSRV shall provide the capability to utilize the SQS with Oriented Gpolygon. Convert SDSRV storage and interpretation of ECS Gpolygon to utilize SQS SDT Oriented Gpolygon.	Aug 11 1999 12:00AM	S-DSS-00174	The SDSRV CI shall process polygons according to the "Right Hand Inside" rule.  This rule states that the inside of the polygon is to the right of each directed arc when viewed from above the earth's surface.	
RM_5B_01	LLBox and Oriented Polygon	12504DT	SQS Oriented Polygons (Allow Polygon Searches Greater Than Half The Globe)	The SDSRV shall provide the capability to utilize the SQS with Oriented Gpolygon. Convert SDSRV storage and interpretation of ECS Gpolygon to utilize SQS SDT Oriented Gpolygon.	Aug 11 1999 12:00AM	S-DSS-00175	The SDSRV CI shall be capable of storing an entire orbit of data as the spatial extent of a granule represented with the Gpolygon data type.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40000	The SBSRV shall detect duplicate event triggers	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40005	The SBSRV shall prevent duplication of event notifications and actions associated with an event trigger.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40020	The SBSRV shall persistently store subscriptions and actions associated with an event trigger to be used when SBSRV is started warm.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40030	The SBSRV shall delete subscriptions and actions from the warm-restart tables as they are processed. 	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40035	The SBSRV shall access the persistent subscription and action tables during a warm restart.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40050	The SBSRV shall allow an operator to list the actions and trigger information in the warm restart action table.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40055	The SBSRV shall allow an operator to delete an action in the warm restart action table.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40070	The SBSRV shall allow an operator to update an action in the warm restart action table.	
RM_5B_02	Persistent Queuing of Subscription Actions	04435ID	Subscription Enhancements - Persistent Queuing	The Subscription Server will provide the capability to persistantly store data needed during an event trigger so that no request will be lost in the event of a fault.	Aug 11 1999 12:00AM	C-CSS-40080	The SBSRV shall retain trigger request information for a configurable amount of time in the trigger information table.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40305	The ECS-GDS Component of the ASTGW CI shall receive Inventory Search Requests from the V0 Client using protocols defined in the V0/ECS ICD	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40306	The ECS-GDS Component of the ASTGW CI shall send Inventory Search Results to the V0 Client using protocols defined in the V0/ECS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40310	The ECS-GDS Component of the ASTGW CI shall send Inventory Search Requests to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40315	The ECS-GDS Component of the ASTGW CI shall receive Inventory Search Results from the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40343	The ECS-GDS Component of the ASTGW CI shall send Integrated Browse Requests to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40346	The ECS-GDS Component of the ASTGW CI shall receive Integrated Browse Results from the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40351	The ECS-GDS Component of the ASTGW CI shall send User Profile Requests to the Management CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40352	The ECS-GDS Component of the ASTGW CI shall receive User Profiles from the Management CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40360	The ECS-GDS Component of the ASTGW CI shall receive Directory Search Requests from the V0 Client using protocols defined in the V0/ECS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40365	The ECS-GDS Component of the ASTGW CI shall send Directory Search Results to the V0 Client using protocols defined in the V0/ECS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40370	The ECS-GDS Component of the ASTGW CI shall receive Product Requests from the ODPRM CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40550	The ECS-GDS Component of the ASTGW CI shall translate ECS system protocols into ASTER GDS system protocols as defined in the ASTER ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40900	The ASTGW CI shall support multiple Service Requests.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20010	The ODFRM CI shall accept as input from the user ASTER on-demand processing parameter values.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20040	The ODFRM CI shall display valid values for ASTER on-demand processing parameters that have a limited set of values.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20050	The ODFRM CI shall display default values for ASTER on-demand processing parameters and apply them if the user does not override these values.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20060	The ODFRM CI shall send the on-demand product request to the ODPRM CI using ODPRMs DCE client I/F	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20070	The ODFRM CI shall allow the user to specify media distribution options for any ASTER on-demand product orders except ASTER L1B.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20080	The ODFRM CI shall verify all user inputs relating to ASTER on-demand processing and return the status of that input to the user.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20090	The ODFRM CI shall reject any ASTER L1B on-demand product order from an unauthorized user.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20170	The ODFRM CI shall send an email notification to the user upon submission of the ASTER on-demand product order.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20180	The ODFRM CI shall allow the user to specify contact information for any on-demand product order, and shipping information for any on-demand product order except L1B.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-DMS-40308	The ECS-GDS Component of the ASTGW CI shall translate the ECS valids for the L1B on-demand processing options into the corresponding GDS valid in an operator configurable fashion.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501IN	Automated On-Demand Production With Non-Default Parameters		Sep 22 1999 12:00AM	S-INS-03110	Upon ingest of ASTER L1B, the INGST CI shall populate meta-data attributes reflecting the ASTERMapProjection and Resampling used in producing the L1B product.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501IN	Automated On-Demand Production With Non-Default Parameters		Sep 22 1999 12:00AM	S-INS-03115	Upon ingest of ASTER L1B, the INGST CI shall populate the InputGranulePointer with the GDS ID of the L1A data granule extracted from the SourceDataProduct object.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75045	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75046	The MSS accountability management service shall mark an order complete when all its subordinate requests have reached one of the following states:  a. Shipped  b. Aborted  c. Canceled  d. Terminated  e. Expired  f. L1B received	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75047	The MSS accountability management service shall support the following order/request states:  a. Pending  b. Operator Intervention  c. Staging  d. Transferring   e. Waiting for Shipment    f. Shipped  g. Aborted  h. Canceled  i. Terminated  j. Subsetting  k. Subsetting Staging  l. Prep for Distribution  m. SDSRV Staging  n. Queued  o. Waiting for data  p. Waiting for processing  q. Being processed  r. Completed processing  s. Expired  t. Awaiting L1B  u. L1B received  v. Null	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75055	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75056	The MSS accountability management service shall provide the capability to identify on demand processing orders and requests.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75061	The MSS accountability management service shall be able to track the status of an ASTER L1B order and its requests.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75062	The MSS accountability management service shall provide an interface for an operator to mark an ASTER on demand request as "canceled" or "aborted".	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75063	The MSS accountability management service shall provide the ability to identify whether a user has the privilege to order ASTER L1B products.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04040	The PLANG CI shall accept a non-standard L1B order request from the ODFRM CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04075	The PLANG CI shall notify the requester via e-mail when an On-Demand ASTER L1B Product is available.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04098	 The PLANG CI shall initialize the status of an L1B request as "Queued".	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04100	The PLANG CI shall notify MSS order tracking of a non-standard L1B change of status to "L1B received" when a L1B request has been inserted into the SDSRV CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04320	The PLANG CI shall  forward production requests for non-standard L1B products to the ECSGDS  component of the ASTGW CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04330	The PLANG CI shall be able to map the ECS valids for the L1B processing options into the corresponding valids used in the L1B metadata in an operator configurable fashion.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41013	The ASTGW CI shall log when a service request is activated from the queue.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41015	The ECS-GDS component of the ASTGW CI shall log when an external connection to the ASTER GDS server has been established.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41016	The ECS-GDS component of the ASTGW CI shall log when the component service request has been submitted to the ASTER GDS server.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41017	The ECS-GDS component of the ASTGW CI shall log when the results from the ASTER GDS server have been successfully returned.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41051	The ASTGW CI shall log the failure of a request.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12008DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [ECS-GDS Product Request]	The ECS-GDS server shall be able to handle product request from ECS clients	Aug 11 1999 12:00AM	S-DMS-40347	The ECS-GDS Component of the ASTGW CI shall receive Product Requests from the V0 Client using protocols defined in the V0/ECS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12008DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [ECS-GDS Product Request]	The ECS-GDS server shall be able to handle product request from ECS clients	Aug 11 1999 12:00AM	S-DMS-40348	The ECS-GDS Component of the ASTGW CI shall send Product Request Results to the V0 Client using protocols defined in the V0/ECS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12008DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [ECS-GDS Product Request]	The ECS-GDS server shall be able to handle product request from ECS clients	Aug 11 1999 12:00AM	S-DMS-40350	The ECS-GDS Component of the ASTGW CI shall send Product Requests to the ASTER GDS using ASTER GDS system protocols as defined in the ASTER ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12008DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [ECS-GDS Product Request]	The ECS-GDS server shall be able to handle product request from ECS clients	Aug 11 1999 12:00AM	S-DMS-40355	The ECS-GDS Component of the ASTGW CI shall receive Product Request Result from the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12008DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [ECS-GDS Product Request]	The ECS-GDS server shall be able to handle product request from ECS clients	Aug 11 1999 12:00AM	S-DMS-40375	The ECS-GDS Component of the ASTGW CI shall return Product Request Message to the ODPRM CI.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	12008DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [ECS-GDS Product Request]	The ECS-GDS server shall be able to handle product request from ECS clients	Aug 11 1999 12:00AM	S-DMS-42080	The ECS-GDS Component of the ASTGW CI shall provide authentication information to the ASTER GDS.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	no data				S-CLS-20004	The ODFRM CI shall accept one GDS  L1A granule ID as input to an on-demand product order for a non-standard L1B Product.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	no data				S-CLS-20005	The ODFRM shall require login as a registered ECS user in order for a user to be able to submit ASTER on-demand product orders.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	no data				S-DMS-40341	The ECS-GDS Component of the ASTGW CI shall receive Integrated Browse Requests from the V0 Client using protocols as defined in the V0/ECS ICD.	
RM_5B_03	On-Demand ASTER L1B and ECS-GDS Gateway Superseded by Ticket BE_S3_01	no data				S-DMS-40342	The ECS-GDS Component of the ASTGW CI shall send Integrated Browse Results to the V0 Client using protocols as defined in the V0/ECS ICD.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20010	The ODFRM CI shall accept as input from the user ASTER on-demand processing parameter values.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20040	The ODFRM CI shall display valid values for ASTER on-demand processing parameters that have a limited set of values.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20050	The ODFRM CI shall display default values for ASTER on-demand processing parameters and apply them if the user does not override these values.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20060	The ODFRM CI shall send the on-demand product request to the ODPRM CI using ODPRMs DCE client I/F	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20070	The ODFRM CI shall allow the user to specify media distribution options for any ASTER on-demand product orders except ASTER L1B.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20080	The ODFRM CI shall verify all user inputs relating to ASTER on-demand processing and return the status of that input to the user.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20160	The ODFRM CI shall submit all on-demand DEM product orders to an ECS operator after getting the OrderId from the ODPRM.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20170	The ODFRM CI shall send an email notification to the user upon submission of the ASTER on-demand product order.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20180	The ODFRM CI shall allow the user to specify contact information for any on-demand product order, and shipping information for any on-demand product order except L1B.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20190	The ODFRM CI shall allow the media distribution options to be configurable by a DAAC operator.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75045	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75046	The MSS accountability management service shall mark an order complete when all its subordinate requests have reached one of the following states:  a. Shipped  b. Aborted  c. Canceled  d. Terminated  e. Expired  f. L1B received	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75047	The MSS accountability management service shall support the following order/request states:  a. Pending  b. Operator Intervention  c. Staging  d. Transferring   e. Waiting for Shipment    f. Shipped  g. Aborted  h. Canceled  i. Terminated  j. Subsetting  k. Subsetting Staging  l. Prep for Distribution  m. SDSRV Staging  n. Queued  o. Waiting for data  p. Waiting for processing  q. Being processed  r. Completed processing  s. Expired  t. Awaiting L1B  u. L1B received  v. Null	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75055	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75056	The MSS accountability management service shall provide the capability to identify on demand processing orders and requests.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75062	The MSS accountability management service shall provide an interface for an operator to mark an ASTER on demand request as "canceled" or "aborted".	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04030	The PLANG CI shall accept a DEM order request from the ODFRM CI.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04060	The PLANG CI shall be able to obtain a geoid from the order request and resolve it into a granule UR.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04070	The PLANG CI shall identify individual granules for distribution as soon as they become available.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04097	 The PLANG CI shall initialize the status of a DEM request as "Queued".	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04190	The PLANG CI shall notify MSS order tracking of a DEM change of status to "Completed processing" when operations has created the DEM and inserted it into ECS -(the request is waiting to be submitted for distribution).	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04210	The PLANG CI shall pass an ODPR's priority to the SDSRV CI when the acquire is submitted for distribution.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04215	The PLANG CI shall submit the user-level acquire/FtpPush request to the SDSRV CI.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04230	The PLANG CI shall create a request in the MSS order tracking database for each generated DPR, and maintain the status of the request.	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04340	The PLANG CI shall submit the request to the SDSRV CI once the state of a DEM distribution request is updated to "Completed Processing."	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	no data				S-CLS-20002	The ODFRM CI shall accept one ASTER L1A or L1B granule ID as input to a DEM on-demand product order	
RM_5B_04	On-Demand ASTER DEM Superseded by Ticket BE_S3_01	no data				S-CLS-20005	The ODFRM shall require login as a registered ECS user in order for a user to be able to submit ASTER on-demand product orders.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20000	The ODFRM CI shall accept one or more GDS ASTER L1B granule IDs as input to an on-demand product order for higher level ASTER products	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20010	The ODFRM CI shall accept as input from the user ASTER on-demand processing parameter values.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20030	The ODFRM CI shall apply the same ASTER on-demand processing parameters for all granules in an ASTER on-demand product order.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20040	The ODFRM CI shall display valid values for ASTER on-demand processing parameters that have a limited set of values.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20050	The ODFRM CI shall display default values for ASTER on-demand processing parameters and apply them if the user does not override these values.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20060	The ODFRM CI shall send the on-demand product request to the ODPRM CI using ODPRMs DCE client I/F	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20070	The ODFRM CI shall allow the user to specify media distribution options for any ASTER on-demand product orders except ASTER L1B.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20080	The ODFRM CI shall verify all user inputs relating to ASTER on-demand processing and return the status of that input to the user.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20100	The ODFRM CI shall assign configurable priorities to all on-demand product orders.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20170	The ODFRM CI shall send an email notification to the user upon submission of the ASTER on-demand product order.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20180	The ODFRM CI shall allow the user to specify contact information for any on-demand product order, and shipping information for any on-demand product order except L1B.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DM	Automated On-Demand Production With Non-Default Parameters	The VO Web Client will allow the user to specify processing options for ASTER on demand products when constructing an order against ASTER L1B or L1A granules.  The ODFORM will support the specification in processing options to the client and acceptance of the request when it comes in	Apr 20 2000 12:00AM	S-CLS-20190	The ODFRM CI shall allow the media distribution options to be configurable by a DAAC operator.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27000	The PRONG CI shall provide the user specified values for PGE runtime parameters when executing an On-Demand PGE.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27010	The PRONG CI shall provide an operator interface to configure the maximum number of On-Demand Data Processing Requests (DPRs) that can concurrently execute.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27030	The PRONG CI shall send an email to the user if the PGE execution for an On-Demand Processing request fails irrecoverably.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27040	The PRONG CI shall notify the PLANG CI (ODPRM) if the PGE execution for an On-Demand Processing request fails irrecoverably.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27050	The PRONG CI shall notify the MSS Order server to update the MSS order tracking database and assign the value "Aborted" to the order status if the PGE execution for an On-Demand Processing request fails irrecoverably.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27060	The PRONG CI shall notify the MSS Order server to update the MSS order tracking database and assign the value "Completed processing" to the order status when the PGE execution for an On-Demand Processing request completes and all its output products are archived.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27070	The PRONG CI shall notify the MSS Order server to update the MSS order tracking database and assign the value "Started processing" to the order status when processing starts executing the DPR.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27080	The PRONG CI shall notify the MSS Order server to update the MSS order tracking database and assign the value "Waiting for data" to the order status when the DPR execution for an On-Demand Processing request is awaiting its input data.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27090	The PRONG CI shall notify the MSS Order server to update the MSS order tracking database and assign the value "Waiting for processing resources" to the order status when the DPR execution for an On-Demand Processing request is awaiting processing resources.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27100	The PRONG CI shall notify Science Data Server to delete the on-demand  products and their metadata from the archive after an operator configurable time in weeks has elapsed since  the products and their metadata of the On-Demand requests have been archived.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27110	The PRONG CI shall maintain a separate priority based queue to queue up on-demand data processing requests (DPRs).	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-27120	The PRONG CI shall concurrently execute DPRs for the same primary input granule using different or the same PGE profile and/or PGE RTI settings for a single PGE.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-42626	The AITTL CI shall allow up to 1000 profiles of a PGE to be registered.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-42627	The AITTL CI shall accept  a profile of a PGE as the default profile which will be executed as the precursor PGE when executing a PGE chain.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-42628	The AITTL CI shall ensure that each profile of an On-Demand PGE is unique.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501DP	Automated On-Demand Production With Non-Default Parameters	Change DPS such that OnDemand Manger is notified of Job states. I/F Changes; SSIT Updates to ODFORM, JobManagement interface changes, JobManagement providing status when requested.	Aug 11 1999 12:00AM	S-DPS-42629	The AITTL CI shall accept, while registering PGEs, the time delay  which will be a minimum of a week between production of on-demand data and the subsequent removal of that data from the archive.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501ID	Automated On-Demad Production With Non-Default Parameters		Aug 11 1999 12:00AM	C-CSS-61870	The Email Service shall accept attribute-value pairs and optional text to be inserted in email notification	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501ID	Automated On-Demad Production With Non-Default Parameters		Aug 11 1999 12:00AM	C-CSS-61880	The Email Service shall read text from file(s)	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75045	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75046	The MSS accountability management service shall mark an order complete when all its subordinate requests have reached one of the following states:  a. Shipped  b. Aborted  c. Canceled  d. Terminated  e. Expired  f. L1B received	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75047	The MSS accountability management service shall support the following order/request states:  a. Pending  b. Operator Intervention  c. Staging  d. Transferring   e. Waiting for Shipment    f. Shipped  g. Aborted  h. Canceled  i. Terminated  j. Subsetting  k. Subsetting Staging  l. Prep for Distribution  m. SDSRV Staging  n. Queued  o. Waiting for data  p. Waiting for processing  q. Being processed  r. Completed processing  s. Expired  t. Awaiting L1B  u. L1B received  v. Null	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75055	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75056	The MSS accountability management service shall provide the capability to identify on demand processing orders and requests.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75058	The MSS accountability management service shall provide a command line interface for an operator to be able to list the queue of on-demand production requests, sorted by one of the following: status, user id, order_id, ESDT id, or date/time queued.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75059	The MSS accountability management service shall provide an interface for an operator to be able to filter on on-demand orders associated with a particular user.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75062	The MSS accountability management service shall provide an interface for an operator to mark an ASTER on demand request as "canceled" or "aborted".	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04010	The PLANG CI shall determine which profile to run based on the user's input requirements.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04020	The PLANG CI shall determine which profile to run based on the ESDT version of each L1B input granule.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04050	The PLANG CI shall accept an order form request for a higher level ASTER product,  from the ODFRM CI.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04060	The PLANG CI shall be able to obtain a geoid from the order request and resolve it into a granule UR.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04070	The PLANG CI shall identify individual granules for distribution as soon as they become available.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04080	The PLANG CI shall notify the requester via e-mail when an ODPR for ASTER High Level Product fails or expires.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04090	The PLANG CI  failure / expiration notification shall describe the reason for the failure/expiration of a higher level product ODPR.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04095	 The PLANG CI shall register all on-demand product requests with the ECS order tracking database as on-demand orders and requests.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04096	 The PLANG CI shall initialize the status of an ASTER higher level ODPR request as "Queued".	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04150	The PLANG CI shall notify MSS order tracking of an Automated  Higher Level ASTER production request change of status to   "Expired" when the request has expired.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04170	 The PLANG CI shall notify MSS order tracking of an Automated  Higher level ASTER production request change of status to " Aborted" when the request has failed.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04210	The PLANG CI shall pass an ODPR's priority to the SDSRV CI when the acquire is submitted for distribution.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04215	The PLANG CI shall submit the user-level acquire/FtpPush request to the SDSRV CI.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04220	The PLANG CI shall be able to generate the appropriate data processing requests that are needed to fulfill an order, based on the user supplied input  forwardedby the ODFRM CI.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04230	The PLANG CI shall create a request in the MSS order tracking database for each generated DPR, and maintain the status of the request.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04240	The PLANG CI shall be able to process Automated Higher Level ASTER production requests which require a single PGE execution.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04260	The PLANG CI  shall release on-demand production requests that are for automatic product generation by ECS (Automated Higher Level ASTER production) when their input data is available on a first in first out basis.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04270	The PLANG CI shall periodically check whether an Automated Higher Level ASTER production request has expired and if so send an expiration notice via e-mail to the requester.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04280	The PLANG CI shall  consider an Automated Higher Level  ASTER production request expired if it is not ready for submission to processing because the inputs are not available, and the current date/time exceeds the date/time of the L1B by an operator configurable amount of time.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04290	The PLANG CI  shall notify the PRONG CI when an Automated Higher Level  ASTER production request expires.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04310	The PLANG CI shall allow the operator to run Automated Higher Level ASTER production requests at a higher priority than routine processing and re-processing.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04362	The PLANG CI  shall save the order request text to the database.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04365	The PLANG CI shall provide a script interface to allow the operator to retrieve the text of an existing order based on order id.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04370	The PLANG CI shall do a periodic (configurable by the operator) clean up of the database tables related to ODPRM processing.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	10501PL	Automated On-Demand Production With Non-Default Parameters	The ODPRM will require interfaces to SDSRV, SBSRV, V0GW, & DPS.   It will also need a  new GUI interface, several new classes as well as modification of existing classes within CoreLib	Aug 11 1999 12:00AM	S-PLS-04380	The PLANG CI shall be able to concurrently execute DPRs for the same primary input granule using different or the same PGE profile and/or PGE RTI settings for a single PGE.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	no data				S-CLS-20005	The ODFRM shall require login as a registered ECS user in order for a user to be able to submit ASTER on-demand product orders.	
RM_5B_05	On-Demand ASTER Higher Level Products Superseded by Ticket BE_S3_01	no data				S-CLS-20185	The ODFRM shall interface with MSS to obtain and apply defaults for contact and shipping information from the user profile where this information is not entered by the user.	
RM_5B_06	Integrated Browse	01680DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The V0-ECS Gateway currently only performs FTP browse.  The ability to retrieve a browse from SDSRV and send it back to the V0 client over the socket is required for Integrated browse.	Aug 11 1999 12:00AM	S-DMS-30384	The GTWAY CI shall have the capability to process V0 Integrated Browse Requests.	
RM_5B_06	Integrated Browse	01680DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The V0-ECS Gateway currently only performs FTP browse.  The ability to retrieve a browse from SDSRV and send it back to the V0 client over the socket is required for Integrated browse.	Aug 11 1999 12:00AM	S-DMS-30396	The GTWAY CI shall receive Integrated Browse Requests from the V0 IMS, using protocols defined in the V0/ECS ICD.	
RM_5B_06	Integrated Browse	01680DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The V0-ECS Gateway currently only performs FTP browse.  The ability to retrieve a browse from SDSRV and send it back to the V0 client over the socket is required for Integrated browse.	Aug 11 1999 12:00AM	S-DMS-30397	The GTWAY CI shall send Integrated Browse Requests to the SDSRV CI.	
RM_5B_06	Integrated Browse	01680DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The V0-ECS Gateway currently only performs FTP browse.  The ability to retrieve a browse from SDSRV and send it back to the V0 client over the socket is required for Integrated browse.	Aug 11 1999 12:00AM	S-DMS-30398	The GTWAY CI shall receive Integrated Browse Results from the SDSRV CI.	
RM_5B_06	Integrated Browse	01680DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The V0-ECS Gateway currently only performs FTP browse.  The ability to retrieve a browse from SDSRV and send it back to the V0 client over the socket is required for Integrated browse.	Aug 11 1999 12:00AM	S-DMS-30399	The GTWAY CI shall return Integrated Browse Results to the V0 IMS using protocols defined in the V0/ECS ICD	
RM_5B_07	M-Tool Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-20934	The DDICT CI shall send ECS Core and Product Specific Attributes with the Dependent Valid Values exported to the V0 IMS.	
RM_5B_07	M-Tool Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-20936	The DDICT CI shall send AM-1 ECS Core and Product Specific Attributes with the Dependent Valid Values exported to the V0 IMS.	
RM_5B_07	M-Tool Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-20938	The DDICT CI shall send AM-1 ECS Core and Product Specific Attribute definitions to the V0 IMS.	
RM_5B_07	M-Tool Enhancements	12005DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [Mtool ASTER Valids Export]	The Data Dictionary Maintenance Tool shall be able to export ECS collection's valids information to ASTER  via creation of a ECS collection valids file	Aug 11 1999 12:00AM	S-DMS-20931	The DDICT CI shall export Dependent Valid Values to the ASTER GDS in accordance to the ASTER GDS ICD.	
RM_5B_07	M-Tool Enhancements	12005DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [Mtool ASTER Valids Export]	The Data Dictionary Maintenance Tool shall be able to export ECS collection's valids information to ASTER  via creation of a ECS collection valids file	Aug 11 1999 12:00AM	S-DMS-20933	The DDICT CI shall allow the operator to select the Data Collections whose Dependent Valid Values will be exported to the ASTER GDS.	
RM_5B_07	M-Tool Enhancements	12006DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [MTool ASTER Attribute Mapping]	The Data Dictionary Maintenance Tool shall be able to map ECS collection's valids information to ASTER  valids information as well as ASTER collection valids to ECS valids for interoperability transparence.	Aug 11 1999 12:00AM	S-DMS-20691	The DDICT CI shall provide the capability allow an operator to add a link between ECS attributes and the ASTER and V0 terminology for these attributes.	
RM_5B_07	M-Tool Enhancements	12006DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [MTool ASTER Attribute Mapping]	The Data Dictionary Maintenance Tool shall be able to map ECS collection's valids information to ASTER  valids information as well as ASTER collection valids to ECS valids for interoperability transparence.	Aug 11 1999 12:00AM	S-DMS-20693	The DDICT CI shall provide the capability to allow an operator delete a link between ECS attributes and the ASTER and V0 terminology for these attributes.	
RM_5B_07	M-Tool Enhancements	12009DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [Mtool ASTER Valids Import]	The Data Dictionary Maintenance Tool shall be able to import ASTER collection's valids information from the ASTER GDS via parsing of a ASTER GDS collection valids file, and inserting those collections, along with their metadata into the Data Dictionary db.	Aug 11 1999 12:00AM	S-DMS-24020	The DDICT CI shall provide the capability to receive Dependent Valid Values from the ASTER GDS in accordance with ASTER GDS ICD.	
RM_5B_07	M-Tool Enhancements	12009DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [Mtool ASTER Valids Import]	The Data Dictionary Maintenance Tool shall be able to import ASTER collection's valids information from the ASTER GDS via parsing of a ASTER GDS collection valids file, and inserting those collections, along with their metadata into the Data Dictionary db.	Aug 11 1999 12:00AM	S-DMS-24030	The DDICT CI shall store the Dependent Valid Values in the DDICT CI database.	
RM_5B_07	M-Tool Enhancements	12009DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests [Mtool ASTER Valids Import]	The Data Dictionary Maintenance Tool shall be able to import ASTER collection's valids information from the ASTER GDS via parsing of a ASTER GDS collection valids file, and inserting those collections, along with their metadata into the Data Dictionary db.	Aug 11 1999 12:00AM	S-DMS-24040	The DDICT CI at the SMC shall have the capability to import ECS collections provided by the DAACs in the format defined in the ASTER GDS/ECS ICD for use by the ASTGW CI.	
RM_5B_08	V0Gateway Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-30371	The GTWAY CI shall accept ECS Core and/or Product Specific Attributes in an Inventory Search Request.	
RM_5B_08	V0Gateway Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-30376	The GTWAY CI shall send ECS Core and/or Product Specific Attributes in the Inventory Search Results.	
RM_5B_08	V0Gateway Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-30540	The GTWAY CI shall provide the capability to translate Version 0 system protocols into ECS system protocols defined in the V0/ECS ICD and LPDS/ECS ICD.	
RM_5B_08	V0Gateway Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-30550	The GTWAY CI shall provide the capability to translate ECS system protocols into Version 0 system protocols defined in the V0/ECS ICD and LPDS/ECS ICD.	
RM_5B_08	V0Gateway Enhancements	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-42190	The GTWAY CI shall accept a granule ID in an Inventory Search Request.	
RM_5B_08	V0Gateway Enhancements	12019DM	V0-ECS GTWAY ftp Push		Sep 22 1999 12:00AM	S-DMS-30413	The GTWAY CI shall have the capability to process ftp push Product Requests.	
RM_5B_08	V0Gateway Enhancements	12019DM	V0-ECS GTWAY ftp Push		Sep 22 1999 12:00AM	S-DMS-30414	The GTWAY CI shall receive ftp Product Requests from the V0 IMS, using protocols defined in the V0/ECS ICD.	
RM_5B_08	V0Gateway Enhancements	12019DM	V0-ECS GTWAY ftp Push		Sep 22 1999 12:00AM	S-DMS-30415	The GTWAY CI shall send ftp push Product Requests to the SDSRV CI.	
RM_5B_08	V0Gateway Enhancements	12019DM	V0-ECS GTWAY ftp Push		Sep 22 1999 12:00AM	S-DMS-30416	The GTWAY CI shall receive ftp push Product Request Results from the SDSRV CI.	
RM_5B_08	V0Gateway Enhancements	12019DM	V0-ECS GTWAY ftp Push		Sep 22 1999 12:00AM	S-DMS-30417	The GTWAY CI shall return ftp push Product Request Results to the V0 IMS using protocols defined in the V0/ECS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	01810DM	Two-Way Interoperability With ASTER GDS For ASTER L1B Processing Requests	The ECS-GDS server shall be able to handle inventory search requests from ECS clients	Aug 11 1999 12:00AM	S-DMS-40900	The ASTGW CI shall support multiple Service Requests.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41011	The ASTGW CI shall log the startup of the ASTGW servers.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41012	The ASTGW CI shall log the shutdown of the ASTGW servers.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41013	The ASTGW CI shall log when a service request is activated from the queue.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41014	The GDS-ECS component of the ASTGW CI shall log when a service request has been successfully decomposed into its component requests.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41018	The GDS-ECS component of the ASTGW CI shall log when the results of the request have been integrated and status is sent to the client.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41019	The ASTGW CI shall log when a successful user authentication has taken place.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41021	The ASTGW CI shall log when an unsuccessful user authentication has taken place.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-41051	The ASTGW CI shall log the failure of a request.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75065	The MSS accountability management service shall provide an ECS wide unique order ID for each Cross-DAAC GDS order.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75068	The MSS accountability management service shall provide an ECS wide unique request ID for each Cross-DAAC GDS request.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75075	The MSS accountability management service shall be able to create an order with a pre-existing order/request ID.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75076	The MSS accountability management service shall be able to create an order/request with a foreign home DAAC value.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75090	The MSS accountability management service shall replicate GDS Order Status from the DAACs to the SMC.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75091	The MSS accountability management service shall prevent GDS Order Status from replicating between the SMC and the DAAC when the GDS Order Status tables have different schemas.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75092	The MSS accountability management service shall allow manual GDS Order Status updates only by DAAC personnel from the processing DAAC.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75093	The MSS accountability management service shall allow automated GDS Order Status updates.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12001MS	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging		Aug 11 1999 12:00AM	C-MSS-75094	The MSS accountability management service shall allow GDS Order Status read-access at the SMC.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40320	The GDS-ECS Component of the ASTGW CI shall receive Inventory Search Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40325	The GDS-ECS Component of the ASTGW CI shall send Inventory Search Results to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40330	The GDS-ECS Component of the ASTGW CI shall support the chunking of inventory search results sent to the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40555	The GDS-ECS Component of the ASTGW CI shall receive and honor Quit Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40560	The GDS-ECS Component of the ASTGW CI shall receive a Product Cancel Request from the ASTER GDS,  using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40565	The GDS-ECS Component of the ASTGW CI shall send a Product Cancel Result with a status code of 10 to the ASTER GDS in response to a Product Cancel Request from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40570	The GDS-ECS Component of the ASTGW CI shall receive a Product Update Information from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40575	The GDS-ECS Component of the ASTGW CI shall send a Product Update Acknowledge with a status code of 10 to the ASTER GDS in response to a Product Update Information from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40603	The GDS-ECS Component of the ASTGW CI shall determine to which Information Manager(s) an Inventory Search Request must be sent.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40604	The GDS-ECS Component of the ASTGW CI shall perform ASTER-to-ECS valids mapping when receiving an Inventory Search Request from the GDS.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40610	The GDS-ECS Component of the ASTGW CI shall send Inventory Requests to the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40611	The GDS-ECS Component of the ASTGW CI shall receive Inventory Request Results from the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40616	The GDS-ECS Component of the ASTGW CI shall perform ECS-to-V0 valids mapping when sending Inventory Search Requests to the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40617	The GDS-ECS Component of the ASTGW CI shall send product requests for Landsat 7 scenes to the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-40618	The GDS-ECS Component of the ASTGW CI shall include in the product requests forwarded to the V0-ECS Gateway at the EDC DAAC the information specified in the ECS-EDC ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12013DM	GDS-ECS Inventory Search		Aug 11 1999 12:00AM	S-DMS-42040	The GDS-ECS Component of the ASTGW CI shall create a UR for each granule in the returned result set of a search request	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40433	The GDS-ECS Component of the ASTGW CI shall return a price of zero (0) for non-Landsat 7 price estimates. 	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40450	The GDS-ECS Component of the ASTGW CI shall interface with MSS to create order and request tracking information.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40452	The GDS-ECS Component of the ASTGW CI shall include the MSS order ID and request ID  when it sends Product Requests to the V0-ECS Gateway that resides where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40454	The V0-ECS Gateway shall provide the order ID and request ID it received from the ASTGW CI to MSS when it creates MSS order and request tracking information.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40600	The GDS-ECS Component of the ASTGW CI shall receive Product Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40607	The GDS-ECS Component of the ASTGW CI shall send Product Requests to the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40608	The GDS-ECS Component of the ASTGW CI shall receive Product Request Acknowledgement from a V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-40609	The GDS-ECS Component of the ASTGW CI shall send Product Request Acknowledgements to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-42130	The GDS-ECS Component of the ASTGW CI shall request user profile information from the MSS based on the authenticator information received in the request, or if none is provided in the request, based on a user ID configured as the default.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12014DM	GDS-ECS Product Request		Aug 11 1999 12:00AM	S-DMS-42140	The GDS-ECS Component of the ASTGW CI shall provide the authenticator received from the GDS in the requests to the V0-ECS Gateways, or if no authenticator was received, send the requests as ECS Guest using the profile information from the default user ID.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12015DM	GDS-ECS Price Estimate		Aug 11 1999 12:00AM	S-DMS-40410	The GDS-ECS Component of the ASTGW CI shall receive Price Estimate Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12015DM	GDS-ECS Price Estimate		Aug 11 1999 12:00AM	S-DMS-40420	The GDS-ECS Component of the ASTGW CI shall send Price Estimates to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12015DM	GDS-ECS Price Estimate		Aug 11 1999 12:00AM	S-DMS-40430	The GDS-ECS Component of the ASTGW CI shall return a configurable Landsat 7 Level 0R fixed scene price estimate to the ASTER GDS.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12015DM	GDS-ECS Price Estimate		Aug 11 1999 12:00AM	S-DMS-40433	The GDS-ECS Component of the ASTGW CI shall return a price of zero (0) for non-Landsat 7 price estimates. 	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12016DM	GDS-ECS Product Request Status		Aug 11 1999 12:00AM	S-DMS-40435	The GDS-ECS Component of the ASTGW CI shall receive Product Status Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12016DM	GDS-ECS Product Request Status		Aug 11 1999 12:00AM	S-DMS-40437	The GDS-ECS Component of the ASTGW CI shall send Order Tracking Status Requests to the Management CI.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12016DM	GDS-ECS Product Request Status		Aug 11 1999 12:00AM	S-DMS-40438	The GDS-ECS Component of the ASTGW CI shall receive Order Tracking Status Results from  the Management CI.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12016DM	GDS-ECS Product Request Status		Aug 11 1999 12:00AM	S-DMS-40440	The GDS-ECS Component of the ASTGW CI shall send Product Status Results to the ASTER GDS using ASTER GDS system protocols as defined in the ASTER ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12017DM	GDS-ECS Integrated Browse		Aug 11 1999 12:00AM	S-DMS-40470	The GDS-ECS Component of the ASTGW CI shall receive Browse Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12017DM	GDS-ECS Integrated Browse		Aug 11 1999 12:00AM	S-DMS-40480	The GDS-ECS Component of the ASTGW CI shall send Browse Results to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12017DM	GDS-ECS Integrated Browse		Aug 11 1999 12:00AM	S-DMS-40612	The GDS-ECS Component of the ASTGW CI shall send Browse Requests to the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12017DM	GDS-ECS Integrated Browse		Aug 11 1999 12:00AM	S-DMS-40613	The GDS-ECS Component of the ASTGW CI shall receive Browse Request Acknowledgements and Integrated Browse Results from the V0-ECS Gateway that resides at the DAAC where the requested data is archived.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12018DM	GDS-ECS Directory Search		Aug 11 1999 12:00AM	S-DMS-40490	The GDS-ECS Component of the ASTGW CI shall receive Directory Search Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12018DM	GDS-ECS Directory Search		Aug 11 1999 12:00AM	S-DMS-40495	The GDS-ECS Component of the ASTGW CI shall process Directory Search Requests using the Data Dictionary.	
RM_5B_09	GDS-to-ECS Gateway Cancelled per Contract Mod 10	12018DM	GDS-ECS Directory Search		Aug 11 1999 12:00AM	S-DMS-40500	The GDS-ECS Component of the ASTGW CI shall send Directory search Results to the ASTER GDS using protocols defined in the ASTER GDS ICD.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	C-CSS-40420	The SBSRV shall validate upon submission of a subscription that the subscription references a user ID associated with a MSS user profile.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	C-CSS-40425	The SBSRV shall pass a valid user profile ID of the user on whose behalf it is submitting an ACQUIRE request to the SDSRV CI along with the request.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06600	The SDSRV CI shall support a QA Time range measured as the number days after the value of the granule level attribute ProductionDateTime for the purpose of restricting access to granules.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06601	The SDSRV CI shall interpret a NULL QA Time range as indicating that the time range restriction rule should be applied to all granules within the collection, independent of ProductionDateTime.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06602	The SDSRV CI shall provide a command line interface for modifying the QA Time range associated with a specific ESDT.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06603	The SDSRV CI shall support access rules based upon the MSS User Profile roles of P, R, and N individually or in any combination.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06604	The SDSRV CI shall support two sets of access rules for both the OperationalQualityFlag and the ScienceQualityFlag  a. one set to be applicable during the QA time range as measured from the granule's production time,   b. the other to define the access rules that are applicable thereafter.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06605	The SDSRV CI shall support the following QA independent access permissions of a specific ESDT:  a. Privileged NASAUsers Only ('P')  b. Privileged and Regular NASAUsers ('PR')  c. Privileged, Regular and Non-NASAUsers (NULL).	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06606	The SDSRV CI shall provide a command line interface for changing the QA independent access permissions of a specific ESDT.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06607	The SDSRV CI shall use the MSS based NASAUSER attribute when evaluating granule access rules.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06608	The SDSRV CI shall send to the MSS Accountability Service a request for User Profile information including the NASAUser attribute.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06609	The SDSRV CI shall receive User Profile information, including the NASAUser attribute, from the MSS Accountability Service.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06610	The SDSRV CI shall process Acquire requests that do not contain a MSS User Profile parameter or whose profile ID starts with a "$" character with the assumption that the user is internal to ECS and thus has the access privilege associated with the NASAUser value of ("P").	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06611	The SDSRV CI shall process Acquire requests that provide an invalid MSS User Profile ID or a MSS User Profile ID of 'ECSGuest', with the assumption that the request is from a Non-NASAUser.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06612	The SDSRV CI shall grant access to any granule within it's inventory if the MSS User Profile associated with the supplied User ID contains a NASAUser attribute with the value of Privileged NASAUser ('P').	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06613	The SDSRV CI shall deny granule access to Regular NASAUsers ('R') if any of the following conditions are true:  a. The Access Permission for the ESDT does not include 'R' and is not NULL  b. The granule has quality flags for measured parameters AND the currently applicable access rule associated with the value of the granule's OperationalQualityFlag exists and does not contain 'R'  c. The granule has quality flags for measured parameters AND the currently applicable access rule associated with the value of the granule's ScienceQualityFlag exists and does not contain 'R'.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06614	The SDSRV CI shall deny granule access to Non-NASAUsers ('N') if any of the following conditions are true:  a. The Access Permission for the ESDT is not NULL and does not contain 'N'  b. The granule has quality flags for measured parameters AND the currently applicable access rule associated with the value of the granule's OperationalQualityFlag exists and does not contain 'N'  c. The granule has quality flags for measured parameters AND the currently applicable access rule associated with the value of the granule's ScienceQualityFlag exists and does not contain 'N'.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06615	The SDSRV CI shall log the user ID, ESDT short name and version, and granule ID to the SDSRV log file when attempts to access a granule are denied.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06616	The SDSRV CI shall assign a null value to the QA time range when a new ESDT is installed.	
RM_5B_10	Restricted Granule Access	12502DT	Restricted Granule Access	The SDSRV shall provide the capability to restrict access of data at the granule level.	Aug 11 1999 12:00AM	S-DSS-06617	The SDSRV CI shall assign a null value to the ESDT specific access permission when a new ESDT is installed.	
RM_5B_11	MSS User Profile Enhancements	10501MS	Automated On-Demand Production With Non-Default Parameters	Additional user profile and order tracking values to support Aster on-demand processing.	Aug 11 1999 12:00AM	C-MSS-75063	The MSS accountability management service shall provide the ability to identify whether a user has the privilege to order ASTER L1B products.	
RM_5B_11	MSS User Profile Enhancements	12502MS	Restricted Granule Access		Aug 11 1999 12:00AM	C-MSS-75021	The MSS accountability management service shall use the current NASA User attribute to distinguish among the following roles:  a. Privileged NASA User (encoded value 'P')  b. Regular NASA User (encoded value 'R')  c. Non-NASA User (encoded value 'N')	
RM_5B_11	MSS User Profile Enhancements	12502MS	Restricted Granule Access		Aug 11 1999 12:00AM	C-MSS-75022	The MSS accountability management service shall permit the setting of the NASA User attribute to one of the supported values when a user profile is entered or changed.	
RM_5B_11	MSS User Profile Enhancements	12502MS	Restricted Granule Access		Aug 11 1999 12:00AM	C-MSS-75023	The MSS accountability management service shall use a value of Non-NASA User ('N') as the default value for the NASA User attribute.	
RM_5B_12	SDSRV Recovery and Queuing Enhancements	12506DT	Recovery Enhancements (SDSRV- HDF-EOS Queue Mgmt)	SEE FOX/MEYER	Aug 11 1999 12:00AM	S-DSS-06300	The SDSRV CI shall provide the capability to limit the number of Asynchronous Acquire Requests that are executed concurrently.	
RM_5B_12	SDSRV Recovery and Queuing Enhancements	12506DT	Recovery Enhancements (SDSRV- HDF-EOS Queue Mgmt)	SEE FOX/MEYER	Aug 11 1999 12:00AM	S-DSS-06301	The SDSRV CI shall provide the capability to limit the number of Asynchronous Subsetting Acquire Requests that are executed concurrently.	
RM_5B_12	SDSRV Recovery and Queuing Enhancements	12506DT	Recovery Enhancements (SDSRV- HDF-EOS Queue Mgmt)	SEE FOX/MEYER	Aug 11 1999 12:00AM	S-DSS-06302	The SDSRV CI shall provide a Cold Start capability for Asynchronous Acquire Requests.	
RM_5B_12	SDSRV Recovery and Queuing Enhancements	12506DT	Recovery Enhancements (SDSRV- HDF-EOS Queue Mgmt)	SEE FOX/MEYER	Aug 11 1999 12:00AM	S-DSS-06303	The SDSRV CI shall provide a Warm Start/Restart capability for Asynchronous Acquire Requests.	
RM_5B_12	SDSRV Recovery and Queuing Enhancements	12506DT	Recovery Enhancements (SDSRV- HDF-EOS Queue Mgmt)	SEE FOX/MEYER	Aug 11 1999 12:00AM	S-DSS-06304	The SDSRV CI shall provide a GUI that displays the Asynchronous Acquire Requests that are waiting in the queue.	
RM_5B_12	SDSRV Recovery and Queuing Enhancements	12506DT	Recovery Enhancements (SDSRV- HDF-EOS Queue Mgmt)	SEE FOX/MEYER	Aug 11 1999 12:00AM	S-DSS-09400	The SDSRV CI shall persistently store Asynchronous Acquire requests.	
RM_5B_13	Update ESDT	01563DM	Update ESDT (update metadata/services)	The Data Dictionary shall be able to accept an update ESDT message from SDSRV in order to update collection metadata in the Data Dictionary database	Aug 11 1999 12:00AM	S-DMS-20161	The DDICT CI shall have the capability to accept updated data dictionary entries from the SDSRV CI Data Server.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06120	The SDSRV CI shall provide operations staff with the ability to update ESDTs by changing a mandatory attribute to optional or updating single-valued collection metadata, multi-valued collection metadata, inventory metadata, attributes of collection-related entities and service signatures.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06121	The SDSRV CI shall maintain a list of attributes that can not be updated through the ESDT update process.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06122	The SDSRV CI shall reject attempts to update attributes that have been determined to be non-updateable to include ShortName and VersionID in the CollectionDescriptionClass Group, AdditionalAttributeName, AdditionalAttributeType, SensorCharacteristicName, SensorCharacteristicType, AnalysisShortName, CampaignShortName, InstrumentShortName, PlatformShortName, and SensorShortName.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06123	The SDSRV CI shall send a command to the ADSRV CI to replace collection metadata when an ESDT is updated by updating selected collection metadata.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06124	The SDSRV CI shall send a command to the DDICT CI to replace collection and inventory metadata when an ESDT is updated by updating selected collection metadata.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06125	The SDSRV CI shall send a command to the DDICT CI to replace collection and inventory metadata when an ESDT is updated by updating selected inventory metadata.	
RM_5B_13	Update ESDT	01563DT	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing n the inventory for that ESDT.	Aug 11 1999 12:00AM	S-DSS-06126	The SDSRV CI shall send a command to the ADSRV CI to replace services when an ESDT is updated by updating the service signature.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40276	The Subscription Service shall accept a command from the SDSRV CI to replace an event when an ESDT is updated by adding additional qualifiers to a previously registered event	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40277	The Subscription Service shall be able to re-execute a replacement command whether or not a previous replacement command succeeded or failed.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40278	The Subscription Service shall return failure notification to the SDSRV CI if an event update is not successful.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40279	The Subscription Service shall pass replace event information in  an  ADSRV CI advertisement, using the ADSRV CI delete and insert interfaces .	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40281	The Subscription Service shall accept and process  advertisement failure notification from the ADSRV CI for ADSRV CI delete and insert interfaces.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40283	The Subscription Service shall preserve any existing subscriptions against events being replaced.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06100	The SDSRV CI shall update ESDTs using the updated version of the ESDT files provided by operations staff.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06101	The SDSRV CI shall provide operations staff with the ability to update ESDTs by adding optional collection metadata, optional inventory metadata, services, events and new qualifiers on existing events.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06102	The SDSRV CI shall send a command to the ADSRV CI to replace collection metadata when an ESDT is updated by adding optional collection metadata.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06103	The SDSRV CI shall send a command to the DDICT CI to replace collection and inventory metadata when an ESDT is updated by adding optional collection metadata.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06104	The SDSRV CI shall send a command to the DDICT CI to replace collection and inventory metadata when an ESDT is updated by adding optional inventory metadata.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06105	The SDSRV CI shall send additional services to the ADSRV CI when an ESDT is updated by adding services.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06106	The SDSRV CI shall send additional events to SBSRV when an ESDT is updated by adding events.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06107	The SDSRV CI shall send a command to SBSRV to replace an event when an ESDT is updated by adding additional qualifiers to a previously registered event.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06108	The SDSRV CI shall provide operations staff with functionality in the SDSRV Operations GUI to install updated ESDTs.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06109	The SDSRV CI shall recover from and process the resubmittal of a partially completed ESDT update.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06110	The SDSRV CI shall prohibit the use of an ESDT that has partially completed ESDT update in any other service calls.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06111	The SDSRV CI shall validate the updated descriptor as part of the Update ESDT process.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06112	The SDSRV CI shall determine the changes to the updated descriptor as part of the ESDT Update process.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06113	The SDSRV CI shall notify operations staff if there are no differences in a descriptor as part of the ESDT process.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06114	The SDSRV CI shall disable all other services during the ESDT Update process.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06115	The SDSRV CI shall only accept ESDT update requests when the SDSRV is operating in a maintenance mode.	
RM_5B_13	Update ESDT	12514ID	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	S-DSS-06131	The SDSRV CI shall provide operations staff with the capability to update ESDTs. 	
RM_5B_13	Update ESDT	12514II	Update ESDT (update metadata/services)	The SDSRV shall provide the capability to update Collection level metadata with granules existing in the inventory for that ESDT. This capability is limited to adding (only) metadata, services, and events	Aug 11 1999 12:00AM	C-CSS-40285	The Subscription Service shall treat a request to insert an event as a request to replace the event if the event already exists	
RM_5B_13	Update ESDT	no data				S-DMS-24120	The DDICT CI shall accept the resubmittal of a previously failed update request.	
RM_5B_13	Update ESDT	no data				S-IOS-00420	The ADSRV CI shall preserve existing advertisements when updating collection metadata.    	
RM_5B_13	Update ESDT	no data				S-IOS-00430	The ADSRV CI shall treat a duplicate add request for service advertisement data as a replace request.	
RM_5B_13	Update ESDT	no data				S-IOS-00440	The ADSRV CI shall accept the resubmittal of a previously failed update request.	
RM_5B_14	ASTER Browse	12517DT	ASTER Browse		Oct 18 1999 12:00AM	S-DSS-07100	SDSRV CI shall associate the BROWSE granule for an ASTER L1A granule with all ASTER L1B  products derived  from that L1A granule.	
RM_5B_14	ASTER Browse	12517DT	ASTER Browse		Oct 18 1999 12:00AM	S-DSS-07101	SDSRV CI shall associate the BROWSE granule for an ASTER L1A granule with all ASTER DEM  products derived  from that L1A granule, or from any L1B granule derived from that L1A.	
RM_5B_14	ASTER Browse	12517DT	ASTER Browse		Oct 18 1999 12:00AM	S-DSS-07102	The SDSRV shall be able to associate the BROWSE granules for pre-existing ASTER L1A with all existing ASTER L1B products derived  from each L1A granule.	
RM_5B_14	ASTER Browse	12517DT	ASTER Browse		Oct 18 1999 12:00AM	S-DSS-07103	The SDSRV shall be able to associate the BROWSE granules for pre-existing ASTER L1A with all existing ASTER DEM products derived  from each L1A granule.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75085	The MSS accountability management service shall only allow read-access of User Profiles at the DAACs.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75086	The MSS accountability management service shall replicate User Profiles from the SMC to the DAACs.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75087	The MSS accountability management service shall be capable of identifying the homeDAAC of an operator accessing the user profile database.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75088	The MSS accountability management service shall allow the approval of User Profile registration requests only by DAAC personnel from the assigned User Profile homeDAAC at the SMC.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75089	The MSS accountability management service shall allow User Profile updates at the SMC only by DAAC personnel from the assigned User Profile homeDAAC.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75095	The MSS accountability management service shall allow the SMC operator to approve user profile registration requests on behalf of any DAAC.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75096	The MSS accountability management service shall allow the SMC operator to perform user profile updates on behalf of any DAAC.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75097	The MSS accountability management service shall be able to identify and recover from a loss of replicate transactions.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75098	The MSS accountability management service shall be able to issue warnings to a DAAC and the SMC when the DAAC did not successfully process a given replication cycle.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75099	The MSS accountability management service shall allow the SMC operator to create a listing of all user profile additions and update that did not successfully replicate to a given DAAC.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75100	The MSS accountability management service shall alert the DAAC operations staff when replication-related servers fail.	
RM_5B_15	User Profile Replication	12021DM	User Profile Replication		Feb  8 2000 12:00AM	C-MSS-75101	The MSS accountability management service shall disable a user's account when the account has been disabled at the user's designated homeDAAC.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-CLS-20250	The ODFRM CI shall not offer physical media distributions (i.e., other than FTP Push and FTP Pull).	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-CSS-40502	The SBSRV GUI shall not offer physical media as a  distribution option.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DMS-30600	The GTWAY CI shall send requests for physical media distributions that it would normally submit to the SDSRV as Product Request messages to the PDS.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DMS-30602	The GTWAY CI shall accept Product Result messages for physical media requests that it forwarded to the PDS.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DMS-30604	The GTWAY CI shall use the DORRAN formats and protocols specified in the ECS-EDC Interface Control Document ICD 423-41-58 for the product request and product response. 	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DMS-30605	The GTWAY CI shall include CD-ROM, DLT, and DVD in the physical media distribution options of the V0 ODL messages it sends to the EDG. 	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01680	The SDSRV Command Line Interface shall accept FTP Push distribution requests and associated parameters.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01681	The SDSRV Command Line Interface shall include the FTP Push parameters in the ACQUIRE request it submits to the SDSRV	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01682	The SDSRV Command Line Interface shall accept an ECSUSERPROFILE parameter.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01683	The SDSRV Command Line Interface shall include the ECSUSERPROFILE parameter in the SDSRV ACQUIRE request it submits.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01684	The SDSRV Command Line Interface shall accept a PRIORITY parameter.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01685	The SDSRV Command Line Interface shall include the PRIORITY parameter  in the SDSRV ACQUIRE request it submits.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01686	The SDSRV Command Line Interface shall accept an UserString parameter.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01687	The SDSRV Command Line Interface shall include the UserString parameter  in the SDSRV ACQUIRE request it submits.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01688	The SDSRV Command Line Interface shall accept an DDISTNOTIFYTYPE and a NOTIFY parameter.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01689	The SDSRV Command Line Interface shall include the DDISTNOTIFYTYPE and a NOTIFY parameters  in the SDSRV ACQUIRE request it submits.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01690	The SDSRV Command Line Interface shall accept a tag parameter.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01691	The SDSRV Command Line Interface shall use the tag parameter to generate an rpcID for the SDSRV ACQUIRE request it submits.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01692	The SDSRV Command Line Interface shall accept a list of up to 100 granule identifiers that represent the granules to be acquired.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01693	The SDSRV Command Line Interface shall accept  granule identifiers specified in V0/DORRAN format (example: 'SC:L70RWRS.001:2000022933').	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01694	The SDSRV Command Line Interface shall submit an ACQUIRE command for the identified granules.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01695	The SDSRV Command Line Interface shall accept requests for a single Landsat floating scene and its associated subsetting parameters.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01696	Upon receipt of a Landsat floating scene request, the SDSRV Command Line Interface shall submit a corresponding Landsat floating scene subsetting request to the SDSRV.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01697	The SDSRV Command Line Interface shall be able to accept requests from multiple PDS instances that may employ different user profiles.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01698	The SDSRV Command Line Interface shall be able to accept requests for a designated mode.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01699	It shall be possible to submit several requests in a given mode via the SDSRV Command Line Interface concurrently.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-01700	It shall be possible to submit requests via the SDSRV Command Line Interface in several different modes concurrently.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-30050	The DDIST CI shall be able to display the UserString parameter of an ACQUIRE command on the DDIST GUI.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-30052	The DDIST CI shall be able to recognize PDS requests based on a configurable lead-in string.  (for example, if the configured string is '$PDS', then a request associated with a user profile ID '$PDS01' would be recognized as a PDS request).	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-30054	The DDIST CI shall cause PDS FTP Push requests to be distributed via HiPPI at sites where a HiPPI connection to the PDS staging area is available.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-30056	The DDIST CI shall cause PDS FTP Push requests to be distributed via the internal (i.e., drg-resident) ftp distribution server.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-30058	The DDIST CI shall suppress the DORRAN DN it currently sends for Landsat data requests if the request is a PDS request.	
RM_5X_01	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-DSS-30060	The DDIST CI shall use the NOTIFY parameter of the ACQUIRE request (if specified) as the target for a DN or Failed DN if the distribution request is not associated with a Request ID. 	
RM_6A_01	Reprocessing	10503DP	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-DPS-23100	The PRONG CI shall provide the capability for the operator to specify at runtime the maximum number of routine processing jobs that may be submitted for execution at a time.	
RM_6A_01	Reprocessing	10503DP	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-DPS-23110	The PRONG CI shall provide the capability for the operator to specify at runtime  the maximum number of reprocessing jobs that may be submitted for execution at a time. 	
RM_6A_01	Reprocessing	10503DP	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-DPS-23120	The PRONG CI shall provide the capability for the reprocessing jobs to be submitted to a separate queue for execution.	
RM_6A_01	Reprocessing	10503PL	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-PLS-00070	The PLANG CI shall accept Reprocessing Production Requests that specify input data for temporal or spatial ranges using an updated PGE.	
RM_6A_01	Reprocessing	10503PL	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-PLS-00071	The PLANG CI shall accept Reprocessing Production Requests that specify input data for temporal or spatial ranges that have been processed previously using the same version PGE.	
RM_6A_01	Reprocessing	10503PL	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-PLS-00700	The PLANG CI shall provide the capability to create Candidate Plans specifying a timeline for PGE execution that will satisfy Production Requests for Reprocessing Products consistent with available and allocated processing resources.	
RM_6A_01	Reprocessing	10503PL	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-PLS-01221	The PLANG CI shall provide the capability to concurrently handle multiple routine and reprocessing Production Requests using the same PGE and requiring the same type of input data.	
RM_6A_01	Reprocessing	10503PL	Reprocessing	The ECS shall have the capability to generate reprocessed data products from any original or updated single data input or combination of data inputs as required by the original or updated Science Software provided by the scientists.	Jan 17 2000 12:00AM	S-PLS-02610	The PLANG CI shall provide the ability for the planner to designate the Production Requests/DPRs as reprocessing jobs.	
RM_6A_04	FTP Pull Subscriptions	04648ID	Subscription Enhancements - FTP Pull Acquire	Subscription Server will support acquires via FTP pull.	Aug 11 1999 12:00AM	C-CSS-30640	The Registry shall store distribution options information. 	
RM_6A_04	FTP Pull Subscriptions	04648ID	Subscription Enhancements - FTP Pull Acquire	Subscription Server will support acquires via FTP pull.	Aug 11 1999 12:00AM	C-CSS-30650	The Registry shall provide an API to retrieve information that is hierarchically structured, containing dependencies between values. 	
RM_6A_04	FTP Pull Subscriptions	04648ID	Subscription Enhancements - FTP Pull Acquire	Subscription Server will support acquires via FTP pull.	Aug 11 1999 12:00AM	C-CSS-40062	The SBSRV shall allow operators to submit subscriptions that specify an FTP Pull Acquire as an action.	
RM_6A_04	FTP Pull Subscriptions	04648ID	Subscription Enhancements - FTP Pull Acquire	Subscription Server will support acquires via FTP pull.	Aug 11 1999 12:00AM	C-CSS-40064	The SBSRV shall acquire a granule on behalf of the user for FTP Pull if the subscription specifies FTP Pull Acquire as its action.	
RM_6A_04	FTP Pull Subscriptions	04648ID	Subscription Enhancements - FTP Pull Acquire	Subscription Server will support acquires via FTP pull.	Aug 11 1999 12:00AM	C-CSS-40500	The SBSRV shall provide an interface to the operator for the selection of distribution options for a product order, using information in the ECS Configuration Registry.	
RM_6A_04	FTP Pull Subscriptions	13500ID	Additional Media Types	The CSS SBSRV will provide an interface to the operator for the selection of CD-ROM or DLT as the distribution media for a product order, using information in the ECS configuration registry.  The CSS MTMGW will validate the selection of CD-ROM or DLT as the distribution media for a product order, using information in the ECS configuration registry.	Feb 24 2000 12:00AM	C-CSS-30640	The Registry shall store distribution options information. 	
RM_6A_04	FTP Pull Subscriptions	13500ID	Additional Media Types	The CSS SBSRV will provide an interface to the operator for the selection of CD-ROM or DLT as the distribution media for a product order, using information in the ECS configuration registry.  The CSS MTMGW will validate the selection of CD-ROM or DLT as the distribution media for a product order, using information in the ECS configuration registry.	Feb 24 2000 12:00AM	C-CSS-30650	The Registry shall provide an API to retrieve information that is hierarchically structured, containing dependencies between values. 	
RM_6A_04	FTP Pull Subscriptions	13500ID	Additional Media Types	The CSS SBSRV will provide an interface to the operator for the selection of CD-ROM or DLT as the distribution media for a product order, using information in the ECS configuration registry.  The CSS MTMGW will validate the selection of CD-ROM or DLT as the distribution media for a product order, using information in the ECS configuration registry.	Feb 24 2000 12:00AM	C-CSS-40500	The SBSRV shall provide an interface to the operator for the selection of distribution options for a product order, using information in the ECS Configuration Registry.	
RM_6A_04	FTP Pull Subscriptions	13501ID	Data Distribution Enhancements - Compression	The CSS SBSRV will provide an interface to the operator for the selection of Unix and GZIP as compression formats for a product order, using information in the ECS configuration registry. The CSS MTMGW will validate the selection of Unix and GZIP as compression formats for a product order, using information in the ECS configuration registry.	Feb 23 2000 12:00AM	C-CSS-30640	The Registry shall store distribution options information. 	
RM_6A_04	FTP Pull Subscriptions	13501ID	Data Distribution Enhancements - Compression	The CSS SBSRV will provide an interface to the operator for the selection of Unix and GZIP as compression formats for a product order, using information in the ECS configuration registry. The CSS MTMGW will validate the selection of Unix and GZIP as compression formats for a product order, using information in the ECS configuration registry.	Feb 23 2000 12:00AM	C-CSS-30650	The Registry shall provide an API to retrieve information that is hierarchically structured, containing dependencies between values. 	
RM_6A_04	FTP Pull Subscriptions	13501ID	Data Distribution Enhancements - Compression	The CSS SBSRV will provide an interface to the operator for the selection of Unix and GZIP as compression formats for a product order, using information in the ECS configuration registry. The CSS MTMGW will validate the selection of Unix and GZIP as compression formats for a product order, using information in the ECS configuration registry.	Feb 23 2000 12:00AM	C-CSS-40500	The SBSRV shall provide an interface to the operator for the selection of distribution options for a product order, using information in the ECS Configuration Registry.	
RM_6A_05	Machine-to-Machine Gateway	15501DT	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	S-DSS-00080	The SDSRV CI shall prevent submission of two asynchronous acquire requests with the same rpcID from leading to faults or errors in the  handling of these requests.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50010	The MTMGW CI shall provide an external communications interface to receive requests for locally archived data and return responses.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50015	The MTMGW CI shall base its external interface on remote shell commands submitted by the SIPS via ssh.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50020	The MTMGW CI shall be able to execute  multiple concurrent requests from a single as well as multiple SIPS.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50022	The MTMGW CI shall allow operators to execute several MTMGW servers concurrently, each to be used by a different SIPS.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50024	The MTMGW CI shall allow operators to provide a separate set of configuration parameter values for each MTMGW server.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50030	The MTMGW CI shall permit operators to configure the maximum number of concurrent requests that can be in progress at each MTMGW server.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50040	The MTMGW CI shall respond to a request that exceeds the maximum number of concurrent requests with an error response indicating that the request exceeded the configured resources.  	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50050	The MTMGW CI shall employ a security mechanism that verifies that requests are coming from an external client authorized to use the ECS machine-to-machine gateway.  	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50060	The MTMGW CI shall reject requests that cannot be identified as coming from an authorized external client. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50070	The MTMGW CI requests and responses shall be ASCII text.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50080	The MTMGW CI shall validate request syntax and return an error response if the syntax is invalid.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50090	The MTMGW CI shall accept the following types of requests via Unix commands from the external client:      1. Inventory search request     2. Product request request    3. Integrated search & order request 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50095	The MTMGW CI shall return the following types of responses to these commands to the external client:       1. Inventory search response following an inventory search request     2. Product request response following an inventory product request     3. Integrated search & order response following an integrated search & order request 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50100	The MTMGW CI shall route requests to the MTMGW server that is configured to handle the requests from the respective external client. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50101	The MTMGW CI shall permit an external client to specify a Message Identifier in each request message. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50102	The MTMGW CI shall assume a Message Identifier of NULL if the client does not provide one.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50104	The MTMGW CI shall return the Message Identifier provided by the client in its response message to that request. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50106	The MTMGW CI shall permit operators at each DAAC to specify the locally archived ESDTs that are available for searching and ordering via a MTMGW server as part of the configuration parameters for that server.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50110	The MTMGW CI shall receive inventory search requests from external clients.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50120	The MTMGW CI shall reject an inventory search request if it references any ESDT that operators have not configured as accessible via the MTMGW server handling the request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50130	The MTMGW CI shall permit an external client to specify the core and product specific inventory attributes that are to be returned as part of the search result.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50140	The MTMGW CI shall allow the use of a generic attribute name to request spatial coverage information regardless of the spatial data type used for that purpose in the ECS inventory.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50150	The MTMGW CI shall translate a search request into a SDSRV inventory search.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50155	The MTMGW CI shall use the generic spatial search type when submitting a search request to the SDSRV.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50160	The MTMGW CI shall submit inventory searches to the local SDSRV CI.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50170	The MTMGW CI shall accept inventory search results from the local SDSRV CI.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50180	The MTMGW CI shall return the inventory search result formatted in XML in the inventory search response.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50185	The MTMGW CI shall include a truncation flag indicating truncation by the SDSRV CI in the inventory search response if the search result was truncated by the SDSRV CI.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50190	The MTMGW CI shall include the ESDT short name, version, granule ID, and local granule ID (if available) for each granule as part of the search result.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50200	The MTMGW CI search request shall permit an external client to specify whether it wants the ECS granule UR returned as part of the search result for each granule.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50202	The MTMGW CI shall include the ECS granule UR for each granule in the search result if and only if this is specified in the search request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50210	The MTMGW CI shall include in the search result, for each granule, the core and product specific inventory attributes as specified in the search request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50220	The MTMGW CI shall allow an external client to specify the maximum size of the search result (in terms of number of granules) to be returned.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50230	The MTMGW CI shall allow operators to configure the maximum size of a search result (in terms of number of granules) that will be used if the external client specifies no maximum result size or one that is larger. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50250	The MTMGW CI shall not return more granules in a search result response than given by the maximum search result size, if one is specified. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50252	If the search result was truncated by the MTMGW gateway, it shall include in the inventory search response:       1. a flag indicating that truncation occurred    2. an indication as to which limit triggered the truncation    3. the value to which the limit was set 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50255	The MTMGW CI shall include in each inventory search response the total number of granules returned by the SDSRV.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50270	The MTMGW CI shall receive product requests from external client.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50272	The MTMGW CI product request shall permit an external client to specify the following information:   1. External Request ID  2. ECS distribution options   3. Contact and shipping information 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50274	The MTMGW CI shall check for each product request whether it already submitted an ACQUIRE for a  product request or integrated search and order request with the same external request ID from the same external client, and return a successful response without further processing request if that is the case. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50280	The MTMGW CI shall reject a product request if it references any ESDT that operators have not configured as accessible via the MTMGW server handling the request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50290	The MTMGW CI product request shall permit an external client to specify the ECS distribution options that shall be applicable to all products ordered in this request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50300	The MTMGW CI product request shall permit an external client to specify contact and shipping information.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50310	The MTMGW CI product request shall permit an external client to specify one or several data granules based on ECS granule UR; or ESDT short name, version, and granule ID; or ESDT short name, version, and local granule ID (if available for that ESDT).	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50320	The MTMGW CI product request shall permit an external client to order the specified data granules.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50330	The MTMGW CI product request shall permit an external client to order BROWSE, QA or PH granules associated with the specified data granules in any combination and in lieu of or along with those granules.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50340	The MTMGW CI requests shall permit an external client to include an MSS User ID in each request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50342	The MTMGW CI shall obtain the MSS user profile of the external client based on the user ID contained in a request, if present.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50350	The MTMGW CI shall use an operator configurable default user ID if a request does not contain a user ID.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50352	The MTMGW CI shall use information in the MSS user profile associated with the user ID of the external client (if one is available) to fill in default contact and shipping information for an order if it is not supplied in a product request or integrated search and order request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50360	The MTMGW CI shall verify on start-up that a valid MSS user ID has been configured as the default user ID.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50365	The MTMGW CI shall reject requests that do not provide a user ID if no default user ID has been configured.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50370	The MTMGW CI shall obtain the priority of a request from the user profile.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50390	The MTMGW CI shall create MSS order tracking information for all product orders it submits to ECS on behalf of product requests and integrated search & order requests.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50392	The MTMGW CI shall initialize the request status to NULL.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50394	The MTMGW CI shall initialize the order type to MM.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50400	The MTMGW CI shall not process product requests, or searches, or integrated search & orders for Landsat products.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50410	The MTMGW CI shall translate product requests into SDSRV asynchronous ACQUIRE requests.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50420	The MTMGW CI shall submit asynchronous ACQUIRE requests without callback for orders resulting from product requests and integrated search & order requests to the local SDSRV CI.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50430	The MTMGW CI shall include the MSS user ID and request priority in all acquire requests it generates.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50432	The MTMGW CI shall include the external request ID in the USERSTRING of any acquire request it submits.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50440	The MTMGW CI shall receive acquire request responses from the local SDSRV CI.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50450	The MTMGW CI shall include the MSS orderID in the product request response if the product request was successfully submitted.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50460	The MTMGW CI shall include the type of error encountered in the product request response if the product request was not accepted.  	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50465	The MTMGW CI shall receive integrated search & order requests from external client.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50470	The MTMGW CI integrated search & order request shall permit an external client to specify a search, as well as the order information to be used in acquiring the found granules.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50472	The MTMGW CI shall reject an integrated search & order request if it references any ESDT that operators have not configured as accessible via the MTMGW server handling the request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50473	The MTMGW CI integrated search & order request shall permit an external client to specify the following information:   1. External Request ID   2. ECS distribution options  3. Contact and shipping information 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50474	The MTMGW CI integrated search & order request shall permit an external client to order the data granules returned by the SDSRV search.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50475	The MTMGW CI integrated search & order request shall permit an external client to order BROWSE, QA or PH granules associated with the data granules returned by the SDSRV search, in any combination and in lieu of or along with those granules.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50476	The MTMGW CI shall include an rpcID in the ACQUIRE submitted for a product request or integrated search & order request. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50477	The MTMGW CI shall ensure that the rpcID for different combinations of external request ID and external client is different; and that it is the same for identical combinations of external request ID and external client if an external request ID is reused while the previous request is still recorded in the MSS order tracking database. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50478	The MTMGW CI shall check for each integrated search & order request whether it already submitted an ACQUIRE for a product request or integrated search & order request with the same external request ID from the same external client, and return a successful response without further processing the request if that is the case. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50480	The MTMGW CI shall allow an external client to specify the maximum size of the search result (in terms of number of granules and/or total number of uncompressed Mbytes) to be used as a limit on product ordering.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50490	The MTMGW CI shall allow operators to configure the maximum size of an order (in terms of number of granules and total number of uncompressed Mbytes) that will be used as a limit on product ordering for product requests and integrated search & order requests; and that will be used if the external client specifies no limit or one that is larger.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50500	The MTMGW CI shall translate the search specified in an integrated search & order requests into an SDSRV inventory search.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50510	The MTMGW CI shall reject a product request and an integrated search & order request if the maximum size permitted for integrated ordering is exceeded.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50512	The MTMGW CI shall include in its response, if a product request or integrated search and order request is rejected because size limits were exceeded, the following:       1. an indication as to which size limit was exceeded    2. the value to which the limit was set, and     3. the size of the order in granules or Mbytes (whichever triggered the rejection) 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50514	The MTMGW CI shall reject an integrated search & order request if the search was truncated by the SDSRV.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50516	The MTMGW CI shall include an indication of the truncation by the SDSRV CI in the response, if an integrated search and order request is rejected because the result was truncated by the SDSRV CI.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50520	The MTMGW CI shall submit an order to ECS for the granules contained in the search result of an integrated search & order requests, and/or their associated BROWSE, QA or PH granules  if the search was not truncated and the maximum size permitted for integrated ordering is not exceeded.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50522	The MTMGW CI shall use information in the MSS user profile associated with the user ID of the external client to fill in default contact and shipping information if it is not supplied in the integrated search & order request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50530	The MTMGW CI shall include in the integrated search & order response the MSS orderID if the product request was successfully submitted.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50532	The MTMGW CI shall include in the  integrated search & order response the type of error that was encountered if the request failed.  	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50534	The MTMGW CI shall include the number of granules that have been ordered in the response for an integrated search & order request.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50540	The MTMGW CI shall allow operators to monitor its state from a system operator console. 	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50550	The MTMGW CI shall allow operators to start and shut it down from a system operator console.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50560	The MTMGW CI shall be able to operate in multiple modes.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50570	The MTMGW CI shall re-initialize its state upon restart, i.e., it shall always cold start.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50650	The MTMGW CI shall log the receipt of each request and the sending of each response along with the following (as applicable): date, time, request type, user ID, MSS order and Request ID, rpcID, external request ID, request/response size, and for responses the type of response (error type or OK).	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50660	The MTMGW CI shall log all errors.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50665	The MTMGW CI shall return an error to the external client when the connection with the MTMGW server processing a request is lost or when such a connection cannot be established.	
RM_6A_05	Machine-to-Machine Gateway	15501ID	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG.	Apr  5 2000 12:00AM	C-CSS-50680	The MTMGW CI shall obtain from the DDICT CI core and product-specific attribute type information specified in a search request.	
RM_6A_05	Machine-to-Machine Gateway	15501II	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	S-DSS-00072	The SDSRV CI shall receive acquire requests from the local MTMGW CI.	
RM_6A_05	Machine-to-Machine Gateway	15501II	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	S-DSS-00073	The SDSRV CI shall update the MSS request status of an asynchronous acquire request to "Pending after it was check-pointed and before returning a response to the submitting application.	
RM_6A_05	Machine-to-Machine Gateway	15501II	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	S-DSS-00074	The SDSRV CI shall interface with the local MTMGW CI to return acquire responses for the acquire requests the MTMGW CI submitted.	
RM_6A_05	Machine-to-Machine Gateway	15501II	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	S-DSS-00168	The SDSRV CI shall accept inventory searches from the local MTMGW CI.	
RM_6A_05	Machine-to-Machine Gateway	15501II	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	S-DSS-00169	The SDSRV CI shall interface with the local MTMGW CI to return inventory search results for the searches the MTMGW CI submitted.	
RM_6A_05	Machine-to-Machine Gateway	15501MS	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	C-MSS-75106	The MSS Accountability Service shall keep an external request ID and an rpcID as part of the order tracking information. 	
RM_6A_05	Machine-to-Machine Gateway	15501MS	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	C-MSS-75107	The MSS Accountability Service GUI shall allow operators to view orders and requests by external request ID; and external request ID plus user ID. 	
RM_6A_05	Machine-to-Machine Gateway	15501MS	Machine-To-Machine Search And Order Gateway For Data Retrieval By External Sources	IDG will provide a SIPS/ECS gateway.  The gateway will accept data orders from  SIPS via ssh commands, specifying the data type, spatial and/or temporal qualification, and other qualifications (TBS by IDG) in a format which maps one-to-one to the GlParameter format of an SDSRV search (TBS by IDG).  The gateway will submit the corresponding search request into ECS, and order the resulting granules for ftp-push or media from ECS (option specifiable in the order submitted by SIPS in format TBS by IDG ..	Apr  5 2000 12:00AM	C-MSS-75108	The MSS Accountability Service shall allow the retrieval of requests and orders based on the external request ID; and external request ID plus user ID. 	
RM_6A_05	Machine-to-Machine Gateway	no data				C-DMS-20131	The DDICT CI shall accept requests for core and product-specific attribute type information specified in a search request from the local MTMGW CI.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-19400	The WKBCH CI DAR Tool shall give a user who is logged in as a valid ECS user the option to invoke the on-demand order forms for submission of standing on-demand processing orders for ASTER higher level products when the user submits a DAR, and by the user selecting a DAR from a DAR query result.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-19410	The WKBCH CI DAR Tool shall pass the user ID, password, DAR ID, and DAR expiration time to the ODFRM CI if the user chooses to exercise the option to submit on-demand processing orders for a DAR.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-20300	The ODFRM CI shall accept the user ID, password, DAR ID, and DAR Expiration from the DAR tool in a secure fashion (i.e., via https) for subsequent use in entering a standing on-demand order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-20320	The ODFRM CI shall allow the user to enter the information for standing on-demand orders for ECS higher level ASTER on-demand products, (i.e., excluding DEM and L1B products).	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-20330	The ODFRM CI shall recognize the DAR ID as the place holder for the future input granules into the actual on-demand orders.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-20340	The ODFRM CI shall submit each standing on-demand processing order entered by a user in association with a DAR to the PLANG CI (ODPRM), identifying it as a standing on-demand processing order. 	
RM_6A_07	EDC processing DPR Attached to a DAR	10504CL	Attached DPR		Feb 23 2000 12:00AM	S-CLS-20350	The ODFRM CI shall include the DAR ID and DAR Expiration in the order information when it submits the order to the PLANG CI (ODPRM). 	
RM_6A_07	EDC processing DPR Attached to a DAR	10504MS	Attached DPR		Feb 23 2000 12:00AM	C-MSS-75200	The MSS Accountability Service shall provide an interface for identifying an order and a request as being for a 'standing on-demand processing order'.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504MS	Attached DPR		Feb 23 2000 12:00AM	C-MSS-75210	The MSS Accountability Service shall provide an API for setting the DAR ID and DAR Expiration Time in the MSS order tracking information created for an on-demand standing processing order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504MS	Attached DPR		Feb 23 2000 12:00AM	C-MSS-75220	The MSS Accountability Service shall support the request states of 'Awaiting DAR Results' and 'Awaiting More DAR Results'.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504MS	Attached DPR		Feb 23 2000 12:00AM	C-MSS-75230	The MSS Accountability Service GUI shall allow operators to list the on-demand standing processing orders, and display the associated DAR ID and DAR Expiration Time.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504MS	Attached DPR		Feb 23 2000 12:00AM	C-MSS-75240	The MSS Accountability Service shall provide an API for setting the DAR ID and original Order ID in the order tracking information.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504MS	Attached DPR		Feb 23 2000 12:00AM	C-MSS-75250	The MSS Accountability GUI shall display DAR ID and original Order ID along with other order tracking information.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-DPS-27115	The PRONG CI shall handle on-demand orders submitted on behalf of a standing on-demand order like any other on-demand order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05010	The PLANG CI (ODPRM) shall accept a standing on-demand processing order from the ODFRM CI.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05020	The PLANG CI (ODPRM) shall interface with the MSS Accountability Service to create an MSS order and an MSS request for the standing on-demand processing order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05030	The PLANG CI (ODPRM) shall identify the MSS order and MSS request created for an on-demand standing processing order as a 'standing on-demand processing order'.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05040	The PLANG CI (ODPRM) shall record the DAR ID and DAR Expiration in the MSS order tracking information created for a standing on-demand processing order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05050	The PLANG CI (ODPRM) shall initialize the state of the MSS request to 'Awaiting DAR Results' for standing on-demand processing orders.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05060	The PLANG CI (ODPRM) shall store a standing on-demand processing order until it expires.  	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05070	The PLANG CI (ODPRM) shall check whether standing on-demand orders have expired when it checks for the expiration of other on-demand orders. 	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05080	The PLANG CI (ODPRM) shall consider a standing on-demand processing order expired if the current date/time exceeds the DAR expiration date/time by an amount of time configurable by the operator specifically for this purpose. 	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05090	The PLANG CI (ODPRM) shall, upon detecting the expiration of a standing on-demand order, interface with the MSS accountability service to change the state of the request associated with that order to 'Expired'.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05100	The PLANG CI (ODPRM) shall send an e-mail notifying the user of the expiration of a standing on-demand order.  	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05110	The PLANG CI (ODPRM) shall include in the expiration e-mail notice sent to the user for a standing on-demand processing order, the DAR ID and DAR Expiration along with the other information normally sent on expiration of on-demand orders.  	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05120	The PLANG CI (ODPRM) shall remove an expired standing on-demand processing order from its database in accordance with the operator configuration setting for keeping expired on-demand orders in general. 	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05130	The PLANG CI (ODPRM) shall, upon receipt of a standard L1B product in response to a DAR, submit to itself an order for all on-demand higher-level processing that uses the L1B as input for standing on-demand processing order(s), except those that are cancelled or expired.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05145	The PLANG CI (ODPRM) shall, after receiving the first granule associated with the standing on-demand order, change the state of the corresponding MSS request to 'Awaiting More DAR Results'.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05150	The PLANG CI (ODPRM) shall, when submitting an order on behalf of a standing on-demand processing order, use information kept in the standing order as the source for the necessary ordering inputs.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05160	The PLANG CI (ODPRM) shall, when submitting an order on behalf of a standing on-demand processing order, include DAR ID, DAR Expiration, and original Order ID in the order information.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05170	The PLANG CI (ODPRM) shall be able to accept DAR ID, DAR Expiration, and original Order ID on orders submitted on behalf of a standing order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05180	The PLANG CI (ODPRM) shall include DAR ID and original Order ID in the MSS order tracking information created for orders that were submitted on behalf of a standing order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05190	The PLANG CI (ODPRM) shall, for queuing and dispatching purposes, consider orders generated from a standing on-demand processing order as having been submitted at the time they were generated. 	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05200	The PLANG CI (ODPRM) shall notify the user via e-mail when accepting the submission of an order on behalf of a standing order.	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05210	The PLANG CI (ODPRM) shall add the following information to the standard confirmation e-mail sent when accepting the submission of an order on behalf of a standing order:    1. original DAR ID  2. DAR Expiration Time  3. order ID of the standing on-demand order  4. input granule UR  	
RM_6A_07	EDC processing DPR Attached to a DAR	10504PL	Attached DPR		Feb 23 2000 12:00AM	S-PLS-05220	The PLANG CI (ODPRM) shall handle on-demand orders submitted on behalf of a standing on-demand order like any other on-demand order.	
RM_6A_08	Landsat-7 Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-06715	The SDSRV CI  command line tool for flagging unmerged L7 F1 and F2 granules as deleted from the archive via the command line, shall provide an option that gives operators the ability to request the physical deletion of the granules, without attempting to also delete associated BROWSE, PH, and QA granules.	
RM_6A_08	Landsat-7 Granule Deletion	12508II	Granule Deletion Administration	The SDSRV has to provide a mechanism for operators to delete data products.  This should be performed through a SDSRV command line utility	Dec 21 1999 12:00AM	S-DSS-06716	The SDSRV CI shall treat a request for physical deletion of L7 F1 and F2 granules in the same way as it treats that for other granules, i.e., make the granule inacessible for normal searching, and eventually allow its removal form the inventory and archive via the deletion clean-up utility.	
RM_6A_09	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-CSS-30635	The ECS Registry shall permit the configuration of generic media options.	
RM_6A_09	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-CSS-30636	The ECS Registry shall support the configuration of media options for specific servers.  For example, it must be possible to configure media options specifically for the ODFRM CI, and differently for different instances of MTMGW CI servers.	
RM_6A_09	Integration of the EDC Product Distribution System (PDS) with ECS	03504DI	PDS Integration	Integration of the EDC Product Distribution System (PDS) with ECS	Dec 19 2000 12:00AM	S-CSS-30637	The ECS Registry shall retrieve the media options that have been configured for the requesting ECS component; and if none have been specifically configured for that component, the generic media options.	
RM_6X_01	Firewall	no data				C-ISS-03000	The ISS shall include an ECS Firewall at each DAAC and the SMC isolating the ECS LAN from all external networks.	
RM_6X_01	Firewall	no data				C-ISS-03005	The ECS Firewall shall provide network address translation to permit the configuration of a private address space for the ECS LAN.	
RM_6X_01	Firewall	no data				C-ISS-03010	The ECS Firewall shall deny all network services not explicitly configured as permitted.	
RM_6X_01	Firewall	no data				C-ISS-03020	The ECS Firewall shall be configurable to permit incoming tcp/ip socket connections on specific sockets and from specific ip addresses to support tcp/ip message traffic with external systems, for example, to perform network ingest (such as required for Landsat) and accept data and user profile requests (such as required for EDG, ASTER GDS, DORRAN, and the Landsat Level 1 processing system).	
RM_6X_01	Firewall	no data				C-ISS-03030	The ECS Firewall shall be configurable to permit outgoing tcp/ip socket connections to support tcp/ip message traffic with remote systems, such as required for sending acknowledgment and notices to LPS, DAR to the ASTER GDS, and requests and responses to external systems such as EDG, ASTER GDS,  and DORRAN.	
RM_6X_01	Firewall	no data				C-ISS-03040	The ECS Firewall shall be configurable to permit incoming ftp connections from specific external ip addresses for ftp ingest, such as required for EDOS.	
RM_6X_01	Firewall	no data				C-ISS-03050	The ECS Firewall shall be configurable to permit incoming ftp connections to the ftp Pull area, such as required for ftp pull distributions.	
RM_6X_01	Firewall	no data				C-ISS-03060	The ECS Firewall shall be configurable to permit outgoing ftp connections for FTP Pull, such as needed by polling FTP ingest from external data providers, SIPS, and cross-DAAC data transfers.	
RM_6X_01	Firewall	no data				C-ISS-03070	The ECS Firewall shall be configurable to permit outgoing ftp connections for FTP Push, such as needed for FTP Push to external users, SIPS, and for cross-DAAC data transfers.	
RM_6X_01	Firewall	no data				C-ISS-03075	The ECS Firewall shall be configurable to permit outgoing anonymous ftp connections, such as needed to obtain a new leap second file from the US Naval Observatory.	
RM_6X_01	Firewall	no data				C-ISS-03080	The ECS Firewall shall be configurable to provide a store-and-forward service supporting outgoing e-mail traffic, such as needed for ECS Subscription Notices, Distribution Notices, and Expedited Data Notices.	
RM_6X_01	Firewall	no data				C-ISS-03090	The ECS Firewall shall be configurable to provide a store-and-forward service supporting incoming e-mail traffic, such as needed for ECS Subscription Requests, ECS Distribution Notices for cross-DAAC ingest and Expedited Data Requests from GDS.	
RM_6X_01	Firewall	no data				C-ISS-03100	The ECS Firewall shall be configurable to permit incoming secure shell connections from specific external ip addresses, such as needed for M&O remote login and the machine-to-machine gateway interactions.	
RM_6X_01	Firewall	no data				C-ISS-03110	The ECS Firewall shall be configurable to permit connection of ECS ntp servers to an external time provider.	
RM_6X_01	Firewall	no data				C-ISS-03120	The ECS Firewall shall be configurable to permit Sybase replication, such as needed for user profile synchronization among the DAAC and SMC.	
RM_6X_01	Firewall	no data				C-ISS-03130	The ECS Firewall shall be configurable to permit incoming web access via Http and sockets to ECS web services, such as ASTER DAR queries and submissions for the JDT.	
RM_6X_01	Firewall	no data				C-ISS-03135	The ECS Firewall shall be configurable to permit outgoing web access via http from individual platforms or subnetworks inside the firewall.	
RM_6X_01	Firewall	no data				C-ISS-03140	The ECS Firewall shall be configurable to permit DNS look up and exchange traffic. 	
RM_6X_01	Firewall	no data				C-ISS-03150	The ECS Firewall shall support connectivity via 10/100 and gigabit Ethernet.	
RM_6X_01	Firewall	no data				C-ISS-03160	The ECS Firewall shall support connectivity via FDDI.	
RM_6X_01	Firewall	no data				C-ISS-03170	The ECS Firewall shall support connectivity via HiPPI.	
RS_6A_05	Archive Improvements	13000ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Provide raw data about data access and staging activity to allow for better loading of the system.  Types of data collected would be the number of bytes archived per volume group, the number of flies archived per volume group, the number of files retrieved per volume group, the number of bytes retrieved, the frequency of volume group switching (tape switching), the number of staging disks created per instance of staging, the number of bytes transferred to the staging, etc.	Aug 11 1999 12:00AM	S-DSS-20036	The STMGT CI shall log events associated with staging activity and the allocation of staging resources.	
RS_6A_05	Archive Improvements	13000ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Provide raw data about data access and staging activity to allow for better loading of the system.  Types of data collected would be the number of bytes archived per volume group, the number of flies archived per volume group, the number of files retrieved per volume group, the number of bytes retrieved, the frequency of volume group switching (tape switching), the number of staging disks created per instance of staging, the number of bytes transferred to the staging, etc.	Aug 11 1999 12:00AM	S-DSS-20045	The STMGT CI shall log, to the Event Log, the successful completion of requests to retrieve data files from the archive.	
RS_6A_05	Archive Improvements	13000ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Provide raw data about data access and staging activity to allow for better loading of the system.  Types of data collected would be the number of bytes archived per volume group, the number of flies archived per volume group, the number of files retrieved per volume group, the number of bytes retrieved, the frequency of volume group switching (tape switching), the number of staging disks created per instance of staging, the number of bytes transferred to the staging, etc.	Aug 11 1999 12:00AM	S-DSS-20570	The STMGT CI shall permit operators to view the progress and throughput of copy operations that are in progress.	
RS_6A_05	Archive Improvements	13000ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Provide raw data about data access and staging activity to allow for better loading of the system.  Types of data collected would be the number of bytes archived per volume group, the number of flies archived per volume group, the number of files retrieved per volume group, the number of bytes retrieved, the frequency of volume group switching (tape switching), the number of staging disks created per instance of staging, the number of bytes transferred to the staging, etc.	Aug 11 1999 12:00AM	S-DSS-20580	The STMGT CI shall provide information on the progress of a copy operation.	
RS_6A_05	Archive Improvements	13000ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Provide raw data about data access and staging activity to allow for better loading of the system.  Types of data collected would be the number of bytes archived per volume group, the number of flies archived per volume group, the number of files retrieved per volume group, the number of bytes retrieved, the frequency of volume group switching (tape switching), the number of staging disks created per instance of staging, the number of bytes transferred to the staging, etc.	Aug 11 1999 12:00AM	S-DSS-20680	The STMGT CI shall maintain a log of files which have been accessed including time stamp and request ID for each access.	
RS_6A_05	Archive Improvements	13000ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Provide raw data about data access and staging activity to allow for better loading of the system.  Types of data collected would be the number of bytes archived per volume group, the number of flies archived per volume group, the number of files retrieved per volume group, the number of bytes retrieved, the frequency of volume group switching (tape switching), the number of staging disks created per instance of staging, the number of bytes transferred to the staging, etc.	Aug 11 1999 12:00AM	S-DSS-30165	The DDIST CI shall log the occurrence of the cancellation of a Data Request in the Event Log.	
RS_6A_05	Archive Improvements	13001ST	Logical Archive ID (Allows archived data to be reallocated for load balancing/failure recovery without impacting inventory DB)	Allows the complete separation of location stored by SDSRV from the physical location of the file in an archive.  This will allow data to be moved between instances of the archive for fault handling, load balancing, and archive upgrades.  Uses the Request Manager	Jan 17 2000 12:00AM	S-DSS-20130	The STMGT CI shall provide operations staff the capability to manually dismount archive media from archive storage devices.	
RS_6A_05	Archive Improvements	13001ST	Logical Archive ID (Allows archived data to be reallocated for load balancing/failure recovery without impacting inventory DB)	Allows the complete separation of location stored by SDSRV from the physical location of the file in an archive.  This will allow data to be moved between instances of the archive for fault handling, load balancing, and archive upgrades.  Uses the Request Manager	Jan 17 2000 12:00AM	S-DSS-20140	The STMGT CI shall provide operations staff the capability to manually mount archive media into archive storage devices.	
RS_6A_05	Archive Improvements	13001ST	Logical Archive ID (Allows archived data to be reallocated for load balancing/failure recovery without impacting inventory DB)	Allows the complete separation of location stored by SDSRV from the physical location of the file in an archive.  This will allow data to be moved between instances of the archive for fault handling, load balancing, and archive upgrades.  Uses the Request Manager	Jan 17 2000 12:00AM	S-DSS-20365	The STMGT CI shall store each data file in the location specified by the Logical File Location provided by the SDSRV CI.	
RS_6A_05	Archive Improvements	13001ST	Logical Archive ID (Allows archived data to be reallocated for load balancing/failure recovery without impacting inventory DB)	Allows the complete separation of location stored by SDSRV from the physical location of the file in an archive.  This will allow data to be moved between instances of the archive for fault handling, load balancing, and archive upgrades.  Uses the Request Manager	Jan 17 2000 12:00AM	S-DSS-20810	The STMGT CI shall provide the operations staff the capability to change the correspondence between an Archive ID, which is assigned to one or more data types, and the physical storage location associated with that Archive ID.	
RS_6A_05	Archive Improvements	13001ST	Logical Archive ID (Allows archived data to be reallocated for load balancing/failure recovery without impacting inventory DB)	Allows the complete separation of location stored by SDSRV from the physical location of the file in an archive.  This will allow data to be moved between instances of the archive for fault handling, load balancing, and archive upgrades.  Uses the Request Manager	Jan 17 2000 12:00AM	S-DSS-21390	The STMGT CI shall maintain the one-to-one correspondence between the Logical File Location for each archived file and the physical location of the file.	
RS_6A_05	Archive Improvements	13002ST	STMGT Request Manager (needed for multi-host scheduling, parallel AMASS I/O, Logical Archive Id) -- moved from 6A	Allows the STMGT client code to checkpoint requests directly to a database.  Permit servers to handle requests within  a fixed number of threads.  Needed for multi-host scheduling, parallel AMASS I/O, and Logical Archive Id.	Aug 11 1999 12:00AM	S-DSS-20011	The STMGT CI shall perform reads and writes to the archive concurrently for each request.	
RS_6A_05	Archive Improvements	13002ST	STMGT Request Manager (needed for multi-host scheduling, parallel AMASS I/O, Logical Archive Id) -- moved from 6A	Allows the STMGT client code to checkpoint requests directly to a database.  Permit servers to handle requests within  a fixed number of threads.  Needed for multi-host scheduling, parallel AMASS I/O, and Logical Archive Id.	Aug 11 1999 12:00AM	S-DSS-20012	The STMGT CI shall permit only a configurable number of files to be written into or read from the archive at the same time.	
RS_6A_05	Archive Improvements	13002ST	STMGT Request Manager (needed for multi-host scheduling, parallel AMASS I/O, Logical Archive Id) -- moved from 6A	Allows the STMGT client code to checkpoint requests directly to a database.  Permit servers to handle requests within  a fixed number of threads.  Needed for multi-host scheduling, parallel AMASS I/O, and Logical Archive Id.	Aug 11 1999 12:00AM	S-DSS-20810	The STMGT CI shall provide the operations staff the capability to change the correspondence between an Archive ID, which is assigned to one or more data types, and the physical storage location associated with that Archive ID.	
RS_6A_05	Archive Improvements	13002ST	STMGT Request Manager (needed for multi-host scheduling, parallel AMASS I/O, Logical Archive Id) -- moved from 6A	Allows the STMGT client code to checkpoint requests directly to a database.  Permit servers to handle requests within  a fixed number of threads.  Needed for multi-host scheduling, parallel AMASS I/O, and Logical Archive Id.	Aug 11 1999 12:00AM	S-DSS-21274	The STMGT CI shall provide operations staff with the ability to display information on queued requests for storage management resources, including request identification, requestor, status, and priority.	
RS_6A_05	Archive Improvements	13003ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Replaces the current scheduling of devices for a given server to use the request manager.  Moves the scheduling logic forward in the processing, allows for retrieval of some information needed for the distribution prior to connecting to a server, and allows for multiple media servers to collaborate in the fulfillment of distribution requests.  Allows both fault recovery and failover.	Aug 11 1999 12:00AM	S-DSS-20550	The STMGT CI shall provide operations staff a mechanism to display/view storage system configuration parameters which affect storage system performance.	
RS_6A_05	Archive Improvements	13004ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Changes the way that STMGT interacts with the Archive from sequential within a request to concurrent accesses for files in a single request.  Uses the Request Manager and Logical Archive Id.	Aug 11 1999 12:00AM	S-DSS-20011	The STMGT CI shall perform reads and writes to the archive concurrently for each request.	
RS_6A_05	Archive Improvements	13004ST	Performance enhancements (e.g., improved inventory search performance, frequency-based archive cache management, improved peripheral scheduling) needed to support distributed and reprocessing)  SDSRV Enhancements, Request Priority, Parallel AMASS I/O, multi-server scheduling.	Changes the way that STMGT interacts with the Archive from sequential within a request to concurrent accesses for files in a single request.  Uses the Request Manager and Logical Archive Id.	Aug 11 1999 12:00AM	S-DSS-20012	The STMGT CI shall permit only a configurable number of files to be written into or read from the archive at the same time.	
RS_6A_05	Archive Improvements	no data				S-DSS-30265	The DDIST CI shall maintain a log of distribution requests which include the following:  1. the request and order id  2. the type of distribution  3. the time the request was received  4. the time the request started  5. the time acquiring data started and ended  6. the time that the request was completed	
RS_6A_05	Archive Improvements	no data				S-DSS-30270	The DDIST CI shall log, to the Event Log, the User Identifier, Data Product(s) Identifiers, Data Destination, and Media Identifiers associated with a completed Media Distribution Request.	
RS_6A_05	Archive Improvements	no data				S-DSS-30275	The DDIST CI shall log, to the Event Log, failures to successfully complete Media Distribution Requests due to failures with media or media recording devices.	
RS_6A_05	Archive Improvements	no data				S-DSS-30280	The DDIST CI shall log, to the Event Log, the User Identifier, the Data Product(s) Identifiers, and Data Destination associated with a completed Electronic Distribution Request.	
RS_6A_05	Archive Improvements	no data				S-DSS-30420	The DDIST CI shall have the capability to log, to the Event Log, the start of the processing of each Data Distribution Request.	
RS_6A_05	Archive Improvements	no data				S-DSS-30425	The DDIST CI shall have the capability to log, to the Event Log, the completion of the processing of each Data Distribution Request.	
RS_6A_05	Archive Improvements	no data				S-DSS-30431	The DDIST CI shall log, to the Event Log, changes in the status of the shipment of media associated with a Media Distribution Request.	
RS_6A_06	Ingest of 6A Data Types	10001IN	Ingest Tailoring For ICESAT Products (equivalent SLOC)	Support for database updates and I/F testing for ICESAT data products.  Assumption is SIPS interface will be utilized and no code changes will be required in Ingest.	Aug 11 1999 12:00AM	S-INS-00541	The INGST CI shall be configured to ingest GLAS data in accordance with the SIPS ICD.	
RS_6A_06	Ingest of 6A Data Types	10011IN	Ingest of MODIS higher-level products from the MODAPS system		Apr  4 2000 12:00AM	S-INS-00543	The INGST CI shall be configured to ingest PM-1 MODAPS data in accordance with the SIPS ICD.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-DSS-01866	The SDSRV CI shall accept secure copy as a valid electronic media type in its acquire requests.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-DSS-01868	The SDSRV CI shall direct the DDIST CI to transmit data and metadata electronically, via secure copy, if specified by a valid Electronic Distribution Request.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-DSS-22122	The STMGT CI shall support secure electronic distribution of data.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-DSS-30648	The DDIST CI shall support electronic distribution of data using secure copy in a configurable manner.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-DSS-30649	The DDIST CI shall accept secure copy as a valid electronic media type in its distribution requests.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-DSS-30650	The DDIST CI shall direct the transfer of data to external file systems, via secure copy, as specified by the SDSRV CI.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-OMS-01023	The Order Management Service CI shall process secure copy distribution requests.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-OMS-01024	The Order Management Service CI shall process secure copy distribution requests in Synergy III mode.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-OMS-03631	The Order Management GUI shall not allow an operator to edit a data distribution request whose MSS request tracking status is 'Canceled' or 'Cancelled', 'Aborted' or 'Abort', or 'Shipped' in the following way: a. Change the media type to secure copy	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-SSS-00311	The NBSRV CI shall support a secure copy service for distribution of data.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-SSS-00312	The NBSRV CI shall allow the operator to select secure copy distribution as a distribution action for a subscription.	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-SSS-00321	If secure copy distribution is selected, the NBSRV CI shall require the operator to enter or select values for the following secure copy parameters: (a) userid (b) password (c) host name (d) destination directory name	
SD_A8_01	Secure Distribution of Subscriptions	no data				S-SSS-10126	The NBSRV CI shall allow the operator to select secure copy as a media type for bundling order.	
SM_5B_01	Ingest Operability and New Data Types	00050IN	INS Allow Operator To Cancel/Resume Ingest Requests	Allows operator to Cancel and Resume Ingest requests via the Ingest GUI.  Request Mgr and Granule Server checks cancel commands from the GUI at various points during processing.	Aug 11 1999 12:00AM	S-INS-00350	The INGST CI shall accept an ingest Cancellation Request from authorized operations staff to cancel an ongoing ingest request, specifying the ingest Request Identifier.	
SM_5B_01	Ingest Operability and New Data Types	00050IN	INS Allow Operator To Cancel/Resume Ingest Requests	Allows operator to Cancel and Resume Ingest requests via the Ingest GUI.  Request Mgr and Granule Server checks cancel commands from the GUI at various points during processing.	Aug 11 1999 12:00AM	S-INS-00364	The INGST CI shall set the state of a request to suspended when the number of retries for a retriable error exceeds the maximum number of retries threshold as configured.	
SM_5B_01	Ingest Operability and New Data Types	00050IN	INS Allow Operator To Cancel/Resume Ingest Requests	Allows operator to Cancel and Resume Ingest requests via the Ingest GUI.  Request Mgr and Granule Server checks cancel commands from the GUI at various points during processing.	Aug 11 1999 12:00AM	S-INS-00366	The INGST CI shall accept an ingest Resumption Request from authorized operations staff to resume ongoing ingest request processing or granule processing for a specified "suspended" ingest Request Identifier or Granule Identifier.	
SM_5B_01	Ingest Operability and New Data Types	00211IN	INS Additional Data Types (more DAS, NCEP03)	Database entries to support additional DAS datatype procducts.  Estimate is encapsulated in ESD ???  Assumes no new code to support these products.	Oct  4 1999 12:00AM	S-INS-00548	The INGST CI shall ingest NCEP Surface Flux, into the GSFC DAAC.	
SM_5B_01	Ingest Operability and New Data Types	00211IN	INS Additional Data Types (more DAS, NCEP03)	Database entries to support additional DAS datatype procducts.  Estimate is encapsulated in ESD ???  Assumes no new code to support these products.	Oct  4 1999 12:00AM	S-INS-00620	The INGST CI shall ingest data, provided by the DAO, from the ESN into the LaRC DAAC.	
SM_5B_01	Ingest Operability and New Data Types	10000IN	Ingest Tailoring For PM-1 AMSR Products	Support for database updates for new data products for PM Instruments(AMSR, CERES, MODIS, AIRS).  Assumption is SIPS interface will be utilized and no code changes will be required in Ingest.	Oct  4 1999 12:00AM	S-INS-00540	The INGST CI shall be configured to ingest PM-1 data in accordance with the SIPS ICD.	
SM_5B_01	Ingest Operability and New Data Types	10010IN	Ingest/EMOS Interface		Aug 11 1999 12:00AM	S-INS-00542	The INGST CI shall be configured to ingest EMOS history file data in accordance with the SIPS ICD.	
SM_5B_01	Ingest Operability and New Data Types	10018IN	5B L0 EDOS Ingest	Ingest PM-1 L0 from EDOS	Aug 11 1999 12:00AM	S-INS-00546	The INGST CI shall ingest PM-1 Level 0 data provided by EDOS data, into the GSFC DAAC.	
SM_5B_01	Ingest Operability and New Data Types	10018IN	5B L0 EDOS Ingest	Ingest PM-1 L0 from EDOS	Aug 11 1999 12:00AM	S-INS-00547	The INGST CI shall ingest PM-1 Level 0 data provided by EDOS data, into the LaRC DAAC.	
SM_5B_01	Ingest Operability and New Data Types	10021IN	Ingest AMSR (ADEOS)		Oct  4 1999 12:00AM	S-INS-00549	The INGST CI shall be configured to ingest AMSR ADEOS data in accordance with the SIPS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-00520	The LIMGR CI shall log the failure of a request.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-01010	The LIMGR CI shall log all Service requests initiated during a session.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-31015	The ECS-V0 Component of the GTWAY CI shall log when an external connection to the LPDS has been established.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-31016	The ECS-V0 Component of the GTWAY CI shall log when the component service request has been submitted to the LPDS.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12001DM	V0 Gateway, GDS Gateway, LIM Graceful Shutdown And Logging	Both the ECS-V0, ECS-GDS and GDS-ECS Gateways shall log the following: initiation of a session, termination of a session, server startup, shutdown, activation of a request, when a request has been decomposed, when a connection to an external GDS server has been made, when the service request has been submitted, when the results have been returned, and when all the results have been integrated, when a request has been submitted to the V0 IMS, and when the results have been returned	Aug 11 1999 12:00AM	S-DMS-31017	The ECS-V0 Component of the GTWAY CI shall log when the request to the LPDS has been successfully returned.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-30540	The GTWAY CI shall provide the capability to translate Version 0 system protocols into ECS system protocols defined in the V0/ECS ICD and LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12004DM	V0 Gateway Enhancements to support (core metadata, PSAs, integrated browse)	The VO ECS Gateway will be modified to be able to accept all ECS ESDT Core & Product Specific attributes (PSA's) as part of an inventory search, and pass them as granule-level attributes search constraints to SDSRV.  The VO ECS Gateway will return the Core & PSA"S and their valids associated with each collection found as part of the inventory search in the inventory results.  The Data Dictionary Maint. tools will have to be modified to include ECS Core and PSA as part of its normal valids export file.  The DDMT will also be modified to create the extend-search Attribute definitions file needed by the VO Client.	Aug 11 1999 12:00AM	S-DMS-30550	The GTWAY CI shall provide the capability to translate ECS system protocols into Version 0 system protocols defined in the V0/ECS ICD and LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-30387	The GTWAY CI shall receive a Price Estimate Request for Landsat 7 Level 0R floating scenes from the V0 Client using protocols defined in the V0/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-30388	The GTWAY CI shall send a Price Estimate Result for Landsat 7 Level 0R floating scenes to the V0 Client using protocols defined in the V0/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-30389	The GTWAY CI shall calculate the Price Estimate for Landsat 7 Level 0R floating scenes.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-30409	The GTWAY CI shall accept Landsat 7 Level 0R floating scene subsetting parameters included in a Product Request from the V0 Client using protocols defined in the V0/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-30412	The GTWAY CI shall send Landsat 7 Level 0R floating scene subsetting parameters included in a Product Request to the SDSRV.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42200	The GTWAY CI shall accept Landsat 7Level 0R BAND subsetting parameters included in a Product Request from the V0 Client using protocols defined in the V0/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42210	The GTWAY CI shall accept Landsat 7 Level 0R non-image subsetting parameters included in a Product Request from the V0 Client using protocols defined in the V0/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42220	The GTWAY CI shall accept Landsat 7 Level 0R floating scene subsetting parameters included in a Product Request from DORRAN, using protocols defined in the LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42230	The GTWAY CI shall accept Landsat 7 Level 0R BAND subsetting parameters included in a Product Request from DORRAN, using protocols defined in the LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42240	The GTWAY CI shall accept Landsat 7 Level 0R non-image subsetting parameters included in a Product Request from DORRAN, using protocols defined in the LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42260	The GTWAY CI shall send Landsat 7 Level 0R BAND subsetting parameters included in a Product Request to the SDSRV.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42270	The GTWAY CI shall send Landsat 7 Level 0R non-image subsetting parameters included in a Product Request to the SDSRV.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42280	The GTWAY CI shall send Landsat 7 Level 0R floating scene subsetting parameters included in a Product Request to DORRAN using protocols defined in the LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42290	The GTWAY CI shall send Landsat 7 Level 0R BAND subsetting parameters included in a Product Request to the DORRAN using protocols defined in the LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DM	Landsat-7 Floating Scene And Band Subsetting	Modify VO-ECS Gateway to be able to accept L7 subsetting parameters from the VO Client as part of a product request and pass them on to SDSRV. The mods to the VO-ECS Gateway will also include its ability to accept a new price Estimate messgae from the VO Client, which in turn will pass the request into a SDSRV I/F used to calculate the price of L7 scences.	Aug 11 1999 12:00AM	S-DMS-42300	The GTWAY CI shall send Landsat 7 Level 0R non-image subsetting parameters included in a Product Request to the DORRAN using protocols defined in the LPDS/ECS ICD.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-DSS-02901	The SDSRV CI shall provide the capability to subset data within a Landsat subinterval granule based on floating scenes.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-DSS-02910	The SDSRV shall accept from the GTWAY CI subsetting requests with Spatial and Parameter constraints.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-DSS-02911	The SDSRV CI shall be able to perform Floating scene Subsetting  for  products of  between 0.5 & 37 scenes.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-DSS-02913	The SDSRV CI shall  calculate the start and stop scanlines for floating scene subsets	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-DSS-02914	The SDSRV CI HDF-EOS Server shall accept and pass on  scanline delimited subsetting requests .	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-DSS-02917	The SDSRV HDF-Server shall interpolate floating scene data by corner points.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12500DT	Landsat-7 Floating Scene And Band Subsetting	newsdsrv3; Redesign Floating Scene Subsetting based on new input and output formats, specifications. ; Calculate number of scenes that would be produced for a given subsetting scenario.	Aug 11 1999 12:00AM	S-TKS-00288	The SDP Toolkit HDF-EOS Library shall accept and process scanline delimited Swath subsetting requests from the SDSRV HDF-EOS Server.	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12512DT	Landsat-7 Band Subsetting		Aug 11 1999 12:00AM	S-DSS-02912	The SDSRV CI shall be able to perform Band scene Subsetting  for  products between  scenes and  from 0 to 9 bands	
SM_5B_02	Landsat-7 Floating Scene Subsetting Cancelled per Contract Mod 25	12512DT	Landsat-7 Band Subsetting		Aug 11 1999 12:00AM	S-DSS-02916	The SDSRV HDF-Server Landsat reformatter shall perform L70R band reformatting on band data.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06701	The SDSRV CI shall provide a command line tool for generating a formatted ASCII text file listing the unmerged granules from the L70RF1 & L70RF2 collections for an operator-provided granule insert time range.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06702	The SDSRV CI shall provide a command line tool for generating a formatted ASCII text file listing the un-merged granules from the L70WRS1 and L70WRS2 collections for an operator-provided granule insert time range.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06703	The SDSRV CI shall include the Landsat base file name, format type, start time, and path/row information in the list of un-merged granules, and sort the list by Landsat base file name (descending), row (ascending), and format type.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06704	The SDSRV CI command line tool for merging and promoting Landsat L70RF1 and L70RF2 granules shall accept as input an ASCII text file formatted in accordance with the un-merged F1/F2 granule listing.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06705	The SDSRV CI command line tool for merging Landsat L70WRS1 and L70WRS2 granules shall accept as input an ASCII text file formatted in accordance with the un-merged WRS1/WRS2 granule listing.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06706	The SDSRV CI shall require operator confirmation for all granule deletions.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06707	The SDSRV CI shall perform all merge, de-merge, promote and delete operations in a way that preserves internal SDSRV database consistency.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06708	The SDSRV CI shall provide a command line tool to initiate the merging of L70RF1 and L70RF2 granules and their child WRS granules.  	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06709	The SDSRV CI shall provide a command line tool to initiate the merging of L70RWRS1 and L70RWRS2 granules.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06711	The SDSRV CI shall provide a command line tool to demerge individual L70R granules into component L70RF1 and L70RF2 child WRS granules in the process.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06712	The SDRSV CI shall provide a command line tool to promote "orphaned"  L70RF1 or L70RF2 granules (both subinterval and scenes) to the L70R and L70RWRS collections.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06713	The SDRSV shall be able to flag unmerged L7 F1 and F2 granules as deleted from the archive via the command line.	
SM_5B_03	Landsat-7 Error Handling Cancelled per Contract Mod 25	12503DT	Landsat-7 F1/F2 Error Handling	The SDSRV must provide a capability to detect, handle and cleanup Format 1/2 granules with a missing "partner" granule.	Aug 11 1999 12:00AM	S-DSS-06714	The SDRSV shall be able to flag unmerged L7 F1 and F2 WRS granules as deleted from the archive via the command line.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19104	The WKBCH CI DAR Tool shall have the capability to receive DARs  from the ASTER  GDS and incorporate the parameters in new ASTER DARs.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19106	The WKBCH CI DART shall have the capability to receive product status information from ASTER GDS.   	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19108	The WKBCH CI DART shall have the capability to submit DAR queries, receive query responses from the ASTER GDS database using calls contained in the ASTER-GDS IMS API, and display the results to the user.  	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19127	The WKBCH CI DAR Tool shall allow an ECS user to display the results of xAR Searches on spatial and textual-based displays.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19139	The WKBCH CI DAR Tool spatial display shall provide the capability to display the following information during the display of xAR Search results:  a) areas of interest with xAR ID  b) terminator crossings  c) equator and other major latitude crossings  d) display of successfully observed scenes with cloud cover by quadrant (in association with the Area of Interest (AOI) polygon).  	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19142	The WKBCH CI DAR TOOL shall provide messages to users of the current state of each user request (DAR search), while waiting for results to be returned from ASTER-GDS.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19174	The WKBCH CI DAR Tool shall have the capability to copy DAR configuration parameters from a DAR retrieved by a search of the ASTER GDS xAR database into a new set of DAR configuration parameters.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19176	The WKBCH CI DAR Tool shall allow the user to delete:  1) a xAR search  2) xAR search results.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19194	The WKBCH CI DAR Tool spatial map shall support the following DAR Tool functions:  a) spatial selection for DAR AOI creation  b) xAR Status AOI/AOS viewing  c) xAR Status Acquired Scenes viewing  	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19198	The WKBCH CI DAR Tool spatial selection function shall support the graphical and textual selection of a minimum bounding rectangle AOS to be used as part of a xAR Search.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19201	The WKBCH CI DAR Tool spatial selection function shall support a minimum bounding rectangle selection on the spatial map by defining a latitude/longitude box to be used as part of a xAR Search.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19204	The WKBCH CI DAR Tool spatial selection function shall allow users to delete AOIs drawn by them on a map prior to their addition to a DAR or xAR search.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19205	The WKBCH CI shall convert the MOJO Gateway  messages into information/data for user display.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19234	The WKBCH CI DAR Tool xAR Status function shall allow the user to highlight or hide a xAR geographic AOI within the viewing window.  	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19236	The WKBCH CI DAR Tool xAR Status function shall support the display of xAR acquired scenes overlaid with the xAR AOI.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19238	The WKBCH CI DAR Tool acquired scenes viewing function shall support the display of the following acquired scenes data, at a minimum:  a) xAR ID  b) Maximum acceptable cloud coverage  c) scene ID  d) date observed  e) cloud cover by quadrant (i.e., distinguishing quadrants that meet the cloud cover criteria from those that do not)  f) latitude/logitude coordinates of scenes	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19240	The WKBCH CI DAR Tool xAR status acquired scenes viewing function shall support  the geographic display of the xAR AOI(s) and the acquired scenes on a map of the world.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19241	The WKBCH CI DAR Tool acquired scenes viewing function shall support the highlighting or hiding of acquired scenes within the viewing window.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19242	The WKBCH CI DAR Tool shall synchronize geographic selection criteria for a xAR  Search so that selection of an area on a xAR Search map display is translated into latitude/longitude coordinates in a Search Request submission window.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19244	The WKBCH CI DAR Tool shall synchronize geographic selection criteria for a xAR  Search so that typed latitude/longitude coordinates in a xAR Search Request submission window are graphically displayed as a minimum bounding rectangle on a xAR Search map display.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19246	The WKBCH CI DAR Tool map displays shall provide the following types of geographic data sets for background reference:   1. land/oceans,  2. major lakes and rivers,  3. mountain ranges,  4. volcanoes,   5. major highways and railroads,  6. urban areas, and  7. political boundaries.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19254	The WKBCH CI DAR Tool shall allow the user to select only one value per attribute with a distinct set of values in support of creating a xAR Search.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19256	The WKBCH CI DAR Tool shall allow the user to search for xAR status using either a DAR ID or DAR attributes, but not both, in the same search.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19260	The WKBCH CI DAR Tool shall allow the xAR search results to be sorted by any of  the attributes listed in the xAR search results display.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19262	The WKBCH CI DAR Tool xAR status function shall allow the user to view the following, at a minimum:  a) xAR status  b) xAR temporal and spatial bounds  c) xAR type  d) xAR requestor (user ID)  e) xAR contents  f) xAR AOIs overlaid with the geographical extent of the status search area (AOS   - Area of Search).  g) xAR acquired scenes	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19296	The WKBCH CI DAR Tool shall synchronize time-related data for a xAR Search Request so that selection of a time range on a Search Request timeline tool will be translated into date/time ranges in a Search Request submission window.	
SM_5B_04	Java DAR Tool	03322CL	Java-based DAR Submit/Query Status Tools (enhancements)		Aug 11 1999 12:00AM	S-CLS-19298	The WKBCH CI DAR Tool temporal selection function shall support the textual selection of temporal ranges in support of DAR creation and xAR searches	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DPL-48010	The DPL CI shall retrieve a granule from the volume group history set for re-processing if the beginning date of the granule's temporal coverage is less than the selection date maintained by the STMGT CI [NOTE: The DPL CI shall behave as today if there is only a single volume group history set defined for the ESDT.].	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DPL-48020	The DPL CI shall retrieve a granule from the volume group history set for forward processing if the beginning date of the granule's temporal coverage is greater than or equal to the selection date maintained by the STMGT CI.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71010	The STMGT CI shall optionally support two configurable volume group history sets per ESDT version. [NOTE: This implies that unless a second volume group history set is configured, granule inserts, retrievals, etc. are handled as today.]	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71020	The STMGT CI shall support adding a volume group history set to an existing ESDT version if and only if the collection currently only has one volume group history set, and permit that volume group history set to be designated as the volume group history set for re-processing or forward processing, with the existing volume group history set then automatically taking on the other role. [NOTE: It desirable to verify on this occasion that the collection provides for temporal coverage.]	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71030	The STMGT CI shall support a configurable selection date that is used to determine, on a per granule basis, which volume group history set is used for insert or retrieval. [NOTE: It is desirable to verify that any granules that may be in an existing volume group history set do not become inaccessible as a result of this.]	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71040	The STMGT CI shall insert or retrieve a granule from the  volume group history set for re-processing if the beginning date of the granule's temporal coverage is less than the selection date.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71050	The STMGT CI shall insert or retrieve a granule from the volume group history set for forward processing if the beginning date of the granule's temporal coverage is greater than or equal to the selection date.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71060	The STMGT CI shall permit a null selection date to be configured when an ESDT version is first created.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71070	The STMGT CI shall permit a selection date to be configured to a non-null value only once per ESDT version. [NOTE: It is desirable to prevent this only after the population of the ESDT version has begun.]	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71080	The STMGT CI shall prohibit a selection date from being set to null (implying the removal of one of the two configured volume group history sets) once it has been set to a non-null value.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71090	The STMGT CI shall allow only a single volume group history set to be configured if the selection date is null, and shall require two volume group history sets to be configured if the selection date is not null.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71100	The STMGT CI shall use the appropriate volume group history set when deleting files from the archive.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71105	The STMGT CI shall be able to accommodate multiple volume group history sets when checking the archive against the SDSRV inventory.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71106	The STMGT CI shall require the same number of volume group history sets to be configured for backup and off-site data as for the primary data copies, and apply the same date and selection rules to them as to the primary volume group sets. 	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71110	When archiving the files for a granule, the SDSRV CI shall pass the beginning date of that granule's temporal coverage to the STMGT CI.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71120	When retrieving the files for a granule, the SDSRV CI shall pass the beginning date of that granule's temporal coverage to the STMGT CI [NOTE: This requirement cannot be verified during integration testing since the ESDTs whose files can be accessed directly by the SDSRV have been removed from ECS scope.]	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71125	The SDSRV CI shall, when forwarding files for deletions to the STMGT CI, include the beginning date of the temporal coverage of the granule for each file.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71130	The SDSRV CI shall include the beginning date of the temporal coverage of each granule included in a distribution request to the DDIST CI.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-DSS-71140	When retrieving the files for a granule, the DDIST CI shall pass the beginning date of that granule's temporal coverage to the STMGT CI.	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-OMS-02110	The OMS CI shall assume a granule resides in the volume group history set for re-processing if the beginning date of the granule's temporal coverage is less than the selection date maintained by the STMGT CI or if that selection date is null.  [NOTE: The OMS CI shall behave as today if there is only a single volume group history set defined for the ESDT.]	
VG_70_01	Multiple Volume Group Histories Per Collection Version	no data				S-OMS-02120	The OMS CI shall assume a granule resides in the volume group history set for forward processing if the beginning date of the granule's temporal coverage is greater than or equal to the selection date maintained by the STMGT CI.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06010	The Data Pool web application service shall offer users the following data conversion services for data that is retrieved from the data pool:         HDF-EOS (grid)-to-GeoTiff with reprojection to a user specified output projection         HDF-EOS (swath)-to- GeoTiff, with reprojection to a user specified output projection          [DESIRABLE] spatial subsetting  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06012	The Data Pool web application service shall create and send an email message to the requesting user after receiving each data conversion request from the web application indicating:    a.) The order ID.    b.) time and date of receipt of the order    c.) For each granule processing request in the order:    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1. The request ID    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. the input granule ID    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3. The conversion actions requested by the user  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06020	The Data Pool web application service shall offer users allowable data conversion services for those data collections in the Data Pool that are listed in Appendix A 'HDF-EOS Data Format Converter User's Guide', (170-TP-013-001), January 2002.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06030	The Data Pool web application service data conversion service shall offer the option for granules of selected data types to be converted from HDF-EOS swath or grid format to GeoTiff format.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06040	The Data Pool web application service data conversion service shall offer the option for granules of selected data types to be converted from one projection to any of the following standard projections:     a.) Geographic    b.) Polar Stereographic    c.) Universal Transverse Mercator  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06050	[DESIRABLE] The Data Pool web application service data conversion service shall offer the option for granules of selected data types to be spatially subset by allowing the user to specify opposing corner points, as lat/lon pairs, of the region to be extracted.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06060	The Data Pool web application service data conversion service shall allow the user to specify allowable conversion options for each granule. 	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06070	The Data Pool web application service data conversion service shall allow the user to specify allowable conversion options that may be applied to multiple granules of the same data type.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06080	The Data Pool web application service data conversion service shall receive a mandatory user email address from the user to which the distribution notification will be sent.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06090	The Data Pool web application service data conversion service shall queue  data conversion requests consisting of a user email address, a set of user selected conversion options, including associated granule identification information, for retrieval by the HEG front-end.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06100	[DESIRABLE] The Data Pool web application service shall log all data conversion requests handled, identifying:    [logged information to be defined during design]  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06110	The Data Pool web application service shall return to the user the status of the placement of the request with the HEG front-end, including a meaningful message.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06114	The Data Pool web application service shall create and send an email message to the requesting user for each successful data conversion order indicating:    a.) The order ID    b.) time and date of the order    c.) For each granule conversion in the order:    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1. The request ID    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. the input granule ID for the request    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3. The conversion actions requested by the user    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4. URLs for the converted granule and [DESIRABLE]the XML metadata file of the input granule.    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5. Expiration time for the granules  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-06116	The Data Pool web application service shall create and send an email message to a configured operations email address for each failed data conversion request indicating the input granule ID    a.) Email address of the user placing the order    b.) Order & request identifiers    c.) the input granule ID    d.) time and date of the request    e.) The conversion actions requested by the user    f.) The reason for the failure  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-13500	The Data Pool Cleanup Utility shall provide the capability to cleanup up configurable directories by deleting all files in the directory whose associated order completion time is more than an operator configurable number of hours before the present time and whose completion status is 'passed' or 'failed'.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-DPL-13520	The Data Pool Cleanup Utility shall retrieve from configuration data the latency time that is to be used to determine those files that have resided in distribution directories sufficiently long and should be deleted.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30010	The HEG front-end shall receive data conversion requests from the Data Pool web application service.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30020	The HEG front-end shall retrieve data conversion requests from the queue for each granule for which conversion processing is requested.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30030	The HEG front-end shall process data conversion request information for each granule conversion into a data conversion request file in the format required for input to the HEG Converter.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30050	The HEG front-end shall include a data conversion order ID & request ID in the data conversion request file.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30060	The HEG front-end shall provide the capability to initiate a HEG data conversion process, providing as input to the processing request the data conversion request file.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30070	The HEG front-end shall make available granules required for data conversion to a location that is accessible by the HEG Converter.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30080	The HEG front-end shall limit the number of executing data conversion processes by not initiating new data conversion processes if the number of executing processes exceeds an operator configurable value.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30090	The HEG front-end shall provide the capability to queue a configurable number of processing requests to be dispatched to the HEG converter for processing.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30100	[DESIRABLE - Design decision to be made] The HEG front-end shall limit the number of executing data conversion processes based upon the expected memory and disk usage for a processing request and the operator allowed limits for memory and disk consumption allocated to this processing.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30110	The HEG front-end shall receive data conversion processing results information from a data conversion process when the process terminates.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30120	The HEG front-end shall make available converted files for distribution to the user, via anonymous FTP.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30150	The HEG front-end shall provide a log file that records the following events and associated information:    a. Receipt of  data conversion request: date/time stamp, granule ID    b. Data conversion request to HEG converter: date/time stamp, data conversion request ID    c. Data conversion processing results information received: date/time stamp, data conversion request ID, request processing status.    d. User notification email sent: date/time stamp, data conversion request ID  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30160	The HEG front-end shall provide a capability for operations to:    a.) start processing entries from the processing request queue    b.) stop processing queue entries,     c.) shutdown the HEG front-end without loss of saved queue entries  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30170	The HEG front-end shall provide the capability to display the entries contained in the processing request queue, including orderID and requestID associated with the entries.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30180	The HEG front-end shall, upon receiving a start request, begin processing queued processing requests through the HEG converter, which are ready to be processed.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30190	The HEG front-end shall provide as an option, the ability to be started or initialized in a stopped processing queue condition.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30200	The HEG front-end shall provide the capability for operators to change the state of individual entries in the processing queue.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30210	The HEG front-end shall, when a shutdown request is received, kill all processing being performed by the HEG converter and exit.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30220	The HEG front-end shall, when a stop queue processing request is received, cease to submit processing requests for HEG converter processing.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30230	The HEG front-end shall, when a processing request is determined to have failed during HEG converter processing, change the status of the associated processing request to 'Failed'.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30240	The HEG front-end shall be able to run in any mode.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30250	The HEG front-end shall be able to run concurrently in different modes.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30260	The HEG front-end shall return a status to the Data Pool web interface in response to each data conversion requests received.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30270	[DESIGN ISSUE] The HEG front-end shall, when the processing queue is full, return a status to the Data Pool web interface in response to a received data conversion requests which indicates that the queue is full.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30280	The HEG front-end shall provide the capability to monitor and record the status of each conversion process thread including:    a.) Data Conversion order ID & request ID    b.) The granule ID for the conversion request    c.) The conversion actions requested by the user    d.) the results of the conversion processing (success or failure)    e.) reason for failure (if applicable)    f.) the filename for the converted data granule (one for each file of the granule)  	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30290	The HEG converter shall return processing result information to the HEG front-end so that the results may be sent independent of the availability of the HEG front-end.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30300	The HEG converter shall remove all temporary files used during the data conversion processing at the end of that processing.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30310	The HEG converter shall be able to run in any mode.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30320	The HEG converter shall be able to run concurrently in different modes.	
WD_S3_01	HDF-EOS Format Converter Integration with Data Pool	no data				S-HEG-30330	The Data Pool Maintenance and Monitor GUI shall provide the ability to display if a collection is enabled for HEG processing for each collection that is configured for the Data Pool.	
WD_S3_02	Data Pool Web Drill Down Interface Improvement	no data				S-DPL-05810	The Data Pool Web Access Service shall support bookmarking the current position in the drill down. 	
WD_S3_02	Data Pool Web Drill Down Interface Improvement	no data				S-DPL-05820	The Data Pool Web Access Service shall regenerate a drill down web page based on a bookmark saved by the user by processing the drill down criteria associated with the web page.	
WD_S3_02	Data Pool Web Drill Down Interface Improvement	no data				S-DPL-05865	Upon user selection to download a multi-file granule displayed on the results page, the Data Pool Web Access Service shall allow user to download all granule files associated with the granule in a single download event.    (Note: Current way requires user to download individual files associated with the granule) 	
WD_S3_02	Data Pool Web Drill Down Interface Improvement	no data				S-DPL-05868	The Data Pool Web Access Service shall provide an option for users to download individual granule files associated with a multi-file granule.	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20010	The HEG Tool shall provide the capability to produce the following types of multiple band output files from a format conversion operation on a single object of an HDF-EOS file:      (a) Multi-band GeoTIFF       (b) Band interleaved (BIL) - DESIRABLE      (c) Band sequential format (BSQ) - DESIRABLE	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20015	The HEG Tool shall provide the capability to produce the following types of multiple band output files from a format conversion operation on multiple objects of an HDF-EOS file:  (a) Multi-band GeoTIFF   (b) Band interleaved (BIL) - DESIRABLE  (c) Band sequential format (BSQ) - DESIRABLE	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20020	The HEG Tool shall perform conversion, reprojection, and subsetting operations on 4-dimensional data structures.	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20030	The HEG Tool shall check that the bounding area requested for a spatial subset for a product is contained within the spatial boundaries of the data product selected for subsetting.  	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20040	The HEG tool shall delete the intermediate TIFF file upon completion of a conversion operation. 	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20060	The HEG tool shall delete the intermediate reprojected files upon completion of a subsetting or stitching operation.	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20080	The HEG tool shall provide the capability to cancel an operation in progress. 	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20090	The HEG tool shall run on IRIX 6.5	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20092	The HEG tool shall run on Windows 98.	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20095	The HEG tool shall run on Linux (Red Hat Version 7.2)	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20100	The HEG tool shall apply file name extensions to the resulting converted files, which are consistent with the requested output format.	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20110	The HEG tool shall support requests for spatial sub-sampling of data products. 	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20120	The HEG Tool shall ensure that the output HDF-EOS file reflects the results of a spatial sub-sampling operation in its metadata.   	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20130	The HEG tool shall reproject to the following map projections:  (a) Transverse Mercator   (b) Lambert Azimuthal - DESIRABLE  (c) Lambert Conformal Conic - DESIRABLE  (d) State Plane - DESIRABLE	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20140	The HEG tool shall provide the capability to correct geometric distortion resulting from a stitching operation of multiple MODIS swath objects. - DESIRABLE	
WD_S3_03	HEG Tool Enhancements	no data				S-HEG-20150	The HEG tool shall provide the capability to produce subsampled stack HDFEOS grid products, providing subsampling intervals between every pixel and line and every fifth pixel and line. - DESIRABLE	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-05057	The Web Access Service shall be able to display the spatial distribution of available granules while meeting or exceeding the existing load and response time specification for Synergy III Web Access for collections other than those whose spatial coverage type is 'Not Supported' or 'Global'	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-05155	The Web Access service shall display an indication of the estimated spatial distribution of available granules on a map of the Earth  used for spatial drill down.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72000	The Data Pool shall provide a 'Spatial Transition' utility to populate the existing Data Pool inventory for a given set of collections with spatial  density information for collections other than those whose spatial coverage type is 'Not Supported' or 'Global'	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72010	The 'Spatial Transition' utility will allow DAAC operators to re-compute the density map for a given collection or all collections based on the existing granule tile lists, verify the result against the actual spatial density map, and after logging an error replace the existing spatial density map if it is found to be incorrect.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72015	The Data Pool Spatial Transition utility shall be able to stop and restart without losing track of which granules have been already processed.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72020	The Data Pool Spatial Transition utility shall not take more than one second in processing time per granule.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72025	The Data Pool Maintenance GUI shall disable spatial drill down for a newly defined ECS collection automatically if the search type for the collection is 'Not Supported' and not allow operators to enabled spatial drill down for such collections..	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72030	The Data Pool Maintenance GUI shall initialize the tiling level for a new collection that is enabled for spatial drill down to 6 unless the spatial coverage of the collection is &quot;Orbit&quot;.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72035	The Data Pool Maintenance GUI shall initialize the tiling level for a new collection that is enabled for spatial drill down and whose spatial coverage is &quot;Orbit&quot; to the level recorded with the polygon-tile cross reference..	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72040	The Data Pool Insert Service shall skip the insertion of spatial coverage and the list of granule tiles if the search type for the collection is &quot;Not Supported&quot; or if the Locality Value for a granule is &quot;Global&quot;.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72045	The Data Pool Insert Service shall skip the computation and insertion of the list of granule tiles for collections for which spatial drill down is not enabled.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72050	The Data Pool Insert Service shall fail the insert of a granule with Locality Value &quot;Global&quot; if the spatial drill down for its collection is enabled.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72055	The Data Pool Insert Service shall fail the insert of a granule whose spatial coverage is &quot;Orbit&quot; if the number of tiles in the list of granule tiles exceeds the maximum permitted by the Data Pool database design.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72060	The Data Pool Insert Service shall lower the tiling level for a non-Orbit collection if this becomes necessary to prevent the number of tiles in the list of granule tiles from exceeding the maximum permitted by the Data Pool database design.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72065	The Data Pool Insert Service shall record in the database together with the list of granule tiles the tiling level that was used to compute the list.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72070	The Data Pool Insert Service shall fail the insert of a granule that is &quot;Nearly Global&quot; if its collection is enabled for spatial drill down.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72075	The Data Pool Insert Service shall assume that a granule is &quot;Nearly Global&quot; if the number of tiles covered by the granule exceeds a configurable percentage of the tiles that make up the global grid. [For the percentage applies to all collection, i.e., this is not configurable at a collection level.  The configuration parameter does not have to be settable by the DPM GUI - it is intended more for our use than for DAAC operations.]	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72080	The Data Pool Insert Service shall fail the insert of a granule belonging to a collection whose spatial search type is something other than 'Orbit' or 'Not Supported' and which is not enabled for spatial drill down when the granule's Locality Value is not 'Global' and its granule coverage is not 'Nearly Global'.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72085	The Data Pool Insert Service shall insert the spatial coverage of ECS granules into the appropriate Data Pool table if its spatial coverage exists in ECS and the Locality Value is not 'Global', no matter whether the collection is enabled for spatial drill down or not.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72090	The Data Pool Web Access service shall support user selection of the next search parameter in the drill down sequence from a list of available search parameters.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72095	The Data Pool Web Access Service shall present drill sequence available search parameters according to a configuration file loaded on startup. . Note: Operations staff can modify default drill down sequence to suit DAAC needs (subject to restrictions imposed by S-DPL-72100)	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72100	The Data Pool Web Access Service shall ensure that the list of next available search parameters offered to the user during a drill down follows the rules: 1) Users can start the search only from theme, or data group, or ESDT. 2) The searches of theme and data group are exclusive. 3) Can not go from ESDT to group 4) If a user starts the search with data group, the user should have to continue the search with ESDT 5) Users cannot select spatial search for collections with a 'NotSupported' spatial coverage type. 6) Users cannot select spatial search for collections with a 'Global' spatial coverage type. 7) Users cannot select cloud cover coverage for collections without cloud cover information. 8) Users cannot select timeOfDay for collections with a 24 hours time range 9) Users cannot select day/night flag for collections with inapplicable day/night flag. 10) Users should select an ESDT before s/he selects QAsearch. If no ESDT is selected (such as the search starting from theme) the scienceQA search parameter shall not appear as an option.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72105	The Data Pool Web Access Service shall allow users to override the default drill down sequence and save it for the duration of their session. NOTE: This allows users to override the default sequence given by the DAAC.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72110	The Data Pool Web Access Service shall offer maximum cloud cover expressed as a percentage, as a drill down choice for those collections for which a cloud cover source has been configured.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72115	Data Pool Web Access Service shall be able to sort a result list by cloud cover in ascending order  and do so by default for those ESDTs which have cloud cover source configured when cloud cover is contained in the search	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72120	Data Pool Web Access Service shall make available to the user the cloud cover calculation algorithm description.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72125	The Data Pool Maintenance GUI shall allow operators to configure for each Data Pool collection, the name of the source attribute which contains the cloud cover, the cloud source type ('PSA' or 'core metadata') as well as an optional description of the algorithm used to calculate the percent value. This description  is to be used as reference information.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72130	The Data Pool Maintenance GUI shall allow operators to mark a  Data Pool Collection as having 'global' spatial coverage, thus excluding it from spatial searches.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72135	The Data Pool Maintenance GUI shall allow operators to mark a Data Pool Collection as not having day/Night flag, thus excluding it from day/Night searches.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72140	The Data Pool Maintenance GUI shall allow operators to mark a Data Pool Collection as having 24 hour coverage, thus excluding it from time of day  searches.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72145	The Data Pool configuration information shall default to 'no cloud cover available' for all collections for which the operator has not explicitly configured a source for the cloud cover information.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72150	The Data Pool configuration information shall default to set the dayNight flag to be applicable for all collections	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72155	The Data Pool configuration information shall default to set the spatial coverage type not to be 'Global' for all collections for which spatial coverage is defined.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72160	The Data Pool configuration information shall default to set the temporal coverage type not to be 24hr for all collections for which temporal coverage is defined.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72165	The Data Pool Insert Service shall retrieve the cloud cover information for each granule as configured for this collection and make it available for drill down.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72170	The Data Pool shall provide a 'Cloud Cover Transition' utility to populate the existing Data Pool inventory for a given set of collections with their cloud cover information.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72175	The Data Pool Cloud Cover transition utility shall be able to stop and restart without losing track of which granules have been already processed.	
WD_S4_01	Improve Data Pool Searching	no data				S-DPL-72180	The Data Pool Cloud Cover transition utility shall not take more than one second per granule in processing time	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05910	The Data Pool Web Access service shall obtain granule level information on band availability before offering it for band subsetting.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05915	The Data Pool Web Access service shall support requests for selecting one or more bands from an individual granule.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05920	The Data Pool Web Access service shall support request for selecting one or more bands from an individual granule offered in the results list.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05925	The Data Pool Web Access service shall support requests for selecting one or more bands for an entire cart of granules from a list of bands common to all granules within that cart.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05930	The Data Pool Web Access service shall include all bands for all granules as a default.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05935	The HEG Front End shall accept requests from Data Pool Web Access Service for band subsetting.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05940	The Data Pool Web Access shall submit HEG conversion requests to the HEG Front End that include a) Input File b) Output Projection c) Output Projection input parameters d) Spatial subsetting parameters e) Object names f) Field names g) Band names h) Band value i) 4th Dimension names j) 4th Dimension values k) Output format l) Granule Id	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05950	The Data Pool Web Access shall offer the option for granules of HEG enabled collections to be converted from one projection to any of the following additional standard projections: a) Lambert's Conformal Conic b) Lambert's Azimuthal Equal Area c) State Plane Coordinate System d) Transverse Mercator	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05955	The DataPool WebAccess service shall allow the user to enter input parameters for all projections as applicable both inside (a) and outside the cart(b)	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-05965	The Data Pool Web Access service shall allow arbitrary selection of any of the conversion services available (for example, there will no order dependency between the selection of projection, spatial subsetting and band subsetting.)	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-23900	When inserting granules belonging to collections enabled for HEG band subsetting, the Data Pool Insert Utility shall obtain the band parameter information from the HDF-EOS file and insert it into the Data Pool inventory without increasing the granule insert by more than 5 seconds.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-23910	The Data Pool Insert Utility shall not fail the insertion if the band information extraction yields no bands or an exception, but shall log the event.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-23930	The Data Pool shall provide a utility to populate the existing Data Pool inventory for a given set of collections with their band availability information.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-23940	The Data Pool Band Transition utility shall be able to stop and restart without loosing track of which granules have been already processed.	
WD_S4_02	HEG Integration Enhancements	no data				S-DPL-23950	The Data Pool Band Transition utility shall not take more than one second in processing time per granule.	
WD_S4_02	HEG Integration Enhancements	no data				S-HEG-20135	The HEG Front End shall accept requests from the Web Access Service for the following map projection conversions: a) Lambert's Conformal Conic b) Lambert's Azimuthal Equal Area c) State Plane Coordinate System d) Transverse Mercator	
WD_S4_02	HEG Integration Enhancements	no data				S-HEG-30285	The HEG front-end shall, provide all appropriate processing status updates to the DPL database.	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30110	The BMGT CI shall generate an XML representation of the QA metadata update information.	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30120	The BMGT CI shall use a naming convention for its generated metadata update files that includes a) DAAC idb) Time stamp	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30130	The BMGT shall not generate full granule-level metadata for those granules whose sole reason for export is an update to their QA flags.	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30140	The BMGT CI shall be able to generate the QA metadata update XML file at the rate of 100,000 QA updates per hour on an unloaded system.	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30150	Each ECSMETU product XML file shall conform to a DTD file according to the document 170-WP-023-007 (Appendix A).	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30160	The BMGT CI shall generate Product Delivery Record (PDR) that conforms to the ECS SIPS interface (423-41-57 section 4.5.3). 	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-BGT-30170	The BMGT CI shall generate ECSMETU metadata (.met) files necessary to support the ingest of ECSMETU products via the SIPS interface.	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-DSS-40500	The SDSRV database shall track QA flag updates	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-DSS-40510	ECS shall provide an ESDT (ECSMETU) that shall store products that contain an XML representation of granule-level QA metadata updates.	
WD_S4_03	ECHO Support - QA Metadata Export	no data				S-INS-70010	The Ingest CSCI shall allow ingest of ECSMETU products through the BMGT SIPS interface.	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75710	The DataPool Web Access Home Page shall display a logo containing the name 'DataPool'.	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75720	The DataPool Web Access Home Page shall identify the physical location in the logo (i.e., DataPool @ DAAC)	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75750	The DataPool Web Access Home Page shall support the display of optional NASA and DAAC logos on right and left side of the DataPool logo.	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75760	The DataPool Web Access Home Page shall support the display of DataPool Web Access common links	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75770	The DataPool Web Access Home Page shall support the configuration of common links (show vs. hide, custom url, etc.) where applicable.  The following links shall be configurable and shall have the following configuration options:  'About DataPool' (on/off); 'About the DAAC' (on/off/url); 'Release Notes' (on/off); 'FTP Site' (on/off) The following links are required and may not be changed:  'Glossary', 'Help'.	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75780	The DataPool Web Access Pages shall support the display of a DAAC supplied site header	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75790	The DataPool Web Access Home Page shall support specification of &lt;META&gt; tags	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75800	The DataPool Web Access  Pages shall include display of the DataPool header with the header  elements( menu links).	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75810	The DataPool Web Access Home Page shall include the ability to support DAAC-supplied text.	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75820	The DataPool Web Access Home Page shall include display of the DataPool 'start search' controls and links	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75830	The DataPool Web Access Pages shall include the display of the Datapool Footer	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75840	The DataPool Web Access  footer shall include the EOS Data Gateway link	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75850	The DataPool Web Access footer shall include the Government warning.	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75860	The DataPool Web Access  footer shall support the insertion of DAAC-supplied text between the EDG link and the government warning	
WD_S4_04	DAAC Data Pool Home Page Customization	no data				S-DPL-75870	The DataPool Web Access Home Page shall support the preservation of each DAAC's  baselined customization on subsequent installs.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-BGT-20210	The BMGT CI's Bulk URL Utility shall ignore 'order only' granule URLs when generating XML for granule inserts and deletes.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-BGT-20220	The BMGT CI's Bulk URL Utility shall FTP both insert and delete bulk URL XML files to a configurable FTP location.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-BGT-20230	The BMGT CI's Bulk URL Utility, upon failure to FTP the bulk URL XML files, shall send an email to a configurable email address describing the failure, and a location where the files can be picked up via anonymous FTP.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14010	The DPL Cleanup Utility shall accept a 'pre-delete' command line parameter.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14020	The DPL Cleanup Utility, when receiving a 'pre-delete' parameter, shall make the list of granules it plans to delete available to the Bulk URL Utility.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14030	The DPL Cleanup Utility, when receiving a 'pre-delete' parameter, shall not delete the granules from the Data Pool.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14040	The DPL Cleanup Utility, when receiving a 'pre-delete' parameter, shall call the Bulk URL Utility.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14050	The DPL Cleanup Utility shall accept a 'delete dpl only' command line parameter.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14060	The DPL Cleanup Utility, when receiving a 'delete dpl only' parameter, shall delete the appropriate granules from the Data Pool.	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14070	The DPL Cleanup Utility, when receiving a 'delete dpl only' parameter, shall not call the Bulk URL Utility	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14075	The DPL Cleanup Utility, when receiving a 'delete dpl only' parameter, shall delete the exact same set of granules that it previously made available to the Bulk URL Utility	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14080	The DPL Cleanup Utility shall accept a 'delete all' command line parameter	
WD_S4_05	ECHO Support - Pre-Delete, Order Only and FTP	no data				S-DPL-14090	The DPL Cleanup Utility, when receiving a 'delete all' parameter, shall delete the appropriate granules from the Data Pool and call the Bulk URL Utility	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-DPL-34010	The DPL CI shall allow operators to specify datasets that are accessible via a WMS	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-DPL-34020	The DPL CI shall allow operators to specify datasets that are accessible via a WCS	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-DPL-34030	The DPL CI's Cleanup Utility, when removing granules from the Data Pool, shall cleanup any database entries and remove the GeoTIFF files for those granules specified as accessible via a WMS or WCS	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00010	The OWS CI shall support a Web Mapping Service that conforms to the OGC OWS WMS 1.1.1 specification, http://www.opengis.org/docs/01-068r2.pdf, dated 2001-12-07	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00020	The OWS CI shall support a Web Coverage Service that conforms to the OGC OWS WCS 1.0 Implementation Paper, http://www.opengis.org/docs/03-065r6.pdf, dated 2003-10-16, with the following exceptions:     The WCS will only support WGS 84 Projections     The WCS will only support GeoTIFF and HDF-EOS formats   	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00030	The OWS CI shall support a Coverage Portrayal Service that conforms to the OGC CPS Discussion Paper, http://www.opengis.org/docs/02-019r1.pdf, dated 2002-02-28 	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00040	The OWS CI shall provide a WCS Request Generator that conforms to the OGC WCS 1.0 Implementation Paper with the following exceptions:     The WCS will only support WGS 84 Projections     The WCS will only support GeoTIFF and HDF-EOS formats   	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00050	The OWS CI's Data Conversion Utility shall automatically convert HDF-EOS granules to GeoTIFF	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00055	The OWS CI's Data Conversion Utility shall place the GeoTIFF files in the same directory as their associated HDF-EOS files	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00060	The OWS CI's Data Conversion Utility shall be runnable as a cron job	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00070	The OWS CI's Data Conversion Utility shall convert granules based on their insert time into the Data Pool	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00080	The OWS CI's Data Conversion Utility shall convert granules based on Data Pool themes	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00090	The OWS CI's Data Conversion Utility shall allow operators to specify a time range as an input parameter	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00095	The OWS CI's Data Conversion Utility shall run in 'previous' time mode such that it will run over a previous unit of time (e.g., year, month, day, hour, minute)	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00097	The OWS CI's Data Conversion Utility shall allow operators to specify input times at one minute granularity	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00100	The OWS CI's WMS Update Utility shall add granules to the WMS server configuration when in insert mode	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00110	The OWS CI's WMS Update Utility shall add granules to the WMS server configuration based on granule insert time	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00120	The OWS CI's WMS Update Utility shall add granules to the WMS server configuration based on Data Pool themes	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00130	The OWS CI's WMS Update Utility shall remove granules from the WMS server configuration when those granules are deleted from the Data Pool when in delete mode	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00140	The OWS CI's WMS Update Utility shall allow operators to specify start and stop times as input parameters	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00150	The OWS CI's WMS Update Utility shall run in 'previous' time mode such that it will run over a previous unit of time (e.g., year, month, day, hour, minute)	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00160	The OWS CI's WMS Update Utility shall allow operators to specify input times at one minute granularity	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00170	The OWS CI's WMS Update Utility shall be runnable as a cron job	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00180	The OWS CI's WCS Update Utility shall add granules to the WCS server configuration when in insert mode	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00190	The OWS CI's WCS Update Utility shall add granules to the WCS server configuration based on granule insert time	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00200	The OWS CI's WCS Update Utility shall add granules to the WCS server configuration based Data Pool themes	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00210	The OWS CI's WCS Update Utility shall remove granules from the WCS server configuration when those granules are deleted from the Data Pool when in delete mode	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00220	The OWS CI's WCS Update Utility shall allow operators to specify start and stop times as input parameters	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00230	The OWS CI's WCS Update Utility shall run in 'previous' time mode such that it will run over a previous unit of time (e.g., year, month, day, hour, minute)	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00240	The OWS CI's WCS Update Utility shall allow operators to specify input times at one minute granularity	
WD_S4_06	Earth Science Gateway (ESG) Support Pilot	no data				S-OWS-00250	The OWS CI's WCS Update Utility shall be runnable as a cron job	
WL_S3_02	Bulk Metadata Generator Tool Performance Improvements  THIS TICKET IS OBSOLETE	no data				S-BGT-30010	The BMGT shall extract and convert to XML format science granule metadata from the ECS Science Data Server Database at a rate of at least  25,000  granules per hour, under normal DAAC Operations.	
WL_S3_02	Bulk Metadata Generator Tool Performance Improvements  THIS TICKET IS OBSOLETE	no data				S-BGT-30020	The BMGT shall extract collection level metadata from the ECS Science Data Server Database and convert it to XML format at a rate of  (no more than or 900 an hour under normal DAAC Operations.	
WL_S3_02	Bulk Metadata Generator Tool Performance Improvements  THIS TICKET IS OBSOLETE	no data				S-BGT-30053	The BMGT shall extract browse cross-reference information from the ECS Science Data Server Database and shall convert extracted browse cross-reference information to XML format at a rate of at least 25,000 granules per hour under normal DAAC load