Level 3s mapped to Level 4s Baseline (Historical Data)																							ALL_L3_L4_B
l3.l3_key	l3.l3_id	l3.release	l3.l3_text	l4.l4_key	l4.l4_id	l4.release	l4.l4_text	l3tol4.ccr_no	l3tol4.ccr_date	l3tol4.comment	
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4961	S-DSS-40030	6B	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. 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4962	S-DSS-40040	6B	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. 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4964	S-DSS-40060	6B	The QAMUT CI shall provide a DAAC configurable e-mail address at which the QA update requests are received. 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4965	S-DSS-40065	6B	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. 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4967	S-DSS-40090	6B	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	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4968	S-DSS-40070	6B	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.	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4969	S-DSS-40075	6B	Upon failure in authenticating the request, the QAMUT CI shall send an e-mail notification to the requester indicating authentication failure. 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4970	S-DSS-40077	6B	Upon failure in authenticating the request, the QAMUT CI shall reject the entire request and terminate the processing.	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4971	S-DSS-40080	6B	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. . 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4972	S-DSS-40110	6B	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	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4973	S-DSS-40115	6B	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	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4974	S-DSS-40120	6B	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	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	4975	S-DSS-40125	6B	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. 	02-1061	12/11/2002  		
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	1855	S-DSS-00160	A	The SDSRV CI shall accept and process Update Metadata Requests to update Granule Inventory Metadata that is user-searchable.	99-0729	08/25/1999  	No Data	
25	DADS0010	Complete	The ECS shall receive updated metadata for products that have been QA'd.	1856	S-DSS-00163	B0	The SDSRV CI shall accept and process Update Metadata Requests that request the update of the QA Attributes for specified data granules.	99-0729	08/25/1999  	No Data	
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4959	S-DSS-40010	6B	The QAMUT CI shall be able to update the metadata QA flags and the corresponding explanation fields in the ECS inventory database.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4960	S-DSS-40020	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4961	S-DSS-40030	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4962	S-DSS-40040	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4963	S-DSS-40045	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4976	S-DSS-40130	6B	Operators shall be able to run the QAMUT  CI from the command line.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4977	S-DSS-40140	6B	The QAMUT CI shall provide an operator configurable mode-specific request directory where all QA update request files intended for that mode reside.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4978	S-DSS-40145	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4979	S-DSS-40146	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4980	S-DSS-40147	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4981	S-DSS-40148	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4982	S-DSS-40149	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4983	S-DSS-40150	6B	The QAMUT CI shall validate the command line parameters for correct syntax (format and valid range). 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4984	S-DSS-40160	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4985	S-DSS-40170	6B	The QAMUT CI shall validate the syntax (format and valid range) of the QA Flag values included in the request before performing the updates.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4986	S-DSS-40175	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4987	S-DSS-40176	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4988	S-DSS-40360	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4989	S-DSS-40190	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4990	S-DSS-40200	6B	The QAMUT CI shall, by default, prompt the operator for confirmation before performing the updates.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4991	S-DSS-40205	6B	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. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4992	S-DSS-40210	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4993	S-DSS-40220	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4994	S-DSS-40230	6B	The QAMUT CI shall suppress all operator prompts if the no-prompt option is specified assuming an affirmative response in these cases.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4995	S-DSS-40232	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4996	S-DSS-40233	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4997	S-DSS-40235	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4998	S-DSS-40240	6B	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 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	4999	S-DSS-40250	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5000	S-DSS-40260	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5001	S-DSS-40280	6B	The QAMUT CI shall use a standard name for its log file.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5002	S-DSS-40290	6B	The QAMUT CI shall create a log file if the log file does not already exist.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5003	S-DSS-40300	6B	The QAMUT CI shall append the log messages to the log file if the log file already exists.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5004	S-DSS-40310	6B	The QAMUT CI shall include time stamp and the process ID in all log messages.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5005	S-DSS-40320	6B	The QAMUT CI shall log the name of the request file at the start of processing each request file. 	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5006	S-DSS-40330	6B	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.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5007	S-DSS-40340	6B	The QAMUT CI shall log all warning and error messages encountered during the run.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5008	S-DSS-40350	6B	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  	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5009	S-DSS-40370	6B	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).	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	5010	S-DSS-40390	6B	The QAMUT shall be able to operate in multiple modes concurrently.	02-1061	12/11/2002  		
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	1855	S-DSS-00160	A	The SDSRV CI shall accept and process Update Metadata Requests to update Granule Inventory Metadata that is user-searchable.	99-0729	08/25/1999  	No Data	
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	1856	S-DSS-00163	B0	The SDSRV CI shall accept and process Update Metadata Requests that request the update of the QA Attributes for specified data granules.	99-0729	08/25/1999  	No Data	
26	DADS0020	Complete	The ECS shall, upon receipt of updated metadata for products which have been QA'd, store the metadata in its inventory.	1857	S-DSS-00165	A	The SDSRV CI shall update Granule Inventory Metadata as specified by valid Update Metadata Requests.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	134	S-INS-00546	5B	The INGST CI shall ingest PM-1 Level 0 data provided by EDOS data, into the GSFC DAAC.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	135	S-INS-00547	5B	The INGST CI shall ingest PM-1 Level 0 data provided by EDOS data, into the LaRC DAAC.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2025	S-DSS-03369	B0	The SDSRV CI shall be capable of receiving and managing the storage of Expedited Data from instruments, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2113	S-DSS-05785	B0	The SDSRV CI shall delete Expedited Data 48 hours after it has been received.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2437	S-INS-00010	IR1	The INGST CI shall accept Network Ingest Requests to request automated electronic network ingest of a collection of Data.  The collection of Data shall describe one or more Data Granules.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2438	S-INS-00020	IR1	The INGST CI shall check the Network Ingest Request to verify that the date/time prior to which the data will remain available is a valid date/time.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2442	S-INS-00060	IR1	The INGST CI shall report status to the provider of a Network Ingest Request for the following:  a. File transfer failure  b. File size discrepancies  c. Invalid Data Type Identifier  d. Missing required metadata  e. Metadata parameters out of range  f. Data conversion failure  g. Failure to archive data  h. Inability to transfer data within the specified time window  i. Missing required request information  j. Successful archive of the data	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2443	S-INS-00070	A	The INGST CI shall provide the capability to periodically check a location accessible to the ESN for the presence of a Delivery Record file describing data to be ingested.  The Delivery Record file shall contain the same information as a Network Ingest Request.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2444	S-INS-00080	A	The INGST CI shall read a Delivery Record file describing data to be ingested at a location accessible to the ESN and submit a corresponding Network Ingest Request to be processed.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2447	S-INS-00090	A	The INGST CI shall provide the capability for authorized operations staff to set the period between checking for the presence of Delivery Record files.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2451	S-INS-00130	A	The INGST CI shall interactively accept Hard Media Ingest Requests from operations staff for data to be ingested from hard media.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2452	S-INS-00140	A	The INGST CI shall check the Hard Media Ingest Request to verify that the Media Type is a type supported by the INGST CI.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2453	S-INS-00150	A	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.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2454	S-INS-00160	A	The INGST CI shall authenticate that the Hard Media Ingest Request is input by operations staff authorized to ingest hard media data.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2455	S-INS-00165	A	The INGST CI shall read a Delivery Record file describing data to be ingested to determine the files to be ingested after hard media data transfer.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2456	S-INS-00170	A	The INGST CI shall report Hard Media Ingest Request status to the submitting operations staff for the following:  a.      Media file transfer failure  b.      Invalid Data Type Identifier  c.      Missing required metadata  d.      Metadata parameters out of range  e.      Data conversion failure  f.      Failure to archive data  g.      Missing file describing media data to be ingested  h.      Unauthorized hard media provider  i.      Unauthorized operations staff  j.      Successful archive of data	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2538	S-INS-00580	A	The INGST CI shall ingest Data, provided by the EDOS, into the GSFC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
27	DADS0130	Complete	The ECS shall receive from the EDOS the following:    a. Production data (L0)	2539	S-INS-00590	A	The INGST CI shall ingest Data, provided by the EDOS, into the LaRC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	1842	S-DSS-00075	B0	The SDSRV CI shall accept and process valid, authenticated Data Insert Requests, from any source, via the Data Insert Request API.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2005	S-DSS-03004	B0	The SDSRV CI shall be capable of receiving and managing the storage of Ancillary Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2006	S-DSS-03030	A	The SDSRV CI shall be capable of receiving and managing the storage of Science Software Archive Packages, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2011	S-DSS-03130	A	The SDSRV CI shall be capable of receiving and managing the storage of Instrument Characterization Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2017	S-DSS-03270	A	The SDSRV CI shall be capable of receiving and managing the storage of Scientific Calibration Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2023	S-DSS-03310	B0	The SDSRV CI shall be capable of receiving and managing the storage of correlated data as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2104	S-DSS-05740	B0	The SDSRV CI shall be capable of receiving and managing the storage of Delivered Algorithm Packages, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
29	DADS0140	5A Future	The ECS DAACs shall receive from other ECS DAACs the following:  a. L0-L4 data  b. Metadata  c. Ancillary data  d. Calibration data  e. Correlative data	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	4228	S-INS-00541	6A	The INGST CI shall be configured to ingest GLAS data in accordance with the SIPS ICD.	00-0020	01/10/2000  		
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	4624	S-INS-00600	6B	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   	01-0506A	07/02/2001  		
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	4625	S-INS-00601	6B	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       	01-0506A	07/02/2001  		
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	4626	S-INS-00602	6B	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   	01-0506A	07/02/2001  		
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	4627	S-INS-00603	6B	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  	01-0506A	07/02/2001  		
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	133	S-INS-00540	5B	The INGST CI shall be configured to ingest PM-1 data in accordance with the SIPS ICD.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	1614	S-DPS-40010	IR1	The AITTL CI shall have the capability to receive a Science Software Delivery from the SCF electronically via the network.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2005	S-DSS-03004	B0	The SDSRV CI shall be capable of receiving and managing the storage of Ancillary Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2023	S-DSS-03310	B0	The SDSRV CI shall be capable of receiving and managing the storage of correlated data as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2104	S-DSS-05740	B0	The SDSRV CI shall be capable of receiving and managing the storage of Delivered Algorithm Packages, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2520	S-INS-00408	A	For each data granule specified in an Ingest Request the INGST CI shall determine by means of an Advertisement the appropriate SDSRV CI in which to store the data granule.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2521	S-INS-00409	A	The INGST CI shall provide the capability to request storage of a data granule by means of a Data Insert Request to the SDSRV CI associated with the type of the data granule.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2551	S-INS-00680	A	The INGST CI shall ingest Data, provided by an SCF into the LaRC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2552	S-INS-00682	B0	The INGST CI shall ingest Data, provided by an SCF, from the LAN into the GSFC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2553	S-INS-00684	B1	The INGST CI shall ingest Data, provided by an SCF, from the LAN into the JPL DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2554	S-INS-00686	B0	The INGST CI shall ingest Data, provided by an SCF into the EDC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2555	S-INS-00688	B0	The INGST CI shall ingest Data, provided by an SCF into the NSIDC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2556	S-INS-00690	B0	The INGST CI shall periodically poll a disk directory on the staging server at the SMC to determine the availability of data to be ingested for the SCFs.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2901	C-MSS-18550	B0	The SMC MSS-MHW CI FTP Server shall provide the capability to stage NOAA NESDIS Ancillary data, IAS Calibration data, PDR data from SCF, and EDOS Performance Summary Data into the SMC for a minimum of 30 days.	99-0729	08/25/1999  	No Data	
35	DADS0190	5A 5B Partial	The ECS shall receive from the external processing systems the following:    a. Special products (L1-L4)    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data    f. Science Software    g.  Standard Products (L1-L4) 	2902	C-MSS-18560	B0	The SMC MSS-MHW CI FTP Server shall have the capability to stage NOAA NESDIS Ancillary data, IAS Calibration data, PDR data from SCF, and EDOS Performance Summary Data into the SMC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2222	S-DSS-21374	B0	The STMGT CI shall transfer data from ingest media as directed by the INGST CI.	02-0369	05/08/2002  		
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	4653	S-DSS-21357	EOC	The STMGT CI shall have the capability to transfer data from DTF-2 tape	02-0369	05/08/2002  		
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	4654	S-INS-03111	EOC	Implement Requirement S-INS-03110 	02-0369	05/08/2002  		
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	4655	S-INS-03116	EOC	Implement Requirement S-INS-03115 	02-0369	05/08/2002  		
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	4657	S-DSS-21384	6A	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.	02-0369	05/08/2002  		
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	4658	S-DSS-21386	6A	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.	02-0369	05/08/2002  		
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2005	S-DSS-03004	B0	The SDSRV CI shall be capable of receiving and managing the storage of Ancillary Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2013	S-DSS-03190	B0	The SDSRV CI shall be capable of receiving and managing the storage of Orbit/Attitude Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2023	S-DSS-03310	B0	The SDSRV CI shall be capable of receiving and managing the storage of correlated data as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2104	S-DSS-05740	B0	The SDSRV CI shall be capable of receiving and managing the storage of Delivered Algorithm Packages, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2563	S-INS-00790	B0	The INGST CI shall ingest data, received on physical media from the ASTER GDS, into the EDC DAAC.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2568	S-INS-00850	B0	The INGST CI shall ingest Data, provided by SAGE III, into the LaRC DAAC.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2648	S-INS-61110	B1	The ICLHW CI at the JPL ECS PO.DAAC shall be capable of ingesting RADAR-ALT data from the JPL V0 PO.DAAC at the nominal daily rate specified in the F&PRS Appendix C, Table C-2.	99-0729	08/25/1999  	No Data	
36	DADS0200	Complete	The ECS shall receive from the LP DAAC the following ASTER GDS data:    a. L1A and L1B data products    b. Metadata associated with data sets	2649	S-INS-61140	B0	The ICLHW CI at the LaRC DAAC shall be capable of ingesting data from SAGE III at the nominal daily rate specified in the Daily Level 0 Data Ingest by DAAC Table.  	99-0729	08/25/1999  	No Data	
486	DADS0202	5B	The ECS shall associate ASTER L1B data products to the browse data that is delivered for ASTER L1A data products.	4101	S-DSS-07100	5B	SDSRV CI shall associate the BROWSE granule for an ASTER L1A granule with all ASTER L1B  products derived  from that L1A granule.	99-1006	10/18/1999  		
486	DADS0202	5B	The ECS shall associate ASTER L1B data products to the browse data that is delivered for ASTER L1A data products.	4103	S-DSS-07102	5B	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.	99-1006	10/18/1999  		
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2222	S-DSS-21374	B0	The STMGT CI shall transfer data from ingest media as directed by the INGST CI.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2376	S-DSS-60950	B1	The ACMHW CI at the GSFC DAAC shall be capable of ingesting Version 0 data at the nominal rate specified in Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2377	S-DSS-61010	B1	The ACMHW CI at the LaRC DAAC shall be capable of ingesting Version 0 data by network data transfer at the nominal rate specified in Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2435	S-DSS-90300	B1	The DIPHW CI at the GSFC DAAC shall be capable of ingesting Version 0 data from physical media agreed upon between ECS and Version 0, at the nominal rate specified in Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2436	S-DSS-90320	B1	The DIPHW CI at the LARC DAAC shall be capable of ingesting Version 0 data from physical media agreed upon between ECS and Version 0, at the nominal rate specified in Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2451	S-INS-00130	A	The INGST CI shall interactively accept Hard Media Ingest Requests from operations staff for data to be ingested from hard media.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2452	S-INS-00140	A	The INGST CI shall check the Hard Media Ingest Request to verify that the Media Type is a type supported by the INGST CI.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2455	S-INS-00165	A	The INGST CI shall read a Delivery Record file describing data to be ingested to determine the files to be ingested after hard media data transfer.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2456	S-INS-00170	A	The INGST CI shall report Hard Media Ingest Request status to the submitting operations staff for the following:  a.      Media file transfer failure  b.      Invalid Data Type Identifier  c.      Missing required metadata  d.      Metadata parameters out of range  e.      Data conversion failure  f.      Failure to archive data  g.      Missing file describing media data to be ingested  h.      Unauthorized hard media provider  i.      Unauthorized operations staff  j.      Successful archive of data	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2522	S-INS-00410	A	The INGST CI shall provide the capability to electronically transfer data to be ingested via the ESN into a specified ECS storage location.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2524	S-INS-00415	IR1	The INGST CI shall provide an interim capability to electronically transfer data to be ingested via the ESN into a specified ECS storage location for early interface testing purposes.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2525	S-INS-00420	A	The INGST CI shall provide the capability for an external application to transfer data to be ingested into a specified ECS storage location.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2526	S-INS-00425	A	The INGST CI shall provide the capability to request transfer of data from an 8mm tape.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2528	S-INS-00430	A	The INGST CI shall provide the capability by means of a Working Storage Allocation Request to the Data Server to allocate storage space for data to be transferred to satisfy an ingest request.	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2564	S-INS-00800	A	The INGST CI shall ingest Data, provided by Version 0, from the LaRC DAAC using any of the following media:  a - Electronic using file transfer protocol  b - 4mm tape  c - 8mm tape	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2565	S-INS-00810	A	The INGST CI shall ingest Data, provided by Version 0, from the GSFC DAAC using any of the following media:  a - Electronic using file transfer protocol  b - 4mm tape  c - 8mm tape	99-0729	08/25/1999  	No Data	
40	DADS0250	Complete	The ECS shall receive data in the following forms:    a.  Electronic network communications	2639	S-INS-60900	B0	The INGST CI shall provide the necessary hardware/software to perform scanning and/or digitizing of hardcopy documents for the purpose of inputting documents from authorized users.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	4534	S-INS-00550	5BP	The Ingest CI shall insert to the SDSRV NCEP AVN data in the GRIB format.	00-0750	07/25/2000  		
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	4535	S-INS-00551	5BP	The Ingest CI shall convert NCEP AVN data from the GRIB format in which it is received into the HDF-EOS grid format.	00-0750	07/25/2000  		
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	4536	S-INS-00552	5BP	The Ingest CI shall insert to the SDSRV the NCEP AVN data after conversion to the HDF-EOS format.	00-0750	07/25/2000  		
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	4560	S-INS-00555	5BP	The Ingest CI shall ingest and store to the SDSRV NCEP PREPQC data in the BUFR format into the GSFC DAAC.	00-0817	08/10/2000  		
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	4566	S-INS-00558	6B	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.	00-1040	10/30/2000  		
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2005	S-DSS-03004	B0	The SDSRV CI shall be capable of receiving and managing the storage of Ancillary Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2023	S-DSS-03310	B0	The SDSRV CI shall be capable of receiving and managing the storage of correlated data as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2448	S-INS-00100	IR1	The INGST CI shall provide the capability to periodically check a location accessible to the ESN for the presence of data granule files.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2449	S-INS-00110	IR1	The INGST CI shall submit an Polling Ingest Request after detecting the presence of data granule files in a location accessible to the ESN.  The request shall contain the file location.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2542	S-INS-00620	5B	The INGST CI shall ingest data, provided by the DAO, from the ESN into the LaRC DAAC.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2544	S-INS-00630	IR1	The INGST CI shall ingest data, provided by NESDIS, from the ESN into the LaRC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2547	S-INS-00640	5B	The INGST CI shall ingest data, provided by the DAO, from the ESN into the GSFC DAAC in accordance with the DAO ICD.	99-0729	08/25/1999  	No Data	
41	DADS0260	5B Partial	The ECS shall receive non-EOS correlative and ancillary digital data.	2550	S-INS-00650	B0	The INGST CI shall ingest data, provided by the DAO, into the EDC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2026	S-DSS-03370	B0	The SDSRV CI shall perform consistency and correctness checks for the  metadata, specified in each valid Data Insert Request.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2027	S-DSS-03750	A	The SDSRV CI shall provide a Data Type Description for each data type listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2029	S-DSS-03780	A	The SDSRV CI shall specify the Attributes and associated Valid Values for the data type in each Data Type Description.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2105	S-DSS-05745	B0	The SDSRV CI shall validate metadata, specified by Data Insert Requests, and return a rejection status to the requester if the metadata fails validation.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2519	S-INS-00406	A	The INGST CI shall check selected parameters from extracted metadata to verify:   a.      That all required metadata parameters exist  b.      For numeric metadata parameters limited by a range of values, that parameter values lie within the specified range  c.      For metadata parameters with values limited to a set of discrete values, that parameter values are listed in the specified set  d.      That the metadata parameter syntax is correct  e.      For metadata containing parameters describing the data size, that the data size is correct (within a specified tolerance)  f.      That date / time values include a valid month, day of month, hour, minute, and second  g.      That date / time values include a year value within a range specific for that date / time value	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2531	S-INS-00460	A	The INGST CI shall determine the size of each file transferred to ECS whenever file sizes are specified in the corresponding Ingest Request.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2532	S-INS-00470	A	The INGST CI shall compare the size of each file after data transfer to ECS with file sizes specified in the corresponding Ingest Request.	99-0729	08/25/1999  	No Data	
44	DADS0290	Complete	The ECS shall check all metadata it receives against validation rules (e.g., required fields and groups, valid values) and correctness of the data set granule size (if specified in the metadata).	2533	S-INS-00480	A	The INGST CI shall verify that all files specified in an Ingest Request are successfully transferred to ECS.	99-0729	08/25/1999  	No Data	
45	DADS0300	Partial	The ECS shall generate status information indicating the success or failure of metadata consistency checks.	2026	S-DSS-03370	B0	The SDSRV CI shall perform consistency and correctness checks for the  metadata, specified in each valid Data Insert Request.	99-0729	08/25/1999  	No Data	
45	DADS0300	Partial	The ECS shall generate status information indicating the success or failure of metadata consistency checks.	2105	S-DSS-05745	B0	The SDSRV CI shall validate metadata, specified by Data Insert Requests, and return a rejection status to the requester if the metadata fails validation.	99-0729	08/25/1999  	No Data	
45	DADS0300	Partial	The ECS shall generate status information indicating the success or failure of metadata consistency checks.	2456	S-INS-00170	A	The INGST CI shall report Hard Media Ingest Request status to the submitting operations staff for the following:  a.      Media file transfer failure  b.      Invalid Data Type Identifier  c.      Missing required metadata  d.      Metadata parameters out of range  e.      Data conversion failure  f.      Failure to archive data  g.      Missing file describing media data to be ingested  h.      Unauthorized hard media provider  i.      Unauthorized operations staff  j.      Successful archive of data	99-0729	08/25/1999  	No Data	
45	DADS0300	Partial	The ECS shall generate status information indicating the success or failure of metadata consistency checks.	2466	S-INS-00220	A	The INGST CI shall report status to the interactive submitter of a Network Ingest Request for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Data conversion failure  g.      Failure to archive data  h.      Inability to transfer data within the specified time window  i.      Unauthorized science user  j.      Missing required request information  k.      Successful archive of the data	99-0729	08/25/1999  	No Data	
45	DADS0300	Partial	The ECS shall generate status information indicating the success or failure of metadata consistency checks.	2475	S-INS-00230	A	The INGST CI shall report status to the interactive submitter of a Document Ingest Request for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Data conversion failure  g.      Failure to archive data  h.      Inability to transfer data within the specified time window  i.      Unauthorized science user  j.      Missing required request information  k.      Successful archive of the data	99-0729	08/25/1999  	No Data	
45	DADS0300	Partial	The ECS shall generate status information indicating the success or failure of metadata consistency checks.	2493	S-INS-00340	A	The INGST CI shall report status on processing of an Ingest Request to the Error Log for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Metadata extraction failure  g.      Data conversion failure  h.      Data reformatting failure  i.      Failure to archive data  j.      Inability to transfer data within the specified time window  k.      Missing required request information  l.      Unauthorized Ingest Request submitter  m.      Successful archive of the data	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	1918	S-DSS-00860	A	The SDSRV CI shall inform a client that a requested service is not accessible if the client attempts to access services outside their access level.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2026	S-DSS-03370	B0	The SDSRV CI shall perform consistency and correctness checks for the  metadata, specified in each valid Data Insert Request.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2027	S-DSS-03750	A	The SDSRV CI shall provide a Data Type Description for each data type listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2029	S-DSS-03780	A	The SDSRV CI shall specify the Attributes and associated Valid Values for the data type in each Data Type Description.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2105	S-DSS-05745	B0	The SDSRV CI shall validate metadata, specified by Data Insert Requests, and return a rejection status to the requester if the metadata fails validation.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2106	S-DSS-05750	B0	The SDSRV CI shall reject requests to access ECS data and services that fail authorization.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2439	S-INS-00030	IR1	The INGST CI shall authenticate the provider of a Network Ingest Request as an authorized provider of data to be ingested.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2440	S-INS-00040	IR1	The INGST CI shall report status to the provider of a Network Ingest Request and to the Error Log indicating successful or unsuccessful authentication of the provider as authorized to submit the request.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2453	S-INS-00150	A	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.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2454	S-INS-00160	A	The INGST CI shall authenticate that the Hard Media Ingest Request is input by operations staff authorized to ingest hard media data.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2456	S-INS-00170	A	The INGST CI shall report Hard Media Ingest Request status to the submitting operations staff for the following:  a.      Media file transfer failure  b.      Invalid Data Type Identifier  c.      Missing required metadata  d.      Metadata parameters out of range  e.      Data conversion failure  f.      Failure to archive data  g.      Missing file describing media data to be ingested  h.      Unauthorized hard media provider  i.      Unauthorized operations staff  j.      Successful archive of data	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2457	S-INS-00175	A	The INGST CI shall report Hard Media Ingest Request status to the MSS event log for the following:   a. Unauthorized hard media provider   b. Unauthorized operations staff	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2463	S-INS-00208	A	The INGST CI shall authenticate that the interactive science user entering a Network Ingest Request is authorized to request ingest of data.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2464	S-INS-00209	A	The INGST CI shall report to the Error Log an unauthorized attempt to interactively request ingest of data.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2472	S-INS-00227	A	The INGST CI shall authenticate that the interactive science user entering a Document Ingest Request is authorized to request ingest of data.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2473	S-INS-00228	A	The INGST CI shall report to the Error Log an unauthorized attempt to interactively request ingest of document data.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2482	S-INS-00290	A	The INGST CI shall authenticate the User Identifier of operations staff requesting status on all ongoing Ingest Requests.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2483	S-INS-00295	A	The INGST CI shall return an error status to the requester and log information in the Error Log if status is requested on  ongoing Ingest Requests from an unauthorized requester.	99-0729	08/25/1999  	No Data	
46	DADS0310	Complete	The ECS shall verify that data received came from an approved/authorized source.	2488	S-INS-00317	A	The INGST CI shall authenticate the User Identifier of an application submitting an Ingest Request.	99-0729	08/25/1999  	No Data	
47	DADS0320	Complete	The ECS shall verify compliance of scientist provided data with EOSDIS defined standards for metadata.	2020	S-DSS-03295	B0	The SDSRV CI shall verify that scientist-provided data and metadata, specified by a valid Data Insert Request, complies with ESDIS approved standards for metadata and file content.	99-0729	08/25/1999  	No Data	
47	DADS0320	Complete	The ECS shall verify compliance of scientist provided data with EOSDIS defined standards for metadata.	2514	S-INS-00400	A	The INGST CI shall convert ingested data into an ECS standard format, for following data types:  a. NCEP GRIB formatted final analysis report.  b. NCEP GRIB formatted medium range forecast report.  c. NESDIS Snow/Ice Product in EDR Mastermap format.  d. TOMS Products in version-7 of the TOMS CDROM format.	99-0729	08/25/1999  	No Data	
47	DADS0320	Complete	The ECS shall verify compliance of scientist provided data with EOSDIS defined standards for metadata.	2515	S-INS-00401	B0	The INGST CI shall convert and reformat ingested data into a form accepted by the SDSRV CI.	99-0729	08/25/1999  	No Data	
47	DADS0320	Complete	The ECS shall verify compliance of scientist provided data with EOSDIS defined standards for metadata.	2516	S-INS-00403	B0	The INGST CI shall perform the following metadata conversions:  a.  PB5 time into ECS standard date / time format; b.  Binary integer values into ASCII integer format; c.  Binary floating point values into ASCII floating point format.	99-0729	08/25/1999  	No Data	
47	DADS0320	Complete	The ECS shall verify compliance of scientist provided data with EOSDIS defined standards for metadata.	2517	S-INS-00404	A	The INGST CI shall extract metadata from ingested data into a form accepted by the Science Data Server as needed, for the following categories of data:  a.  Metadata parameters stored by parameter byte order and parameter byte length; b.  Metadata parameters stored in PVL format; c.  Metadata parameters stored in HDF format; d.  Dataset-specific metadata formats	99-0729	08/25/1999  	No Data	
47	DADS0320	Complete	The ECS shall verify compliance of scientist provided data with EOSDIS defined standards for metadata.	2587	S-INS-03103	B0	The INGST CI shall extract metadata from ingested data into a form accepted by the Science Data Server, as needed, for the following categories of data: a. Metadata parameters stored in a data-set-specific format	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	1851	S-DSS-00144	B0	The SDSRV CI shall assign a unique Granule ID to each granule of data stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2039	S-DSS-04021	B0	The SDSRV CI shall store a granule's Granule Inventory Metadata into the Metadata Database when the data file(s) for the granule is successfully stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2064	S-DSS-04515	B0	The SDSRV CI shall assign a unique Logical File Location to each data file specified by a valid Data Insert Request.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2111	S-DSS-05775	B0	The SDSRV CI shall store the checksum, provided by the STMGT CI for each archived file, into the Metadata Database.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2155	S-DSS-20365	6A	The STMGT CI shall store each data file in the location specified by the Logical File Location provided by the SDSRV CI.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2170	S-DSS-20622	A	The STMGT CI shall compute a checksum against each file stored as a result of a storage request, and provide that checksum to the originator of the request.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2492	S-INS-00325	A	The INGST CI shall determine the ingest start/stop dates and times for all ingested data.	99-0729	08/25/1999  	No Data	
48	DADS0350	Complete	The ECS shall generate the following metadata items for each data granule:  a. Unique Granule ID  b. Date and time of storage  c. Physical location   d.  Data check status	2518	S-INS-00405	A	The INGST CI shall append the following ingest-specific metadata to metadata corresponding to ingested data:  a.      Ingest start date and time  b.      Ingest stop date and time  c.      Metadata parameter check status  d.      Total data volume	99-0729	08/25/1999  	No Data	
49	DADS0405	Complete	The ECS shall provide the capability to archive multiple versions of  selected archive data.	9002	S-DPL-08010	7.22	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.]	08-0406	09/11/2008  		
49	DADS0405	Complete	The ECS shall provide the capability to archive multiple versions of  selected archive data.	9003	S-DPL-08020	7.22	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.] 	08-0406	09/11/2008  		
49	DADS0405	Complete	The ECS shall provide the capability to archive multiple versions of  selected archive data.	1843	S-DSS-00085	B1	The SDSRV CI shall provide the capability to manage, and provide access to, multiple versions of Data Products.	99-0729	08/25/1999  	No Data	
50	DADS0425	Complete	Archive and backup media at each ECS DAAC shall have a rated shelf life of at least 10 years as determined by the National Archives and Records Administration (NARA), National Institute for Standards and Technology (NIST), NASA, or a professional or industry organization such as ANSI, the Society of Motion Picture and Television Engineers (SMPTE) or the National Association of Broadcasters (NAB).	2235	S-DSS-21655	A	The DRPHW CI shall utilize media with a rated shelf life of at least 10 years as determined by National Archives and Record Administration (NARA), National Institute for Standards and Technology (NIST), NASA or an industry organization.	99-0729	08/25/1999  	No Data	
1	DADS0430	6A Partial	The ECS shall provide its operations personnel the capability to manually alter the routing of data sets to physical storage locations.	6340	S-DPL-45030	SY4	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.	08-0426	09/29/2008  		
1	DADS0430	6A Partial	The ECS shall provide its operations personnel the capability to manually alter the routing of data sets to physical storage locations.	6352	S-DPL-45110	SY5	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.]	08-0426	09/29/2008  		
1	DADS0430	6A Partial	The ECS shall provide its operations personnel the capability to manually alter the routing of data sets to physical storage locations.	9002	S-DPL-08010	7.22	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.]	08-0406	09/11/2008  		
1	DADS0430	6A Partial	The ECS shall provide its operations personnel the capability to manually alter the routing of data sets to physical storage locations.	1863	S-DSS-00222	B0	The SDSRV CI shall provide the operations staff the capability to assign, for each data type, an Archive ID which maps to a physical storage location for that data type.	99-0729	08/25/1999  	No Data	
1	DADS0430	6A Partial	The ECS shall provide its operations personnel the capability to manually alter the routing of data sets to physical storage locations.	2181	S-DSS-20810	6A	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.	99-0729	08/25/1999  	No Data	
2	DADS0435	Complete	The ECS shall provide its operations personnel the capability to add new physical volumes and eject physical volumes from the archive for off-line or off-site permanent storage.	2140	S-DSS-20095	B0	The STGMT CI shall have the capability to automatically mount archive media into storage devices.	99-0729	08/25/1999  	No Data	
2	DADS0435	Complete	The ECS shall provide its operations personnel the capability to add new physical volumes and eject physical volumes from the archive for off-line or off-site permanent storage.	2141	S-DSS-20110	B1	The DRPHW CI shall provide operations staff the capability to manually insert media into archive storage devices.	99-0729	08/25/1999  	No Data	
2	DADS0435	Complete	The ECS shall provide its operations personnel the capability to add new physical volumes and eject physical volumes from the archive for off-line or off-site permanent storage.	2142	S-DSS-20120	B1	The DRPHW CI shall provide operations staff the capability to manually remove media from archive storage devices.	99-0729	08/25/1999  	No Data	
2	DADS0435	Complete	The ECS shall provide its operations personnel the capability to add new physical volumes and eject physical volumes from the archive for off-line or off-site permanent storage.	2145	S-DSS-20130	6A	The STMGT CI shall provide operations staff the capability to manually dismount archive media from archive storage devices.	99-0729	08/25/1999  	No Data	
2	DADS0435	Complete	The ECS shall provide its operations personnel the capability to add new physical volumes and eject physical volumes from the archive for off-line or off-site permanent storage.	2146	S-DSS-20140	6A	The STMGT CI shall provide operations staff the capability to manually mount archive media into archive storage devices.	99-0729	08/25/1999  	No Data	
2	DADS0435	Complete	The ECS shall provide its operations personnel the capability to add new physical volumes and eject physical volumes from the archive for off-line or off-site permanent storage.	2147	S-DSS-20180	B0	The STMGT CI shall have the capability to automatically dismount archive media from storage devices.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	9002	S-DPL-08010	7.22	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.]	08-0406	09/11/2008  		
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	9003	S-DPL-08020	7.22	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.] 	08-0406	09/11/2008  		
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2005	S-DSS-03004	B0	The SDSRV CI shall be capable of receiving and managing the storage of Ancillary Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2023	S-DSS-03310	B0	The SDSRV CI shall be capable of receiving and managing the storage of correlated data as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2104	S-DSS-05740	B0	The SDSRV CI shall be capable of receiving and managing the storage of Delivered Algorithm Packages, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2219	S-DSS-21365	A	The STMGT CI shall provide storage for the data types listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2517	S-INS-00404	A	The INGST CI shall extract metadata from ingested data into a form accepted by the Science Data Server as needed, for the following categories of data:  a.  Metadata parameters stored by parameter byte order and parameter byte length; b.  Metadata parameters stored in PVL format; c.  Metadata parameters stored in HDF format; d.  Dataset-specific metadata formats	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2520	S-INS-00408	A	For each data granule specified in an Ingest Request the INGST CI shall determine by means of an Advertisement the appropriate SDSRV CI in which to store the data granule.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2521	S-INS-00409	A	The INGST CI shall provide the capability to request storage of a data granule by means of a Data Insert Request to the SDSRV CI associated with the type of the data granule.	99-0729	08/25/1999  	No Data	
3	DADS0440	Complete	The ECS shall provide storage for the following EOS data:  a. Standard Products  b. Associated correlative data sets  c. Associated ancillary data sets  d. Associated calibration data sets  e. Associated metadata  f. Science Software	2588	S-INS-03105	B1	The INGST CI shall extract metadata from ingested data into a form accepted by the Document Data Server, as needed, for the following categories of data:  a.  Metadata parameters stored in a data-set-specific format	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	9002	S-DPL-08010	7.22	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.]	08-0406	09/11/2008  		
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	9003	S-DPL-08020	7.22	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.] 	08-0406	09/11/2008  		
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2219	S-DSS-21365	A	The STMGT CI shall provide storage for the data types listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2520	S-INS-00408	A	For each data granule specified in an Ingest Request the INGST CI shall determine by means of an Advertisement the appropriate SDSRV CI in which to store the data granule.	99-0729	08/25/1999  	No Data	
5	DADS0460	Complete	The ECS shall provide storage for non-EOS data required for Standard Product production.	2521	S-INS-00409	A	The INGST CI shall provide the capability to request storage of a data granule by means of a Data Insert Request to the SDSRV CI associated with the type of the data granule.	99-0729	08/25/1999  	No Data	
7	DADS0472	5A Future	The ECS shall provide the capability to  store and provide access to an average of 4 scenes per day up to a maximum of 10 scenes per day of ASTER Level 1A and 1B expedited data.	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
7	DADS0472	5A Future	The ECS shall provide the capability to  store and provide access to an average of 4 scenes per day up to a maximum of 10 scenes per day of ASTER Level 1A and 1B expedited data.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
7	DADS0472	5A Future	The ECS shall provide the capability to  store and provide access to an average of 4 scenes per day up to a maximum of 10 scenes per day of ASTER Level 1A and 1B expedited data.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
7	DADS0472	5A Future	The ECS shall provide the capability to  store and provide access to an average of 4 scenes per day up to a maximum of 10 scenes per day of ASTER Level 1A and 1B expedited data.	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
7	DADS0472	5A Future	The ECS shall provide the capability to  store and provide access to an average of 4 scenes per day up to a maximum of 10 scenes per day of ASTER Level 1A and 1B expedited data.	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
7	DADS0472	5A Future	The ECS shall provide the capability to  store and provide access to an average of 4 scenes per day up to a maximum of 10 scenes per day of ASTER Level 1A and 1B expedited data.	2265	S-DSS-22230	B0	The STMGT CI shall delete Expedited Data from temporary storage 48 hours after receipt of the data.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	7816	S-DPL-46200	72	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.	08-0426	09/29/2008  		
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	7971	S-DPL-46640	72	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.]	08-0426	09/29/2008  		
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	9002	S-DPL-08010	7.22	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.]	08-0406	09/11/2008  		
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	9003	S-DPL-08020	7.22	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.] 	08-0406	09/11/2008  		
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2109	S-DSS-05765	B0	The SDSRV CI shall reject requests to delete EDOS Level 0 data if no equivalent Level 1A data resides in the archive.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2110	S-DSS-05770	B0	The SDSRV CI shall reject requests to delete Level 1A data, derived from EDOS Level 0 data, if no equivalent Level 1A or EDOS Level 0 data resides in the archive.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2520	S-INS-00408	A	For each data granule specified in an Ingest Request the INGST CI shall determine by means of an Advertisement the appropriate SDSRV CI in which to store the data granule.	99-0729	08/25/1999  	No Data	
9	DADS0488	Complete	The ECS shall archive the EDOS production data sets (Level 0) received from EDOS.	2521	S-INS-00409	A	The INGST CI shall provide the capability to request storage of a data granule by means of a Data Insert Request to the SDSRV CI associated with the type of the data granule.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	7971	S-DPL-46640	72	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.]	08-0406	09/11/2008  		
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	9002	S-DPL-08010	7.22	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.]	08-0406	09/11/2008  		
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	9003	S-DPL-08020	7.22	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.] 	08-0406	09/11/2008  		
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2219	S-DSS-21365	A	The STMGT CI shall provide storage for the data types listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2520	S-INS-00408	A	For each data granule specified in an Ingest Request the INGST CI shall determine by means of an Advertisement the appropriate SDSRV CI in which to store the data granule.	99-0729	08/25/1999  	No Data	
10	DADS0490	EOC Partial	The ECS shall archive Level 1B - Level 4 data products.	2521	S-INS-00409	A	The INGST CI shall provide the capability to request storage of a data granule by means of a Data Insert Request to the SDSRV CI associated with the type of the data granule.	99-0729	08/25/1999  	No Data	
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4210	S-DSS-01500	6A	The SDSRV CI shall provide a command line utility for the deletion of granules.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4211	S-DSS-01505	6A	The SDSRV CI shall permit an ECS operator to perform granule deletions while it performs other requests concurrently. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4212	S-DSS-01510	6A	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.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4213	S-DSS-01515	6A	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).	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4214	S-DSS-01520	6A	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. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4215	S-DSS-01525	6A	The SDSRV CI shall display to the ECS operator the number of granules which have been selected for deletion before performing the deletion. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4216	S-DSS-01530	6A	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. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4217	S-DSS-01535	6A	The SDSRV CI shall allow the operator to request suppression of confirmation prompts via a command line parameter. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4218	S-DSS-01545	6A	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. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4219	S-DSS-01555	6A	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. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4220	S-DSS-01560	6A	The SDSRV CI shall log all deletion requests in the application log and in a separate granule deletion log file specified by the operator.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4221	S-DSS-01565	6A	The SDSRV CI shall log all delete errors in the application log and in a separate granule deletion log file specified by the operator.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4222	S-DSS-01570	6A	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  	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4223	S-DSS-01575	6A	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  	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4224	S-DSS-01580	6A	The SDSRV CI shall perform delete operations such that they can be restarted and completed successfully if they are interrupted by a fault.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4225	S-DSS-01540	6A	The SDSRV CI shall perform the requested granule deletion immediately after operator confirmation. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4226	S-DSS-01550	6A	The SDSRV CI shall, by default, not physically delete granules that are being referenced as inputs by other granules. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4252	S-DSS-01537	6A	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)  	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4253	S-DSS-01546	6A	The SDSRV CI shall permit an ECS operator to suppress deletion of the BROWSE, QA, PH via command line option.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4254	S-DSS-01552	6A	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.	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4255	S-DSS-01577	6A	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  	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4256	S-DMS-31060	6A	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. 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4257	S-DSS-01582	6A	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 	00-0114	02/07/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4348	S-DSS-01542	6A	The SDSRV CI shall make physically deleted granules inaccessible for normal SDSRV access commands.     	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4349	S-DSS-01556	6A	The SDSRV CI shall append output to the granule deletion log file if it already exists, or create it if it does not.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4350	S-DSS-01585	6A	The SDSRV CI shall provide a 'deletion cleanup' command line utility.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4351	S-DSS-01588	6A	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.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4352	S-DSS-01590	6A	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). 	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4353	S-DSS-01595	6A	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.  	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4354	S-DSS-01600	6A	The SDSRV CI shall provide the list of files eligible for removal from the archive to the STMGT CI.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4355	S-DSS-01603	6A	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  	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4356	S-DSS-01605	6A	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   	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4357	S-DSS-01610	6A	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.    	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4358	S-DSS-01615	6A	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.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4359	S-DSS-01620	6A	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.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4360	S-DSS-20700	6A	The STMGT CI shall accept the list of files eligible for deletion from the SDSRV CI.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4361	S-DSS-20710	6A	The STMGT CI shall provide an operator interface to remove the files that are eligible for deletion from the archive directories.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4362	S-DSS-20720	6A	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.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4363	S-DSS-20730	6A	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.	00-0261	03/20/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4537	S-DSS-06715	6A	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.	00-0751	07/25/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	4538	S-DSS-06716	6A	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.	00-0751	07/25/2000  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9003	S-DPL-08020	7.22	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.] 	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9005	S-DPL-08040	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9006	S-DPL-08050	7.22	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.	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9007	S-DPL-08060	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9008	S-DPL-08070	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9009	S-DPL-08080	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9010	S-DPL-08090	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9011	S-DPL-08100	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9012	S-DPL-08110	7.22	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.	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9013	S-DPL-08120	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9014	S-DPL-08130	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9015	S-DPL-08140	7.22	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.]	08-0406	09/11/2008  		
11	DADS0491	5A 6A	The ECS shall provide the capability for an authorized operator to delete data products.	9016	S-DPL-08150	7.22	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.	08-0406	09/11/2008  		
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	4823	S-OMS-01020	SY3	The Order Manager shall process data distribution requests that were released from hold by the operator.	02-1045	12/04/2002  		
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	4910	S-OMS-03145	SY3	The Order Management Operator GUI shall permit an operator to fail a granule that exceeded the capacity of the media type. 	02-1045	12/04/2002  		
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	4911	S-OMS-03150	SY3	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.	02-1045	12/04/2002  		
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	1861	S-DSS-00210	B1	The SDSRV CI shall provide operations staff the capability to update the Priority Information for any entry in the Service Request List.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	1862	S-DSS-00220	B1	The SDSRV CI shall provide operations staff the capability to issue Cancellation Requests for any Service Request in the Service Request List.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	1865	S-DSS-00230	B1	The SDSRV CI shall provide the user the capability to issue Cancellation Requests for the user's own Service Requests.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	1964	S-DSS-01785	B1	The SDSRV CI shall accept and process Cancellation Requests for the cancellation of a specified Service request in the Service Request List.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2103	S-DSS-05735	B1	The SDSRV CI shall return a unique Request Identifier to the requesting client, whenever a valid Service Request is received.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2271	S-DSS-30045	A	The DDIST CI shall send a Distribution Notification to the user in the event that the user's Distribution Request is canceled by the operations staff.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2279	S-DSS-30130	B1	The DDIST CI shall provide the capability for operations staff to cancel the processing of Electronic Distribution Requests prior to the start of the transmission of the data.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2281	S-DSS-30137	B0	The DDIST CI shall provide the capability for operations staff to cancel the processing of a queued Electronic Distribution Request.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2285	S-DSS-30150	B0	The DDIST CI shall provide the capability for operations staff to cancel the processing of a Media Distribution Request once the requested data has been output to media and queued for shipment.	99-0729	08/25/1999  	No Data	
12	DADS0525	6A 6B	The ECS shall accept from operators updates/cancellations of data order requests.	2364	S-DSS-31540	B0	The DDIST CI shall provide the capability for the operations staff to cancel the processing of a queued media Distribution Request.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	4851	S-OMS-01170	SY3	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.	02-1045	12/04/2002  		
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	4852	S-OMS-01180	SY3	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.	02-1045	12/04/2002  		
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	264	S-DSS-06600	5B	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.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	265	S-DSS-06601	5B	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.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	267	S-DSS-06603	5B	The SDSRV CI shall support access rules based upon the MSS User Profile roles of P, R, and N individually or in any combination.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	268	S-DSS-06604	5B	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.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	269	S-DSS-06605	5B	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).	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	271	S-DSS-06607	5B	The SDSRV CI shall use the MSS based NASAUSER attribute when evaluating granule access rules.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	272	S-DSS-06608	5B	The SDSRV CI shall send to the MSS Accountability Service a request for User Profile information including the NASAUser attribute.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	273	S-DSS-06609	5B	The SDSRV CI shall receive User Profile information, including the NASAUser attribute, from the MSS Accountability Service.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	274	S-DSS-06610	5B	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").	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	275	S-DSS-06611	5B	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.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	276	S-DSS-06612	5B	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').	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	277	S-DSS-06613	5B	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'.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	278	S-DSS-06614	5B	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'.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	279	S-DSS-06615	5B	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.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	280	S-DSS-06616	5B	The SDSRV CI shall assign a null value to the QA time range when a new ESDT is installed.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	281	S-DSS-06617	5B	The SDSRV CI shall assign a null value to the ESDT specific access permission when a new ESDT is installed.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	1834	S-DSS-00015	A	The SDSRV CI shall insure that each Data Request includes a User Identifier, a Request Priority, and a Data Identifier.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	1835	S-DSS-00025	A	The SDSRV CI shall verify that each Service Request specifies a User Identifier, a Request Priority, and other required parameters.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	1844	S-DSS-00095	IR1	The SDSRV CI shall return a Reject Notification including the reason for rejection if a Service Request fails validation.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
14	DADS0570	5B Partial	The ECS shall verify product orders, and withhold granules from distribution which the user is not authorized to receive.	1918	S-DSS-00860	A	The SDSRV CI shall inform a client that a requested service is not accessible if the client attempts to access services outside their access level.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4684	S-SSS-10020	SY3	The NSBRV CI shall store bundling order information persistently. 	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4692	S-SSS-10100	SY3	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).   	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4693	S-SSS-10110	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4694	S-SSS-10120	SY3	The NSBRV CI shall allow the operator to select a valid ECS physical media type for the bundling order.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4695	S-SSS-10125	SY3	The NSBRV CI shall allow the operator to select ftp push or ftp pull as media types for a bundling order.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4696	S-SSS-10130	SY3	The NSBRV CI shall allow the operator to enter the distribution options that are valid for the selected media type into a bundling order.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4697	S-SSS-10140	SY3	The NSBRV CI shall require the operator to enter all distribution options into a bundling order that are mandatory for the selected media type.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4698	S-SSS-10150	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4706	S-SSS-10210	SY3	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']	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4719	S-SSS-10320	SY3	The NSBRV CI shall allow the operator to update the distribution priority associated with an existing bundling order. 	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4720	S-SSS-10330	SY3	The NSBRV CI shall allow the operator to modify the media type and distribution options associated with an existing bundling order.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4724	S-SSS-10360	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4725	S-SSS-10370	SY3	The NSBRV CI shall allow the operator to cancel an individual bundling order.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4726	S-SSS-10374	SY3	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'.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4733	S-SSS-05205	SY3	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.]	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4745	S-OMS-05112	SY3	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'. 	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4753	S-OMS-05320	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4757	C-MSS-75290	SY3	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]	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4758	C-MSS-75291	SY3	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]	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4759	C-MSS-75292	SY3	The MSS Accountability GUI shall allow operators to list the standing bundling orders. [Note: corresponds to C-MSS-75230]	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4760	C-MSS-75293	SY3	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]	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4794	S-OMS-00100	SY3	The Order Management Service shall require that a data distribution request specify a set of distribution options.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4795	S-OMS-00110	SY3	The Order Management Service shall accept any valid combination of electronic or physical media distribution options that are supported by ECS.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4796	S-OMS-00120	SY3	The Order Management Service shall require that a data distribution request specify a single media type.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4803	S-OMS-00180	SY3	The Order Management Service shall accept an optional PRIORITY parameter for a distribution request that specifies one of the ECS priorities.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4812	S-OMS-00270	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4813	S-OMS-00280	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4814	S-OMS-00285	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4928	S-OMS-03310	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4929	S-OMS-03320	SY3	The Order Management GUI shall update the MSS order tracking status for requests released from hold to 'Queued'.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4930	S-OMS-03330	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4931	S-OMS-03340	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4932	S-OMS-03350	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4933	S-OMS-03360	SY3	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)	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4934	S-OMS-03370	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4935	S-OMS-03380	SY3	The Order Management GUI shall update the MSS order tracking information for a request failed by the operator to a status of 'Canceled'. 	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4936	S-OMS-03390	SY3	The Order Management GUI shall record the date/time and the nature of the disposition of an operator intervention in the Order Management Database.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4937	S-OMS-03400	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4938	S-OMS-03410	SY3	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.	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	4956	C-MSS-75924	SY3	The MSS CI shall accept the following new MSS request status values:  a. Partitioned	02-1045	12/04/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5443	S-SSS-00260	SY2	The NSBRV CI shall allow a distribution action to be associated with a subscription.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5444	S-SSS-00270	SY2	The NSBRV CI shall require the operator to associate the userid of a registered ECS user with a distribution action.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5445	S-SSS-00275	SY2	The NSBRV CI shall provide the userid of the registered ECS user associated with the subscription as the default userid for the distribution action.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5448	S-SSS-00290	SY2	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.)	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5449	S-SSS-00300	SY2	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).   	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5450	S-SSS-00305	SY2	The NSBRV CI shall provide the distribution priority in the user profile of the userid associated with the subscription as the default distribution priority.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5451	S-SSS-00310	SY2	The NSBRV CI shall allow the operator to select FtpPush distribution.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5452	S-SSS-00320	SY2	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  	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5453	S-SSS-00330	SY2	The NSBRV CI shall allow the operator to select FtpPull distribution.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5454	S-SSS-00340	SY2	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  	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5455	S-SSS-00380	SY2	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.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	5456	S-SSS-00384	SY2	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.	02-1088	12/18/2002  		
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	86	C-MSS-75046	5B	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	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	87	C-MSS-75047	5B	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	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	88	C-MSS-75056	5B	The MSS accountability management service shall provide the capability to identify on demand processing orders and requests.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	89	C-MSS-75058	5B	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.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	90	C-MSS-75059	5B	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.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	91	C-MSS-75061	5B	The MSS accountability management service shall be able to track the status of an ASTER L1B order and its requests.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	101	C-MSS-75055	5B	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	1072	C-CSS-40410	B0	The Subscription Service shall provide the capability to store subscriptions and event types persistently.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	1839	S-DSS-00057	B1	The SDSRV CI shall maintain, for each entry in the Service Request List, an indicator that determines whether the associated Service Request is being processed or is waiting to be processed.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	1927	S-DSS-01090	B1	The SDSRV CI shall maintain a Service Request List that lists received Service Requests, associated Priority Information, and all other information required to process each request.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	2274	S-DSS-30095	B0	The DDIST CI shall maintain a queue of Distribution Requests that are waiting to be processed, and shall maintain, for each queued request, the request type, user, priority, and all other information necessary to process the request.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
15	DADS0660	Complete SY2	The ECS shall maintain the following information for each order, including standing orders:    a. Priorities  b. Distribution directions  c. State (i.e., active, canceled, suspended)	2291	S-DSS-30180	A	The DDIST CI shall process queued Distribution Requests in order, according to their assigned Priority Information.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	4803	S-OMS-00180	SY3	The Order Management Service shall accept an optional PRIORITY parameter for a distribution request that specifies one of the ECS priorities.	02-1045	12/04/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	4824	S-OMS-01030	SY3	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.]  	02-1045	12/04/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5051	S-DSS-99000	SY2	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.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5052	S-DSS-99010	SY2	The DCLI shall accept a mandatory DDISTMEDIATYPE parameter.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5053	S-DSS-99020	SY2	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	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5054	S-DSS-99030	SY2	The DCLI shall include the DDISTMEDIATYPE parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5055	S-DSS-99040	SY2	The DCLI shall accept the following FTP Push parameters (all strings) if the DDISTMEDIATYPE is FtpPush:  FTPUSER  FTPPASSWORD  FTPHOST  FTPPUSHDEST	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5056	S-DSS-99050	SY2	The DCLI shall verify that all four FTP Push parameters are provided if the DDISTMEDIATYPE is FtpPush, and return a fatal error if not.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5057	S-DSS-99060	SY2	The DCLI shall include the FTP Push parameters in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5058	S-DSS-99070	SY2	The DCLI shall accept an optional DDISTMEDIAFORMAT parameter	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5059	S-DSS-99080	SY2	The DCLI shall verify that the DDISTMEDIAFORMAT parameter, if present, specifies a value of 'FILEFORMAT' and return a fatal error if not.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5060	S-DSS-99090	SY2	The DCLI shall include the DDISTMEDIAFORMAT parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5061	S-DSS-99100	SY2	The DCLI shall accept a mandatory ECSUSERPROFILE parameter.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5062	S-DSS-99110	SY2	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.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5063	S-DSS-99120	SY2	The DCLI shall include the ECSUSERPROFILE parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5064	S-DSS-99130	SY2	The DCLI shall accept a mandatory ORDERID and a mandatory REQUESTID parameter.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5065	S-DSS-99140	SY2	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.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5066	S-DSS-99150	SY2	The DCLI shall include the REQUESTID parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5067	S-DSS-99160	SY2	The DCLI shall accept an optional PRIORITY parameter.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5068	S-DSS-99170	SY2	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	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5069	S-DSS-99180	SY2	The DCLI shall include the PRIORITY parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5070	S-DSS-99190	SY2	The DCLI shall accept an optional UserString parameter specifying a string of a maximum length of 80 characters.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5071	S-DSS-99200	SY2	The DCLI shall verify that the UserString parameter does not exceed the maximum length and return a fatal error if it does.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5072	S-DSS-99210	SY2	The DCLI shall include the UserString parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5073	S-DSS-99220	SY2	The DCLI shall accept an optional DDISTNOTIFYTYPE parameter.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5074	S-DSS-99230	SY2	The DCLI shall verify that the DDISTNOTIFYTYPE parameter, if present, is set to MAIL, and return a fatal error if not.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5075	S-DSS-99240	SY2	The DCLI shall accept a mandatory NOTIFY parameter specifying an e-mail address string.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5076	S-DSS-99250	SY2	The DCLI shall verify that the NOTIFY parameter is present and return a fatal error if not.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5077	S-DSS-99260	SY2	The DCLI shall include the DDISTNOTIFYTYPE and NOTIFY parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5078	S-DSS-99270	SY2	The DCLI shall accept a mandatory tag parameter as a string of up to 20 characters.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5079	S-DSS-99280	SY2	The DCLI shall verify that the tag parameter is present and at most 20 characters in length, and return a fatal error if not.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5080	S-DSS-99290	SY2	The DCLI shall use the tag parameter to generate an rpcID for the DDIST distribution request it submits.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5081	S-DSS-99300	SY2	The DCLI shall generate the identical rpcID only if it receives the identical tag on different submission requests, the generated rpcID otherwise being different.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5082	S-DSS-99310	SY2	The DCLI shall accept a list of up to 100 fully qualified file/path names that represent the files to be distributed.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5083	S-DSS-99320	SY2	The DCLI shall return a fatal error if less than one and more than 100 file/path names are provided.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5084	S-DSS-99330	SY2	The DCLI shall assume the following default values for the corresponding optional parameters if they are not provided:  DDISTMEDIAFORMAT  = FILEFORMAT  PRIORITY = NORMAL  DDISTNOTIFYTYPE = MAIL	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5085	S-DSS-99340	SY2	The DCLI shall submit an asynchronous distribution request for the identified files to DDIST.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5086	S-DSS-99350	SY2	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.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5087	S-DSS-99360	SY2	The DCLI shall be able to accept requests for a designated mode.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5088	S-DSS-99370	SY2	It shall be possible to submit several requests in a given mode via the DCLI concurrently.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5089	S-DSS-99380	SY2	It shall be possible to submit requests via the DCLI in several different modes concurrently.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	5090	S-DSS-99390	SY2	The DCLI shall be able to receive and process distribution requests through to DDIST at the rate of 40 requests per hour.	02-1064	12/11/2002  		
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	1835	S-DSS-00025	A	The SDSRV CI shall verify that each Service Request specifies a User Identifier, a Request Priority, and other required parameters.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	1837	S-DSS-00052	B1	The SDSRV CI shall process each Service Request, in order, according to its relative priority in the Service Request List.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	1838	S-DSS-00055	B1	The SDSRV CI shall initiate the processing of Service Requests of equal priority in the order in which they are received.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	1861	S-DSS-00210	B1	The SDSRV CI shall provide operations staff the capability to update the Priority Information for any entry in the Service Request List.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	1970	S-DSS-01865	B0	The SDSRV CI shall provide Priority Information for each Data Distribution Request to the DDIST CI.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	2274	S-DSS-30095	B0	The DDIST CI shall maintain a queue of Distribution Requests that are waiting to be processed, and shall maintain, for each queued request, the request type, user, priority, and all other information necessary to process the request.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
16	DADS0690	6A 6B	The ECS shall support the prioritized retrieval and delivery of data based on the priority information specified in the data retrieval request.	2291	S-DSS-30180	A	The DDIST CI shall process queued Distribution Requests in order, according to their assigned Priority Information.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5051	S-DSS-99000	SY2	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.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5052	S-DSS-99010	SY2	The DCLI shall accept a mandatory DDISTMEDIATYPE parameter.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5053	S-DSS-99020	SY2	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	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5054	S-DSS-99030	SY2	The DCLI shall include the DDISTMEDIATYPE parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5055	S-DSS-99040	SY2	The DCLI shall accept the following FTP Push parameters (all strings) if the DDISTMEDIATYPE is FtpPush:  FTPUSER  FTPPASSWORD  FTPHOST  FTPPUSHDEST	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5056	S-DSS-99050	SY2	The DCLI shall verify that all four FTP Push parameters are provided if the DDISTMEDIATYPE is FtpPush, and return a fatal error if not.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5057	S-DSS-99060	SY2	The DCLI shall include the FTP Push parameters in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5058	S-DSS-99070	SY2	The DCLI shall accept an optional DDISTMEDIAFORMAT parameter	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5059	S-DSS-99080	SY2	The DCLI shall verify that the DDISTMEDIAFORMAT parameter, if present, specifies a value of 'FILEFORMAT' and return a fatal error if not.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5060	S-DSS-99090	SY2	The DCLI shall include the DDISTMEDIAFORMAT parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5061	S-DSS-99100	SY2	The DCLI shall accept a mandatory ECSUSERPROFILE parameter.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5062	S-DSS-99110	SY2	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.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5063	S-DSS-99120	SY2	The DCLI shall include the ECSUSERPROFILE parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5064	S-DSS-99130	SY2	The DCLI shall accept a mandatory ORDERID and a mandatory REQUESTID parameter.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5065	S-DSS-99140	SY2	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.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5066	S-DSS-99150	SY2	The DCLI shall include the REQUESTID parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5067	S-DSS-99160	SY2	The DCLI shall accept an optional PRIORITY parameter.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5068	S-DSS-99170	SY2	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	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5069	S-DSS-99180	SY2	The DCLI shall include the PRIORITY parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5070	S-DSS-99190	SY2	The DCLI shall accept an optional UserString parameter specifying a string of a maximum length of 80 characters.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5071	S-DSS-99200	SY2	The DCLI shall verify that the UserString parameter does not exceed the maximum length and return a fatal error if it does.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5072	S-DSS-99210	SY2	The DCLI shall include the UserString parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5073	S-DSS-99220	SY2	The DCLI shall accept an optional DDISTNOTIFYTYPE parameter.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5074	S-DSS-99230	SY2	The DCLI shall verify that the DDISTNOTIFYTYPE parameter, if present, is set to MAIL, and return a fatal error if not.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5075	S-DSS-99240	SY2	The DCLI shall accept a mandatory NOTIFY parameter specifying an e-mail address string.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5076	S-DSS-99250	SY2	The DCLI shall verify that the NOTIFY parameter is present and return a fatal error if not.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5077	S-DSS-99260	SY2	The DCLI shall include the DDISTNOTIFYTYPE and NOTIFY parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5078	S-DSS-99270	SY2	The DCLI shall accept a mandatory tag parameter as a string of up to 20 characters.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5079	S-DSS-99280	SY2	The DCLI shall verify that the tag parameter is present and at most 20 characters in length, and return a fatal error if not.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5080	S-DSS-99290	SY2	The DCLI shall use the tag parameter to generate an rpcID for the DDIST distribution request it submits.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5081	S-DSS-99300	SY2	The DCLI shall generate the identical rpcID only if it receives the identical tag on different submission requests, the generated rpcID otherwise being different.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5082	S-DSS-99310	SY2	The DCLI shall accept a list of up to 100 fully qualified file/path names that represent the files to be distributed.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5083	S-DSS-99320	SY2	The DCLI shall return a fatal error if less than one and more than 100 file/path names are provided.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5084	S-DSS-99330	SY2	The DCLI shall assume the following default values for the corresponding optional parameters if they are not provided:  DDISTMEDIAFORMAT  = FILEFORMAT  PRIORITY = NORMAL  DDISTNOTIFYTYPE = MAIL	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5085	S-DSS-99340	SY2	The DCLI shall submit an asynchronous distribution request for the identified files to DDIST.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5086	S-DSS-99350	SY2	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.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5087	S-DSS-99360	SY2	The DCLI shall be able to accept requests for a designated mode.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5088	S-DSS-99370	SY2	It shall be possible to submit several requests in a given mode via the DCLI concurrently.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5089	S-DSS-99380	SY2	It shall be possible to submit requests via the DCLI in several different modes concurrently.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	5090	S-DSS-99390	SY2	The DCLI shall be able to receive and process distribution requests through to DDIST at the rate of 40 requests per hour.	02-1064	12/11/2002  		
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	1994	S-DSS-02900	A	The SDSRV CI shall provide the data type services as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2096	S-DSS-05660	B0	The SDSRV CI shall provide the capability to extract ASCII data from EOS-HDF data granules containing ASCII data and direct the distribution of the extracted data, as specified in valid Data Distribution Requests.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2097	S-DSS-05670	B0	The SDSRV CI shall provide the capability to extract binary data from EOS-HDF data granules containing binary data and direct the distribution of the extracted data, as specified in valid Data Distribution Requests.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
18	DADS0760	Complete	The ECS shall distribute data in native archive format.	2316	S-DSS-30515	A	The DDIST CI shall distribute data in the approved ECS standard format in which it is stored. (i.e., HDF-EOS, V0 native, or Landsat 7 standard format.)	99-0729	08/25/1999  	No Data	
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	87	C-MSS-75047	5B	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	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	100	C-MSS-75045	5B	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1378	S-DMS-30368	Complete	The GTWAY CI shall have the capability to process V0 Inventory Search Requests.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1381	S-DMS-30375	Complete	The GTWAY CI shall send inventory search results to the Version 0 Client using Version 0 protocols.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1382	S-DMS-30392	Complete	The GTWAY CI shall receive inventory search requests from the Version 0 Client using Version 0 protocols.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1385	S-DMS-30404	Complete	The GTWAY CI shall have the capability to process V0 Product Requests.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1386	S-DMS-30406	Complete	The GTWAY CI shall receive Product Requests from the Version 0 IMS using Version 0 protocols.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1387	S-DMS-30408	Complete	The GTWAY CI shall have the capability to send Product Request acknowledgements to the V0 Client using Version 0 system protocols.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	1391	S-DMS-30890	Complete	The GTWAY CI shall  support multiple concurrent requests.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5011	C-CSS-30700	SY2	The Registry Service shall be capable of storing subsetting options for any ECS collection.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5012	C-CSS-30710	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5013	C-CSS-30720	SY2	The Registry Service shall provide the capability to update subsetting options for an ECS Collection specified by shortname/version.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5014	C-CSS-30730	SY2	The Registry Service shall provide capabilities to retrieve subsetting options including subsetter location information for an ECS Collection by ESDT shortname/version. 	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5015	C-CSS-30740	SY2	The Registry Service shall be capable of storing location information for each External Subsetter.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5016	C-CSS-30750	SY2	The Registry Service shall provide the capability to update location information for a specified external subsetter.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5017	C-CSS-30760	SY2	The Registry Service shall be capable of supporting 3 or more External Subsetters.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5018	S-DMS-33300	SY2	The GTWAY CI shall retrieve subset options, including subsetter location information, from the Registry by shortname/version.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5019	S-DMS-33320	SY2	The GTWAY CI shall construct inventory search result messages that include subset options constructed from the External Subsetter options for that shortname/version.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5020	S-DMS-33330	SY2	The GTWAY CI shall construct subset options that contain references to metadata containing data set specific temporal extents. 	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5021	S-DMS-33340	SY2	The GTWAY CI shall construct subset options that contain references to metadata containing data set specific spatial extents. 	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5022	S-DMS-33350	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5023	S-DMS-33360	SY2	The GTWAY CI shall generate a new product request messages for each MSS request pertaining to an external subsetter.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5024	S-DMS-33370	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5025	S-DMS-33380	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5026	S-DMS-33390	SY2	The GTWAY CI shall assign the initial value of  'NULL' to the MSS request for subsetting product requests. 	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5027	S-DMS-33400	SY2	The GTWAY CI shall include the MSS orderID/requestID in the product request message sent to the external subsetter.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5028	S-DMS-33410	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5029	S-DMS-33420	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5030	S-DMS-33430	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5031	S-DMS-33440	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5032	S-DMS-33450	SY2	The GTWAY CI shall create an MSS Order and request object for Product Request submitted by External Subsetter.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5033	S-DMS-33460	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5034	S-DMS-33470	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5035	S-DMS-33480	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5036	S-DMS-33490	SY2	The GTWAY CI shall be able to interface with three or more external subsetters. 	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5037	S-DSS-31600	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5038	S-DSS-31610	SY2	The EPD shall poll configured directories to identify and retrieve product delivery record  (PDR) messages from external subsetters.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5039	S-DSS-31620	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5040	S-DSS-31625	SY2	The EPD shall validate the UserID and RequestID contained in the Product Request file.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5041	S-DSS-31630	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5042	S-DSS-31640	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5043	S-DSS-31650	SY2	The EPD shall transfer distribution request messages via the DDIST Command Line Interface (DCLI) to DDIST for the distribution of external subsetter products.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5044	S-DSS-31660	SY2	The EPD shall access MSS order tracking data to determine the status of orders that correspond to distribution requests submitted to DDIST by EPD.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5045	S-DSS-31670	SY2	The EPD shall delete files received from external subsetters when the MSS order status for the distribution request corresponding to those files is 'Shipped'.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5046	S-DSS-31680	SY2	The EPD shall be capable of supporting 3 or more External Subsetters concurrently to receive external subsetter product distribution requests.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5047	S-DSS-31690	SY2	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.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5048	S-DSS-31700	SY2	The EPD shall log all distribution requests submitted to DCLI.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5049	S-DSS-31710	SY2	The EPD shall log all distribution requests status messages received from the DLCI, including successful, failed, or failed with retryable errors.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5050	S-DSS-31720	SY2	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'.	02-1064	12/11/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5259	S-HEG-00010	SY2	The HDF-EOS Format Conversion Tool shall be operable on a Sun Solaris 2.5.1 operating system.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5260	S-HEG-00020	SY2	The HDF-EOS Format Conversion Tool shall be operable on an SGI IRIX 6.5 operating system.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5261	S-HEG-00040	SY2	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).	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5262	S-HEG-00060	SY2	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.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5263	S-HEG-00065	SY2	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.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5264	S-HEG-00070	SY2	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)'.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5265	S-HEG-00250	SY2	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. 	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5266	S-HEG-00080	SY2	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.)	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5267	S-HEG-00090	SY2	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)'.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5268	S-HEG-00100	SY2	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.)	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5269	S-HEG-00110	SY2	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.)	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5270	S-HEG-00260	SY2	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. 	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5271	S-HEG-00120	SY2	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	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5272	S-HEG-00130	SY2	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  	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5273	S-HEG-00140	SY2	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	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5274	S-HEG-00145	SY2	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. 	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5275	S-HEG-00150	SY2	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).	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5276	S-HEG-00160	SY2	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.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5277	S-HEG-00165	SY2	It is desirable that the HDF-EOS Format Conversion Tool allow a user to spatially subset an output file containing stitched HDF-EOS objects.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5278	S-HEG-00170	SY2	The HDF-EOS Format Conversion Tool shall be able to be invoked from a command line interface.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5279	S-HEG-00180	SY2	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)	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5280	S-HEG-00190	SY2	The HDF-EOS Format Conversion Tool shall be downloadable to a user's workstation via ftp.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5281	S-HEG-00200	SY2	The HDF-EOS Format Conversion Tool shall be able to be run via a web-based GUI.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5283	S-HEG-00220	SY2	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. 	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5284	S-HEG-00230	SY2	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.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5285	S-HEG-00235	SY2	The HDF-EOS Format Conversion Tool GUI shall allow the user to configure the name of a default local file system.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5286	S-HEG-00240	SY2	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.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5287	S-HEG-00280	SY2	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.	02-1088	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5369	S-HEG-20010	SY3	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	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5370	S-HEG-20015	SY3	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	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5371	S-HEG-20020	SY3	The HEG Tool shall perform conversion, reprojection, and subsetting operations on 4-dimensional data structures.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5372	S-HEG-20030	SY3	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.  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5373	S-HEG-20040	SY3	The HEG tool shall delete the intermediate TIFF file upon completion of a conversion operation. 	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5374	S-HEG-20060	SY3	The HEG tool shall delete the intermediate reprojected files upon completion of a subsetting or stitching operation.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5375	S-HEG-20080	SY3	The HEG tool shall provide the capability to cancel an operation in progress. 	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5376	S-HEG-20090	SY3	The HEG tool shall run on IRIX 6.5	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5377	S-HEG-20092	SY3	The HEG tool shall run on Windows 98.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5378	S-HEG-20095	SY3	The HEG tool shall run on Linux (Red Hat Version 7.2)	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5379	S-HEG-20100	SY3	The HEG tool shall apply file name extensions to the resulting converted files, which are consistent with the requested output format.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5380	S-HEG-20110	SY3	The HEG tool shall support requests for spatial sub-sampling of data products. 	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5381	S-HEG-20120	SY3	The HEG Tool shall ensure that the output HDF-EOS file reflects the results of a spatial sub-sampling operation in its metadata.   	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5382	S-HEG-20130	SY3	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	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5383	S-HEG-20140	SY3	The HEG tool shall provide the capability to correct geometric distortion resulting from a stitching operation of multiple MODIS swath objects. - DESIRABLE	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5384	S-HEG-20150	SY3	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	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5507	S-DPL-06010	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5508	S-DPL-06012	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5509	S-DPL-06020	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5510	S-DPL-06030	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5511	S-DPL-06040	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5512	S-DPL-06050	SY3	[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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5513	S-DPL-06060	SY3	The Data Pool web application service data conversion service shall allow the user to specify allowable conversion options for each granule. 	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5514	S-DPL-06070	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5515	S-DPL-06080	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5516	S-DPL-06090	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5517	S-DPL-06100	SY3	[DESIRABLE] The Data Pool web application service shall log all data conversion requests handled, identifying:    [logged information to be defined during design]  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5518	S-DPL-06110	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5519	S-DPL-06114	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5520	S-DPL-06116	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5521	S-DPL-13500	SY3	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'.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5522	S-DPL-13520	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5523	S-HEG-30010	SY3	The HEG front-end shall receive data conversion requests from the Data Pool web application service.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5524	S-HEG-30020	SY3	The HEG front-end shall retrieve data conversion requests from the queue for each granule for which conversion processing is requested.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5525	S-HEG-30030	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5526	S-HEG-30050	SY3	The HEG front-end shall include a data conversion order ID & request ID in the data conversion request file.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5527	S-HEG-30060	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5528	S-HEG-30070	SY3	The HEG front-end shall make available granules required for data conversion to a location that is accessible by the HEG Converter.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5529	S-HEG-30080	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5530	S-HEG-30090	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5531	S-HEG-30100	SY3	[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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5532	S-HEG-30110	SY3	The HEG front-end shall receive data conversion processing results information from a data conversion process when the process terminates.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5533	S-HEG-30120	SY3	The HEG front-end shall make available converted files for distribution to the user, via anonymous FTP.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5534	S-HEG-30150	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5535	S-HEG-30160	SY3	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  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5536	S-HEG-30170	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5537	S-HEG-30180	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5538	S-HEG-30190	SY3	The HEG front-end shall provide as an option, the ability to be started or initialized in a stopped processing queue condition.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5539	S-HEG-30200	SY3	The HEG front-end shall provide the capability for operators to change the state of individual entries in the processing queue.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5540	S-HEG-30210	SY3	The HEG front-end shall, when a shutdown request is received, kill all processing being performed by the HEG converter and exit.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5541	S-HEG-30220	SY3	The HEG front-end shall, when a stop queue processing request is received, cease to submit processing requests for HEG converter processing.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5542	S-HEG-30230	SY3	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'.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5543	S-HEG-30240	SY3	The HEG front-end shall be able to run in any mode.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5544	S-HEG-30250	SY3	The HEG front-end shall be able to run concurrently in different modes.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5545	S-HEG-30260	SY3	The HEG front-end shall return a status to the Data Pool web interface in response to each data conversion requests received.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5546	S-HEG-30270	SY3	[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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5547	S-HEG-30280	SY3	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)  	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5548	S-HEG-30290	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5549	S-HEG-30300	SY3	The HEG converter shall remove all temporary files used during the data conversion processing at the end of that processing.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5550	S-HEG-30310	SY3	The HEG converter shall be able to run in any mode.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5551	S-HEG-30320	SY3	The HEG converter shall be able to run concurrently in different modes.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5552	S-HEG-30330	SY3	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.	02-1094	12/18/2002  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5884	S-HEG-30285	SY4	The HEG front-end shall, provide all appropriate processing status updates to the DPL database.	03-0673	10/02/2003  		
515	DADS0810	SY2 SY3	The ECS shall provide tools for subsetting, re-projecting and re-formatting HDF data products.	5887	S-HEG-20135	SY4	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	03-0673	10/02/2003  		
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2301	S-DSS-30270	6A	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.	99-1175	12/01/1999  		
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2303	S-DSS-30280	6A	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.	99-1175	12/01/1999  		
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	4164	S-DSS-30265	6A	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	99-1175	12/01/1999  		
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1871	S-DSS-00330	B1	The SDSRV CI shall record Request Identifiers to be used for accounting purposes.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1872	S-DSS-00331	B1	The SDSRV CI shall record the User Identifier of the science investigator associated with a Service Request, to be used for accounting purposes.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1875	S-DSS-00340	B1	The SDSRV CI shall record the level of CPU utilization for each Service Request to be used for accounting.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1876	S-DSS-00350	B1	The SDSRV CI shall record the level of I/O utilization for each Service Request to be used for accounting.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1877	S-DSS-00360	B1	The SDSRV CI shall record, for accounting purposes, a fixed personnel cost for Service Requests requiring interaction with operations staff.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1878	S-DSS-00370	B1	The SDSRV CI shall record a archival storage cost based on the number of bytes stored, to be used for accounting.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1883	S-DSS-00400	B1	The SDSRV CI shall accept pricing information, based on disk, CPU and media utilization, from CSMS.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	1884	S-DSS-00410	B1	The SDSRV CI shall provide actual cost information by the completion of a Service Request.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2035	S-DSS-03990	B1	The SDSRV CI shall be capable of receiving actual disk utilization from the PLANG CI.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2036	S-DSS-04000	B1	The SDSRV CI shall be capable of receiving actual CPU utilization from the PLANG CI.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2037	S-DSS-04010	B1	The SDSRV CI shall be capable of receiving actual disk utilization from the STMGT CI.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2211	S-DSS-21340	B1	The STMGT CI shall provide data to support administrative requests for Accounting Management Data.	99-0729	08/25/1999  	No Data	
21	DADS0890	6A	The ECS shall generate distribution resource statistics consisting of:    a. Request number and user identification    b. Media type and quantity	2212	S-DSS-21350	B1	The STMGT CI shall collect Accounting Management Data as defined in Reference Table:  Data Glossary.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	2305	S-DSS-30345	6A	The DDIST CI shall send to the requesting client a Distribution Nofification that describes the reason for the unsuccessful completion of a Distribution Request.	99-1175	12/01/1999  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4162	S-DSS-30028	6A	The DDIST CI shall include the type of media and the media identifiers in each Distribution Notification sent for successful media distribution of data.	99-1175	12/01/1999  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4163	S-DSS-30040	6A	The DDIST CI shall provide a configurable preamble for the Distribution Notification for each type of media that data is distributed on.	99-1175	12/01/1999  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4828	S-OMS-01035	SY3	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.	02-1045	12/04/2002  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4829	S-OMS-01036	SY3	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.	02-1045	12/04/2002  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4853	S-OMS-01190	SY3	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).	02-1045	12/04/2002  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4857	S-OMS-01230	SY3	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.	02-1045	12/04/2002  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4858	S-OMS-01240	SY3	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'.	02-1045	12/04/2002  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	4888	S-OMS-02030	SY3	The Order Management Service Command Line Utility shall return status information indicating success or the nature of the failure of a request submission. [OSS]	02-1045	12/04/2002  		
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	52	S-PLS-04090	5B	The PLANG CI  failure / expiration notification shall describe the reason for the failure/expiration of a higher level product ODPR.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	60	S-PLS-04170	5B	 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.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	64	S-PLS-04230	5B	The PLANG CI shall create a request in the MSS order tracking database for each generated DPR, and maintain the status of the request.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	68	S-PLS-04270	5B	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.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	1059	C-CSS-40300	B0	The Subscription Service shall provide the capability to notify subscriber via email upon occurrence of the event if no action has been specified.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	1067	C-CSS-40360	B0	The Subscription Service shall provide acknowledgment of receipt of a request after the request is submitted.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	1840	S-DSS-00060	IR1	The SDSRV CI shall acknowledge the receipt of Service Requests from local and remote clients.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	1844	S-DSS-00095	IR1	The SDSRV CI shall return a Reject Notification including the reason for rejection if a Service Request fails validation.	99-0729	08/25/1999  	No Data	
22	DADS1020	5B Partial	The ECS shall generate data retrieval status  to acknowledge the acceptance or rejection, including the reason for rejection (e.g., distribution parameters missing, data not present or unreadable), of a product order.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	4826	S-OMS-01033	SY3	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.	02-1045	12/04/2002  		
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	4830	S-OMS-01037	SY3	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.	02-1045	12/04/2002  		
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	4831	S-OMS-01038	SY3	Operators shall be able to configure the DORRAN e-mail address.	02-1045	12/04/2002  		
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	4834	S-OMS-01039	SY3	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.	02-1045	12/04/2002  		
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2301	S-DSS-30270	6A	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.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2302	S-DSS-30275	6A	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.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2303	S-DSS-30280	6A	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.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2304	S-DSS-30285	6A	The DDIST CI shall log, to the Event Log, failures to successfully complete Electronic Distribution Requests due to transmission failures.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2307	S-DSS-30410	6A	The DDIST CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2308	S-DSS-30415	6A	The DDIST CI shall log, to the Event Log, the failure of the retrieval of a data granule.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2309	S-DSS-30420	6A	The DDIST CI shall have the capability to log, to the Event Log, the start of the processing of each Data Distribution Request.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2310	S-DSS-30425	6A	The DDIST CI shall have the capability to log, to the Event Log, the completion of the processing of each Data Distribution Request.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2311	S-DSS-30430	B1	The DDIST CI shall provide the capability for the operations staff to manually enter the status (i.e. "waiting for shipment" or "shipped") of a physical media shipment.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2312	S-DSS-30431	6A	The DDIST CI shall log, to the Event Log, changes in the status of the shipment of media associated with a Media Distribution Request.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2326	S-DSS-30670	6A	The DDIST CI shall log, to the Event Log, all occurrences of transmission failures associated with Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
23	DADS1030	Complete	The ECS shall generate data distribution status to monitor the progress of the distribution process.	2966	C-MSS-36575	B0	The Management Agent Service shall have the capability to receive status of data distribution from the DSS.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	1844	S-DSS-00095	IR1	The SDSRV CI shall return a Reject Notification including the reason for rejection if a Service Request fails validation.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2112	S-DSS-05780	B0	The SDSRV CI shall provide the INGST CI a status indicating whether or not a Data Insert Request for the storage of data has been successful.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2170	S-DSS-20622	A	The STMGT CI shall compute a checksum against each file stored as a result of a storage request, and provide that checksum to the originator of the request.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2261	S-DSS-22180	B0	The STMGT CI shall provide the SDSRV CI a status indicating whether or not a request for the storage of data files has been successful.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2442	S-INS-00060	IR1	The INGST CI shall report status to the provider of a Network Ingest Request for the following:  a. File transfer failure  b. File size discrepancies  c. Invalid Data Type Identifier  d. Missing required metadata  e. Metadata parameters out of range  f. Data conversion failure  g. Failure to archive data  h. Inability to transfer data within the specified time window  i. Missing required request information  j. Successful archive of the data	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2446	S-INS-00085	A	The INGST CI shall report status to the provider of a polling ingest request (delivery record file) for the following:   a.  File transfer failure  b.  File size discrepancies  c.  Invalid Data Type Identifier  d.  Missing required metadata  e.  Metadata parameters out of range  f.  Data conversion failure  g.  Failure to archive data  h.  Inability to transfer data within the specified time window  i.  Missing required request information  j.  Successful archive of the data	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2456	S-INS-00170	A	The INGST CI shall report Hard Media Ingest Request status to the submitting operations staff for the following:  a.      Media file transfer failure  b.      Invalid Data Type Identifier  c.      Missing required metadata  d.      Metadata parameters out of range  e.      Data conversion failure  f.      Failure to archive data  g.      Missing file describing media data to be ingested  h.      Unauthorized hard media provider  i.      Unauthorized operations staff  j.      Successful archive of data	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2466	S-INS-00220	A	The INGST CI shall report status to the interactive submitter of a Network Ingest Request for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Data conversion failure  g.      Failure to archive data  h.      Inability to transfer data within the specified time window  i.      Unauthorized science user  j.      Missing required request information  k.      Successful archive of the data	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2475	S-INS-00230	A	The INGST CI shall report status to the interactive submitter of a Document Ingest Request for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Data conversion failure  g.      Failure to archive data  h.      Inability to transfer data within the specified time window  i.      Unauthorized science user  j.      Missing required request information  k.      Successful archive of the data	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2476	S-INS-00235	A	The INGST CI shall accept ingest Status Requests from science users to determine the status of:  a.      A specified ongoing Ingest Request, previously submitted by the science user who is requesting status and identified by the ingest Request Identifier  b.      All of the user's ongoing Ingest Requests	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2477	S-INS-00240	A	The INGST CI shall determine the User Identifier for a science user submitting an ingest Status Request.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2478	S-INS-00250	A	The INGST CI shall return status on a science user's ongoing Network Ingest Requests,  based on User Identifier, to the user.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2479	S-INS-00260	A	The INGST CI shall provide science users the capability to display the status of the user's ongoing request processing.  Displayed status shall include the External Data Provider, ingest Request Identifier, total ingest data volume, and Request State.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2480	S-INS-00270	A	The INGST CI shall accept ingest Status Requests from authorized operations staff to determine the status of:  a.      A specified ongoing Ingest Request identified by ingest Request Identifier  b.      All ongoing Ingest Requests associated with a specified User Identifier  c.      All ongoing Ingest Requests	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2481	S-INS-00280	A	The INGST CI shall determine the User Identifier for an operations staff member submitting an ingest Status Request.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2482	S-INS-00290	A	The INGST CI shall authenticate the User Identifier of operations staff requesting status on all ongoing Ingest Requests.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2483	S-INS-00295	A	The INGST CI shall return an error status to the requester and log information in the Error Log if status is requested on  ongoing Ingest Requests from an unauthorized requester.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2484	S-INS-00300	A	The INGST CI shall return status on ongoing Ingest Requests to an authorized operations staff member.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2485	S-INS-00310	A	The INGST CI shall provide authorized operations staff the capability to view the status of ongoing ingest processing.  Displayed status shall include the External Data Provider, ingest Request Identifier, total ingest data volume, and Request State.	99-0729	08/25/1999  	No Data	
24	DADS1070	Complete	The ECS shall send  data check and storage status to the provider of ingest data.	2486	S-INS-00315	A	The INGST CI shall provide the capability for authorized operations staff to select status of ongoing Ingest Request processing for viewing by means of the External Data Provider.	99-0729	08/25/1999  	No Data	
51	DADS1080	Complete	The ECS shall maintain an external data receipt log.	1954	S-DSS-01435	B0	The SDSRV CI shall log, to the Event Log, the successful completion of Data Insert Requests.	99-0729	08/25/1999  	No Data	
51	DADS1080	Complete	The ECS shall maintain an external data receipt log.	1956	S-DSS-01445	B0	The SDSRV CI shall log the following when archived data is inserted, updated, deleted, or accessed:  a. User Identifier  b. Data and time of the operation performed  c. The identity of the data	99-0729	08/25/1999  	No Data	
51	DADS1080	Complete	The ECS shall maintain an external data receipt log.	2132	S-DSS-20025	B0	The STMGT CI shall place an entry in the Archive Activity Log corresponding to each Insert Request. The STMGT CI shall log, to the Event Log, the successful completion of requests to store data files into the archive.	99-0729	08/25/1999  	No Data	
51	DADS1080	Complete	The ECS shall maintain an external data receipt log.	2534	S-INS-00490	A	The INGST CI shall log the following information in an Ingest History Log for each received Ingest Request:  a.      Ingest start/stop dates and times  b.      Ingest Request Identifier  c.      External Data Provider  d.      Final Service Request Status  e.      Data Type Identifiers  f.      Ingest data volume  g.      # of data sets  h.      # of data files	99-0729	08/25/1999  	No Data	
51	DADS1080	Complete	The ECS shall maintain an external data receipt log.	2535	S-INS-00500	A	The INGST CI shall provide operations staff the capability to view selected entries from the Ingest History Log.	99-0729	08/25/1999  	No Data	
51	DADS1080	Complete	The ECS shall maintain an external data receipt log.	2536	S-INS-00510	A	The INGST CI shall provide the capability to select Ingest History Log entries for viewing by the following parameters:    a.      Ingest start/stop dates and times  b.      External Data Provider  c.      Data Type Identifier  d.      Final Service Request Status  e.      Test or operational mode	99-0729	08/25/1999  	No Data	
52	DADS1085	6A Future	The ECS shall maintain a data access log.	4168	S-DSS-20050	6A	The STMGT CI shall not write data of a sensitive nature (e.g. passwords) to a log in the clear.	99-1176	12/01/1999  		
52	DADS1085	6A Future	The ECS shall maintain a data access log.	4172	S-DSS-20680	6A	The STMGT CI shall maintain a log of files which have been accessed including time stamp and request ID for each access.	99-1176	12/01/1999  		
52	DADS1085	6A Future	The ECS shall maintain a data access log.	1887	S-DSS-00470	B1	The SDSRV CI shall log all access to data in a Data Access Log.	99-0729	08/25/1999  	No Data	
52	DADS1085	6A Future	The ECS shall maintain a data access log.	1888	S-DSS-00480	B1	The SDSRV CI shall provide the capability for operations staff to view the Data Access Log.	99-0729	08/25/1999  	No Data	
52	DADS1085	6A Future	The ECS shall maintain a data access log.	1889	S-DSS-00500	B1	The SDSRV CI shall provide the capability for operations staff to sort the Data Access Log by time frame, source of access and data type.	99-0729	08/25/1999  	No Data	
52	DADS1085	6A Future	The ECS shall maintain a data access log.	1890	S-DSS-00510	B1	The SDSRV CI shall provide the capability for operations staff to select for viewing from the Data Access Log entries related to data type, source of access, or time frame.	99-0729	08/25/1999  	No Data	
52	DADS1085	6A Future	The ECS shall maintain a data access log.	1956	S-DSS-01445	B0	The SDSRV CI shall log the following when archived data is inserted, updated, deleted, or accessed:  a. User Identifier  b. Data and time of the operation performed  c. The identity of the data	99-0729	08/25/1999  	No Data	
52	DADS1085	6A Future	The ECS shall maintain a data access log.	2136	S-DSS-20045	6A	The STMGT CI shall log, to the Event Log, the successful completion of requests to retrieve data files from the archive.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	1932	S-DSS-01155	B0	The SDSRV CI shall log all updates to the Metadata Database in a Database Transaction Log.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	1944	S-DSS-01365	B0	The SDSRV CI shall provide operations staff the capability to recover the Metadata Database using the database backup and the Database Transaction Log.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	2178	S-DSS-20670	A	The STMGT CI shall log all updates to the Archive Database, in a Database Transaction Log.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	2225	S-DSS-21390	6A	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.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	2228	S-DSS-21460	A	The STMGT CI shall provide operations staff the capability to recover the contents of the File Directory in the case of file corruption.	99-0729	08/25/1999  	No Data	
53	DADS1100	Complete	The ECS shall maintain a log of all updates to the local inventory. The log shall be used to generate status reports and, in conjunction with the inventory backup, recreate the local inventory in the event of catastrophic failure.	2845	C-MSS-04010	B0	The MSS-MHW CI Local Management Server shall maintain one backup of all software and security audit trails and logs in a separate physical location.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2287	S-DSS-30165	6A	The DDIST CI shall log the occurrence of the cancellation of a Data Request in the Event Log.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2301	S-DSS-30270	6A	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.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2302	S-DSS-30275	6A	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.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2303	S-DSS-30280	6A	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.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2304	S-DSS-30285	6A	The DDIST CI shall log, to the Event Log, failures to successfully complete Electronic Distribution Requests due to transmission failures.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2307	S-DSS-30410	6A	The DDIST CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2308	S-DSS-30415	6A	The DDIST CI shall log, to the Event Log, the failure of the retrieval of a data granule.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2309	S-DSS-30420	6A	The DDIST CI shall have the capability to log, to the Event Log, the start of the processing of each Data Distribution Request.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2310	S-DSS-30425	6A	The DDIST CI shall have the capability to log, to the Event Log, the completion of the processing of each Data Distribution Request.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2312	S-DSS-30431	6A	The DDIST CI shall log, to the Event Log, changes in the status of the shipment of media associated with a Media Distribution Request.	99-0729	08/25/1999  	No Data	
54	DADS1110	6A Future	The ECS shall maintain a data distribution log.	2326	S-DSS-30670	6A	The DDIST CI shall log, to the Event Log, all occurrences of transmission failures associated with Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
55	DADS1114	6A Future:	The ECS shall maintain a  log of staging activity.	4234	S-DSS-20570	6A	The STMGT CI shall permit operators to view the progress and throughput of copy operations that are in progress.	00-0034	01/17/2000  		
55	DADS1114	6A Future:	The ECS shall maintain a  log of staging activity.	4235	S-DSS-20580	6A	The STMGT CI shall provide information on the progress of a copy operation.	00-0034	01/17/2000  		
55	DADS1114	6A Future:	The ECS shall maintain a  log of staging activity.	2135	S-DSS-20036	6A	The STMGT CI shall log events associated with staging activity and the allocation of staging resources.	99-0729	08/25/1999  	No Data	
55	DADS1114	6A Future:	The ECS shall maintain a  log of staging activity.	2303	S-DSS-30280	6A	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.	99-0729	08/25/1999  	No Data	
55	DADS1114	6A Future:	The ECS shall maintain a  log of staging activity.	2310	S-DSS-30425	6A	The DDIST CI shall have the capability to log, to the Event Log, the completion of the processing of each Data Distribution Request.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	1898	S-DSS-00620	A	The SDSRV CI shall categorize messages to the operations staff into informational, warning or error categories.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	1899	S-DSS-00630	A	The SDSRV CI shall notify operations staff of any system error or fault detected by the CI.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	1963	S-DSS-01760	IR1	The SDSRV CI shall log all detected errors, as they occur.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2134	S-DSS-20034	B0	The STMGT CI shall log, to the Event Log, all errors associated with media and media handling devices.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2139	S-DSS-20085	B0	The STMGT CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2148	S-DSS-20220	A	The STMGT CI shall notify the operations staff, select an alternate media cartridge and resume processing, if an uncorrectable error occurs during an archive file storage operation.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2151	S-DSS-20250	A	The STMGT CI shall terminate the data retrieval operation and notify the operations staff whenever the retrieval of a file fails due to an uncorrectible error.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2210	S-DSS-21330	B0	The STMGT CI shall notify operations staff whenever a device failure condition occurs.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2260	S-DSS-22170	B0	The STMGT CI shall terminate the write operation and notify the operations staff when an uncorrectable error occurs while writing to distribution media.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2307	S-DSS-30410	6A	The DDIST CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2308	S-DSS-30415	6A	The DDIST CI shall log, to the Event Log, the failure of the retrieval of a data granule.	99-0729	08/25/1999  	No Data	
58	DADS1300	Complete	The ECS shall display all faults to the system operators.	2493	S-INS-00340	A	The INGST CI shall report status on processing of an Ingest Request to the Error Log for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Metadata extraction failure  g.      Data conversion failure  h.      Data reformatting failure  i.      Failure to archive data  j.      Inability to transfer data within the specified time window  k.      Missing required request information  l.      Unauthorized Ingest Request submitter  m.      Successful archive of the data	99-0729	08/25/1999  	No Data	
59	DADS1310	Complete	The ECS shall track problems such as missing or corrupted files requiring restoration or regeneration of data.	2134	S-DSS-20034	B0	The STMGT CI shall log, to the Event Log, all errors associated with media and media handling devices.	99-0729	08/25/1999  	No Data	
59	DADS1310	Complete	The ECS shall track problems such as missing or corrupted files requiring restoration or regeneration of data.	2137	S-DSS-20046	B0	The STMGT CI shall log, to the Event Log, any failure to retrieve a requested file from the archive.	99-0729	08/25/1999  	No Data	
59	DADS1310	Complete	The ECS shall track problems such as missing or corrupted files requiring restoration or regeneration of data.	2138	S-DSS-20048	B0	The STMGT CI shall log, to the Event Log, any failure to retrieve a backup copy of a requested file from the archive.	99-0729	08/25/1999  	No Data	
59	DADS1310	Complete	The ECS shall track problems such as missing or corrupted files requiring restoration or regeneration of data.	2224	S-DSS-21380	A	In the event of storage device or archive media failure, the STMGT CI shall notify operations staff and provide appropriate information to include failed device name or media, failure code or reason and time/date of failure.	99-0729	08/25/1999  	No Data	
59	DADS1310	Complete	The ECS shall track problems such as missing or corrupted files requiring restoration or regeneration of data.	3191	C-MSS-60390	B0	The MSS Fault Management Application Service at the sites shall, for faults detected within its site, isolate, locate, and identify faults to the level of:   a. subsystem   b. equipment   c. software	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	1881	S-DSS-00377	B0	The SDSRV CI shall register its managed objects using CSS registration services.	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	1899	S-DSS-00630	A	The SDSRV CI shall notify operations staff of any system error or fault detected by the CI.	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	1963	S-DSS-01760	IR1	The SDSRV CI shall log all detected errors, as they occur.	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	2139	S-DSS-20085	B0	The STMGT CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	2307	S-DSS-30410	6A	The DDIST CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	2493	S-INS-00340	A	The INGST CI shall report status on processing of an Ingest Request to the Error Log for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Metadata extraction failure  g.      Data conversion failure  h.      Data reformatting failure  i.      Failure to archive data  j.      Inability to transfer data within the specified time window  k.      Missing required request information  l.      Unauthorized Ingest Request submitter  m.      Successful archive of the data	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	3143	C-MSS-60012	B0	The MSS Fault Management Service shall provide fault detection and isolation capabilities for each mode.	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
60	DADS1320	Complete	The ECS shall provide fault isolation information at the system and subsystem levels.	3191	C-MSS-60390	B0	The MSS Fault Management Application Service at the sites shall, for faults detected within its site, isolate, locate, and identify faults to the level of:   a. subsystem   b. equipment   c. software	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	4160	S-DSS-30020	6A	The DDIST CI shall encrypt any user provided data of a sensitive nature (e.g. passwords) before writing that data to a log.	99-1175	12/01/1999  		
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	1881	S-DSS-00377	B0	The SDSRV CI shall register its managed objects using CSS registration services.	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	1899	S-DSS-00630	A	The SDSRV CI shall notify operations staff of any system error or fault detected by the CI.	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	1963	S-DSS-01760	IR1	The SDSRV CI shall log all detected errors, as they occur.	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	2139	S-DSS-20085	B0	The STMGT CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	2307	S-DSS-30410	6A	The DDIST CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	2493	S-INS-00340	A	The INGST CI shall report status on processing of an Ingest Request to the Error Log for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Metadata extraction failure  g.      Data conversion failure  h.      Data reformatting failure  i.      Failure to archive data  j.      Inability to transfer data within the specified time window  k.      Missing required request information  l.      Unauthorized Ingest Request submitter  m.      Successful archive of the data	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	3143	C-MSS-60012	B0	The MSS Fault Management Service shall provide fault detection and isolation capabilities for each mode.	99-0729	08/25/1999  	No Data	
61	DADS1330	Complete	The ECS shall provide information to support fault isolation between ECS-unique components and external interfaces.	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	5632	S-DPL-41230	SY3	The DPIU shall populate the Data Pool inventory and warehouse from the XML file.	08-0426	09/29/2008  		
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	7704	S-DPL-60710	72	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.]	08-0426	09/29/2008  		
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	7709	S-DPL-60760	72	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.]	08-0426	09/29/2008  		
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	1906	S-DSS-00790	B0	The STMGT CI shall provide tools to analyze the performance of the storage system when such tools are supplied by the FSMS vendor.	99-0729	08/25/1999  	No Data	
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	2164	S-DSS-20480	B1	The STMGT CI shall provide operations staff the capability to perform physical inventories of archive media resident in archive storage devices.	99-0729	08/25/1999  	No Data	
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	2165	S-DSS-20510	B0	The STMGT CI shall provide operations staff with the ability to display and modify storage resource and device configuration information.	99-0729	08/25/1999  	No Data	
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	2198	S-DSS-21170	B0	The STMGT CI shall provide operations staff the capability to query the operational state (UP or DOWN) of storage devices.	99-0729	08/25/1999  	No Data	
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	2201	S-DSS-21270	B1	The STMGT CI shall provide the operations staff the capability to display information about archive storage devices, including current status, current operation, # operations completed, # errors reported, time/date of last error.	99-0729	08/25/1999  	No Data	
62	DADS1360	Complete	The ECS shall monitor the status and performance of all storage systems used.	2203	S-DSS-21274	6A	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.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2111	S-DSS-05775	B0	The SDSRV CI shall store the checksum, provided by the STMGT CI for each archived file, into the Metadata Database.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2170	S-DSS-20622	A	The STMGT CI shall compute a checksum against each file stored as a result of a storage request, and provide that checksum to the originator of the request.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2171	S-DSS-20623	A	The STMGT CI shall compute a checksum against each file retrieved as a result of a retrieval request and compare that checksum against the checksum provided in the request.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2172	S-DSS-20624	B1	The STMGT CI shall provide a mechanism to monitor checksum errors of archive media for purposes of statistical analysis.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2173	S-DSS-20627	B1	The STMGT CI shall use checksums to determine the quality of the products retrieved.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2174	S-DSS-20632	B1	The STMGT CI shall terminate the retrieval of a product if the product cannot be retrieved or fails the quality check.	99-0729	08/25/1999  	No Data	
63	DADS1370	EOC Future	The ECS shall provide a mechanism for statistically monitoring both the raw and corrected bit error rate (BER) of storage media in the archive.	2263	S-DSS-22200	B0	The STMGT CI shall return an error status to the requester in the event that the checksum calculated on a retrieved file is different than the checksum calculated for that file when it was archived.	99-0729	08/25/1999  	No Data	
64	DADS1375	6A Partial	The ECS shall support management and copying/refresh of archive media.	2149	S-DSS-20230	B1	The STMGT CI shall notify operations staff to discard source archive media after its contents have been re-created on the new media.	99-0729	08/25/1999  	No Data	
64	DADS1375	6A Partial	The ECS shall support management and copying/refresh of archive media.	2152	S-DSS-20255	B1	If an uncorrectable error occurs during retrieval operations, STMGT CI shall automatically recreate the contents on new media.	99-0729	08/25/1999  	No Data	
64	DADS1375	6A Partial	The ECS shall support management and copying/refresh of archive media.	2175	S-DSS-20634	B1	The STMGT CI shall notify the operator and automatically retrieve a local backup copy of product upon the failure of the retrieval of the primary copy of the product.	99-0729	08/25/1999  	No Data	
64	DADS1375	6A Partial	The ECS shall support management and copying/refresh of archive media.	2180	S-DSS-20740	B0	The STMGT CI shall provide operations staff the capability to restore the primary copy of a product from either the local backup copy or the offsite backup copy.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2268	S-DSS-30014	B0	The DDIST CI shall send to the requesting client a Distribution Notification that notifies the client that requested data has been transmitted in response to a "push" Electronic Distribution Request.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2304	S-DSS-30285	6A	The DDIST CI shall log, to the Event Log, failures to successfully complete Electronic Distribution Requests due to transmission failures.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2325	S-DSS-30665	B0	The DDIST CI shall initiate the re-transmission of data in the event of a transmission failure, in order to complete a request for the electronic distribution of data.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2326	S-DSS-30670	6A	The DDIST CI shall log, to the Event Log, all occurrences of transmission failures associated with Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2442	S-INS-00060	IR1	The INGST CI shall report status to the provider of a Network Ingest Request for the following:  a. File transfer failure  b. File size discrepancies  c. Invalid Data Type Identifier  d. Missing required metadata  e. Metadata parameters out of range  f. Data conversion failure  g. Failure to archive data  h. Inability to transfer data within the specified time window  i. Missing required request information  j. Successful archive of the data	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2476	S-INS-00235	A	The INGST CI shall accept ingest Status Requests from science users to determine the status of:  a.      A specified ongoing Ingest Request, previously submitted by the science user who is requesting status and identified by the ingest Request Identifier  b.      All of the user's ongoing Ingest Requests	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2477	S-INS-00240	A	The INGST CI shall determine the User Identifier for a science user submitting an ingest Status Request.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2478	S-INS-00250	A	The INGST CI shall return status on a science user's ongoing Network Ingest Requests,  based on User Identifier, to the user.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2479	S-INS-00260	A	The INGST CI shall provide science users the capability to display the status of the user's ongoing request processing.  Displayed status shall include the External Data Provider, ingest Request Identifier, total ingest data volume, and Request State.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2480	S-INS-00270	A	The INGST CI shall accept ingest Status Requests from authorized operations staff to determine the status of:  a.      A specified ongoing Ingest Request identified by ingest Request Identifier  b.      All ongoing Ingest Requests associated with a specified User Identifier  c.      All ongoing Ingest Requests	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2481	S-INS-00280	A	The INGST CI shall determine the User Identifier for an operations staff member submitting an ingest Status Request.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2482	S-INS-00290	A	The INGST CI shall authenticate the User Identifier of operations staff requesting status on all ongoing Ingest Requests.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2483	S-INS-00295	A	The INGST CI shall return an error status to the requester and log information in the Error Log if status is requested on  ongoing Ingest Requests from an unauthorized requester.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2484	S-INS-00300	A	The INGST CI shall return status on ongoing Ingest Requests to an authorized operations staff member.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2485	S-INS-00310	A	The INGST CI shall provide authorized operations staff the capability to view the status of ongoing ingest processing.  Displayed status shall include the External Data Provider, ingest Request Identifier, total ingest data volume, and Request State.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2486	S-INS-00315	A	The INGST CI shall provide the capability for authorized operations staff to select status of ongoing Ingest Request processing for viewing by means of the External Data Provider.	99-0729	08/25/1999  	No Data	
65	DADS1380	Complete	The ECS shall monitor data transfer between external (non-ECS) elements and the ECS.	2494	S-INS-00345	A	The INGST CI shall report status on the performance of ingest requests to the MSS with the following information:  a. file transfer duration  b. file processing duration  c. data insert duration	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2268	S-DSS-30014	B0	The DDIST CI shall send to the requesting client a Distribution Notification that notifies the client that requested data has been transmitted in response to a "push" Electronic Distribution Request.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2325	S-DSS-30665	B0	The DDIST CI shall initiate the re-transmission of data in the event of a transmission failure, in order to complete a request for the electronic distribution of data.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2326	S-DSS-30670	6A	The DDIST CI shall log, to the Event Log, all occurrences of transmission failures associated with Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2476	S-INS-00235	A	The INGST CI shall accept ingest Status Requests from science users to determine the status of:  a.      A specified ongoing Ingest Request, previously submitted by the science user who is requesting status and identified by the ingest Request Identifier  b.      All of the user's ongoing Ingest Requests	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2477	S-INS-00240	A	The INGST CI shall determine the User Identifier for a science user submitting an ingest Status Request.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2478	S-INS-00250	A	The INGST CI shall return status on a science user's ongoing Network Ingest Requests,  based on User Identifier, to the user.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2479	S-INS-00260	A	The INGST CI shall provide science users the capability to display the status of the user's ongoing request processing.  Displayed status shall include the External Data Provider, ingest Request Identifier, total ingest data volume, and Request State.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2480	S-INS-00270	A	The INGST CI shall accept ingest Status Requests from authorized operations staff to determine the status of:  a.      A specified ongoing Ingest Request identified by ingest Request Identifier  b.      All ongoing Ingest Requests associated with a specified User Identifier  c.      All ongoing Ingest Requests	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2481	S-INS-00280	A	The INGST CI shall determine the User Identifier for an operations staff member submitting an ingest Status Request.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2482	S-INS-00290	A	The INGST CI shall authenticate the User Identifier of operations staff requesting status on all ongoing Ingest Requests.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2483	S-INS-00295	A	The INGST CI shall return an error status to the requester and log information in the Error Log if status is requested on  ongoing Ingest Requests from an unauthorized requester.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2484	S-INS-00300	A	The INGST CI shall return status on ongoing Ingest Requests to an authorized operations staff member.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2485	S-INS-00310	A	The INGST CI shall provide authorized operations staff the capability to view the status of ongoing ingest processing.  Displayed status shall include the External Data Provider, ingest Request Identifier, total ingest data volume, and Request State.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2486	S-INS-00315	A	The INGST CI shall provide the capability for authorized operations staff to select status of ongoing Ingest Request processing for viewing by means of the External Data Provider.	99-0729	08/25/1999  	No Data	
66	DADS1390	Complete	The ECS shall monitor data transfer between components of the  ECS.	2494	S-INS-00345	A	The INGST CI shall report status on the performance of ingest requests to the MSS with the following information:  a. file transfer duration  b. file processing duration  c. data insert duration	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	4177	S-DSS-21355	6A	The STMGT CI shall have the capability to transfer data to and from D3 tape.	00-0060	01/24/2000  		
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	1842	S-DSS-00075	B0	The SDSRV CI shall accept and process valid, authenticated Data Insert Requests, from any source, via the Data Insert Request API.	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	2004	S-DSS-03002	B0	The SDSRV CI shall be capable of receiving and managing the storage of L0 - L4 Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	2091	S-DSS-05610	B0	The SDSVR CI shall notify the operator whenever requested Level 0 data, or equivalent Level 1A data, cannot be retrieved or recreated.	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	2119	S-DSS-05800	B0	The SDSRV CI shall have the capability to restore lost or unreadable Level 1A or Level 0 data from corresponding replacement products received from EDOS.	99-0729	08/25/1999  	No Data	
67	DADS1450	6A	The ECS shall, upon detection that L0 data has been lost, generate a request for a replacement product from EDOS, dispatch the request, and ingest the replacement product.	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
68	DADS1470	6A Partial	The ECS shall manage element resource utilization.	1935	S-DSS-01190	B1	The SDSRV CI shall provide the capability for operations staff to view the resources used and allocated by a client.	99-0729	08/25/1999  	No Data	
68	DADS1470	6A Partial	The ECS shall manage element resource utilization.	2181	S-DSS-20810	6A	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.	99-0729	08/25/1999  	No Data	
68	DADS1470	6A Partial	The ECS shall manage element resource utilization.	2203	S-DSS-21274	6A	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.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	1836	S-DSS-00040	B1	The SDSRV CI shall provide operations staff the capability to view the entries in the Service Request List.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	1837	S-DSS-00052	B1	The SDSRV CI shall process each Service Request, in order, according to its relative priority in the Service Request List.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	1839	S-DSS-00057	B1	The SDSRV CI shall maintain, for each entry in the Service Request List, an indicator that determines whether the associated Service Request is being processed or is waiting to be processed.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	1861	S-DSS-00210	B1	The SDSRV CI shall provide operations staff the capability to update the Priority Information for any entry in the Service Request List.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	1927	S-DSS-01090	B1	The SDSRV CI shall maintain a Service Request List that lists received Service Requests, associated Priority Information, and all other information required to process each request.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	1981	S-DSS-01970	B0	The SDSRV CI shall have the capacity to accept a daily average of two (2) percent of the daily data throughput as expedited data for use in mission functions of calibration and anomalies.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2166	S-DSS-20550	6A	The STMGT CI shall provide operations staff a mechanism to display/view storage system configuration parameters which affect storage system performance.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2203	S-DSS-21274	6A	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.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2233	S-DSS-21520	B1	The SDSRV CI shall be capable of processing a combined maximum number of Data Requests per hour (across ECS) from the Data Management Subsystem and/or the Client Subsystem as derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2234	S-DSS-21570	A	The SDSRV CI shall have the capability to process Data Insert Requests at a rate sufficient to support the archiving of data volumes as derived from Tables C2 and C6 in the Appendix C of the F&PRS.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2273	S-DSS-30090	B1	The DDIST CI shall provide the capability to give the processing of Electronic Distribution Requests priority over the processing of Media Distribution Requests.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2274	S-DSS-30095	B0	The DDIST CI shall maintain a queue of Distribution Requests that are waiting to be processed, and shall maintain, for each queued request, the request type, user, priority, and all other information necessary to process the request.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2291	S-DSS-30180	A	The DDIST CI shall process queued Distribution Requests in order, according to their assigned Priority Information.	99-0729	08/25/1999  	No Data	
69	DADS1472	6A 6B EOC	The ECS shall contain the capacity to respond to contingencies and peak loads.	2576	S-INS-01000	A	The ICLHW CI at the LaRC DAAC shall be capable of ingesting data from the SDPF at a maximum daily rate that is three times the nominal rate specified in Table E-3 of Appendix E of the current version of 304-CD-002 for Release A.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	1994	S-DSS-02900	A	The SDSRV CI shall provide the data type services as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	1995	S-DSS-02901	5B	The SDSRV CI shall provide the capability to subset data within a Landsat subinterval granule based on floating scenes.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	1996	S-DSS-02902	5B	The SDSRV CI shall provide the capability to subset data within a Landsat subinterval granule based on Spectral band.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	1997	S-DSS-02903	B1	The SDSRV CI shall provide the capability to subset, subsample, or average data within a granule based on Time for products as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	1998	S-DSS-02904	B0	The SDSRV CI shall provide the capability to subset, subsample, or average data within a granule based on WRS for products as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	2003	S-DSS-02909	B0	The SDSRV CI shall provide the capability to subset MODIS Level 1B data by parameter.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	2096	S-DSS-05660	B0	The SDSRV CI shall provide the capability to extract ASCII data from EOS-HDF data granules containing ASCII data and direct the distribution of the extracted data, as specified in valid Data Distribution Requests.	99-0729	08/25/1999  	No Data	
70	DADS1475	Future	The ECS shall provide tools to the users to perform:  a. Format conversion of HDF-EOS tabular data to ASCII  or binary format  b. Subsetting of HDF-EOS grid, swath and profile data	2097	S-DSS-05670	B0	The SDSRV CI shall provide the capability to extract binary data from EOS-HDF data granules containing binary data and direct the distribution of the extracted data, as specified in valid Data Distribution Requests.	99-0729	08/25/1999  	No Data	
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	5797	S-DPL-21400	SY2	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 	08-0426	09/29/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9017	S-DPL-08160	7.22	The DPL CI shall provide an inventory validation function. [NOTE: This rewords and replaces S-DPL-60010.]	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9018	S-DPL-08170	7.22	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.]	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9019	S-DPL-08180	7.22	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.  	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9020	S-DPL-08190	7.22	The Data Pool Inventory Validation shall log each identified discrepancy between the DPL and AIM inventories.	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9021	S-DPL-08200	7.22	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.] 	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9022	S-DPL-08210	7.22	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.]  	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9023	S-DPL-08480	7.22	DELETED	08-0406	09/11/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9075	S-DPL-08415	7.22	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.]	08-0496	11/20/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	9076	S-DPL-08455	7.22	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.]  	08-0496	11/20/2008  		
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	1840	S-DSS-00060	IR1	The SDSRV CI shall acknowledge the receipt of Service Requests from local and remote clients.	99-0729	08/25/1999  	No Data	
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	1891	S-DSS-00520	A	The SDSRV CI shall return a successful completion status to the provider of data only after all data and associated Metadata has been successfully stored.	99-0729	08/25/1999  	No Data	
71	DADS1510	Complete	The ECS shall ensure that metadata is maintained on all products that are stored in the ECS.	2098	S-DSS-05710	B0	The SDSRV CI shall notify the requesting client that a Data Insert Request has completed successfully once the storage of the associated data and metadata has been confirmed.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	1902	S-DSS-00715	B0	The SDSRV CI shall provide users the capability to insert and retrieve data, within a given DAAC, without requiring the user to specify the location of the data within the DAAC.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2150	S-DSS-20240	A	If the end of the archive media is encountered before completing a write operation, the STMGT CI shall select new media and complete the write operation with the new archive media.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2187	S-DSS-21060	A	The STMGT CI shall provide external CIs the capability to write information into files resident on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2188	S-DSS-21070	A	The STMGT CI shall provide external CIs the capability to read files resident on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2189	S-DSS-21080	A	The STMGT CI shall provide external CIs the capability to delete files resident on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2190	S-DSS-21090	A	The STMGT CI shall provide external CIs the capability to rename files resident on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2191	S-DSS-21100	A	The STMGT CI shall provide external CIs the capability to obtain the file name and file size for files resident on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2192	S-DSS-21110	A	The STMGT CI shall provide external CIs the capability to allocate storage on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2193	S-DSS-21120	A	The STMGT CI shall provide external CIs the capability to deallocate storage on staging devices in the WKSHW CI.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2217	S-DSS-21360	A	The STMGT CI shall use a hierarchy of disk and/or tape storage devices and associated storage media to store data.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2220	S-DSS-21370	A	The STMGT CI shall use, where appropriate, a hierarchy of disk and/or tape storage devices and associated storage media to retrieve data.	99-0729	08/25/1999  	No Data	
72	DADS1520	Complete	The ECS shall provide a file storage management capability that supports a hierarchy of devices and media, with location-transparent access to the files.	2264	S-DSS-22210	B0	The STMGT CI shall provide a file management system that utilizes automatic tape libraries for the storage and retrieval of files.	99-0729	08/25/1999  	No Data	
73	DADS1530	Complete	The ECS shall maintain a  file directory of all files archived under its control.	5632	S-DPL-41230	SY3	The DPIU shall populate the Data Pool inventory and warehouse from the XML file.	08-0426	09/29/2008  		
73	DADS1530	Complete	The ECS shall maintain a  file directory of all files archived under its control.	5801	S-DPL-21800	SY2	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.	08-0426	09/29/2008  		
73	DADS1530	Complete	The ECS shall maintain a  file directory of all files archived under its control.	7371	S-DPL-18165	SY6	The Data Pool Insert Service shall transfer an ingested granule that resides in the Data Pool in a non-public location to the public Data Pool when processing a request for inserting that granule into the public Data Pool, to include the addition of any necessary Data Pool inventory and warehouse information and browse files.	08-0426	09/29/2008  		
73	DADS1530	Complete	The ECS shall maintain a  file directory of all files archived under its control.	2225	S-DSS-21390	6A	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.	99-0729	08/25/1999  	No Data	
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	8918	S-DPL-08700	7.22	The Data Pool On-line Archive Recovery shall return an exit code indicating whether it encountered an error or not.	08-0426	09/29/2008  		
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	9070	S-DPL-08605	7.22	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).	08-0426	09/29/2008  		
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	9071	S-DPL-08606	7.22	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).	08-0426	09/29/2008  		
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	9083	S-DPL-08646	7.22	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.	09-0018	02/05/2009  		
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	1932	S-DSS-01155	B0	The SDSRV CI shall log all updates to the Metadata Database in a Database Transaction Log.	99-0729	08/25/1999  	No Data	
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	1944	S-DSS-01365	B0	The SDSRV CI shall provide operations staff the capability to recover the Metadata Database using the database backup and the Database Transaction Log.	99-0729	08/25/1999  	No Data	
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	2227	S-DSS-21450	A	The STMGT CI shall provide operations staff the capability to backup the contents of the File Directory.	99-0729	08/25/1999  	No Data	
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	2228	S-DSS-21460	A	The STMGT CI shall provide operations staff the capability to recover the contents of the File Directory in the case of file corruption.	99-0729	08/25/1999  	No Data	
74	DADS1540	Complete	The ECS shall provide, in case of corruption or catastrophic failure, capabilities for recovering the archive  file directory.	9077	S-DPL-08645	7.22	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.	08-0496	11/20/2008  		
75	DADS1550	Complete	The ECS operations/systems personnel shall be able to access, list, or modify the contents of the archive  file directory in a special privileged mode.	1946	S-DSS-01385	B0	The SDSRV CI shall restrict the capability to update Granule Inventory Metadata that is not user-searchable to the operations staff only.	99-0729	08/25/1999  	No Data	
75	DADS1550	Complete	The ECS operations/systems personnel shall be able to access, list, or modify the contents of the archive  file directory in a special privileged mode.	2073	S-DSS-04590	A	The SDSRV CI shall provide the operations staff the capability to modify all Granule Inventory Metadata for any specified data granules in a special privileged mode.	99-0729	08/25/1999  	No Data	
75	DADS1550	Complete	The ECS operations/systems personnel shall be able to access, list, or modify the contents of the archive  file directory in a special privileged mode.	2121	S-DSS-05825	B0	The SDSRV CI shall provide the operations staff the capability to display and list all Granule Inventory Metadata.	99-0729	08/25/1999  	No Data	
75	DADS1550	Complete	The ECS operations/systems personnel shall be able to access, list, or modify the contents of the archive  file directory in a special privileged mode.	2226	S-DSS-21420	A	The STMGT CI shall provide authorized operations staff a mechanism to display selected records in the File Directory.	99-0729	08/25/1999  	No Data	
76	DADS1610	Complete	The ECS file storage management capability shall provide for continued performance, albeit in a degraded mode, when a device (e.g., disk or cartridge drive, operator's console) fails.	7298	S-DPL-17630	SY6	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.] 	08-0426	09/29/2008  		
76	DADS1610	Complete	The ECS file storage management capability shall provide for continued performance, albeit in a degraded mode, when a device (e.g., disk or cartridge drive, operator's console) fails.	7631	S-DPL-17565	SY6	The Data Pool Ingest Service shall suspend dispatching archive write operations for an archive while an alert is pending for it.	08-0426	09/29/2008  		
76	DADS1610	Complete	The ECS file storage management capability shall provide for continued performance, albeit in a degraded mode, when a device (e.g., disk or cartridge drive, operator's console) fails.	2148	S-DSS-20220	A	The STMGT CI shall notify the operations staff, select an alternate media cartridge and resume processing, if an uncorrectable error occurs during an archive file storage operation.	99-0729	08/25/1999  	No Data	
76	DADS1610	Complete	The ECS file storage management capability shall provide for continued performance, albeit in a degraded mode, when a device (e.g., disk or cartridge drive, operator's console) fails.	2157	S-DSS-20380	A	The STMGT CI shall provide the capability to continue operations in the event of a failure of a tape drive or a disk drive.	99-0729	08/25/1999  	No Data	
76	DADS1610	Complete	The ECS file storage management capability shall provide for continued performance, albeit in a degraded mode, when a device (e.g., disk or cartridge drive, operator's console) fails.	2224	S-DSS-21380	A	In the event of storage device or archive media failure, the STMGT CI shall notify operations staff and provide appropriate information to include failed device name or media, failure code or reason and time/date of failure.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4861	S-OMS-01280	SY3	The Order Manager shall allow operators to suspend the submission of requests to the PDS in total as well as by media type.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4863	S-OMS-01290	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4865	S-OMS-01320	SY3	The Order Manager shall allow operators to suspend the submission of requests to the SDSRV in total as well as by media type.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4867	S-OMS-01330	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4870	S-OMS-01360	SY3	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	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4871	S-OMS-01370	SY3	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  	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4872	S-OMS-01380	SY3	The Order Manager shall generate a default name for the log file compatible with ECS log file names.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4873	S-OMS-01390	SY3	The Order Manager shall append output to the log file if it already exists.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4874	S-OMS-01400	SY3	The Order Manager shall create the log file if it does not already exist.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4875	S-OMS-01410	SY3	Different instances of the Order Manager shall be able to operate in different modes concurrently.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4876	S-OMS-01420	SY3	The Order Manager startup scripts shall prevent the operation of more than one Order Manager on the same platform in the same mode.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4877	S-OMS-01425	SY3	The Order Manager startup scripts shall prevent the operation of more than one Order Manager in the same mode within the same DAAC.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4879	S-OMS-01440	SY3	The Order Manager shall allow an operator to shut it down.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4890	S-OMS-02070	SY3	It shall be possible to submit data distribution requests in multiple modes concurrently via the Order Management Service Command Line Utility. [OSS]	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4891	S-OMS-02080	SY3	It shall be possible to submit multiple data distribution requests in the same mode concurrently via the Order Management Service Command Line Utility. [OSS]	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4892	S-OMS-03010	SY3	The Order Management Service shall provide an Operator GUI.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4893	S-OMS-03020	SY3	The Order Management Operator GUI shall be accessible via the web browsers in the ECS configuration baseline.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4894	S-OMS-03030	SY3	The Order Management Operator GUI shall permit an operator to suspend and resume the processing of new data distribution requests.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4895	S-OMS-03040	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4896	S-OMS-03050	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4897	S-OMS-03055	SY3	The Order Management Operator GUI shall permit an operator to suspend and resume the sending of e-mail notifications.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4898	S-OMS-03060	SY3	The Order Management Operator GUI shall permit an operator to view the current setting of all suspension options.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4899	S-OMS-03070	SY3	The Order Management Operator GUI shall permit an operator to monitor for pending or held operator interventions.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4900	S-OMS-03080	SY3	The Order Management Operator GUI shall permit an operator to select and view a pending or held operator intervention.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4901	S-OMS-03082	SY3	The Order Management Operator GUI shall permit an operator to select a pending operator intervention, annotate it and place it on hold.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4902	S-OMS-03084	SY3	The Order Management Operator GUI shall permit an operator to select a held operator request, update its annotation, and retain it on hold.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4903	S-OMS-03090	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4904	S-OMS-03100	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4905	S-OMS-03110	SY3	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)	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4906	S-OMS-03120	SY3	The Order Management Operator GUI shall permit an operator to fail a data distribution request that was placed on hold. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4909	S-OMS-03140	SY3	The Order Management Operator GUI shall permit an operator to assign a request that was placed on hold to a different media type.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4910	S-OMS-03145	SY3	The Order Management Operator GUI shall permit an operator to fail a granule that exceeded the capacity of the media type. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4912	S-OMS-03160	SY3	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]	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4913	S-OMS-03170	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4914	S-OMS-03180	SY3	The operator shall be able to configure a target granule count limit for requests with and without subsetting, independent of media type.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4915	S-OMS-03182	SY3	The Order Management Operator GUI shall support the pacing of partitioned requests over an extended time period based on operator input.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4916	S-OMS-03210	SY3	The Order Management Operator GUI shall save the new requests resulting from partitioning in the Order Management Database.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4917	S-OMS-03215	SY3	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.]	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4918	S-OMS-03216	SY3	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. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4919	S-OMS-03220	SY3	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	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4920	S-OMS-03240	SY3	The Order Management Operator GUI shall permit an operator to accept the granules that were skipped as failed.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4921	S-OMS-03242	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4922	S-OMS-03244	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4923	S-OMS-03250	SY3	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'.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4924	S-OMS-03260	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4925	S-OMS-03262	SY3	[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'.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4926	S-OMS-03264	SY3	[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).	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4927	S-OMS-03270	SY3	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.]	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4928	S-OMS-03310	SY3	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.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4939	S-OMS-03420	SY3	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). 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4940	S-OMS-03430	SY3	The Order Management GUI shall allow an operator to select a past operator intervention and view it. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4941	S-OMS-03440	SY3	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). 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4942	S-OMS-03450	SY3	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. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4943	S-OMS-03460	SY3	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	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4944	S-OMS-03470	SY3	The Order Management GUI shall support concurrent operation in multiple modes.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4945	S-OMS-03480	SY3	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. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4946	S-OMS-03485	SY3	The Order Management GUI shall display the mode in which it is operating. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4947	S-OMS-03490	SY3	The capabilities of the Order Management GUI shall be accessible to multiple operators on multiple platforms concurrently. 	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4948	S-OMS-03500	SY3	The Order Management GUI shall be accessible whether or not the Order Manager for that mode is operating or not.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4950	S-OMS-03510	SY3	The Order Management GUI shall allow an operator to monitor whether the Order Manager for the designated mode is operating or not.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4957	C-MSS-75925	SY3	The MSS CI shall allow operators to display and filter orders by the new MSS request status values.	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	4958	C-MSS-75926	SY3	The MSS CI shall recognize the following new status values as indicating that the request has been terminated:  a. Partitioned	02-1045	12/04/2002  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	5921	S-OMS-03025	SY4	The Order Management Operator GUI shall display the external request ID in the screens displaying request and order details.	03-0682	10/09/2003  		
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	1863	S-DSS-00222	B0	The SDSRV CI shall provide the operations staff the capability to assign, for each data type, an Archive ID which maps to a physical storage location for that data type.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	1864	S-DSS-00226	B1	The SDSRV CI shall provide operations staff the capability to display the file name, status, size, archive location, and back up locations associated with a data product.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	1881	S-DSS-00377	B0	The SDSRV CI shall register its managed objects using CSS registration services.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2151	S-DSS-20250	A	The STMGT CI shall terminate the data retrieval operation and notify the operations staff whenever the retrieval of a file fails due to an uncorrectible error.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2164	S-DSS-20480	B1	The STMGT CI shall provide operations staff the capability to perform physical inventories of archive media resident in archive storage devices.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2165	S-DSS-20510	B0	The STMGT CI shall provide operations staff with the ability to display and modify storage resource and device configuration information.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2166	S-DSS-20550	6A	The STMGT CI shall provide operations staff a mechanism to display/view storage system configuration parameters which affect storage system performance.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2181	S-DSS-20810	6A	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.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2197	S-DSS-21160	B0	The STMGT CI shall provide operations staff the capability to set the operational state (UP or DOWN) of storage devices.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2198	S-DSS-21170	B0	The STMGT CI shall provide operations staff the capability to query the operational state (UP or DOWN) of storage devices.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2201	S-DSS-21270	B1	The STMGT CI shall provide the operations staff the capability to display information about archive storage devices, including current status, current operation, # operations completed, # errors reported, time/date of last error.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2203	S-DSS-21274	6A	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.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2256	S-DSS-22130	B0	The STMGT CI shall provide the capability to  limit access to Data in the user pull area to the data requester and the operations staff.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2257	S-DSS-22140	B0	The STMGT CI shall monitor the percentage of space utilized in the user pull area.  	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2258	S-DSS-22150	B0	The STMGT CI shall provide a mechanism for the operations staff to view/display the percentage of space utilized in the user pull area.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2259	S-DSS-22160	B0	The STMGT CI shall notify the operations staff if the percent utilization in the user pull area exceeds a specified threshold.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2260	S-DSS-22170	B0	The STMGT CI shall terminate the write operation and notify the operations staff when an uncorrectable error occurs while writing to distribution media.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2278	S-DSS-30125	B0	The DDIST CI shall provide the capability for operations staff to list Media Distribution Requests according to media type.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2280	S-DSS-30135	B0	The DDIST CI shall provide the capability for operations staff to list Distribution Requests according to distribution status.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2289	S-DSS-30171	Complete	The DDIST CI shall respond to Status Requests from operations staff with a Request State indicating that the specified Distribution Request is "pending", "staging", or "transferring".	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	2324	S-DSS-30660	A	The DDIST CI shall provide the capability to resume the processing of a Media Distribution Request, using new media or an alternate device, in the event of a failure with the distribution media or its associated device.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	3204	C-MSS-66001	B0	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components      a. network components         1.  routers         2.  links         3.  bridges         4.  gateways      b. hosts      c. operating systems      d. peripherals      e. databases     f. ECS applications.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	3205	C-MSS-66002	B0	The MSS Performance Management Applications Service shall have the capability to monitor each mode for performance statistics.	99-0729	08/25/1999  	No Data	
77	DADS1620	6A Partial	The ECS at each DAAC shall provide tools for operations/systems/maintenance personnel to monitor performance, carry out maintenance, and alter operating parameters.	3217	C-MSS-66100	IR1	The MSS performance management application service shall be capable of retrieving the following data for all hosts:  a. total CPU utilization  b. memory utilization  c. physical disk i/o's  d. disk storage size  e. disk storage used  f. number of active processes  g. length of run queue  h. network i/o's (packets)  i. network errors	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2148	S-DSS-20220	A	The STMGT CI shall notify the operations staff, select an alternate media cartridge and resume processing, if an uncorrectable error occurs during an archive file storage operation.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2151	S-DSS-20250	A	The STMGT CI shall terminate the data retrieval operation and notify the operations staff whenever the retrieval of a file fails due to an uncorrectible error.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2152	S-DSS-20255	B1	If an uncorrectable error occurs during retrieval operations, STMGT CI shall automatically recreate the contents on new media.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2158	S-DSS-20390	A	The STMGT CI shall provide tools for recovering data from failed archive media when such tools are supplied by the vendor of the supporting FSMS product(s).	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2159	S-DSS-20400	A	The STMGT CI shall provide tools for recovering data from failed archive devices, when such tools are supplied by either the vendor of the supporting FSMS product(s) or by the vendor of the affected hardware.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2161	S-DSS-20420	A	The STMGT CI shall be capable of producing a backup copy of designated EOS data.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2176	S-DSS-20650	B0	The STMGT CI shall provide operations staff the capability to specify the products to be backed up at both local and offsite archives.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2177	S-DSS-20660	B0	The STMGT CI shall provide operations staff the capability to restore backups of specified data holdings.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2180	S-DSS-20740	B0	The STMGT CI shall provide operations staff the capability to restore the primary copy of a product from either the local backup copy or the offsite backup copy.	99-0729	08/25/1999  	No Data	
78	DADS1630	Complete	The ECS at each DAAC shall provide tools for recovery of data from failed media and devices.	2324	S-DSS-30660	A	The DDIST CI shall provide the capability to resume the processing of a Media Distribution Request, using new media or an alternate device, in the event of a failure with the distribution media or its associated device.	99-0729	08/25/1999  	No Data	
79	DADS1640	EOC Partial	The ECS shall support the number of files derivable from Appendix C, with the ability to expand to match growth.	2232	S-DSS-21510	B1	The STMGT CI shall have the capability to expand its storage capacity by 200% with no change to its architecture or design.	99-0729	08/25/1999  	No Data	
79	DADS1640	EOC Partial	The ECS shall support the number of files derivable from Appendix C, with the ability to expand to match growth.	2405	S-DSS-80600	B0	The DRPHW CI at the GSFC DAAC shall have the capacity to store 15027K files.	99-0729	08/25/1999  	No Data	
79	DADS1640	EOC Partial	The ECS shall support the number of files derivable from Appendix C, with the ability to expand to match growth.	2406	S-DSS-80601	B0	The DRPHW CI at the LaRC DAAC shall have the capacity to store 3561K files.	99-0729	08/25/1999  	No Data	
79	DADS1640	EOC Partial	The ECS shall support the number of files derivable from Appendix C, with the ability to expand to match growth.	2407	S-DSS-80602	B0	The DRPHW CI at the EDC DAAC shall have the capacity to store 8506K files.	99-0729	08/25/1999  	No Data	
79	DADS1640	EOC Partial	The ECS shall support the number of files derivable from Appendix C, with the ability to expand to match growth.	2408	S-DSS-80603	B0	The DRPHW CI at the NSIDC DAAC shall have the capacity to store 1437K files.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	5616	S-DPL-41120	SY3	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].	08-0426	09/29/2008  		
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	5775	S-DPL-20200	SY2	The Data Pool Insert Service shall allow an operator to specify, as configuration items, the mapping of ESDTs to Data Pool Collection groups.	08-0426	09/29/2008  		
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	1923	S-DSS-00940	B0	The SDSRV CI shall direct the retrieval and distribution of the data files, associated with each granule requested in a valid Data Request, using the Logical File Location for each file.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2048	S-DSS-04365	B0	The SDSRV CI shall maintain Collection Metadata, for standard products, containing key organizations and personnel for all product-related DAACs, ADCs, and ODCs.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2050	S-DSS-04372	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Navigation Data, including Spacecraft Orbit and Attitude Data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2051	S-DSS-04374	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Browse Data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2052	S-DSS-04375	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Ancillary Data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2053	S-DSS-04378	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related QA and validation Data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2058	S-DSS-04400	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Calibration Data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2059	S-DSS-04420	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Instrument Engineering Data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2060	S-DSS-04450	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Production History Data, including data generation software and its associated parameters and input data.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2061	S-DSS-04470	A	The SDSRV CI shall store and maintain Granult Inventory Metadata that identifies the data production facility for the product.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2062	S-DSS-04480	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related QA Statistics.	99-0729	08/25/1999  	No Data	
81	DADS1780	Complete	The ECS shall provide the capability to store as a single entity logically grouped sets of data.	2063	S-DSS-04490	B1	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related reference documentation.	99-0729	08/25/1999  	No Data	
82	DADS1790	Complete	The ECS shall periodically verify that all data sets are present and accounted for.	1900	S-DSS-00695	B1	The SDSRV CI shall provide the capability to receive directories from the STMGT of all data stored by the STMGT.	99-0729	08/25/1999  	No Data	
82	DADS1790	Complete	The ECS shall periodically verify that all data sets are present and accounted for.	1945	S-DSS-01375	B1	The SDSRV CI shall provide the capability to compare directories, received from the STMGT CI, with Granule Inventory Metadata.	99-0729	08/25/1999  	No Data	
82	DADS1790	Complete	The ECS shall periodically verify that all data sets are present and accounted for.	2154	S-DSS-20361	B1	The STMGT CI shall have the capability to provide the SDSRV CI directories, of all stored data files, indexed by Logical File Location.	99-0729	08/25/1999  	No Data	
82	DADS1790	Complete	The ECS shall periodically verify that all data sets are present and accounted for.	2225	S-DSS-21390	6A	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.	99-0729	08/25/1999  	No Data	
83	DADS1791	Complete	The ECS shall have the capability to mount archival media via automated means.	2140	S-DSS-20095	B0	The STGMT CI shall have the capability to automatically mount archive media into storage devices.	99-0729	08/25/1999  	No Data	
83	DADS1791	Complete	The ECS shall have the capability to mount archival media via automated means.	2147	S-DSS-20180	B0	The STMGT CI shall have the capability to automatically dismount archive media from storage devices.	99-0729	08/25/1999  	No Data	
84	DADS1795	Complete	The ECS shall update internal file directories with the unique Data set ID.	1851	S-DSS-00144	B0	The SDSRV CI shall assign a unique Granule ID to each granule of data stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
84	DADS1795	Complete	The ECS shall update internal file directories with the unique Data set ID.	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
84	DADS1795	Complete	The ECS shall update internal file directories with the unique Data set ID.	2039	S-DSS-04021	B0	The SDSRV CI shall store a granule's Granule Inventory Metadata into the Metadata Database when the data file(s) for the granule is successfully stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
84	DADS1795	Complete	The ECS shall update internal file directories with the unique Data set ID.	2064	S-DSS-04515	B0	The SDSRV CI shall assign a unique Logical File Location to each data file specified by a valid Data Insert Request.	99-0729	08/25/1999  	No Data	
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	5640	S-DPL-41300	SY3	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.	08-0426	09/29/2008  		
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	2039	S-DSS-04021	B0	The SDSRV CI shall store a granule's Granule Inventory Metadata into the Metadata Database when the data file(s) for the granule is successfully stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	2064	S-DSS-04515	B0	The SDSRV CI shall assign a unique Logical File Location to each data file specified by a valid Data Insert Request.	99-0729	08/25/1999  	No Data	
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	2065	S-DSS-04517	B0	The SDSRV CI shall direct the STMGT CI to archive data files in locations specified by each file's assigned Logical File Location.	99-0729	08/25/1999  	No Data	
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	2155	S-DSS-20365	6A	The STMGT CI shall store each data file in the location specified by the Logical File Location provided by the SDSRV CI.	99-0729	08/25/1999  	No Data	
85	DADS1800	Complete	The ECS shall maintain data storage inventories defining the physical location of files.	2225	S-DSS-21390	6A	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.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	1851	S-DSS-00144	B0	The SDSRV CI shall assign a unique Granule ID to each granule of data stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2039	S-DSS-04021	B0	The SDSRV CI shall store a granule's Granule Inventory Metadata into the Metadata Database when the data file(s) for the granule is successfully stored by the STMGT CI.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2064	S-DSS-04515	B0	The SDSRV CI shall assign a unique Logical File Location to each data file specified by a valid Data Insert Request.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2065	S-DSS-04517	B0	The SDSRV CI shall direct the STMGT CI to archive data files in locations specified by each file's assigned Logical File Location.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2114	S-DSS-05790	B0	The SDSRV CI at the GSFC DAAC shall have the capability to store Inventory Metadata for 8963 granules per day.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2115	S-DSS-05791	B0	The SDSRV CI at the LaRC DAAC shall have the capability to store Inventory Metadata for 4331 granules per day.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2116	S-DSS-05792	B0	The SDSRV CI at the EDC DAAC shall have the capability to store Inventory Metadata for 5356 granules per day.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2117	S-DSS-05793	B0	The SDSRV CI at the NSIDC DAAC shall have the capability to store Inventory Metadata for 1125 granules per day.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2155	S-DSS-20365	6A	The STMGT CI shall store each data file in the location specified by the Logical File Location provided by the SDSRV CI.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2225	S-DSS-21390	6A	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.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2409	S-DSS-80605	B0	The DRPHW CI at the GSFC DAAC shall have the capacity to store 5009K Inventory Metadata entries.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2410	S-DSS-80606	B0	The DRPHW CI at the LaRC DAAC shall have the capacity to store 1187K Inventory Metadata entries.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2411	S-DSS-80607	B0	The DRPHW CI at the EDC DAAC shall have the capacity to store 2764K Inventory Metadata entries.	99-0729	08/25/1999  	No Data	
86	DADS1805	EOC Partial	The ECS shall provide an inventory system capable of the following:  a. Accepting the number of new inventory entries, one per granule, for the number of granules per day as specified in Appendix C  b. Uniquely identifying each data granule  c. Tracking the physical location of each data granule	2412	S-DSS-80608	B0	The DRPHW CI at the NSIDC DAAC shall have the capacity to store 479K Inventory Metadata entries.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	8969	S-AIM-00360	7.22	The AIM CI shall log each file that failed checksum verification during a tape archive repair.	08-0406	09/11/2008  		
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	1923	S-DSS-00940	B0	The SDSRV CI shall direct the retrieval and distribution of the data files, associated with each granule requested in a valid Data Request, using the Logical File Location for each file.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	1924	S-DSS-00965	B0	The SDSRV CI shall provide the capability to direct the retrieval and distribution of any data granules listed in the Granule Inventory Metadata, as specified by valid Data Request.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2118	S-DSS-05795	B0	The SDSRV CI shall access the Granule Inventory Metadata, for each granule specified in a Data Request, in order to determine the Logical File Location for each of the granule's constituent files.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
87	DADS1806	Complete	The ECS shall provide the capability of retrieving any data granule stored in the archives.	2169	S-DSS-20620	A	The STMGT CI shall be capable of retrieving any stored data file specified by the file's unique Logical File Location.	99-0729	08/25/1999  	No Data	
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4684	S-SSS-10020	SY3	The NSBRV CI shall store bundling order information persistently. 	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4685	S-SSS-10030	SY3	The NSBRV CI shall assign a unique identification to each bundling order and display the ID to the operator.  	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4699	S-SSS-10160	SY3	The NSBRV CI shall support bundle completion criteria that include a minimum bundle size, a minimum bundle granule count, and a maximum bundle age. 	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4723	S-SSS-10350	SY3	The NSBRV CI shall preserve the id of a bundling order when it is updated.	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4724	S-SSS-10360	SY3	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.	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4732	S-SSS-10060	SY3	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.]	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4734	S-SSS-10400	SY3	The NSBRV CI shall submit all ECS data distribution requests to the Order Management Service.  [Note, currently the NSBRV uses the SCLI].	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4744	S-OMS-05110	SY3	The Order Management Service shall accept bundled data distribution requests.	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4746	S-OMS-05210	SY3	The Order Manager shall be able to recognize when a data distribution request is bundled, i.e., references a bundling order.	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4747	S-OMS-05220	SY3	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.] 	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4748	S-OMS-05250	SY3	The Order Manager shall check a bundle against the completion criteria of the related bundling order when adding granules to a bundle. 	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4749	S-OMS-05260	SY3	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]	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4750	S-OMS-05270	SY3	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.	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4754	S-OMS-05330	SY3	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.] 	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4755	S-OMS-05340	SY3	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.	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	4756	S-OMS-05510	SY3	The Order Management Service Command Line Utility shall allow the submission of data distribution requests that reference bundling orders. [OSS]	02-1045	12/04/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	5403	S-SSS-00015	SY2	The NSBRV CI shall store subscription information persistently. 	02-1088	12/18/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	5475	S-SSS-00590	SY2	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.	02-1088	12/18/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	5476	S-SSS-00600	SY2	The NSBRV CI shall allow the operator to filter the subscription list by user id, collection name, and current status.	02-1088	12/18/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	5477	S-SSS-00610	SY2	The NSBRV CI shall allow the operator to sort the subscription list by subscription id, user id, collection name, expiration date, and current status.	02-1088	12/18/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	5478	S-SSS-00620	SY2	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.	02-1088	12/18/2002  		
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	1045	C-CSS-40180	A	The Subscription Service shall provide the capability for authorized users to obtain a list of the stored Subscriptions.	99-0729	08/25/1999  	No Data	
88	DADS2160	Complete SY2	The ECS shall maintain a list of standing orders.	1845	S-DSS-00100	B0	The SDSRV CI shall provide the operations staff the capability to set, at subsystem startup, a threshold for the number of Service Requests that can be accepted and processed asynchronously.	99-0729	08/25/1999  	No Data	
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4790	C-DMS-39010	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4791	C-DMS-39030	SY3	The V0 Gateway shall not retry submission of a request if the Order Management Service returns an error.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4793	S-OMS-00010	SY3	The Order Management Service shall accept data distribution requests.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4797	S-OMS-00130	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4798	S-OMS-00140	SY3	The Order Management Service shall accept an optional valid MSS user profile identifier (including ECSGuest) for a distribution request.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4799	S-OMS-00150	SY3	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] 	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4800	S-OMS-00160	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4801	S-OMS-00165	SY3	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').]	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4812	S-OMS-00270	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4813	S-OMS-00280	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4820	S-OMS-00340	SY3	It shall be possible to run different instances of ECS applications that use the Order Management Service in different modes concurrently.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4821	S-OMS-00350	SY3	The Order Management Service shall be multi-thread safe, capable of accepting distribution requests concurrently from multiple threads in the same client process.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4822	S-OMS-01010	SY3	The Order Manager shall process new data distribution requests.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4823	S-OMS-01020	SY3	The Order Manager shall process data distribution requests that were released from hold by the operator.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4824	S-OMS-01030	SY3	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.]  	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4825	S-OMS-01032	SY3	The Order Manager shall support pacing a set of distribution requests. [See requirement S-OMS-03082 for the purpose.]  	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4835	S-OMS-01040	SY3	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]	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4837	S-OMS-01050	SY3	The Order Manager shall allow operators to resume the queuing and dispatching of data distribution requests if it was suspended.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4841	S-OMS-01075	SY3	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.]  	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4846	S-OMS-01120	SY3	The Order Manager shall place on hold, i.e., not continue to process, requests that exceed a request limit.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4848	S-OMS-01140	SY3	The Order Manager shall place on hold, i.e., not continue to process, requests containing granules that violated the media capacity limit.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4849	S-OMS-01150	SY3	The Order Manager shall ignore all configured size limits when processing requests which have been flagged as exempt from limit checking. 	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4855	S-OMS-01210	SY3	The Order Manager shall place a request on hold that contains granules that were skipped.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4856	S-OMS-01220	SY3	The Order Manager shall request operator intervention when it places a request on hold.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4859	S-OMS-01250	SY3	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	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4860	S-OMS-01260	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4861	S-OMS-01280	SY3	The Order Manager shall allow operators to suspend the submission of requests to the PDS in total as well as by media type.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4862	S-OMS-01285	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4863	S-OMS-01290	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4864	S-OMS-01300	SY3	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. 	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4866	S-OMS-01325	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4868	S-OMS-01340	SY3	The Order Manager shall be able to limit the number of requests it processes concurrently.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4869	S-OMS-01350	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4880	S-OMS-01450	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4881	S-OMS-01460	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4882	S-OMS-01470	SY3	Upon warm restart, the Order Manager shall reinstate any suspensions that are currently in force.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4886	S-OMS-02020	SY3	The Order Management Service Command Line Utility shall save the distribution request in the Order Management Database. [OSS]	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4887	S-OMS-02025	SY3	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]	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4889	S-OMS-02040	SY3	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]	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4907	S-OMS-03130	SY3	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.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	4908	S-OMS-03135	SY3	The Order Management GUI shall remove an operator intervention from its pending state after the corresponding data distribution request has been failed.	02-1045	12/04/2002  		
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	1837	S-DSS-00052	B1	The SDSRV CI shall process each Service Request, in order, according to its relative priority in the Service Request List.	99-0729	08/25/1999  	No Data	
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	1845	S-DSS-00100	B0	The SDSRV CI shall provide the operations staff the capability to set, at subsystem startup, a threshold for the number of Service Requests that can be accepted and processed asynchronously.	99-0729	08/25/1999  	No Data	
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	1927	S-DSS-01090	B1	The SDSRV CI shall maintain a Service Request List that lists received Service Requests, associated Priority Information, and all other information required to process each request.	99-0729	08/25/1999  	No Data	
89	DADS2170	Complete	The ECS shall maintain a list of one-time orders.	2274	S-DSS-30095	B0	The DDIST CI shall maintain a queue of Distribution Requests that are waiting to be processed, and shall maintain, for each queued request, the request type, user, priority, and all other information necessary to process the request.	99-0729	08/25/1999  	No Data	
90	DADS2190	Complete	The ECS shall maintain a list  of products which could not be delivered electronically (e.g., workstation off-line).	2270	S-DSS-30018	Complete	The DDIST CI shall, for each synchronous Electronic Distribution Request that requires the transmission of data to the requesting client, return a successful completion status to the client if and only if the STMGT CI reports that the transmission has been completed successfully.	99-0729	08/25/1999  	No Data	
90	DADS2190	Complete	The ECS shall maintain a list  of products which could not be delivered electronically (e.g., workstation off-line).	2282	S-DSS-30139	B0	The DDIST CI shall suspend any Electronic Distribution Request that could not be completed because the requested data could not be delivered.  	99-0729	08/25/1999  	No Data	
90	DADS2190	Complete	The ECS shall maintain a list  of products which could not be delivered electronically (e.g., workstation off-line).	2283	S-DSS-30141	B0	The DDIST CI shall provide the operations staff the capability to cancel the processing of a suspended Distribution Request.  	99-0729	08/25/1999  	No Data	
90	DADS2190	Complete	The ECS shall maintain a list  of products which could not be delivered electronically (e.g., workstation off-line).	2284	S-DSS-30143	B0	The DDIST CI shall provide the operations staff the capability to resume the processing of a suspended Distribution Request.    	99-0729	08/25/1999  	No Data	
90	DADS2190	Complete	The ECS shall maintain a list  of products which could not be delivered electronically (e.g., workstation off-line).	2305	S-DSS-30345	6A	The DDIST CI shall send to the requesting client a Distribution Nofification that describes the reason for the unsuccessful completion of a Distribution Request.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	1944	S-DSS-01365	B0	The SDSRV CI shall provide operations staff the capability to recover the Metadata Database using the database backup and the Database Transaction Log.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2056	S-DSS-04386	B0	The SDSRV CI shall maintain the location of each primary copy of a locally-archived data product, and the location of the product's local and off-site backup copies, if they exist.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2088	S-DSS-04900	B0	The SDSRV CI shall, at the direction and approval of the operations staff, retrieve an offsite copy of a product.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2161	S-DSS-20420	A	The STMGT CI shall be capable of producing a backup copy of designated EOS data.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2162	S-DSS-20430	A	The STMGT CI shall be capable of producing backup archive media which is compatible with approved ECS formats.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2176	S-DSS-20650	B0	The STMGT CI shall provide operations staff the capability to specify the products to be backed up at both local and offsite archives.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2177	S-DSS-20660	B0	The STMGT CI shall provide operations staff the capability to restore backups of specified data holdings.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2178	S-DSS-20670	A	The STMGT CI shall log all updates to the Archive Database, in a Database Transaction Log.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2399	S-DSS-80250	B0	The DRPHW CI shall have sufficient capacity to backup 2% of the primary copies of locally-archived data products.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2400	S-DSS-80260	B0	The DRPHW CI, at LaRC, shall have the storage capacity to meet the GSFC DAAC requirements for off-site backup.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2401	S-DSS-80270	B0	The DRPHW CI, at GSFC, shall have sufficient storage capacity to store the offsite backup copies required by the EDC, LaRC and the NSIDC DAACs.	99-0729	08/25/1999  	No Data	
91	DADS2270	Complete	The ECS shall provide an off-site backup copy of all EOS data which would be impossible or difficult to recover in case of loss (e.g., ancillary data, metadata,  Science Software, calibration data, systems and applications software, selected data products, depending on need).	2845	C-MSS-04010	B0	The MSS-MHW CI Local Management Server shall maintain one backup of all software and security audit trails and logs in a separate physical location.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2054	S-DSS-04382	B0	The SDSRV CI shall maintain a backup indicator, for each data type, that specifies whether or not backup copies are to be created and maintained for that data type.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2055	S-DSS-04384	B0	The SDSRV CI shall request that the STMGT CI create both a local backup copy and off-site backup copy of a data product, as determined by the data product's backup indicator.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2056	S-DSS-04386	B0	The SDSRV CI shall maintain the location of each primary copy of a locally-archived data product, and the location of the product's local and off-site backup copies, if they exist.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2160	S-DSS-20410	B0	The STMGT CI shall notify the operator upon the failure of retrieval of a local or offsite backup copy.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2175	S-DSS-20634	B1	The STMGT CI shall notify the operator and automatically retrieve a local backup copy of product upon the failure of the retrieval of the primary copy of the product.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2176	S-DSS-20650	B0	The STMGT CI shall provide operations staff the capability to specify the products to be backed up at both local and offsite archives.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2177	S-DSS-20660	B0	The STMGT CI shall provide operations staff the capability to restore backups of specified data holdings.	99-0729	08/25/1999  	No Data	
92	DADS2276	Complete	The ECS shall  have the capability to  restore its archive from a backup copy of EOS data or backup copy of information required to regenerate the data.	2180	S-DSS-20740	B0	The STMGT CI shall provide operations staff the capability to restore the primary copy of a product from either the local backup copy or the offsite backup copy.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	1944	S-DSS-01365	B0	The SDSRV CI shall provide operations staff the capability to recover the Metadata Database using the database backup and the Database Transaction Log.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	2161	S-DSS-20420	A	The STMGT CI shall be capable of producing a backup copy of designated EOS data.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	2178	S-DSS-20670	A	The STMGT CI shall log all updates to the Archive Database, in a Database Transaction Log.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	2180	S-DSS-20740	B0	The STMGT CI shall provide operations staff the capability to restore the primary copy of a product from either the local backup copy or the offsite backup copy.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	2227	S-DSS-21450	A	The STMGT CI shall provide operations staff the capability to backup the contents of the File Directory.	99-0729	08/25/1999  	No Data	
93	DADS2300	Complete	The ECS  shall provide a capability for local and offsite backup/restore of system files.	2228	S-DSS-21460	A	The STMGT CI shall provide operations staff the capability to recover the contents of the File Directory in the case of file corruption.	99-0729	08/25/1999  	No Data	
94	DADS2302	Complete	The ECS offsite and local backup media shall be based on published, open, and non-proprietary formats which fully describe the physical organization and structure of files.	2161	S-DSS-20420	A	The STMGT CI shall be capable of producing a backup copy of designated EOS data.	99-0729	08/25/1999  	No Data	
94	DADS2302	Complete	The ECS offsite and local backup media shall be based on published, open, and non-proprietary formats which fully describe the physical organization and structure of files.	2162	S-DSS-20430	A	The STMGT CI shall be capable of producing backup archive media which is compatible with approved ECS formats.	99-0729	08/25/1999  	No Data	
95	DADS2307	6A	The ECS shall fulfill requests for L0 data from EDOS with L0.	2099	S-DSS-05715	B0	The SDSRV CI shall provide the operations staff the capability to obtain ECS granule identifiers, for ECS Level 0 data granules or equivalent ECS Level 1A data granules, that correspond to EDOS-specified PDS IDs.	99-0729	08/25/1999  	No Data	
95	DADS2307	6A	The ECS shall fulfill requests for L0 data from EDOS with L0.	2100	S-DSS-05720	B0	The SDSRV CI shall provide the operations staff the capability to obtain ECS granule identifiers, for ECS Level 0 data granules or equivalent ECS Level 1A data granules, that correspond to EDOS-specified APIDs and associated start/stop times.	99-0729	08/25/1999  	No Data	
95	DADS2307	6A	The ECS shall fulfill requests for L0 data from EDOS with L0.	2101	S-DSS-05725	B0	The SDSRV CI shall provide the operations staff the capability to issue Media Distribution Requests for ECS Level 0 data granules and ECS Level 1A data granules.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	1901	S-DSS-00710	A	The SDSRV CI shall accept and process valid, authenticated Data Requests, from any source, via the Data Request API.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	1924	S-DSS-00965	B0	The SDSRV CI shall provide the capability to direct the retrieval and distribution of any data granules listed in the Granule Inventory Metadata, as specified by valid Data Request.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	1994	S-DSS-02900	A	The SDSRV CI shall provide the data type services as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2089	S-DSS-05000	A	The SDSRV CI shall manage algorithm packages as defined in the ECS Core Metadata Model, and provide interfaces for storing and accessing them.  	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
97	DADS2340	Complete	The ECS shall have the capability to send from one DAAC to another DAAC the following:    a. L0-L4 data    b. Metadata    c. Ancillary data    d. Calibration data    e. Correlative data	2331	S-DSS-30711	A	The DDIST CI shall be capable of sending data to a remote DAAC.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	5365	S-BGT-10300	SY3	The BMGT shall include an association between each AIRS granule and its ASBP during the generation of the ECSBBR browse XML file.	02-1094	12/18/2002  		
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	5366	S-BGT-10310	SY3	The BMGT shall only include AIRS summary browse if the corresponding AIRS ESDTs are included in the list of ESDTs designated for metadata generation.	02-1094	12/18/2002  		
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	5367	S-BGT-10320	SY3	The BMGT shall convert extracted browse cross-reference information to XML format at a rate of at least 25,000 granules per hour.	02-1094	12/18/2002  		
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	5368	S-DSS-90350	SY3	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.	02-1094	12/18/2002  		
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	1685	S-DPS-41900	A	The AITTL CI shall provide an HTML page describing the ECS instruments and providing hyperlinks to the PGE Listing Page for each team.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	1686	S-DPS-41901	A	The AITTL CI shall provide an HTML PGE Listing Page for each instrument team, identifying each PGE for which a software package is available, with references to its Software Version Page (if it exists) or else to  its Software Listing Page.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	1687	S-DPS-41902	A	The AITTL CI shall provide an HTML Software Version Page for each PGE, if multiple baseline software versions for that PGE are available, identifying the instrument and PGE, the version number and date, and provide a reference to the Software Listing Page.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	1688	S-DPS-41903	A	The AITTL CI shall provide an HTML Software Listing Page for each baselined PGE version, identifying each existing component of the PGE software package (as defined in the ECS Core Metadata Model) and provide a hyperlink that can be used to retrieve that component.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	1924	S-DSS-00965	B0	The SDSRV CI shall provide the capability to direct the retrieval and distribution of any data granules listed in the Granule Inventory Metadata, as specified by valid Data Request.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2089	S-DSS-05000	A	The SDSRV CI shall manage algorithm packages as defined in the ECS Core Metadata Model, and provide interfaces for storing and accessing them.  	99-0729	08/25/1999  	No Data	
99	DADS2370	Complete	The ECS shall have the capability to send to the user the following:  a. L0-L4 data  b. Special products (L1-L4)  c. Metadata  d. Ancillary data  e. Calibration data  f. Correlative data  g. Science Software  h. Browse data	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4734	S-SSS-10400	SY3	The NSBRV CI shall submit all ECS data distribution requests to the Order Management Service.  [Note, currently the NSBRV uses the SCLI].	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4735	S-SSS-10405	SY3	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. 	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4736	S-SSS-10410	SY3	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. 	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4737	S-SSS-10420	SY3	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.	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4751	S-OMS-05290	SY3	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.	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4752	S-OMS-05310	SY3	The Order Manager shall submit the data distribution request created from a bundle to the Order Management Service for processing and distribution.	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4860	S-OMS-01260	SY3	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.	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4864	S-OMS-01300	SY3	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. 	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	4912	S-OMS-03160	SY3	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]	02-1045	12/04/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5051	S-DSS-99000	SY2	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.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5052	S-DSS-99010	SY2	The DCLI shall accept a mandatory DDISTMEDIATYPE parameter.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5053	S-DSS-99020	SY2	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	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5054	S-DSS-99030	SY2	The DCLI shall include the DDISTMEDIATYPE parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5055	S-DSS-99040	SY2	The DCLI shall accept the following FTP Push parameters (all strings) if the DDISTMEDIATYPE is FtpPush:  FTPUSER  FTPPASSWORD  FTPHOST  FTPPUSHDEST	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5056	S-DSS-99050	SY2	The DCLI shall verify that all four FTP Push parameters are provided if the DDISTMEDIATYPE is FtpPush, and return a fatal error if not.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5057	S-DSS-99060	SY2	The DCLI shall include the FTP Push parameters in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5058	S-DSS-99070	SY2	The DCLI shall accept an optional DDISTMEDIAFORMAT parameter	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5059	S-DSS-99080	SY2	The DCLI shall verify that the DDISTMEDIAFORMAT parameter, if present, specifies a value of 'FILEFORMAT' and return a fatal error if not.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5060	S-DSS-99090	SY2	The DCLI shall include the DDISTMEDIAFORMAT parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5061	S-DSS-99100	SY2	The DCLI shall accept a mandatory ECSUSERPROFILE parameter.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5062	S-DSS-99110	SY2	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.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5063	S-DSS-99120	SY2	The DCLI shall include the ECSUSERPROFILE parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5064	S-DSS-99130	SY2	The DCLI shall accept a mandatory ORDERID and a mandatory REQUESTID parameter.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5065	S-DSS-99140	SY2	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.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5066	S-DSS-99150	SY2	The DCLI shall include the REQUESTID parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5067	S-DSS-99160	SY2	The DCLI shall accept an optional PRIORITY parameter.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5068	S-DSS-99170	SY2	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	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5069	S-DSS-99180	SY2	The DCLI shall include the PRIORITY parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5070	S-DSS-99190	SY2	The DCLI shall accept an optional UserString parameter specifying a string of a maximum length of 80 characters.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5071	S-DSS-99200	SY2	The DCLI shall verify that the UserString parameter does not exceed the maximum length and return a fatal error if it does.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5072	S-DSS-99210	SY2	The DCLI shall include the UserString parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5073	S-DSS-99220	SY2	The DCLI shall accept an optional DDISTNOTIFYTYPE parameter.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5074	S-DSS-99230	SY2	The DCLI shall verify that the DDISTNOTIFYTYPE parameter, if present, is set to MAIL, and return a fatal error if not.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5075	S-DSS-99240	SY2	The DCLI shall accept a mandatory NOTIFY parameter specifying an e-mail address string.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5076	S-DSS-99250	SY2	The DCLI shall verify that the NOTIFY parameter is present and return a fatal error if not.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5077	S-DSS-99260	SY2	The DCLI shall include the DDISTNOTIFYTYPE and NOTIFY parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5078	S-DSS-99270	SY2	The DCLI shall accept a mandatory tag parameter as a string of up to 20 characters.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5079	S-DSS-99280	SY2	The DCLI shall verify that the tag parameter is present and at most 20 characters in length, and return a fatal error if not.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5080	S-DSS-99290	SY2	The DCLI shall use the tag parameter to generate an rpcID for the DDIST distribution request it submits.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5081	S-DSS-99300	SY2	The DCLI shall generate the identical rpcID only if it receives the identical tag on different submission requests, the generated rpcID otherwise being different.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5082	S-DSS-99310	SY2	The DCLI shall accept a list of up to 100 fully qualified file/path names that represent the files to be distributed.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5083	S-DSS-99320	SY2	The DCLI shall return a fatal error if less than one and more than 100 file/path names are provided.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5084	S-DSS-99330	SY2	The DCLI shall assume the following default values for the corresponding optional parameters if they are not provided:  DDISTMEDIAFORMAT  = FILEFORMAT  PRIORITY = NORMAL  DDISTNOTIFYTYPE = MAIL	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5085	S-DSS-99340	SY2	The DCLI shall submit an asynchronous distribution request for the identified files to DDIST.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5086	S-DSS-99350	SY2	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.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5087	S-DSS-99360	SY2	The DCLI shall be able to accept requests for a designated mode.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5088	S-DSS-99370	SY2	It shall be possible to submit several requests in a given mode via the DCLI concurrently.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5089	S-DSS-99380	SY2	It shall be possible to submit requests via the DCLI in several different modes concurrently.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	5090	S-DSS-99390	SY2	The DCLI shall be able to receive and process distribution requests through to DDIST at the rate of 40 requests per hour.	02-1064	12/11/2002  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	9074	S-DPL-09075	7.22	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.]  	08-0426	09/29/2008  		
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	1924	S-DSS-00965	B0	The SDSRV CI shall provide the capability to direct the retrieval and distribution of any data granules listed in the Granule Inventory Metadata, as specified by valid Data Request.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
102	DADS2410	Complete	The ECS shall distribute data from the archive in response to receipt of a product order.	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	4860	S-OMS-01260	SY3	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.	02-1045	12/04/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	4864	S-OMS-01300	SY3	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. 	02-1045	12/04/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	4912	S-OMS-03160	SY3	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]	02-1045	12/04/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5051	S-DSS-99000	SY2	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.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5052	S-DSS-99010	SY2	The DCLI shall accept a mandatory DDISTMEDIATYPE parameter.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5053	S-DSS-99020	SY2	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	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5054	S-DSS-99030	SY2	The DCLI shall include the DDISTMEDIATYPE parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5055	S-DSS-99040	SY2	The DCLI shall accept the following FTP Push parameters (all strings) if the DDISTMEDIATYPE is FtpPush:  FTPUSER  FTPPASSWORD  FTPHOST  FTPPUSHDEST	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5056	S-DSS-99050	SY2	The DCLI shall verify that all four FTP Push parameters are provided if the DDISTMEDIATYPE is FtpPush, and return a fatal error if not.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5057	S-DSS-99060	SY2	The DCLI shall include the FTP Push parameters in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5058	S-DSS-99070	SY2	The DCLI shall accept an optional DDISTMEDIAFORMAT parameter	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5059	S-DSS-99080	SY2	The DCLI shall verify that the DDISTMEDIAFORMAT parameter, if present, specifies a value of 'FILEFORMAT' and return a fatal error if not.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5060	S-DSS-99090	SY2	The DCLI shall include the DDISTMEDIAFORMAT parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5061	S-DSS-99100	SY2	The DCLI shall accept a mandatory ECSUSERPROFILE parameter.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5062	S-DSS-99110	SY2	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.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5063	S-DSS-99120	SY2	The DCLI shall include the ECSUSERPROFILE parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5064	S-DSS-99130	SY2	The DCLI shall accept a mandatory ORDERID and a mandatory REQUESTID parameter.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5065	S-DSS-99140	SY2	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.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5066	S-DSS-99150	SY2	The DCLI shall include the REQUESTID parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5067	S-DSS-99160	SY2	The DCLI shall accept an optional PRIORITY parameter.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5068	S-DSS-99170	SY2	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	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5069	S-DSS-99180	SY2	The DCLI shall include the PRIORITY parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5070	S-DSS-99190	SY2	The DCLI shall accept an optional UserString parameter specifying a string of a maximum length of 80 characters.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5071	S-DSS-99200	SY2	The DCLI shall verify that the UserString parameter does not exceed the maximum length and return a fatal error if it does.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5072	S-DSS-99210	SY2	The DCLI shall include the UserString parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5073	S-DSS-99220	SY2	The DCLI shall accept an optional DDISTNOTIFYTYPE parameter.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5074	S-DSS-99230	SY2	The DCLI shall verify that the DDISTNOTIFYTYPE parameter, if present, is set to MAIL, and return a fatal error if not.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5075	S-DSS-99240	SY2	The DCLI shall accept a mandatory NOTIFY parameter specifying an e-mail address string.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5076	S-DSS-99250	SY2	The DCLI shall verify that the NOTIFY parameter is present and return a fatal error if not.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5077	S-DSS-99260	SY2	The DCLI shall include the DDISTNOTIFYTYPE and NOTIFY parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5078	S-DSS-99270	SY2	The DCLI shall accept a mandatory tag parameter as a string of up to 20 characters.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5079	S-DSS-99280	SY2	The DCLI shall verify that the tag parameter is present and at most 20 characters in length, and return a fatal error if not.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5080	S-DSS-99290	SY2	The DCLI shall use the tag parameter to generate an rpcID for the DDIST distribution request it submits.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5081	S-DSS-99300	SY2	The DCLI shall generate the identical rpcID only if it receives the identical tag on different submission requests, the generated rpcID otherwise being different.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5082	S-DSS-99310	SY2	The DCLI shall accept a list of up to 100 fully qualified file/path names that represent the files to be distributed.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5083	S-DSS-99320	SY2	The DCLI shall return a fatal error if less than one and more than 100 file/path names are provided.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5084	S-DSS-99330	SY2	The DCLI shall assume the following default values for the corresponding optional parameters if they are not provided:  DDISTMEDIAFORMAT  = FILEFORMAT  PRIORITY = NORMAL  DDISTNOTIFYTYPE = MAIL	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5085	S-DSS-99340	SY2	The DCLI shall submit an asynchronous distribution request for the identified files to DDIST.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5086	S-DSS-99350	SY2	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.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5087	S-DSS-99360	SY2	The DCLI shall be able to accept requests for a designated mode.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5088	S-DSS-99370	SY2	It shall be possible to submit several requests in a given mode via the DCLI concurrently.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5089	S-DSS-99380	SY2	It shall be possible to submit requests via the DCLI in several different modes concurrently.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	5090	S-DSS-99390	SY2	The DCLI shall be able to receive and process distribution requests through to DDIST at the rate of 40 requests per hour.	02-1064	12/11/2002  		
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	1923	S-DSS-00940	B0	The SDSRV CI shall direct the retrieval and distribution of the data files, associated with each granule requested in a valid Data Request, using the Logical File Location for each file.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	1924	S-DSS-00965	B0	The SDSRV CI shall provide the capability to direct the retrieval and distribution of any data granules listed in the Granule Inventory Metadata, as specified by valid Data Request.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
103	DADS2430	Complete	The ECS shall be capable of distributing any data granule stored in the archive.	2169	S-DSS-20620	A	The STMGT CI shall be capable of retrieving any stored data file specified by the file's unique Logical File Location.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	4803	S-OMS-00180	SY3	The Order Management Service shall accept an optional PRIORITY parameter for a distribution request that specifies one of the ECS priorities.	02-1045	12/04/2002  		
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	1834	S-DSS-00015	A	The SDSRV CI shall insure that each Data Request includes a User Identifier, a Request Priority, and a Data Identifier.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	1837	S-DSS-00052	B1	The SDSRV CI shall process each Service Request, in order, according to its relative priority in the Service Request List.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	1838	S-DSS-00055	B1	The SDSRV CI shall initiate the processing of Service Requests of equal priority in the order in which they are received.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	1970	S-DSS-01865	B0	The SDSRV CI shall provide Priority Information for each Data Distribution Request to the DDIST CI.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	2273	S-DSS-30090	B1	The DDIST CI shall provide the capability to give the processing of Electronic Distribution Requests priority over the processing of Media Distribution Requests.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	2274	S-DSS-30095	B0	The DDIST CI shall maintain a queue of Distribution Requests that are waiting to be processed, and shall maintain, for each queued request, the request type, user, priority, and all other information necessary to process the request.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
104	DADS2440	6A 6B	The ECS shall distribute data under a multi-level priority system.	2291	S-DSS-30180	A	The DDIST CI shall process queued Distribution Requests in order, according to their assigned Priority Information.	99-0729	08/25/1999  	No Data	
106	DADS2460	6A 6B	The ECS shall have a manual override function capable of altering the priority of a distribution request.	1861	S-DSS-00210	B1	The SDSRV CI shall provide operations staff the capability to update the Priority Information for any entry in the Service Request List.	99-0729	08/25/1999  	No Data	
106	DADS2460	6A 6B	The ECS shall have a manual override function capable of altering the priority of a distribution request.	2274	S-DSS-30095	B0	The DDIST CI shall maintain a queue of Distribution Requests that are waiting to be processed, and shall maintain, for each queued request, the request type, user, priority, and all other information necessary to process the request.	99-0729	08/25/1999  	No Data	
106	DADS2460	6A 6B	The ECS shall have a manual override function capable of altering the priority of a distribution request.	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
106	DADS2460	6A 6B	The ECS shall have a manual override function capable of altering the priority of a distribution request.	2291	S-DSS-30180	A	The DDIST CI shall process queued Distribution Requests in order, according to their assigned Priority Information.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5051	S-DSS-99000	SY2	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.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5052	S-DSS-99010	SY2	The DCLI shall accept a mandatory DDISTMEDIATYPE parameter.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5053	S-DSS-99020	SY2	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	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5054	S-DSS-99030	SY2	The DCLI shall include the DDISTMEDIATYPE parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5055	S-DSS-99040	SY2	The DCLI shall accept the following FTP Push parameters (all strings) if the DDISTMEDIATYPE is FtpPush:  FTPUSER  FTPPASSWORD  FTPHOST  FTPPUSHDEST	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5056	S-DSS-99050	SY2	The DCLI shall verify that all four FTP Push parameters are provided if the DDISTMEDIATYPE is FtpPush, and return a fatal error if not.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5057	S-DSS-99060	SY2	The DCLI shall include the FTP Push parameters in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5058	S-DSS-99070	SY2	The DCLI shall accept an optional DDISTMEDIAFORMAT parameter	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5059	S-DSS-99080	SY2	The DCLI shall verify that the DDISTMEDIAFORMAT parameter, if present, specifies a value of 'FILEFORMAT' and return a fatal error if not.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5060	S-DSS-99090	SY2	The DCLI shall include the DDISTMEDIAFORMAT parameter in the distribution request it submits to the DDIST.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5061	S-DSS-99100	SY2	The DCLI shall accept a mandatory ECSUSERPROFILE parameter.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5062	S-DSS-99110	SY2	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.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5063	S-DSS-99120	SY2	The DCLI shall include the ECSUSERPROFILE parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5064	S-DSS-99130	SY2	The DCLI shall accept a mandatory ORDERID and a mandatory REQUESTID parameter.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5065	S-DSS-99140	SY2	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.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5066	S-DSS-99150	SY2	The DCLI shall include the REQUESTID parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5067	S-DSS-99160	SY2	The DCLI shall accept an optional PRIORITY parameter.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5068	S-DSS-99170	SY2	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	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5069	S-DSS-99180	SY2	The DCLI shall include the PRIORITY parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5070	S-DSS-99190	SY2	The DCLI shall accept an optional UserString parameter specifying a string of a maximum length of 80 characters.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5071	S-DSS-99200	SY2	The DCLI shall verify that the UserString parameter does not exceed the maximum length and return a fatal error if it does.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5072	S-DSS-99210	SY2	The DCLI shall include the UserString parameter in the DDIST distribution request it submits.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5073	S-DSS-99220	SY2	The DCLI shall accept an optional DDISTNOTIFYTYPE parameter.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5074	S-DSS-99230	SY2	The DCLI shall verify that the DDISTNOTIFYTYPE parameter, if present, is set to MAIL, and return a fatal error if not.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5075	S-DSS-99240	SY2	The DCLI shall accept a mandatory NOTIFY parameter specifying an e-mail address string.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5076	S-DSS-99250	SY2	The DCLI shall verify that the NOTIFY parameter is present and return a fatal error if not.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5077	S-DSS-99260	SY2	The DCLI shall include the DDISTNOTIFYTYPE and NOTIFY parameters in the DDIST distribution request it submits.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5078	S-DSS-99270	SY2	The DCLI shall accept a mandatory tag parameter as a string of up to 20 characters.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5079	S-DSS-99280	SY2	The DCLI shall verify that the tag parameter is present and at most 20 characters in length, and return a fatal error if not.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5080	S-DSS-99290	SY2	The DCLI shall use the tag parameter to generate an rpcID for the DDIST distribution request it submits.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5081	S-DSS-99300	SY2	The DCLI shall generate the identical rpcID only if it receives the identical tag on different submission requests, the generated rpcID otherwise being different.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5082	S-DSS-99310	SY2	The DCLI shall accept a list of up to 100 fully qualified file/path names that represent the files to be distributed.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5083	S-DSS-99320	SY2	The DCLI shall return a fatal error if less than one and more than 100 file/path names are provided.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5084	S-DSS-99330	SY2	The DCLI shall assume the following default values for the corresponding optional parameters if they are not provided:  DDISTMEDIAFORMAT  = FILEFORMAT  PRIORITY = NORMAL  DDISTNOTIFYTYPE = MAIL	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5085	S-DSS-99340	SY2	The DCLI shall submit an asynchronous distribution request for the identified files to DDIST.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5086	S-DSS-99350	SY2	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.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5087	S-DSS-99360	SY2	The DCLI shall be able to accept requests for a designated mode.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5088	S-DSS-99370	SY2	It shall be possible to submit several requests in a given mode via the DCLI concurrently.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5089	S-DSS-99380	SY2	It shall be possible to submit requests via the DCLI in several different modes concurrently.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	5090	S-DSS-99390	SY2	The DCLI shall be able to receive and process distribution requests through to DDIST at the rate of 40 requests per hour.	02-1064	12/11/2002  		
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	1994	S-DSS-02900	A	The SDSRV CI shall provide the data type services as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	1995	S-DSS-02901	5B	The SDSRV CI shall provide the capability to subset data within a Landsat subinterval granule based on floating scenes.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	1996	S-DSS-02902	5B	The SDSRV CI shall provide the capability to subset data within a Landsat subinterval granule based on Spectral band.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	1997	S-DSS-02903	B1	The SDSRV CI shall provide the capability to subset, subsample, or average data within a granule based on Time for products as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	1998	S-DSS-02904	B0	The SDSRV CI shall provide the capability to subset, subsample, or average data within a granule based on WRS for products as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	1999	S-DSS-02905	B1	 The SDSRV CI shall provide the capability to subset data within a granule through the use of geographical masking for products as specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2003	S-DSS-02909	B0	The SDSRV CI shall provide the capability to subset MODIS Level 1B data by parameter.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2057	S-DSS-04390	A	Standard Product related Metadata at the Data Server shall include Metadata associated with static subsetted, subsampled, and summary products.	99-0729	08/25/1999  	No Data	
107	DADS2470	Complete	The ECS shall transfer Standard Products and subsetted data to the requester.	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5156	S-BGT-00010	5BP	The ECS Bulk Metadata Generator Tool (BMGT) shall export metadata for an operator-configurable set of ESDT versions.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5157	S-BGT-00020	5BP	The BMGT shall allow the operator to specify a date range to be processed.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5158	S-BGT-00030	5BP	The BMGT shall allow the operator to specify a default date range of the previous day.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5159	S-BGT-00040	5BP	The BMGT may be executed as a cron job.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5160	S-BGT-00050	5BP	The BMGT may be executed at the discretion of the operator.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5161	S-BGT-00060	5BP	The BMGT shall run in accordance to ECS mode conventions.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5162	S-BGT-00070	5BP	The BMGT shall allow the operator to specify mappings between ESDT versions and groups.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5163	S-BGT-00080	5BP	The BMGT shall allow the operator to specify a destination directory for the products that are created.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5164	S-BGT-00090	5BP	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).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5165	S-BGT-00100	5BP	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).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5166	S-BGT-00110	5BP	The BMGT shall incur no more than 10 % performance degradation on the ECS Science Data Server Database under nominal operation load during data extraction.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5167	S-BGT-00120	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5168	S-BGT-00130	5BP	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.   	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5169	S-BGT-00140	5BP	Data group names and content  shall be configurable by the operator.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5170	S-BGT-00150	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5171	S-BGT-00160	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5172	S-BGT-00170	5BP	The BMGT shall generate collection level metadata for a specific collection only once per execution.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5173	S-BGT-00180	5BP	Each ECSMETC product shall consist of a single XML file. There shall be one granule for each group.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5174	S-BGT-00190	5BP	Each ECSMETC granule shall contain the metadata specified in document 170-WP-023-001 (section 2.2.1).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5175	S-BGT-00200	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5176	S-BGT-00210	5BP	Each ECSMETC product XML file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5177	S-BGT-00220	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5178	S-BGT-00230	5BP	The BMGT shall convert extracted collection level metadata to XML format at a rate of at least  25,000  collections per hour.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5179	S-BGT-00240	5BP	The ECS shall provide an ESDT (ECSMETG) that shall store products that contain an XML representation of ECS granule level metadata.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5180	S-BGT-00250	5BP	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. 	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5181	S-BGT-00260	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5182	S-BGT-00270	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5183	S-BGT-00280	5BP	The BMGT shall generate granule level metadata for a specific granule only once per execution.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5184	S-BGT-00290	5BP	The BMGT shall not generate granule level metadata for a granule that was both inserted and deleted within the temporal constraint.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5185	S-BGT-00300	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5186	S-BGT-00310	5BP	Each ECSMETG product shall consist of a single XML file. There shall be one product for each group.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5187	S-BGT-00320	5BP	Each ECSMETG granule shall contain the metadata specified in document 170-WP-023-001 (section 2.2.1).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5188	S-BGT-00330	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5189	S-BGT-00340	5BP	Each ECSMETG product XML file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5190	S-BGT-00350	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5191	S-BGT-00360	5BP	The BMGT shall convert extracted granule level metadata to XML format at a rate of at least 25,000 granules per hour.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5192	S-BGT-00370	5BP	ECS shall provide an ESDT (ECSMETV) that shall store products that contain an XML representation of ECS collection and granule valid values.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5193	S-BGT-00380	5BP	The BMGT shall generate a single ECSMETV product per execution if one or more ECSMETC products were generated during that execution.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5194	S-BGT-00390	5BP	Each ECSMETV product shall consist of a single XML file.	02-0979	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5195	S-BGT-00400	5BP	Each ECSMETV granule shall contain the metadata specified in document 170-WP-023-001 (section 2.2.1).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5196	S-BGT-00410	5BP	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).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5197	S-BGT-00420	5BP	Each ECSMETV product XML file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5198	S-BGT-00430	5BP	The ECS shall provide an ESDT (ECSBBR) that shall store products that contain an XML representation of ECS Bulk Browse products.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5199	S-BGT-00440	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5200	S-BGT-00450	5BP	The BMGT shall generate bulk browse metadata for a specific browse product only once per execution.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5201	S-BGT-00460	5BP	The BMGT shall not generate bulk browse metadata for a browse product that was both inserted and deleted within the temporal constraint.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5202	S-BGT-00480	5BP	Each ECSBBR product shall consist of a single XML file called the Browse Reference File (BRF).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5203	S-BGT-00490	5BP	Each ECSBBR granule shall contain the metadata specified in document 170-WP-023-001 (section 3.2).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5204	S-BGT-00500	5BP	The file naming convention of the BRF files shall be in accordance of document 170-WP-023-001 (p 13).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5205	S-BGT-00510	5BP	Each BRF file shall conform to a DTD file according to the document 170-WP-023-001 (Appendix A).	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5206	S-BGT-00520	5BP	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.)	02-0979	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5207	S-BGT-00530	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5208	S-BGT-00540	5BP	The BMGT shall convert extracted browse cross-reference information to XML format at a rate of at least25,000 granules per hour.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5209	S-BGT-00604	5BP	The Ingest CSCI shall allow ingest of products of types ECSMETC, ECSMETG, ECSMETV, and ECSBBR through the SIPS interface.	02-0979	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5210	S-BGT-00550	5BP	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.	02-1087	12/12/2002  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5770	S-BGT-30010	6A	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.	02-1102	01/08/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5771	S-BGT-30020	6A	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.	02-1102	01/08/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5772	S-BGT-30053	6A	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	02-1102	01/08/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5836	S-BGT-30110	SY4	The BMGT CI shall generate an XML representation of the QA metadata update information.	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5837	S-BGT-30120	SY4	The BMGT CI shall use a naming convention for its generated metadata update files that includes a) DAAC idb) Time stamp	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5838	S-BGT-30130	SY4	The BMGT shall not generate full granule-level metadata for those granules whose sole reason for export is an update to their QA flags.	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5839	S-BGT-30140	SY4	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.	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5840	S-BGT-30150	SY4	Each ECSMETU product XML file shall conform to a DTD file according to the document 170-WP-023-007 (Appendix A).	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5841	S-BGT-30160	SY4	The BMGT CI shall generate Product Delivery Record (PDR) that conforms to the ECS SIPS interface (423-41-57 section 4.5.3). 	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5842	S-BGT-30170	SY4	The BMGT CI shall generate ECSMETU metadata (.met) files necessary to support the ingest of ECSMETU products via the SIPS interface.	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5843	S-DSS-40500	SY4	The SDSRV database shall track QA flag updates	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5844	S-DSS-40510	SY4	ECS shall provide an ESDT (ECSMETU) that shall store products that contain an XML representation of granule-level QA metadata updates.	03-0495	07/23/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5856	S-BGT-20210	SY4	The BMGT CI's Bulk URL Utility shall ignore 'order only' granule URLs when generating XML for granule inserts and deletes.	03-0583	08/21/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5857	S-BGT-20220	SY4	The BMGT CI's Bulk URL Utility shall FTP both insert and delete bulk URL XML files to a configurable FTP location.	03-0583	08/21/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	5858	S-BGT-20230	SY4	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.	03-0583	08/21/2003  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8667	S-BGT-01011	7.21	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.]	08-0313	07/22/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8668	S-BGT-01001	7.21	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.]	08-0313	07/22/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8669	S-BGT-00996	7.21	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.]	08-0313	07/22/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8670	S-DPL-18105	7.21	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.	08-0313	07/22/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8687	S-BGT-31160	7.22	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.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8688	S-BGT-31170	7.22	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 	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8690	S-BGT-31190	7.22	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]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8691	S-BGT-31200	7.22	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	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8693	S-BGT-31220	7.22	The BMGT shall permit DAAC staff to request the start of a corrective metadata export operation.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8694	S-BGT-31230	7.22	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. 	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8695	S-BGT-31240	7.22	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.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8696	S-BGT-31250	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8697	S-BGT-31260	7.22	The BMGT shall process the re-export queue during manual corrective exports and no other types of  export operations.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8698	S-BGT-31270	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8704	S-BGT-31330	7.22	The BMGT shall remove all re-export action from the re-export queue after they were processed successfully by a manual corrective export.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8718	S-BGT-31470	7.22	The BMGT shall include granule URL information in re-exports only if the corresponding collection is enabled for granule URL export.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8719	S-BGT-31480	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8721	S-BGT-31500	7.22	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 	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8724	S-BGT-31530	7.22	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.  	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8725	S-BGT-31540	7.22	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).	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8772	S-BGT-31180	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8795	S-BGT-31410	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8800	S-BGT-31460	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8805	S-BGT-31510	7.22	The BMGT shall sort the re-export queue report by initial export attempt (most recent first), collection, and type of object.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8806	S-BGT-31520	7.22	The BMGT shall allow DAAC staff to filter the re-export queue report (see requirement S-BGT-31500) based on collection and collection group. 	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8817	S-BGT-31100	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8818	S-BGT-31110	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8819	S-BGT-31120	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8820	S-BGT-31130	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8821	S-BGT-31140	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8822	S-BGT-31150	7.22	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.]	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8823	S-BGT-31000	7.22	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 	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8828	S-BGT-31050	7.22	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.	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8829	S-BGT-31060	7.22	DELETED	08-0316	07/24/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8831	S-BGT-31245	7.22	The BMGT shall identify corrective exports as such in the audit trail.	08-0398	09/05/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8832	S-BGT-31525	7.22	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.	08-0398	09/05/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8833	S-BGT-31545	7.22	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.	08-0398	09/05/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8834	S-BGT-31535	7.22	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.	08-0398	09/05/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8665	S-BGT-00641	7.21	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.]	08-0313	07/22/2008  		
516	DADS2480	5BP SY2 SY3	The ECS shall support the export of inventory metadata using the Extensible Markup Language (XML).	8666	S-BGT-00642	7.21	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.	08-0313	07/22/2008  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4177	S-DSS-21355	6A	The STMGT CI shall have the capability to transfer data to and from D3 tape.	99-1176	12/01/1999  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4249	C-CSS-40500	6A	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.	00-0174	02/23/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4250	C-CSS-30640	6A	The Registry shall store distribution options information. 	00-0174	02/23/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4251	C-CSS-30650	6A	The Registry shall provide an API to retrieve information that is hierarchically structured, containing dependencies between values. 	00-0174	02/23/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4570	S-CLS-20250	5BX	The ODFRM CI shall not offer physical media distributions (i.e., other than FTP Push and FTP Pull).	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4571	S-DMS-30600	5BX	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.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4572	S-DMS-30602	5BX	The GTWAY CI shall accept Product Result messages for physical media requests that it forwarded to the PDS.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4573	S-DMS-30604	5BX	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. 	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4574	S-DMS-30605	5BX	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. 	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4575	S-CSS-40502	5BX	The SBSRV GUI shall not offer physical media as a  distribution option.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4576	S-DSS-01680	5BX	The SDSRV Command Line Interface shall accept FTP Push distribution requests and associated parameters.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4577	S-DSS-01681	5BX	The SDSRV Command Line Interface shall include the FTP Push parameters in the ACQUIRE request it submits to the SDSRV	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4578	S-DSS-01682	5BX	The SDSRV Command Line Interface shall accept an ECSUSERPROFILE parameter.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4579	S-DSS-01683	5BX	The SDSRV Command Line Interface shall include the ECSUSERPROFILE parameter in the SDSRV ACQUIRE request it submits.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4580	S-DSS-01684	5BX	The SDSRV Command Line Interface shall accept a PRIORITY parameter.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4581	S-DSS-01685	5BX	The SDSRV Command Line Interface shall include the PRIORITY parameter  in the SDSRV ACQUIRE request it submits.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4582	S-DSS-01686	5BX	The SDSRV Command Line Interface shall accept an UserString parameter.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4583	S-DSS-01687	5BX	The SDSRV Command Line Interface shall include the UserString parameter  in the SDSRV ACQUIRE request it submits.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4584	S-DSS-01688	5BX	The SDSRV Command Line Interface shall accept an DDISTNOTIFYTYPE and a NOTIFY parameter.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4585	S-DSS-01689	5BX	The SDSRV Command Line Interface shall include the DDISTNOTIFYTYPE and a NOTIFY parameters  in the SDSRV ACQUIRE request it submits.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4586	S-DSS-01690	5BX	The SDSRV Command Line Interface shall accept a tag parameter.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4587	S-DSS-01691	5BX	The SDSRV Command Line Interface shall use the tag parameter to generate an rpcID for the SDSRV ACQUIRE request it submits.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4588	S-DSS-01692	5BX	The SDSRV Command Line Interface shall accept a list of up to 100 granule identifiers that represent the granules to be acquired.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4589	S-DSS-01693	5BX	The SDSRV Command Line Interface shall accept  granule identifiers specified in V0/DORRAN format (example: 'SC:L70RWRS.001:2000022933').	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4590	S-DSS-01694	5BX	The SDSRV Command Line Interface shall submit an ACQUIRE command for the identified granules.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4591	S-DSS-01695	5BX	The SDSRV Command Line Interface shall accept requests for a single Landsat floating scene and its associated subsetting parameters.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4592	S-DSS-01696	5BX	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.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4593	S-DSS-01697	5BX	The SDSRV Command Line Interface shall be able to accept requests from multiple PDS instances that may employ different user profiles.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4594	S-DSS-01698	5BX	The SDSRV Command Line Interface shall be able to accept requests for a designated mode.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4595	S-DSS-01699	5BX	It shall be possible to submit several requests in a given mode via the SDSRV Command Line Interface concurrently.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4596	S-DSS-01700	5BX	It shall be possible to submit requests via the SDSRV Command Line Interface in several different modes concurrently.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4597	S-DSS-30050	5BX	The DDIST CI shall be able to display the UserString parameter of an ACQUIRE command on the DDIST GUI.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4598	S-DSS-30052	5BX	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).	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4599	S-DSS-30054	5BX	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.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4600	S-DSS-30056	5BX	The DDIST CI shall cause PDS FTP Push requests to be distributed via the internal (i.e., drg-resident) ftp distribution server.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4601	S-DSS-30058	5BX	The DDIST CI shall suppress the DORRAN DN it currently sends for Landsat data requests if the request is a PDS request.	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4602	S-DSS-30060	5BX	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. 	00-1155	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4603	S-CSS-30635	6A	The ECS Registry shall permit the configuration of generic media options.	00-1156	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4604	S-CSS-30636	6A	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.	00-1156	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4605	S-CSS-30637	6A	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.	00-1156	12/19/2000  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	4694	S-SSS-10120	SY3	The NSBRV CI shall allow the operator to select a valid ECS physical media type for the bundling order.	02-1045	12/04/2002  		
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	1969	S-DSS-01861	B0	The SDSRV CI shall direct the DDIST CI to distribute data and metadata, via physical media, if specified by a valid Media Distribution Request.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2213	S-DSS-21352	B0	The STMGT CI shall have the capability to transfer data to and from 8mm tape.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2214	S-DSS-21354	B0	The STMGT CI shall have the capability to transfer data to and from 4mm tape.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2215	S-DSS-21356	B1	The STMGT CI shall have the capability to transfer data to and from 3480/3490 tape.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2218	S-DSS-21362	B0	The STMGT CI shall have the capability to transfer data to and from 6250 BPI tape.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2272	S-DSS-30065	B0	The DDIST CI shall allocate files to media based on a specific media capacity and the following rules:  (1) granules are allocated to media based on the order specified in the Media Distribution Request; (2) a granule of files in the  Media Distribution Request shall not cross media boundaries.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2313	S-DSS-22175	6A	The STMGT CI shall abort the operation and automatically request a new piece of media from the operations staff if the number of correctable errors exceeds a system threshold for a piece of media.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2330	S-DSS-30705	A	The DDIST CI shall, for each successful Media Distribution Request, generate a packing list identifying each item of physical media and the data recorded on that media.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2333	S-DSS-30730	B0	The DIPHW CI shall provide operations staff the capability to manually insert media into data input/output devices used for media ingest and distribution.	99-0729	08/25/1999  	No Data	
108	DADS2490	6A Partial	The ECS shall have the capability to distribute data on the following approved high density storage media:   a. CD-R    b.  DLT    c.  DVD-R	2335	S-DSS-30740	B0	The DIPHW CI shall provide operations staff the capability to manually remove media from data input/output devices used for media ingest and distribution.	99-0729	08/25/1999  	No Data	
503	DADS2492	5B	The ECS shall have the capability to produce duplicate media from a single master image for the following approved high density storage media:   a. CD-R    b. DVD-R	4679	0-000-00004	5B	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. 	02-0547	07/01/2002  		
504	DADS2494	5B	The ECS shall have the capability to generate media labels for the following approved high density storage media:   a. CD-R    b. DLT     c. DVD-R	4679	0-000-00004	5B	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. 	02-0547	07/01/2002  		
505	DADS2496	5B	The ECS shall have the capability of printing jewel case inserts for the following approved high density storage media:    a. CD-R    b. DVD-R	4679	0-000-00004	5B	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. 	02-0547	07/01/2002  		
506	DADS2498	5B	The ECS shall have the capability of performing post-production quality checks on the following approved high density storage media:     a.  CD-R      b. DLT      c. DVD-R	4679	0-000-00004	5B	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. 	02-0547	07/01/2002  		
109	DADS2510	Complete	The ECS shall copy data to the class of approved physical media specified in the corresponding product order.	1969	S-DSS-01861	B0	The SDSRV CI shall direct the DDIST CI to distribute data and metadata, via physical media, if specified by a valid Media Distribution Request.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	4247	C-CSS-40062	6A	The SBSRV shall allow operators to submit subscriptions that specify an FTP Pull Acquire as an action.	00-0076	01/31/2000  		
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	4248	C-CSS-40064	6A	The SBSRV shall acquire a granule on behalf of the user for FTP Pull if the subscription specifies FTP Pull Acquire as its action.	00-0076	01/31/2000  		
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	4249	C-CSS-40500	6A	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.	00-0076	01/31/2000  		
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	4250	C-CSS-30640	6A	The Registry shall store distribution options information. 	00-0076	01/31/2000  		
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	4251	C-CSS-30650	6A	The Registry shall provide an API to retrieve information that is hierarchically structured, containing dependencies between values. 	00-0076	01/31/2000  		
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	1971	S-DSS-01867	B0	The SDSRV CI shall direct the DDIST CI to transmit data and metadata electronically, via ftp, if specified by a valid Electronic Distribution Request.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	1972	S-DSS-01869	B0	The SDSRV CI shall direct the DDIST CI to stage the data and metadata in the User Pull Area if specified by a valid Electronic Distribution Request.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2256	S-DSS-22130	B0	The STMGT CI shall provide the capability to  limit access to Data in the user pull area to the data requester and the operations staff.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2266	S-DSS-30010	A	The DDIST CI shall direct the distribution of data and metadata to users, via physical media, via electronic transmission, or via staging to the User Pull Area as specified by the SDSRV CI.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2317	S-DSS-22125	Complete	The STMGT CI shall provide the capability to place Data in publicly available disks for users to "pull" the data via ftp at their discretion as specified by valid Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2318	S-DSS-30570	A	The DDIST CI shall send to the requesting client a Distribution Notification that notifies the client that the Data is available for a limited time.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2319	S-DSS-22162	Complete	The STMGT CI shall notify operations staff when the time limit has expired for Data in the user pull area.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2320	S-DSS-22163	Complete	The STMGT CI shall, after operator confirmation, delete expired Data from the user pull area.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2321	S-DSS-22164	Complete	The STMGT CI shall give operations staff the ability to turn off the function of operator confirmation associated with the automatic deletion of Data in the user pull area.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2322	S-DSS-30600	A	The DDIST CI shall direct the transfer of data to external file systems, via ftp, as specified by the SDSRV CI.	99-0729	08/25/1999  	No Data	
110	DADS2580	6A Partial	The ECS shall distribute data electronically.	2337	S-DSS-22165	Complete	The STMGT CI shall provide the capability for the operations staff to specify a percent utilization threshold for the user pull area above which operations staff will be notified.	99-0729	08/25/1999  	No Data	
111	DADS2675	Complete	The ECS shall maintain a log of all transmission problems and take internal corrective  action when network performance interrupts distribution efforts.	2133	S-DSS-20032	B0	The STMGT CI shall log, to the Event Log, transmission errors and re-transmission attempts associated with Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
111	DADS2675	Complete	The ECS shall maintain a log of all transmission problems and take internal corrective  action when network performance interrupts distribution efforts.	2304	S-DSS-30285	6A	The DDIST CI shall log, to the Event Log, failures to successfully complete Electronic Distribution Requests due to transmission failures.	99-0729	08/25/1999  	No Data	
111	DADS2675	Complete	The ECS shall maintain a log of all transmission problems and take internal corrective  action when network performance interrupts distribution efforts.	2307	S-DSS-30410	6A	The DDIST CI shall log all detected errors and faults to the Event Log.	99-0729	08/25/1999  	No Data	
111	DADS2675	Complete	The ECS shall maintain a log of all transmission problems and take internal corrective  action when network performance interrupts distribution efforts.	2325	S-DSS-30665	B0	The DDIST CI shall initiate the re-transmission of data in the event of a transmission failure, in order to complete a request for the electronic distribution of data.	99-0729	08/25/1999  	No Data	
111	DADS2675	Complete	The ECS shall maintain a log of all transmission problems and take internal corrective  action when network performance interrupts distribution efforts.	2326	S-DSS-30670	6A	The DDIST CI shall log, to the Event Log, all occurrences of transmission failures associated with Electronic Distribution Requests.	99-0729	08/25/1999  	No Data	
111	DADS2675	Complete	The ECS shall maintain a log of all transmission problems and take internal corrective  action when network performance interrupts distribution efforts.	2327	S-DSS-30680	B1	The DDIST CI shall provide the operations staff the capability to control the number of re-transmissions that will be attempted in order to complete a request for the electronic transmission of data.	99-0729	08/25/1999  	No Data	
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5091	S-DPL-13010	SY2	The Data Pool Service shall include a Data Pool Cleanup Utility for removing granules from the data pool disks and inventory.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5092	S-DPL-13020	SY2	Operators shall be able to run the Data Pool Cleanup Utility from the command line and in back ground.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5093	S-DPL-13030	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5094	S-DPL-13031	SY2	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. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5095	S-DPL-13032	SY2	The Data Pool Cleanup Utility shall validate the syntax of the command line parameters.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5096	S-DPL-13034	SY2	If the command line parameters fail the syntax validation, the Data Pool Cleanup Utility shall display the error and the correct command line syntax.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5097	S-DPL-13040	SY2	The Data Pool Cleanup Utility shall suppress all operator prompts if the no-prompt option is specified, assuming an affirmative response in these cases.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5098	S-DPL-13042	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5099	S-DPL-13050	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5100	S-DPL-13060	SY2	The Data Pool Cleanup Utility shall accept the cut-off  hours as a positive or negative number, including 0.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5101	S-DPL-13065	SY2	The Data Pool Cleanup Utility shall consider the date/time cut-off parameter optional with a default value of 0.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5102	S-DPL-13070	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5103	S-DPL-13080	SY2	The Data Pool Cleanup Utility shall prompt the operator for confirmation of the date/time cut-off if it is in the future. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5104	S-DPL-13091	SY2	The Data Pool Cleanup Utility shall accept the priority limit as a positive number between 1 and 255.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5105	S-DPL-13093	SY2	If a priority limit is not specified, the Data Pool Cleanup Utility shall assume a configurable default priority limit.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5106	S-DPL-13094	SY2	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	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5107	S-DPL-13100	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5108	S-DPL-13110	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5109	S-DPL-13120	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5110	S-DPL-13125	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5111	S-DPL-13130	SY2	The Data Pool Cleanup Utility shall remove all browse granules from the inventory that have been orphaned by the clean-up of science granules.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5112	S-DPL-13140	SY2	The Data Pool Cleanup Utility shall remove the files belonging to cleaned up browse granules from the Data Pool disks.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5113	S-DPL-13142	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5114	S-DPL-13144	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5115	S-DPL-13160	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5116	S-DPL-13170	SY2	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)	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5117	S-DPL-13180	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5118	S-DPL-13190	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5119	S-DPL-13200	SY2	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	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5120	S-DPL-13210	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5121	S-DPL-13212	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5122	S-DPL-13220	SY2	The Data Pool Cleanup Utility shall log all cleanup attempts for a granule, including completion status to the cleanup log file.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5123	S-DPL-13230	SY2	The Data Pool Cleanup Utility shall log the start of a cleanup run to the cleanup log file.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5124	S-DPL-13240	SY2	The Data Pool Cleanup Utility shall log the completion of a cleanup run to the cleanup log file.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5125	S-DPL-13260	SY2	The Data Pool Cleanup Utility shall log the total amount of space it cleaned up to the cleanup log file.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5126	S-DPL-13270	SY2	The Data Pool Cleanup Utility log entries shall include the date and time of the cleanup log file entry (at least to the millisecond).	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5127	S-DPL-13290	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5128	S-DPL-13300	SY2	The Data Pool Cleanup Utility shall generate a default name for the cleanup log file.  	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5129	S-DPL-13310	SY2	The Data Pool Cleanup Utility shall append output to the cleanup log file if it already exists.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5130	S-DPL-13320	SY2	The Data Pool Cleanup Utility shall create the cleanup log file if it does not exist.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5131	S-DPL-13330	SY2	The Data Pool Cleanup Utility shall create the cleanup log file if it does not exist.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5132	S-DPL-00010	SY2	The Data Pool shall provide anonymous FTP service for accessing the data pool.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5133	S-DPL-00020	SY2	The Data Pool service shall support FTP sessions in interactive mode.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5134	S-DPL-00021	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5135	S-DPL-00022	SY2	The Data Pool FTP service shall allow the FTP  banner to be configurable by the operator.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5136	S-DPL-00030	SY2	The Data Pool service shall support FTP sessions via script execution. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5137	S-DPL-00040	SY2	The Data Pool FTP service shall be accessible via the Data Pool web service.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5138	S-DPL-00050	SY2	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.  	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5139	S-DPL-00070	SY2	The Data Pool FTP service shall allow users to list the content of the data pool directories.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5140	S-DPL-00071	SY2	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. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5141	S-DPL-00080	SY2	The Data Pool FTP service shall allow users to traverse the data pool directory structure.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5142	S-DPL-00090	SY2	The Data Pool FTP service shall allow users to transfer single or multiple data files from the data pool to a remote host. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5143	S-DPL-00110	SY2	The Data Pool FTP service shall prevent users from deleting any files or directories. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5144	S-DPL-00120	SY2	The Data Pool FTP service shall prevent users from renaming any files or directories.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5145	S-DPL-00130	SY2	The Data Pool FTP service shall prevent users from modifying any files or directories.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5146	S-DPL-00131	SY2	The Data Pool FTP service shall prevent users from creating a new directory in the data pool.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5147	S-DPL-00132	SY2	The Data Pool FTP service shall prevent users from modifying access privileges on any files or directories in the data pool.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5148	S-DPL-00140	SY2	The Data Pool FTP service shall prevent users from transferring a file into the data pool.  	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5149	S-DPL-00150	SY2	The Data Pool FTP service shall prevent users from accessing any files or directories other than those included in the data pool. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5150	S-DPL-00160	SY2	The Data Pool FTP service shall provide an operator-configurable option for logging user events and errors.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5151	S-DPL-00190	SY2	The Data Pool FTP service shall log user events and errors.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5152	S-DPL-00200	SY2	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 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5153	S-DPL-00205	SY2	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) 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5154	S-DPL-00220	SY2	The Data Pool FTP service shall terminate a user session upon detecting inactivity for a preconfigured timeout period. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5155	S-DPL-00230	SY2	The Data Pool FTP service shall allow the operator to set the inactivity timeout period. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5211	S-DPL-05010	SY2	The Data Pool Service shall provide a Data Pool Web Access Service at each DAAC.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5212	S-DPL-05020	SY2	The Data Pool Web Access Service shall be accessible by users outside a DAAC as well as within a DAAC	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5213	S-DPL-05030	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5214	S-DPL-05040	SY2	The Data Pool Web Access Service shall include general information about the Data Pool on its home page. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5215	S-DPL-05050	SY2	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. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5216	S-DPL-05060	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5217	S-DPL-05070	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5218	S-DPL-05075	SY2	The Data Pool Web Access Service shall display on each page following a drill down the count of the remaining granules.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5219	S-DPL-05080	SY2	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	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5220	S-DPL-05090	SY2	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..	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5221	S-DPL-05100	SY2	The Data Pool Web Access Service shall support the following additional granule level metadata attributes for drill down:    a. Science QA Flag	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5222	S-DPL-05105	SY2	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	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5223	S-DPL-05110	SY2	The Data Pool Web Access Service shall allow the user to drill down on Date by entering or selecting a date range.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5224	S-DPL-05120	SY2	The Data Pool Web Access Service shall allow the user to drill down on Time of Day by entering or selecting a time range.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5225	S-DPL-05130	SY2	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).	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5226	S-DPL-05132	SY2	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).	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5227	S-DPL-05134	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5228	S-DPL-05140	SY2	The Data Pool Web Access Service shall allow the user to drill down on spatial coverage by drawing a LLBOX on a world map.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5229	S-DPL-05150	SY2	The Data Pool Web Access Service shall include explanatory information with each drill down choice, e.g., similar to what the EDG interface provides).	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5230	S-DPL-05160	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5231	S-DPL-05170	SY2	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).	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5232	S-DPL-05180	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5233	S-DPL-05190	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5234	S-DPL-05200	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5235	S-DPL-05210	SY2	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). 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5236	S-DPL-05220	SY2	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. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5237	S-DPL-05225	SY2	The Data Pool Web Access Service shall allow operators to configure the default display chunk size. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5238	S-DPL-05230	SY2	The Data Pool Web Access Service shall initiate the display of the results page by displaying the first chunk.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5239	S-DPL-05240	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5240	S-DPL-05250	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5241	S-DPL-05260	SY2	The Data Pool Web Access Service results page shall display with each granule a list of core metadata.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5242	S-DPL-05270	SY2	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	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5243	S-DPL-05280	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5244	S-DPL-05285	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5245	S-DPL-05290	SY2	The Data Pool Web Access Service results page shall display with each granule a link for accessing and displaying its XML metadata file.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5246	S-DPL-05295	SY2	The Data Pool Web Access Service shall allow the user to display the contents of the XML metadata file in a new browser window.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5247	S-DPL-05300	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5248	S-DPL-05305	SY2	The Data Pool Web Access Service shall permit a user to save the XML file locally that is currently being displayed.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5249	S-DPL-05310	SY2	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.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5250	S-DPL-05315	SY2	The Data Pool Web Access Service shall permit a user to save the browse image locally that is currently being displayed.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5251	S-DPL-05320	SY2	The Data Pool Web Access Service results page shall display with each granule links that support the ftp download of the granule files.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5252	S-DPL-05330	SY2	The Data Pool Web Access Service shall log all access to metadata files.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5253	S-DPL-05340	SY2	The Data Pool Web Access Service shall log all access to browse files.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5254	S-DPL-05350	SY2	The Data Pool Web Access Service shall log all access failures.	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5255	S-DPL-05360	SY2	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. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5256	S-DPL-05370	SY2	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. 	02-1086	12/12/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5288	S-DPL-32010	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5289	S-DPL-32020	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5290	S-DPL-32030	SY2	The DPASU shall be able to concurrently process the FTP Server log and the Web Access Service log.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5291	S-DPL-32040	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5292	S-DPL-32050	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5293	S-DPL-32060	SY2	The DPASU shall allow the initiation of parse processing of the FTP Server log and the Web Access Service log upon operator command.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5294	S-DPL-32070	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5295	S-DPL-32080	SY2	The DPASU shall prevent parse processing from occurring for given 24 hour period until the end time for that period has passed.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5296	S-DPL-32090	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5297	S-DPL-32100	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5298	S-DPL-32110	SY2	The DPASU operator initiated access log processing capability shall accept operator input to identify input log files.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5299	S-DPL-32120	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5300	S-DPL-32130	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5301	S-DPL-32140	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5302	S-DPL-32150	SY2	The DPASU shall not include duplicate entries of parsed information into the DPAL.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5303	S-DPL-32160	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5306	S-DPL-32170	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5307	S-DPL-32180	SY2	If syntax validation fails for any command line parameter, the DPASU capability shall notify the operator of the failure and display the correct syntax	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5308	S-DPL-32190	SY2	The DPASU shall allow the operator to request suppression of confirmation prompts and warning/error messages via a command line parameter.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5309	S-DPL-32200	SY2	If the operator requests that warning and error messages be suppressed, the DPASU shall write these messages to its error log.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5310	S-DPL-32210	SY2	The DPASU shall log all errors.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5311	S-DPL-32220	SY2	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)	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5312	S-DPL-32230	SY2	The DPASU shall record information in the DPAL sufficient to uniquely identify each granule access.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5336	S-DPL-30010	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5337	S-DPL-30015	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5338	S-DPL-30020	SY2	Operators shall be able to run the Data Pool Update Expiration utility from the command line and in the background.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5339	S-DPL-30025	SY2	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)	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5340	S-DPL-30030	SY2	The Data Pool Update Expiration utility shall accept the new expiration date as a date. 	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5341	S-DPL-30032	SY2	The Data Pool Update Expiration utility shall accept the new cleanup priority as a positive integer between 1 and 255 inclusive.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5342	S-DPL-30035	SY2	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	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5343	S-DPL-30040	SY2	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	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5344	S-DPL-30060	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5345	S-DPL-30065	SY2	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)	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5346	S-DPL-30070	SY2	The Data Pool Update Expiration utility shall, by default, prompt the operator for confirmation after displaying the confirmation information.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5347	S-DPL-30082	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5348	S-DPL-30085	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5349	S-DPL-30090	SY2	The Data Pool Update Expiration utility shall perform the requested updates immediately after operator confirmation.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5350	S-DPL-30110	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5351	S-DPL-30115	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5352	S-DPL-30140	SY2	The Data Pool Update Expiration utility shall log all updates. 	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5353	S-DPL-30142	SY2	The Data Pool Update Expiration utility log entries shall include the date and time of the log entry (at least to the millisecond).	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5354	S-DPL-30144	SY2	The Data Pool Update Expiration utility shall generate a default name for its log file.  	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5355	S-DPL-30146	SY2	The Data Pool Update Expiration utility shall append output to its log file if it already exists.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5356	S-DPL-30148	SY2	The Data Pool Update Expiration utility shall create its log file if it does not exist.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5357	S-DPL-30150	SY2	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'	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5358	S-DPL-30160	SY2	The Data Pool Update Expiration utility shall log all update errors in the Update Expiration log file. 	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5359	S-DPL-30170	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5360	S-DPL-30180	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5361	S-DPL-30185	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5362	S-DPL-30190	SY2	The Data Pool Update Expiration utility shall perform update operations such that they can be restarted and completed successfully if interrupted by a fault.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5363	S-DPL-30200	SY2	The Data Pool Update Expiration utility shall prevent database corruption due to conflicts with other Data Pool operations.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5364	S-DPL-30210	SY2	The Data Pool Update Expiration utility shall be able to operate in multiple modes concurrently.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5385	S-BGT-20010	SY3	The EcOsBulkURL utility shall accept a mandatory input parameter determining if the utility is to run in the 'Insert' mode or the 'Delete' mode.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5386	S-BGT-20020	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5387	S-BGT-20030	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5388	S-BGT-20040	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5389	S-BGT-20050	SY3	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	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5390	S-BGT-20060	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5391	S-BGT-20070	SY3	The EcOsBulkURL utility shall place URL insert and deletion file in an area accessible to ECHO via ftp pull	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5392	S-BGT-20080	SY3	The EcOsBulkURL utility shall be able to detect and export URL location for DPL holdings that were populated from ECS Archive.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5393	S-BGT-20090	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5394	S-BGT-20100	SY3	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)	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5395	S-BGT-20110	SY3	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).	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5396	S-BGT-20120	SY3	[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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5397	S-BGT-20130	SY3	The EcOsBulkURL utility shall be able to be run in multiple modes concurrently.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5398	S-BGT-20140	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5399	S-BGT-20160	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5400	S-DPL-13600	SY3	The Data Pool Cleanup Utility shall invoke the EcOsBulkURL as part of its normal operation, with the -delete parameter.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5401	S-DPL-13610	SY3	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	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5507	S-DPL-06010	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5508	S-DPL-06012	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5509	S-DPL-06020	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5510	S-DPL-06030	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5511	S-DPL-06040	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5512	S-DPL-06050	SY3	[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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5513	S-DPL-06060	SY3	The Data Pool web application service data conversion service shall allow the user to specify allowable conversion options for each granule. 	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5514	S-DPL-06070	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5515	S-DPL-06080	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5516	S-DPL-06090	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5517	S-DPL-06100	SY3	[DESIRABLE] The Data Pool web application service shall log all data conversion requests handled, identifying:    [logged information to be defined during design]  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5518	S-DPL-06110	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5519	S-DPL-06114	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5520	S-DPL-06116	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5521	S-DPL-13500	SY3	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'.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5522	S-DPL-13520	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5523	S-HEG-30010	SY3	The HEG front-end shall receive data conversion requests from the Data Pool web application service.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5524	S-HEG-30020	SY3	The HEG front-end shall retrieve data conversion requests from the queue for each granule for which conversion processing is requested.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5525	S-HEG-30030	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5526	S-HEG-30050	SY3	The HEG front-end shall include a data conversion order ID & request ID in the data conversion request file.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5527	S-HEG-30060	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5528	S-HEG-30070	SY3	The HEG front-end shall make available granules required for data conversion to a location that is accessible by the HEG Converter.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5529	S-HEG-30080	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5530	S-HEG-30090	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5531	S-HEG-30100	SY3	[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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5532	S-HEG-30110	SY3	The HEG front-end shall receive data conversion processing results information from a data conversion process when the process terminates.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5533	S-HEG-30120	SY3	The HEG front-end shall make available converted files for distribution to the user, via anonymous FTP.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5534	S-HEG-30150	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5535	S-HEG-30160	SY3	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  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5536	S-HEG-30170	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5537	S-HEG-30180	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5538	S-HEG-30190	SY3	The HEG front-end shall provide as an option, the ability to be started or initialized in a stopped processing queue condition.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5539	S-HEG-30200	SY3	The HEG front-end shall provide the capability for operators to change the state of individual entries in the processing queue.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5540	S-HEG-30210	SY3	The HEG front-end shall, when a shutdown request is received, kill all processing being performed by the HEG converter and exit.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5541	S-HEG-30220	SY3	The HEG front-end shall, when a stop queue processing request is received, cease to submit processing requests for HEG converter processing.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5542	S-HEG-30230	SY3	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'.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5543	S-HEG-30240	SY3	The HEG front-end shall be able to run in any mode.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5544	S-HEG-30250	SY3	The HEG front-end shall be able to run concurrently in different modes.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5545	S-HEG-30260	SY3	The HEG front-end shall return a status to the Data Pool web interface in response to each data conversion requests received.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5546	S-HEG-30270	SY3	[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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5547	S-HEG-30280	SY3	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)  	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5548	S-HEG-30290	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5549	S-HEG-30300	SY3	The HEG converter shall remove all temporary files used during the data conversion processing at the end of that processing.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5550	S-HEG-30310	SY3	The HEG converter shall be able to run in any mode.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5551	S-HEG-30320	SY3	The HEG converter shall be able to run concurrently in different modes.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5552	S-HEG-30330	SY3	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.	02-1094	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5553	S-DMS-50010	SY3	The GTWAY CI Inventory Search Result shall include an optional group containing the URL location for science granules residing in the Data Pool.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5554	S-DMS-50020	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5555	S-DMS-50025	SY3	The GTWAY CI shall have the ability to provide all necessary URL location information to handle multifile granules seamlessly.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5556	S-DMS-50030	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5557	S-DMS-50040	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5558	S-DMS-50050	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5559	S-DMS-50070	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5560	S-DMS-50080	SY3	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 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5561	S-DMS-50090	SY3	The GTWAY CI shall not degrade its performance in Inventory Search Result generation by more than 10%.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5562	S-DMS-50100	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5563	S-DMS-50110	SY3	The GTWAY CI shall format the expiration date for a data pool URL in universal time code (UTC). 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5564	S-DMS-50120	SY3	The GTWAY CI shall indicate when the Data Pool Inventory is offline in its inventory result to the EDG. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5565	S-DPL-40000	SY3	The Data Pool shall include a batch insert utility.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5566	S-DPL-40010	SY3	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	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5567	S-DPL-40020	SY3	The Data Pool Batch Insert Utility shall accept an optional command line parameter providing the Unix path name pointing to the input file.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5568	S-DPL-40030	SY3	The Data Pool Batch Insert Utility shall assume that the input is provided via standard input if the input path name parameter is missing.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5569	S-DPL-40040	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5570	S-DPL-40050	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5571	S-DPL-40055	SY3	The Data Pool Batch Insert Utility shall require that a batch label be provided if the granule list is provided via standard input.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5572	S-DPL-40060	SY3	The Data Pool Batch Insert Utility shall accept an optional command line parameter specifying a valid retention priority.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5573	S-DPL-40065	SY3	The Data Pool Batch Insert Utility shall use the configured default retention priority if none was specified in the command line parameters.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5574	S-DPL-40070	SY3	The Data Pool Batch Insert Utility shall accept an optional command line parameter specifying a valid retention period.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5575	S-DPL-40075	SY3	The Data Pool Batch Insert Utility shall use the configured default retention period if none was specified in the command line parameters.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5576	S-DPL-40080	SY3	The Data Pool Batch Insert Utility shall accept an optional command line parameter specifying whether the granule insert shall include only the metadata file.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5577	S-DPL-40090	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5578	S-DPL-40092	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5579	S-DPL-40094	SY3	The Data Pool Batch Insert Utility shall skip a granule if the collection is not eligible for inserts	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5580	S-DPL-40100	SY3	The Data Pool Batch Insert Utility shall accept an optional parameter providing a valid Theme name.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5581	S-DPL-40105	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5582	S-DPL-40110	SY3	The Data Pool Batch Insert Utility shall accept an optional parameter specifying an insert dispatch priority as an integer from 1 to 255.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5583	S-DPL-40120	SY3	The Data Pool Batch Insert Utility shall assume the lowest possible value for the dispatch priority if no dispatch priority parameter is specified.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5584	S-DPL-40130	SY3	The Data Pool Batch Insert Utility shall not perform the insert and return an error if any of the parameters have invalid values.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5585	S-DPL-40140	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5586	S-DPL-40145	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5587	S-DPL-40150	SY3	The Data Pool Batch Insert Utility shall log the provided identifiers of any granules that it skips and the reason for skipping.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5588	S-DPL-40160	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5589	S-DPL-40162	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5590	S-DPL-40164	SY3	The Data Pool Batch Insert Utility shall remove the duplicates if any input file contains or results in duplicate dbid.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5591	S-DPL-40170	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5592	S-DPL-40180	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5593	S-DPL-40182	SY3	Different instances of the Data Pool Batch Insert Utility shall be able to operate in different modes concurrently.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5594	S-DPL-40184	SY3	Multiple instances of the Data Pool Batch Insert Utility shall be able to operate in the same modes concurrently.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5595	S-DPL-40200	SY3	The Data Pool Batch Insert Utility shall not place any restrictions on the number of granules contained in a single insert batch.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5596	S-DPL-40210	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5597	S-DPL-40220	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5598	S-DPL-40300	SY3	The Data Pool Maintenance GUI shall be able to include status, batch label and insert dispatch priority in its action queue display.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5599	S-DPL-40310	SY3	The Data Pool Maintenance GUI shall be able to filter the insert action queue by  batch label and status individually and in combination.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5600	S-DPL-40320	SY3	The Data Pool Maintenance GUI shall allow the operator to display for each batch label, a summary of the actions by status.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5601	S-DPL-41005	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5602	S-DPL-41010	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5603	S-DPL-41020	SY3	The Data Pool Batch Insert Utility shall not accept both a Non-ECS Insert List and an ECS Insert List.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5604	S-DPL-41030	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5605	S-DPL-41040	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5606	S-DPL-41045	SY3	The Data Pool Batch Insert Utility for non-ECS granules shall skip duplicate entries in the Non-ECS Granule List.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5607	S-DPL-41050	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5608	S-DPL-41054	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5609	S-DPL-41060	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5610	S-DPL-41070	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5611	S-DPL-41080	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5612	S-DPL-41082	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5613	S-DPL-41084	SY3	The Data Pool Batch Insert Utility shall support requirements S-DPL-40090 to S-DPL-40094.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5614	S-DPL-41086	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5615	S-DPL-41110	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5616	S-DPL-41120	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5617	S-DPL-41130	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5618	S-DPL-41132	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5619	S-DPL-41122	SY3	The Data Pool Maintenance GUI shall require operators to enter a spatial search type when defining a non-ECS collection.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5620	S-DPL-41124	SY3	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)	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5621	S-DPL-41126	SY3	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).	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5622	S-DPL-41128	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5623	S-DPL-41129	SY3	The Data Pool Maintenance GUI shall allow operators to update the description of a non-ECS Data Pool collection.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5624	S-DPL-41150	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5625	S-DPL-41160	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5626	S-DPL-41170	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5627	S-DPL-41180	SY3	The DPAD shall support S-DPL-40220 in ticket DP_S3_01 regardless of whether a batch is for ECS or non-ECS granules.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5628	S-DPL-41190	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5629	S-DPL-41200	SY3	The DPIU shall parse the XML file, validate its correctness against the DTD, and return a fatal error if it fails validation.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5630	S-DPL-41210	SY3	The Data Pool Insert Service shall generate a unique Data Pool internal granule identifier for non-ECS granules.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5631	S-DPL-41220	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5632	S-DPL-41230	SY3	The DPIU shall populate the Data Pool inventory and warehouse from the XML file.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5633	S-DPL-41250	SY3	The DPIU shall return a fatal error if any mandatory metadata is missing.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5634	S-DPL-41260	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5635	S-DPL-41270	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5636	S-DPL-41275	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5637	S-DPL-41280	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5638	S-DPL-41290	SY3	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..]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5639	S-DPL-41295	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5640	S-DPL-41300	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5641	S-DPL-41320	SY3	The DPIU shall copy the XML metadata file into the target data pool directory.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5642	S-DPL-41330	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5643	S-DPL-41340	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5644	S-DPL-41350	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5645	S-DPL-41352	SY3	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.   	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5646	S-DPL-41354	SY3	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.    	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5647	S-DPL-41356	SY3	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.    	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5648	S-DPL-41360	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5649	S-DPL-41362	SY3	The Data Pool Insert Service shall skip the insertion of browse granules that are not in HDF format or do not contain jpeg images.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5650	S-DPL-41364	SY3	The Data Pool Insert Service shall log any skipped browse granules and the reason for skipping them.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5651	S-DPL-41370	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5652	S-DPL-41380	SY3	The Data Pool Insert Service shall insert cross references between the science granule and each  inserted browse granule into the Data Pool inventory.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5653	S-DPL-41390	SY3	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).  	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5654	S-DPL-41400	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5655	S-DPL-41410	SY3	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	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5656	S-DPL-41420	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5657	S-DPL-41430	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5658	S-DPL-41440	SY3	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.  	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5659	S-DPL-13650	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5660	S-DPL-30400	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5662	S-DPL-42010	SY3	The Data Pool Maintenance GUI shall allow an Operator to define a theme.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5663	S-DPL-42020	SY3	The Data Pool Maintenance GUI shall store the information associated with themes persistently in the Data Pool database.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5664	S-DPL-42030	SY3	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')	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5665	S-DPL-42040	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5666	S-DPL-42050	SY3	The Data Pool Maintenance GUI shall allow an Operator to list the themes in alphabetic order.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5667	S-DPL-42060	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5668	S-DPL-42070	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5669	S-DPL-42080	SY3	The Data Pool Maintenance GUI shall allow an Operator to select a theme from the displayed list for deletion.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5670	S-DPL-42090	SY3	The Data Pool Maintenance GUI shall require the Operator to confirm the deletion of a theme before actually deleting it.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5671	S-DPL-42100	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5672	S-DPL-42110	SY3	The Data Pool Maintenance GUI shall allow an Operator to select a theme from the displayed list for viewing.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5673	S-DPL-42120	SY3	The Data Pool Maintenance GUI shall allow an Operator to select a theme from the displayed list for editing.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5674	S-DPL-42130	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5675	S-SSS-11010	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5676	S-SSS-11020	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5677	S-SSS-11030	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5678	S-SSS-11040	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5679	S-SSS-11045	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5680	S-SSS-11050	SY3	The NSBRV CI shall allow an operator to list the subscriptions having insert actions associated with a particular theme.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5681	S-SSS-11060	SY3	The NSBRV CI shall allow an operator to select one or all subscriptions listed for a theme and suspend them.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5682	S-SSS-11070	SY3	The NSBRV CI shall allow an operator to select one or all subscriptions listed for a theme and resume them.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5683	S-SSS-11080	SY3	The NSBRV CI shall allow an operator to select any one of the subscriptions listed for a theme and view it.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5684	S-SSS-11090	SY3	The NSBRV CI shall allow an operator to select any one of the subscriptions listed for a theme and edit it.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5685	S-SSS-11100	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5686	S-SSS-11110	SY3	The NSBRV CI shall not queue a Data Pool insert action if it is associated with a theme that is not enabled for insert.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5687	S-DPL-42140	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5688	S-DPL-42150	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5689	S-DPL-42152	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5690	S-DPL-42154	SY3	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].	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5691	S-DPL-42160	SY3	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]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5692	S-DPL-05550	SY3	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.  	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5693	S-DPL-05560	SY3	The Data Pool Web Access Service shall offer a theme for drill down if and only if it is activated for web drill down. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5694	S-DPL-05570	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5695	S-DPL-13700	SY3	The Data Pool Cleanup Utility shall remove the cross references between themes and granules that are being cleaned up.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5696	S-DPL-13710	SY3	The Data Pool Cleanup Utility shall support a command line parameter to restrict the cleanup to the granules of a specific theme.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5697	S-DPL-13720	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5698	S-DPL-13730	SY3	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.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5699	S-DPL-13740	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5700	S-DPL-30450	SY3	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'.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5701	S-DPL-30460	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5702	S-DPL-30470	SY3	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. 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5703	S-DPL-30480	SY3	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.]	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5704	S-DPL-30490	SY3	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.] 	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5705	S-DPL-30500	SY3	The Data Pool Update Expiration utility shall ignore any command line parameter specifying verbose confirmation.	02-1095	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5706	S-DPL-00500	SY3	The Data Pool FTP service shall provide a data compression capability upon data download.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5707	S-DPL-00510	SY3	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 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5708	S-DPL-00520	SY3	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. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5709	S-DPL-00530	SY3	The data compression options supported by the Data Pool FTP service shall be operator configurable. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5711	S-DPL-00550	SY3	The Data Pool FTP service shall log the length of time it takes for transferring each data file. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5712	S-DPL-05700	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5713	S-DPL-05705	SY3	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 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5714	S-DPL-05710	SY3	The data compression options supported by the Data Pool Web access service shall be programmer configurable.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5715	S-DPL-05720	SY3	The Data Pool Web access service shall not provide Unix or gzip compression option  for Browse and metadata files. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5716	S-DPL-05725	SY3	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. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5717	S-DPL-05730	SY3	a. The Data Pool Web access service shall allow users to choose specific compression option explicitly for each download activity.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5718	S-DPL-00540	SY3	The Data Pool FTP log shall indicate whether or not compression was used for each data file transferred. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5719	S-DPL-60010	SY3	The Data Pool Service shall include a Data Pool inventory validation function.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5720	S-DPL-60020	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5721	S-DPL-60030	SY3	The Data Pool Inventory Cleanup Utility shall check the syntax of the new command line parameters pertaining to inventory validation.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5722	S-DPL-60035	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5723	S-DPL-60040	SY3	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies that orphan checking shall be performed. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5724	S-DPL-60042	SY3	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).	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5725	S-DPL-60044	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5726	S-DPL-60050	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5727	S-DPL-60055	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5728	S-DPL-60060	SY3	The Data Pool Inventory Cleanup Utility shall accept an optional command line parameter that specifies that phantom checking shall be performed.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5729	S-DPL-60070	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5730	S-DPL-60075	SY3	The Data Pool Inventory Cleanup Utility shall verify that the collection groups specified on the command line are valid Data Pool collection groups.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5731	S-DPL-60080	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5732	S-DPL-60090	SY3	The Data Pool Inventory Cleanup Utility shall pass the command line parameters that control the validation to the Data Pool inventory validation function.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5733	S-DPL-60092	SY3	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.] 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5734	S-DPL-60100	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5735	S-DPL-60110	SY3	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.]	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5736	S-DPL-60112	SY3	The Data Pool inventory validation function shall use an operator configurable default maximum orphan age if none is specified on the command line.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5737	S-DPL-60120	SY3	Operators shall be able to configure the default maximum orphan age in days.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5738	S-DPL-60130	SY3	The Data Pool inventory validation function shall remove all orphaned files from the data pool disks unless fixing discrepancies was suppressed. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5739	S-DPL-60140	SY3	The Data Pool inventory validation function shall log the orphaned files.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5740	S-DPL-60150	SY3	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]	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5741	S-DPL-60160	SY3	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.]	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5742	S-DPL-60170	SY3	The Data Pool inventory validation function shall log the phantom granules.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5743	S-DPL-60175	SY3	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)	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5744	S-DPL-60180	SY3	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. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5745	S-DPL-60185	SY3	The Data Pool inventory validation function shall log the temporary files whose age exceeds the maximum orphan age. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5746	S-DPL-60190	SY3	The Data Pool inventory validation function shall log the start of a validation.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5747	S-DPL-60192	SY3	The Data Pool inventory validation function shall include the validation settings in the log entry for the validation start.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5748	S-DPL-60195	SY3	The Data Pool inventory validation function shall log the completion of a validation.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5749	S-DPL-60200	SY3	The Data Pool inventory validation function shall log at completion the total number of orphans that were found if orphan checking was requested.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5750	S-DPL-60205	SY3	The Data Pool inventory validation function shall log at completion the total number of phantoms that were found if phantom checking was requested.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5751	S-DPL-60207	SY3	The Data Pool inventory validation function shall log at completion the total number of temp files that exceeded the maximum orphan age.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5752	S-DPL-60210	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5753	S-DPL-60215	SY3	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).	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5754	S-DPL-60220	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5755	S-DPL-60230	SY3	The Data Pool inventory validation function shall include the  pathname of all removed files in the corresponding log entry.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5756	S-DPL-60240	SY3	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..	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5757	S-DPL-60250	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5758	S-DPL-60260	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5759	S-DPL-60270	SY3	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.  	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5760	S-DPL-60280	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5761	S-DPL-60290	SY3	The Data Pool inventory validation function shall support multiple modes.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5762	S-DPL-60300	SY3	Different instances of the Data Pool inventory validation function shall be able to execute concurrently in different modes.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5763	S-DPL-05600	SY3	The Data Pool Web Access Service must be able to operate correctly and without fault while an inventory validation is in progress.  	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5764	S-DPL-42200	SY3	The Data Pool Insert Service must be able to operate correctly and without fault while an inventory validation is in progress.  	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5766	S-DPL-05810	SY3	The Data Pool Web Access Service shall support bookmarking the current position in the drill down. 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5767	S-DPL-05820	SY3	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.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5768	S-DPL-05865	SY3	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) 	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5769	S-DPL-05868	SY3	The Data Pool Web Access Service shall provide an option for users to download individual granule files associated with a multi-file granule.	02-1098	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5773	S-DPL-20100	SY2	The Data Pool Insert Service shall allow configuration of a default retention period for all Data Pool Insert actions.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5774	S-DPL-20150	SY2	The Data Pool Insert Service shall allow configuration of a default retention priority for all Data Pool Insert actions.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5775	S-DPL-20200	SY2	The Data Pool Insert Service shall allow an operator to specify, as configuration items, the mapping of ESDTs to Data Pool Collection groups.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5776	S-DPL-20350	SY2	The Data Pool Insert Service shall prevent the insertion of ineligible data types in the Data Pool.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5777	S-DPL-20400	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5778	S-DPL-20450	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5779	S-DPL-20500	SY2	The Data Pool Insert Service  shall prevent duplicate insertion of an ECS granule into the Data Pool.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5780	S-DPL-20600	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5781	S-DPL-20650	SY2	The Data Pool Insert Service shall allow an operator to suspend all Data Pool insert actions.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5782	S-DPL-20660	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5783	S-DPL-20670	SY2	The Data Pool Insert Service shall allow an operator to resume all Data Pool insert actions after they have been suspended.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5784	S-DPL-20680	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5785	S-DPL-20700	SY2	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).	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5786	S-DPL-20740	SY2	The Data Pool Insert Service shall allow the operator to determine the number of insert processes running, and the status of each.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5787	S-DPL-20750	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5788	S-DPL-20760	SY2	The Data Pool Insert Service shall allow the operator to cancel a pending Data Pool insert request.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5789	S-DPL-20770	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5790	S-DPL-20800	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5791	S-DPL-20900	SY2	The metadata file shall contain all ECS granule level metadata for that granule.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5792	S-DPL-21000	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5793	S-DPL-21050	SY2	The Data Pool Insert Service shall create the appropriate lowest level directory if it does not exist.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5794	S-DPL-21100	SY2	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).	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5795	S-DPL-21200	SY2	The Data Pool Insert Service shall insert the metadata file into the Data Pool disks with an .xml extension.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5796	S-DPL-21300	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5797	S-DPL-21400	SY2	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 	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5798	S-DPL-21500	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5799	S-DPL-21600	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5800	S-DPL-21700	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5801	S-DPL-21800	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5802	S-DPL-21900	SY2	The Data Pool Insert Service shall insert the science data file(s) into the Data Pool disks in the original ECS format.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5803	S-DPL-22000	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5804	S-DPL-22100	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5805	S-DPL-22200	SY2	The Data Pool Insert Service shall insert into the Data Pool all Browse images associated with science granules residing in the Data Pool . 	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5806	S-DPL-22300	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5807	S-DPL-22350	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5808	S-DPL-22400	SY2	The Data Pool Insert Service shall insert the Browse images into the Data Pool disks in jpeg format.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5809	S-DPL-22500	SY2	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	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5810	S-DPL-22600	SY2	The Data Pool Insert Service shall insert the Browse images into the Data Pool disks with a .jpg file extension.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5811	S-DPL-22700	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5812	S-DPL-22800	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5813	S-DPL-22900	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5814	S-DPL-23000	SY2	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	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5815	S-DPL-23200	SY2	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)	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5816	S-DPL-23250	SY2	The Data Pool Insert Service shall generate a default name for the insert log file.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5817	S-DPL-23260	SY2	The Data Pool Insert Service shall append output to the insert log file if it already exists.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5818	S-DPL-23270	SY2	The Data Pool Insert Service shall create the insert log file if it does not exist.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5819	S-DPL-23300	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5820	S-DPL-23350	SY2	The Data Pool Insert Service shall not start further Data Pool Insert actions if the 'No Free Space' flag is set.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5821	S-DPL-23355	SY2	The Data Pool Insert Service shall automatically resume processing of Data Pool Insert actions when the 'No Free Space' flag is cleared.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5822	S-DPL-23360	SY2	The Data Pool Insert Service shall allow the operator to determine whether the 'No Free Space'flag is set.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5823	S-DPL-23370	SY2	The Data Pool Insert Service shall allow the operator to reset the 'No Free Space' flag.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5824	S-DPL-23400	SY2	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)	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5825	S-DPL-23450	SY2	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.)	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5826	S-DPL-23500	SY2	The Data Pool Insert Service shall be able to operate in multiple modes concurrently.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5827	S-SSS-08500	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5828	S-SSS-08510	SY2	The NSBRV CI shall allow a Data Pool Insert action to be associated with any subscription placed on an ECS Insert event.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5829	S-SSS-08515	SY2	The NSBRV CI shall not allow a Data Pool Insert action to be associated with a subscription placed on ECS UpdateMetadata or Delete events.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5830	S-SSS-08520	SY2	The NSBRV CI shall allow an operator to associate a retention period with each Data Pool Insert action.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5831	S-SSS-08540	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5832	S-SSS-08550	SY2	The NSBRV CI shall allow an operator to associate a retention priority with each Data Pool Insert subscription.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5833	S-SSS-08560	SY2	The NSBRV CI shall accept the retention priority as a positive integer between 1 and 255.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5834	S-SSS-08600	SY2	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.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5835	S-SSS-08650	SY2	The NSBRV CI shall issue a warning if the operator enters a retention period of less than 3 days on a DataPoolInsert subscription.	02-1090	12/18/2002  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5846	S-DPL-14010	SY4	The DPL Cleanup Utility shall accept a 'pre-delete' command line parameter.	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5847	S-DPL-14020	SY4	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.	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5848	S-DPL-14030	SY4	The DPL Cleanup Utility, when receiving a 'pre-delete' parameter, shall not delete the granules from the Data Pool.	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5849	S-DPL-14040	SY4	The DPL Cleanup Utility, when receiving a 'pre-delete' parameter, shall call the Bulk URL Utility.	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5850	S-DPL-14050	SY4	The DPL Cleanup Utility shall accept a 'delete dpl only' command line parameter.	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5851	S-DPL-14060	SY4	The DPL Cleanup Utility, when receiving a 'delete dpl only' parameter, shall delete the appropriate granules from the Data Pool.	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5852	S-DPL-14070	SY4	The DPL Cleanup Utility, when receiving a 'delete dpl only' parameter, shall not call the Bulk URL Utility	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5853	S-DPL-14075	SY4	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	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5854	S-DPL-14080	SY4	The DPL Cleanup Utility shall accept a 'delete all' command line parameter	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5855	S-DPL-14090	SY4	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	03-0583	08/21/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5874	S-DPL-23910	SY4	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.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5875	S-DPL-05915	SY4	The Data Pool Web Access service shall support requests for selecting one or more bands from an individual granule.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5876	S-DPL-05920	SY4	The Data Pool Web Access service shall support request for selecting one or more bands from an individual granule offered in the results list.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5877	S-DPL-05925	SY4	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.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5878	S-DPL-05930	SY4	The Data Pool Web Access service shall include all bands for all granules as a default.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5879	S-DPL-05935	SY4	The HEG Front End shall accept requests from Data Pool Web Access Service for band subsetting.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5880	S-DPL-05940	SY4	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	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5881	S-DPL-23930	SY4	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.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5882	S-DPL-23940	SY4	The Data Pool Band Transition utility shall be able to stop and restart without loosing track of which granules have been already processed.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5883	S-DPL-23950	SY4	The Data Pool Band Transition utility shall not take more than one second in processing time per granule.	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5885	S-DPL-05950	SY4	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	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5886	S-DPL-05955	SY4	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)	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5888	S-DPL-05965	SY4	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.)	03-0673	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5900	S-DPL-65010	SY4	The Data Pool CI shall provide a QA Update Propagation Utility that is executable via a Unix command line.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5901	S-DPL-65020	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5902	S-DPL-65030	SY4	The Data Pool QA Update Propagation Utility shall accept as input information created by the QAMUT CI that identifies its ECS QA flag updates.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5903	S-DPL-65040	SY4	The Data Pool QA Update Propagation Utility shall apply the ECS QA flag updates to the affected Data Pool inventory database entries.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5904	S-DPL-65050	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5905	S-DPL-65060	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5906	S-DPL-65070	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5907	S-DPL-65080	SY4	The Data Pool QA Update Propagation Utility shall be able to operate in multiple modes concurrently.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5908	S-DPL-65090	SY4	The Data Pool QA Update Propagation Utility shall prevent multiple concurrent executions in the same mode.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5909	S-DPL-65100	SY4	The Data Pool QA Update Propagation Utility shall log the following information. a. any command line parameters b. any errors.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5910	S-DPL-65110	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5911	S-DPL-65120	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5912	S-DSS-40410	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5913	S-DSS-40355	SY4	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.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	5914	S-DSS-40420	SY4	The QAMUT CI shall be able to provide a record of its QA updates to the DPL subsystem in multiple modes concurrently.	03-0674	10/02/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6147	S-DPL-66005	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6148	S-DPL-66010	SY4	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	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6149	S-DPL-66015	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6150	S-DPL-66020	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6151	S-DPL-66025	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6152	S-DPL-66030	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6153	S-DPL-66035	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6154	S-DPL-66040	SY4	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).	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6155	S-DPL-66045	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6156	S-DPL-66050	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6157	S-DPL-66055	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6159	S-DPL-66065	SY4	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.)	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6160	S-DPL-66070	SY4	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).	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6161	S-DPL-66075	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6162	S-DPL-66080	SY4	The Collection-to-Group Remapping  utility shall be able to detect and recover from an aborted utility run.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6163	S-DPL-66085	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6164	S-DPL-66090	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6165	S-DPL-66095	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6166	S-DPL-66100	SY4	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.	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6167	S-DPL-66105	SY4	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).	03-0710	10/23/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6198	S-DPL-40510	SY4	The Data Pool Database shall support group ids of up to 12 characters.	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6199	S-DPL-40520	SY4	The Data Pool Database shall support the association of a display name of up to 12 characters with each Data Pool group.	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6200	S-DPL-40530	SY4	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).	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6201	S-DPL-40535	SY4	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.'	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6202	S-DPL-40540	SY4	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.	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6203	S-DPL-40545	SY4	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.	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6204	S-DPL-40550	SY4	The Data Pool Maintenance GUI shall allow full capability operators to update the 'display name' of  a Data Pool group.	03-0720	10/28/2003  		
514	DADS2676	SY2 SY3	The ECS shall provide an on-line cache of data products that is accessible by end users via the Web and FTP.  The minimal capacity of these caches shall be as follows:     a. EDC DAAC:  50 Terabytes     b.  ASDC DAAC:  30 Terabytes    c. NSIDC DAAC: 50 Terabytes	6205	S-DPL-40560	SY4	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.	03-0720	10/28/2003  		
112	DADS2770	Complete	Upon receipt and approval of a request, the ECS shall make stored data products available for delivery to the requester within 24 hours for data distributed on physical media.	1968	S-DSS-01860	B1	The SDSRV CI shall support making stored Data Products available on physical media within 24 hours of receipt of a Media Distribution Request.	99-0729	08/25/1999  	No Data	
112	DADS2770	Complete	Upon receipt and approval of a request, the ECS shall make stored data products available for delivery to the requester within 24 hours for data distributed on physical media.	2231	S-DSS-21500	B1	The SDSRV CI shall support making stored Data Products available on physical media within 24 hours	99-0729	08/25/1999  	No Data	
112	DADS2770	Complete	Upon receipt and approval of a request, the ECS shall make stored data products available for delivery to the requester within 24 hours for data distributed on physical media.	2340	S-DSS-30800	B1	The DDIST CI shall support making stored products available on physical media within 24 hours.	99-0729	08/25/1999  	No Data	
112	DADS2770	Complete	Upon receipt and approval of a request, the ECS shall make stored data products available for delivery to the requester within 24 hours for data distributed on physical media.	2345	S-DSS-30950	B1	The DIPHW CI shall be sized to temporarily store the total number of bytes of distribution data derived from Reference Table: TBD.	99-0729	08/25/1999  	No Data	
112	DADS2770	Complete	Upon receipt and approval of a request, the ECS shall make stored data products available for delivery to the requester within 24 hours for data distributed on physical media.	2346	S-DSS-30960	B1	The DIPHW CI shall be sized to support a sustained I/O rate of 1x the production volume for media distribution, where 1x production volume is derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	4170	S-DSS-20011	6A	The STMGT CI shall perform reads and writes to the archive concurrently for each request.	99-1176	12/01/1999  		
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	4171	S-DSS-20012	6A	The STMGT CI shall permit only a configurable number of files to be written into or read from the archive at the same time.	99-1176	12/01/1999  		
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2381	S-DSS-70200	B0	The WKSHW CI at the GSFC DAAC shall be capable of supporting the ingest of 574 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2382	S-DSS-70201	B0	The WKSHW CI at the LaRC DAAC shall be capable of supporting the ingest of 295 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2383	S-DSS-70202	B0	The WKSHW CI at the EDC DAAC shall be capable of supporting the ingest of 540 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2384	S-DSS-70203	B0	The WKSHW CI at the NSIDC DAAC shall be capable of supporting the ingest of 20 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2403	S-DSS-80420	B0	The DRPHW CI at the LaRC DAAC shall be sized to store and maintain the volume of EDOS Level 0 data for a 1-year period of time as derived from Table C-1 of Appendix C of the F&PRS.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2413	S-DSS-80610	B0	The DRPHW CI at the GSFC DAAC shall have the capacity to store 574 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2414	S-DSS-80611	B0	The DRPHW CI at the LaRC DAAC shall have the capacity to store 295 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2415	S-DSS-80612	B0	The DRPHW CI at the EDC DAAC shall have the capacity to store 540 GB in any given day.	99-0729	08/25/1999  	No Data	
113	DADS2778	EOC Partial	The ECS shall be capable of receiving and archiving three days' worth of data (see Appendix C) in any given day.	2416	S-DSS-80613	B0	The DRPHW CI at the NSIDC DAAC shall have the capacity to store 20 GB in any given day.	99-0729	08/25/1999  	No Data	
114	DADS2900	EOC Partial	The ECS shall provide archival capacity for current volume requirements plus one year.  Volume requirements are specified in Appendix C.	2404	S-DSS-80430	B0	The DRPHW CI at the GSFC DAAC shall be sized to store and maintain the volume of EDOS Level 0 data for a 1-year period of time as derived from Table C-1 of Appendix C of the F&PRS.	99-0729	08/25/1999  	No Data	
114	DADS2900	EOC Partial	The ECS shall provide archival capacity for current volume requirements plus one year.  Volume requirements are specified in Appendix C.	2417	S-DSS-80615	B0	The DRPHW CI at the GSFC DAAC shall have the capacity to store 245 terabytes.	99-0729	08/25/1999  	No Data	
114	DADS2900	EOC Partial	The ECS shall provide archival capacity for current volume requirements plus one year.  Volume requirements are specified in Appendix C.	2418	S-DSS-80616	B0	The DRPHW CI at the LaRC DAAC shall have the capacity to store 83 terabytes.	99-0729	08/25/1999  	No Data	
114	DADS2900	EOC Partial	The ECS shall provide archival capacity for current volume requirements plus one year.  Volume requirements are specified in Appendix C.	2419	S-DSS-80617	B0	The DRPHW CI at the EDC DAAC shall have the capacity to store 215 terabytes.	99-0729	08/25/1999  	No Data	
114	DADS2900	EOC Partial	The ECS shall provide archival capacity for current volume requirements plus one year.  Volume requirements are specified in Appendix C.	2420	S-DSS-80618	B0	The DRPHW CI at the NSIDC DAAC shall have the capacity to store 8 terabytes.	99-0729	08/25/1999  	No Data	
115	DADS2910	Complete	The ECS archival storage at each DAAC shall be field-expandable.	2168	S-DSS-20590	A	The STMGT CI shall provide archival storage which can be expanded to support greater storage capacity without removing it from the archive site.	99-0729	08/25/1999  	No Data	
116	DADS2950	6A Future	The ECS archive media shall be capable of being manually mounted at each DAAC, in case of failure of the automated system.	2141	S-DSS-20110	B1	The DRPHW CI shall provide operations staff the capability to manually insert media into archive storage devices.	99-0729	08/25/1999  	No Data	
116	DADS2950	6A Future	The ECS archive media shall be capable of being manually mounted at each DAAC, in case of failure of the automated system.	2142	S-DSS-20120	B1	The DRPHW CI shall provide operations staff the capability to manually remove media from archive storage devices.	99-0729	08/25/1999  	No Data	
116	DADS2950	6A Future	The ECS archive media shall be capable of being manually mounted at each DAAC, in case of failure of the automated system.	2145	S-DSS-20130	6A	The STMGT CI shall provide operations staff the capability to manually dismount archive media from archive storage devices.	99-0729	08/25/1999  	No Data	
116	DADS2950	6A Future	The ECS archive media shall be capable of being manually mounted at each DAAC, in case of failure of the automated system.	2146	S-DSS-20140	6A	The STMGT CI shall provide operations staff the capability to manually mount archive media into archive storage devices.	99-0729	08/25/1999  	No Data	
117	DADS3000	Complete	The ECS archive media shall support a bit error rate after correction of less than 1 in 10 to the 12th.	2236	S-DSS-21750	A	The DRPHW CI shall provide a bit error rate after correction less than 1 in 1 X 10**12. (This requirement may be fulfilled with a combination of hardware and software components.)	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2054	S-DSS-04382	B0	The SDSRV CI shall maintain a backup indicator, for each data type, that specifies whether or not backup copies are to be created and maintained for that data type.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2055	S-DSS-04384	B0	The SDSRV CI shall request that the STMGT CI create both a local backup copy and off-site backup copy of a data product, as determined by the data product's backup indicator.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2056	S-DSS-04386	B0	The SDSRV CI shall maintain the location of each primary copy of a locally-archived data product, and the location of the product's local and off-site backup copies, if they exist.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2088	S-DSS-04900	B0	The SDSRV CI shall, at the direction and approval of the operations staff, retrieve an offsite copy of a product.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2145	S-DSS-20130	6A	The STMGT CI shall provide operations staff the capability to manually dismount archive media from archive storage devices.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2160	S-DSS-20410	B0	The STMGT CI shall notify the operator upon the failure of retrieval of a local or offsite backup copy.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2161	S-DSS-20420	A	The STMGT CI shall be capable of producing a backup copy of designated EOS data.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2162	S-DSS-20430	A	The STMGT CI shall be capable of producing backup archive media which is compatible with approved ECS formats.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2175	S-DSS-20634	B1	The STMGT CI shall notify the operator and automatically retrieve a local backup copy of product upon the failure of the retrieval of the primary copy of the product.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2176	S-DSS-20650	B0	The STMGT CI shall provide operations staff the capability to specify the products to be backed up at both local and offsite archives.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2177	S-DSS-20660	B0	The STMGT CI shall provide operations staff the capability to restore backups of specified data holdings.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2180	S-DSS-20740	B0	The STMGT CI shall provide operations staff the capability to restore the primary copy of a product from either the local backup copy or the offsite backup copy.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2399	S-DSS-80250	B0	The DRPHW CI shall have sufficient capacity to backup 2% of the primary copies of locally-archived data products.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2400	S-DSS-80260	B0	The DRPHW CI, at LaRC, shall have the storage capacity to meet the GSFC DAAC requirements for off-site backup.	99-0729	08/25/1999  	No Data	
118	DADS3040	Complete	The ECS backup media shall be removable from the DAAC (e.g., for safe off-site storage).	2401	S-DSS-80270	B0	The DRPHW CI, at GSFC, shall have sufficient storage capacity to store the offsite backup copies required by the EDC, LaRC and the NSIDC DAACs.	99-0729	08/25/1999  	No Data	
119	DADS3055	Complete	At each ECS DAAC all backup media shall be capable of being mounted automatically where appropriate, with the provision for manual failover.	2140	S-DSS-20095	B0	The STGMT CI shall have the capability to automatically mount archive media into storage devices.	99-0729	08/25/1999  	No Data	
119	DADS3055	Complete	At each ECS DAAC all backup media shall be capable of being mounted automatically where appropriate, with the provision for manual failover.	2141	S-DSS-20110	B1	The DRPHW CI shall provide operations staff the capability to manually insert media into archive storage devices.	99-0729	08/25/1999  	No Data	
119	DADS3055	Complete	At each ECS DAAC all backup media shall be capable of being mounted automatically where appropriate, with the provision for manual failover.	2142	S-DSS-20120	B1	The DRPHW CI shall provide operations staff the capability to manually remove media from archive storage devices.	99-0729	08/25/1999  	No Data	
119	DADS3055	Complete	At each ECS DAAC all backup media shall be capable of being mounted automatically where appropriate, with the provision for manual failover.	2145	S-DSS-20130	6A	The STMGT CI shall provide operations staff the capability to manually dismount archive media from archive storage devices.	99-0729	08/25/1999  	No Data	
119	DADS3055	Complete	At each ECS DAAC all backup media shall be capable of being mounted automatically where appropriate, with the provision for manual failover.	2146	S-DSS-20140	6A	The STMGT CI shall provide operations staff the capability to manually mount archive media into archive storage devices.	99-0729	08/25/1999  	No Data	
119	DADS3055	Complete	At each ECS DAAC all backup media shall be capable of being mounted automatically where appropriate, with the provision for manual failover.	2147	S-DSS-20180	B0	The STMGT CI shall have the capability to automatically dismount archive media from storage devices.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	7134	S-DPL-16280	SY6	The Data Pool Ingest GUI shall permit authorized (ingest tuning) operators to configure the maximum number of concurrent FTP operations that may be in progress by ECS host on which an ingest FTP client is running. 	08-0426	09/29/2008  		
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	7164	S-DPL-16460	SY6	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.]	08-0426	09/29/2008  		
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	7680	S-DPL-60510	72	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.]	08-0426	09/29/2008  		
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	7681	S-DPL-60520	72	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.]	08-0426	09/29/2008  		
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	1967	S-DSS-01850	B1	The SDSRV CI shall be capable of supporting 200% growth in the number of Data Requests it accepts and validates without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2232	S-DSS-21510	B1	The STMGT CI shall have the capability to expand its storage capacity by 200% with no change to its architecture or design.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2238	S-DSS-21770	A	The DRPHW CI shall be capable of providing of 200 percent expansion in capacity without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2344	S-DSS-30875	B1	The DDIST CI shall be capable of providing 200% expansion in capacity without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2571	S-INS-00900	B0	The INGST CI at the GSFC DAAC shall be capable of 200 percent expansion in throughput without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2572	S-INS-00910	B0	The INGST CI at the LaRC DAAC shall be capable of 200 percent expansion in throughput without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2573	S-INS-00925	B0	The INGST CI at the EDC DAAC shall be capable of 200 percent expansion in throughput without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2574	S-INS-00927	B0	The INGST CI at the NSIDC DAAC shall be capable of 200 percent expansion in throughput without architecture or design change.	99-0729	08/25/1999  	No Data	
120	DADS3090	Complete	The ECS shall be capable of 200% expansion in data archive input/output throughput and archive capacity without architecture or design change.	2575	S-INS-00930	B1	The INGST CI at the JPL DAAC shall be capable of 200 percent expansion in throughput without architecture or design change.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	1979	S-DSS-01950	B1	The SSDSRV CI shall support distributing the number of bytes of data per day derived from Reference Table:  TBD, to the PRONG CI (in support of production) by accepting and validating the number requests per day from the PRONG CI derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	1980	S-DSS-01960	B1	The SDSRV CI shall support distributing the bytes of data per day derived from Reference Table:  TBD, to the PRONG CI (in support of production) by retrieving and staging the number of bytes per day for the PRONG CI derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	1982	S-DSS-02010	B1	The ACMHW CI shall be sized to support the number of operations/second derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2343	S-DSS-30870	B1	The DAAC DDIST CI shall be capable of electronically distributing data to users in support of Electronic Distribution Requests at a rate equivalent to daily product volume, L1-L4.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2346	S-DSS-30960	B1	The DIPHW CI shall be sized to support a sustained I/O rate of 1x the production volume for media distribution, where 1x production volume is derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2385	S-DSS-70205	B0	The WHSHW CI at the GSFC DAAC shall be capable of supporting the distribution of 368 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2386	S-DSS-70206	B0	The WHSHW CI at the LaRC DAAC shall be capable of supporting the distribution of 146 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2387	S-DSS-70207	B0	The WHSHW CI at the EDC DAAC shall be capable of supporting the distribution of 88 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2388	S-DSS-70208	B0	The WHSHW CI at the NSIDC DAAC shall be capable of supporting the distribution of 11 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2421	S-DSS-80620	B0	The DRPHW CI at the GSFC DAAC shall be capable of supporting the retrieval of 368 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2422	S-DSS-80621	B0	The DRPHW CI at the LaRC DAAC shall be capable of supporting the retrieval of 146 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2423	S-DSS-80622	B0	The DRPHW CI at the EDC DAAC shall be capable of supporting the retrieval of 88 GB/day.	99-0729	08/25/1999  	No Data	
121	DADS3100	EOC Partial	The ECS shall be capable of  transmitting data over communications network in support of:    a. External data production at the data rate specified in the SIPS ICD    b. Data distribution requests at a rate equivalent to 80 percent of daily product archive volume (L0-L4)	2424	S-DSS-80623	B0	The DRPHW CI at the NSIDC DAAC shall be capable of supporting the retrieval of 11 GB/day.	99-0729	08/25/1999  	No Data	
123	DADS3110	EOC Partial	The ECS shall be capable of distributing data via approved physical media at a rate equivalent to 20 percent of the daily product archive volume (L0-L4 data) at that DAAC as specified in Appendix C.	2341	S-DSS-30810	B1	The DDIST CI shall be capable of distributing Data via physical media generated a rate equivalent to the daily rate data are ingested at that site.	99-0729	08/25/1999  	No Data	
123	DADS3110	EOC Partial	The ECS shall be capable of distributing data via approved physical media at a rate equivalent to 20 percent of the daily product archive volume (L0-L4 data) at that DAAC as specified in Appendix C.	2345	S-DSS-30950	B1	The DIPHW CI shall be sized to temporarily store the total number of bytes of distribution data derived from Reference Table: TBD.	99-0729	08/25/1999  	No Data	
123	DADS3110	EOC Partial	The ECS shall be capable of distributing data via approved physical media at a rate equivalent to 20 percent of the daily product archive volume (L0-L4 data) at that DAAC as specified in Appendix C.	2346	S-DSS-30960	B1	The DIPHW CI shall be sized to support a sustained I/O rate of 1x the production volume for media distribution, where 1x production volume is derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	1976	S-DSS-01900	B1	The SDSRV CI shall be capable of receiving a combined maximum number of Data Requests per hour (across ECS) from the Data Management Subsystem and/or the client Subsystem as derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	1977	S-DSS-01910	B1	The SDSRV CI shall be capable of receiving a combined maximum number of Browse Requests per hour (across ECS) from the Data Management Subsystem and/or the Client Subsystem as derived from Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	1978	S-DSS-01920	B1	The SDSRV CI shall support making pre-computed Browse Data available to a requester in 58 seconds after accepting and validating the request in the number of seconds specified in Reference Table:  TBD.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	2045	S-DSS-04032	B1	The SDSRV CI shall have the capability  to support the transaction rates as specified in Table 7-4 of the Functional and Performance Requirements Specification for the ECS.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	2153	S-DSS-20315	B1	The STMGT CI shall have the capability  to support the transaction rates as specified in Table 7-4 of the Functional and Performance Requirements Specification for the ECS.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	2375	S-DSS-60310	B1	The ACMHW CI shall have the capability  to support the transaction rates as specified in Table 7-4 of the Functional and Performance Requirements Specification for the ECS.	99-0729	08/25/1999  	No Data	
124	DADS3135	Complete	The ECS shall have the capability to support the transaction rate and response times as specified in Table 6-1.	2402	S-DSS-80310	B1	The DRPHW CI shall have the capability  to support the transaction rates as specified in Table 7-4 of the Functional and Performance Requirements Specification for the ECS.	99-0729	08/25/1999  	No Data	
125	EOSD0020	Complete	The ECS shall use and support the  EDOS/EMSn interface to obtain the data capture, data archival, and data distribution services needed to achieve full end-to-end ECS functionality.	2799	C-ISS-11195	B0	The ISS shall provide for connectivity with EBnet at the following ECS sites:     a. GSFC DAAC     b. GSFC EOC     c. GSFC SMC     d. LaRC DAAC       h. NSIDC DAAC     i.  EDC DAAC	99-0729	08/25/1999  	No Data	
125	EOSD0020	Complete	The ECS shall use and support the  EDOS/EMSn interface to obtain the data capture, data archival, and data distribution services needed to achieve full end-to-end ECS functionality.	2822	C-ISS-21195	B1	The ISS shall provide for connectivity with EBnet at the JPL DAAC.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2900	C-MSS-18500	5A	The MSS-MCI shall ensure that the following calendar transitions are handled completely and accurately:  a. New Year  b. New Decade  c. New Century  d. Leap Year.	00-0939	09/21/2000  		
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2976	C-MSS-36820	5A	The MSS-MACI shall ensure that the following calendar transitions are handled completely and accurately:  a. New Year  b. New Decade  c. New Century  d. Leap Year.	00-0939	09/21/2000  		
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	3075	C-MSS-45330	5A	The MSS-MLCI shall ensure that the following calendar transitions are handled completely and accurately:  a. New Year  b. New Decade  c. New Century  d. Leap Year.	00-0939	09/21/2000  		
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	330	S-CLS-10010	B1	The WKBCH CI shall provide the capability for users to compose Search Requests based on product specific  attributes.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	358	S-CLS-10220	B0	The WKBCH CI shall allow users to formulate a Product Request based on the results of searching the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	1094	C-CSS-60520	IR1	The CSS File Access Service shall support the File Transfer Protocol (FTP).	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	1841	S-DSS-00070	B0	The SDSRV CI shall accept Service Requests from the Data Processing subsystem and, as a result, provide access to Data for the purpose of reprocessing.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	1847	S-DSS-00115	B1	The SDSRV CI shall accept Search Status Requests for a specified active Search Request and, if requested, provide all Search Results accumulated for that Search Request.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	1848	S-DSS-00116	B1	The SDSRV CI shall accept Search Status Requests for a specified active Search Request and, if requested, provide all Search Results accumulated since the last Search Status Request for that Search Request.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2559	S-INS-00780	A	The INGST CI shall ingest data, provided by the Landsat 7 Processing System (LPS), into the EDC DAAC using a  file transfer protocol.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2561	S-INS-00785	B0	The INGST CI shall ingest Data, provided by the Landsat 7 Image Assessment System (IAS), from the LAN into the EDC DAAC via SMC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2562	S-INS-00787	6A	The INGST CI shall ingest Data, provided by the Landsat 7 International Ground Stations (IGSs), into the EDC DAAC on 8 mm cartridge tape.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2657	S-IOS-00080	A	The ADSRV CI shall provide a capability to access Advertisements for ECS and non-ECS data and services.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	2689	S-IOS-00690	B1	The ADSRV CI shall accept Search Requests in a format compatible with the Earth Science Query Language.	99-0729	08/25/1999  	No Data	
127	EOSD0030	EOC	The ECS shall, during its lifetime, ingest, archive, distribute and provide search and access for EOS and related non-EOS data and products.	3524	S-PLS-00604	B0	The PLANG CI shall be able to access advertisements for ECS and non-ECS data and services from the IOS.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	669	S-CLS-17100	B1	When WKBCH CI mode-specific applications are not configured in OPS mode, it shall not be possible for them to write to OPS data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	670	S-CLS-17110	B1	The WKBCH CI shall include the mode identifier in activity log record entries for cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	671	S-CLS-17140	B1	WKBCH CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	672	S-CLS-17150	B1	WKBCH CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	673	S-CLS-17160	B1	WKBCH CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	674	S-CLS-17170	B1	WKBCH CI client applications shall incorporate a mode-identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	675	S-CLS-17180	B1	The WKBCH CI shall be capable of using simulated time values supplied by CSS when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	676	S-CLS-17190	B1	WKBCH CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1319	S-DMS-01090	Complete	The LIMGR CI shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1320	S-DMS-01094	Complete	The LIMGR CI shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1321	S-DMS-01095	Complete	The LIMGR CI shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1322	S-DMS-01096	Complete	The LIMGR CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1323	S-DMS-01098	Complete	The LIMGR CI shall use the CSS time service when obtaining system time.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1324	S-DMS-01099	Complete	The LIMGR CI executables and scripts shall accept a specific mode at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1368	S-DMS-23920	Complete	The DDICT CI shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1369	S-DMS-23924	Complete	The DDICT CI shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1370	S-DMS-23925	Complete	The DDICT CI shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1371	S-DMS-23926	Complete	The DDICT CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1372	S-DMS-23927	Complete	The DDICT CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1373	S-DMS-23928	Complete	The DDICT CI shall use the CSS time service when obtaining the system time.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1374	S-DMS-23929	Complete	The DDICT CI mode-specific executables and scripts shall accept a specific mode at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1404	S-DMS-32020	Complete	The GTWAY CI shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1405	S-DMS-32024	Complete	The GTWAY CI shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1406	S-DMS-32025	Complete	The GTWAY CI shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1407	S-DMS-32026	Complete	The GTWAY CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1408	S-DMS-32029	Complete	The GTWAY CI and scripts shall accept a specific mode at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1444	S-DMS-42020	Future	The ASTGW CI shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1445	S-DMS-42024	5B	The ASTGW CI shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1446	S-DMS-42025	5B	The ASTGW CI shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1447	S-DMS-42026	B1	The ASTGW CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1448	S-DMS-42029	B1	The ASTGW CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1581	S-DPS-24005	B0	PRONG CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1582	S-DPS-24010	B1	The PRONG CI shall include the mode identifier in activity log record entries for cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1586	S-DPS-24040	B0	PRONG CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1588	S-DPS-24050	B0	PRONG CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1590	S-DPS-24060	B0	PRONG CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1591	S-DPS-24070	B0	PRONG CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1592	S-DPS-24080	B0	The PRONG CI shall be capable of using simulated time values supplied by CSS, when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1593	S-DPS-24090	B0	PRONG CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	1779	S-DPS-60940	A	The SPRHW CI shall be capable of simultaneously supporting the Independent Verification & Validation (IV&V) activities and the ECS development activities, both before and after flight operations begin.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2080	S-DSS-04800	B0	SDSRV CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2081	S-DSS-04810	B0	SDSRV CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2082	S-DSS-04820	B0	SDSRV CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2083	S-DSS-04830	B0	The SDSRV CI shall be capable of using simulated time values supplied by CSS, when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2084	S-DSS-04840	B0	SDSRV CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2085	S-DSS-04850	B0	SDSRV CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2086	S-DSS-04860	B0	SDSRV CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2087	S-DSS-04870	B1	The SDSRV CI shall include the mode identifier in activity log record entries for cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2246	S-DSS-22000	B0	The STMGT CI shall include capabilities which make it possible to ensure that data written by applications executing in different modes will not be mixed on the same tape.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2247	S-DSS-22010	B0	STMGT CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2248	S-DSS-22020	B1	STMGT CI shall include the mode identifier in activity log record entries for the cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2249	S-DSS-22050	B0	The STMGT CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2250	S-DSS-22060	B0	The STMGT CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2251	S-DSS-22070	B0	STMGT CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2252	S-DSS-22080	B0	STMGT CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2253	S-DSS-22090	B0	The STMGT CI shall be capable of using simulated time values when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2254	S-DSS-22100	B0	STMGT CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2351	S-DSS-31110	B0	DDIST CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2353	S-DSS-31150	B0	The DDIST CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2354	S-DSS-31160	B0	The DDIST CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2355	S-DSS-31170	B0	DDIST CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2356	S-DSS-31180	B0	DDIST CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2357	S-DSS-31190	B0	The DDIST CI shall be capable of using simulated time values supplied by CSS, when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2358	S-DSS-31200	B0	DDIST CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2591	S-INS-03300	B0	INGST CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2592	S-INS-03310	B0	The INGST CI shall include the mode identifier in activity log record entries for cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2593	S-INS-03320	B0	INGST CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2594	S-INS-03330	B0	INGST CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2595	S-INS-03340	B0	INGST CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2596	S-INS-03350	B0	INGST CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2597	S-INS-03360	B0	INGST CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2720	S-IOS-60370	B0	ADSRV CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2721	S-IOS-60371	B0	The ADSRV CI shall include the mode identifier in activity log record entries for cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2722	S-IOS-60374	B0	ADSRV CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2723	S-IOS-60375	B0	ADSRV CI mode-specific applications shall be capable of simultaneous execution in different modes on different machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2724	S-IOS-60376	B0	ADSRV CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2726	S-IOS-60378	B0	The ADSRV CI shall be capable of using simulated time values supplied by CSS when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2727	S-IOS-60379	B0	ADSRV CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2881	C-MSS-18042	B0	The MSS MDA shall have the capability to distinguish MSS log file records according to mode identifier.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2882	C-MSS-18044	B0	The MSS MDA shall support a separate management database for each active mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2883	C-MSS-18046	B0	The MSS MDA shall transfer MSS log file records to the appropriate management database based on the event's mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2884	C-MSS-18048	B0	The MSS MDA shall transfer non-mode specific MSS log file records to all mode specific management databases.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2908	C-MSS-36012	B0	The MSS Management MACI shall have the capability to obtain the mode identifier of managed application.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2909	C-MSS-36014	B0	The MSS MACI shall incorporate the mode identifier into all metrics collected.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	2910	C-MSS-36016	B0	The MSS MACI shall be able to distinguish managed applications based on mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3098	C-MSS-56020	B0	The MSS Mode Management Service shall support a test mode capability	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3103	C-MSS-56070	B0	The MSS Mode Management Service shall be capable of executing a test mode simultaneously with the production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3104	C-MSS-56080	B0	The MSS Mode Management Service shall be capable of executing a training mode simultaneously with the production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3106	C-MSS-56084	B0	The MSS Mode Management Service shall provide the capability to control life cycle activities within each given mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3107	C-MSS-56086	B0	The MSS Mode Management Service shall have the capability to provide a mode identifier to initialize ECS applications.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3108	C-MSS-56088	B0	The MSS Mode Management Service shall provide a GUI for mode initiation.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3110	C-MSS-56092	B0	The MSS Mode Management Service shall provide provide a GUI for mode monitoring.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3111	C-MSS-56094	B0	The MSS Mode Management Service shall provide a GUI for mode control.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3112	C-MSS-56096	B0	The MSS Mode Management Service shall support concurrently executing non-production modes.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3113	C-MSS-56098	B0	The MSS Mode Management Service shall support no more than one production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3114	C-MSS-56100	B0	The MSS Mode Management Service shall have the capability to provide a simulated time value.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3115	C-MSS-56102	B0	The MSS Management Framework shall provide a mode specific view of ECS applications for any active mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3396	C-MSS-92015	B0	The MSS Report Generation Service shall be able to create mode specific reports.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3621	S-PLS-03000	B0	PLANG CI mode-specific applications shall access data only for the mode in which the application is configured.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3622	S-PLS-03010	B0	The PLANG CI shall include the mode identifier in activity log record entries for cost and accounting data.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3623	S-PLS-03040	B0	PLANG CI mode-specific applications shall be capable of simultaneous execution in different modes on the same machine.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3624	S-PLS-03050	B0	PLANG CI mode-specific applications shall be capable of simultaneous execution in different modes on different machines.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3625	S-PLS-03060	B0	PLANG CI server applications shall register within their mode-associated namespace in the CSS name service.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3626	S-PLS-03070	B0	PLANG CI client applications shall incorporate a mode identifier for CSS name service lookups.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3627	S-PLS-03080	B0	The PLANG CI shall be capable of using simulated time values supplied by CSS, when executing in a non-production mode.	99-0729	08/25/1999  	No Data	
128	EOSD0630	Complete	The ECS shall be capable of simultaneously supporting the Independent Verification and Validation (IV&V) activities and ECS development activities, both before and after flight operations begin.	3628	S-PLS-03090	B0	PLANG CI mode-specific executables and scripts shall accept a specific mode only at startup.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	1782	S-DPS-60970	IR1	The SPRHW CI shall be capable of being monitored during testing.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	1791	S-DPS-61171	IR1	The SPRHW CI  shall have provision for a dynamic analyzer  to support the capability to check Science Software source code for memory leaks.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	1802	S-DPS-70070	IR1	The AITHW CI shall have a status monitoring capability.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	2606	S-INS-60190	IR1	The ICLHW CI shall have a status monitoring capability.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	2619	S-INS-60650	IR1	The ICLHW CI shall be capable of being monitored during testing.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3098	C-MSS-56020	B0	The MSS Mode Management Service shall support a test mode capability	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3100	C-MSS-56040	B0	The MSS Mode Management Service shall have the capability to monitor each independently executing mode for performance statistics.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3101	C-MSS-56050	B1	 The MSS Mode Management Service shall provide fault detection and isolation capabilities for each independently executing mode.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3102	C-MSS-56060	B1	The MSS Mode Management Service shall maintain a collection of management statistics for each mode supported.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3105	C-MSS-56082	B0	The MSS Mode Management Service shall provide the capability to initiate a new mode of execution.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3143	C-MSS-60012	B0	The MSS Fault Management Service shall provide fault detection and isolation capabilities for each mode.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3144	C-MSS-60014	B0	The MSS Fault Management Service shall provide the capability to distinguish faults between different modes.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3145	C-MSS-60016	B0	The MSS Fault Management Service shall maintain fault statistics for each mode.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3184	C-MSS-60330	B0	The MSS Fault Management Application Service at each site shall have the capability to perform periodic testing of all ECS communication links at that site to verify that they are operational.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3205	C-MSS-66002	B0	The MSS Performance Management Applications Service shall have the capability to monitor each mode for performance statistics.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3206	C-MSS-66004	B0	The MSS Performance Management Application Service shall provide the capability to distinguish performance metrics between different modes.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3207	C-MSS-66006	B0	The MSS Performance Management Application Service shall maintain performance statistics for a given mode.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3219	C-MSS-66121	B0	The MSS performance management application service shall be capable of determining the operational state of all network components, hosts, and peripherals to be:      a. on-line      b. off-line      c. in test mode      d. In maintenance,      e. in simulation mode.	99-0729	08/25/1999  	No Data	
132	EOSD0780	Complete	The ECS shall be capable of being monitored during testing.	3644	S-PLS-61150	A	The PLNHW CI shall be capable of being monitored during testing.	99-0729	08/25/1999  	No Data	
134	EOSD1015	EOC Partial	Each ECS DAAC that receives instrument Level 0 data from EDOS shall provide the capability to ingest and archive the data at a rate that is equivalent to 1.2 times the DAAC's average Level 0 input rate.	2622	S-INS-60751	B0	The ICLHW CI at the GSFC DAAC shall be sized to temporarily store the volume of EDOS data as specified in the Ingest Subsystem Capabilities and Performance Capabilities by DAAC Table.	99-0729	08/25/1999  	No Data	
134	EOSD1015	EOC Partial	Each ECS DAAC that receives instrument Level 0 data from EDOS shall provide the capability to ingest and archive the data at a rate that is equivalent to 1.2 times the DAAC's average Level 0 input rate.	2624	S-INS-60756	B0	The ICLHW CI at the LaRC DAAC shall be sized to temporarily store the volume of EDOS data as specified in the Ingest Subsystem Capabilities and Performance Capabilities by DAAC Table.	99-0729	08/25/1999  	No Data	
134	EOSD1015	EOC Partial	Each ECS DAAC that receives instrument Level 0 data from EDOS shall provide the capability to ingest and archive the data at a rate that is equivalent to 1.2 times the DAAC's average Level 0 input rate.	2641	S-INS-61010	B0	The ICLHW CI at the GSFC DAAC shall be capable of ingesting data from the EDOS at a maximum daily rate that is 1.2 times the nominal rate specified in the Ingest Subsystem Capabilities and Performance Capabilities by DAAC Table.	99-0729	08/25/1999  	No Data	
134	EOSD1015	EOC Partial	Each ECS DAAC that receives instrument Level 0 data from EDOS shall provide the capability to ingest and archive the data at a rate that is equivalent to 1.2 times the DAAC's average Level 0 input rate.	2643	S-INS-61025	B0	The ICLHW CI at the LaRC DAAC shall be capable of ingesting data from the EDOS at a maximum daily rate that is 1.2 times the nominal rate specified in the Ingest Subsystem Capabilities and Performance Capabilities by DAAC Table.	99-0729	08/25/1999  	No Data	
135	EOSD1030	EOC Partial	The ECS shall have the capacity to accept a daily average of two (2) per cent of the daily data throughput as expedited data for use in mission functions of calibration and anomalies.	1981	S-DSS-01970	B0	The SDSRV CI shall have the capacity to accept a daily average of two (2) percent of the daily data throughput as expedited data for use in mission functions of calibration and anomalies.	99-0729	08/25/1999  	No Data	
135	EOSD1030	EOC Partial	The ECS shall have the capacity to accept a daily average of two (2) per cent of the daily data throughput as expedited data for use in mission functions of calibration and anomalies.	2025	S-DSS-03369	B0	The SDSRV CI shall be capable of receiving and managing the storage of Expedited Data from instruments, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
135	EOSD1030	EOC Partial	The ECS shall have the capacity to accept a daily average of two (2) per cent of the daily data throughput as expedited data for use in mission functions of calibration and anomalies.	2445	S-INS-00083	B0	The INGST CI shall determine the data type for expedited  data provided by EDOS.	99-0729	08/25/1999  	No Data	
142	EOSD1140	Complete	ECS shall have the capability to allocate 10% of development resources, including processing, storage, and networks, for the IV&V activity.	2827	C-MSS-00200	A	The MSS services shall allocate 10% of development resources for IV&V activity.	99-0729	08/25/1999  	No Data	
144	EOSD1502	Complete	The ECS shall use EMSn for data communications for the following types of data:    a. Production data sets (Level 0 data)    b. Expedited data sets    c. Data requested from back-up archive    d. EMOS Activity Schedules    e. Production Data Transfers between DAACs    f. Management Data exchange with SMC 	2799	C-ISS-11195	B0	The ISS shall provide for connectivity with EBnet at the following ECS sites:     a. GSFC DAAC     b. GSFC EOC     c. GSFC SMC     d. LaRC DAAC       h. NSIDC DAAC     i.  EDC DAAC	99-0729	08/25/1999  	No Data	
144	EOSD1502	Complete	The ECS shall use EMSn for data communications for the following types of data:    a. Production data sets (Level 0 data)    b. Expedited data sets    c. Data requested from back-up archive    d. EMOS Activity Schedules    e. Production Data Transfers between DAACs    f. Management Data exchange with SMC 	3160	C-MSS-60162	B0	The MSS SMC Trouble Ticket Application Service shall have the capability to exchange notifications of detected faults and degradation of performance with:  a. EBnet  b. NSI  c. ASTER	99-0729	08/25/1999  	No Data	
144	EOSD1502	Complete	The ECS shall use EMSn for data communications for the following types of data:    a. Production data sets (Level 0 data)    b. Expedited data sets    c. Data requested from back-up archive    d. EMOS Activity Schedules    e. Production Data Transfers between DAACs    f. Management Data exchange with SMC 	3162	C-MSS-60182	B0	The MSS SMC Fault Management Application Service shall be capable of receiving summarized fault notification and performance degradation data from Site Fault Management Applications.	99-0729	08/25/1999  	No Data	
144	EOSD1502	Complete	The ECS shall use EMSn for data communications for the following types of data:    a. Production data sets (Level 0 data)    b. Expedited data sets    c. Data requested from back-up archive    d. EMOS Activity Schedules    e. Production Data Transfers between DAACs    f. Management Data exchange with SMC 	3193	C-MSS-60400	A	The MSS Fault Management Application Service shall support, maintain, and update system fault management policies and procedures, to include:   a. Fault Identification   b. Fault priorities   c. Recovery or corrective actions	99-0729	08/25/1999  	No Data	
144	EOSD1502	Complete	The ECS shall use EMSn for data communications for the following types of data:    a. Production data sets (Level 0 data)    b. Expedited data sets    c. Data requested from back-up archive    d. EMOS Activity Schedules    e. Production Data Transfers between DAACs    f. Management Data exchange with SMC 	3194	C-MSS-60410	A	The MSS Site Fault Management Application Service shall have the capability to receive Fault Management Policies and Procedures from the EMC.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	4568	C-MSS-75445	5BP	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  	00-1097	11/22/2000  		
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	132	S-INS-00366	5B	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.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1551	S-DPS-21970	A	The PRONG CI shall provide a user interface for the operations staff to modify the Priority Information associated with a  Data Processing Request.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1619	S-DPS-40100	IR1	The AITTL CI shall provide the operations staff with the capability to display Science Software documentation stored in any of the following formats: a) PostScript, b) ASCII, c) Hypertext Markup Language (HTML), d) Microsoft Word, e) WordPerfect, f) Adobe Acrobat Portable Document Format (PDF).	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1661	S-DPS-41100	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to display a list of Science Software Archive Packages in the Data Server.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1662	S-DPS-41110	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to display the metadata for a specific Science Software Archive Package.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1663	S-DPS-41120	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to display a list of the files that comprise a specific Science Software Archive Package.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1664	S-DPS-41130	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to retrieve a copy of a specified file belonging to a specific Science Software Archive Package.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1665	S-DPS-41140	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to add a new Science Software Archive Package to the Data Server.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1666	S-DPS-41150	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to add or remove a file to or from the set of files comprising a specific Science Software Archive Package.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1667	S-DPS-41160	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to edit the metadata for a specific Science Software Archive Package.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1668	S-DPS-41170	B0	The AITTL CI shall provide to the operations staff, via a GUI, the capability to remove a specific Science Software Archive Package from the Data Server.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1671	S-DPS-41300	A	The AITTL CI shall provide to the operations staff, via a GUI, the capability to display a list of PGE Database Entries.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1672	S-DPS-41310	A	The AITTL CI shall provide to the operations staff, via a GUI, the capability to display a specific PGE Database Entry.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1713	S-DPS-42355	B0	The operations staff shall be able to enter new PGEs into the PGE Database, along with scheduling, input/output, performance and resource utilization information.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1864	S-DSS-00226	B1	The SDSRV CI shall provide operations staff the capability to display the file name, status, size, archive location, and back up locations associated with a data product.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1867	S-DSS-00251	A	The SDSRV CI GUI shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1868	S-DSS-00255	A	The SDSRV CI GUI shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	1935	S-DSS-01190	B1	The SDSRV CI shall provide the capability for operations staff to view the resources used and allocated by a client.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2164	S-DSS-20480	B1	The STMGT CI shall provide operations staff the capability to perform physical inventories of archive media resident in archive storage devices.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2165	S-DSS-20510	B0	The STMGT CI shall provide operations staff with the ability to display and modify storage resource and device configuration information.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2166	S-DSS-20550	6A	The STMGT CI shall provide operations staff a mechanism to display/view storage system configuration parameters which affect storage system performance.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2197	S-DSS-21160	B0	The STMGT CI shall provide operations staff the capability to set the operational state (UP or DOWN) of storage devices.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2198	S-DSS-21170	B0	The STMGT CI shall provide operations staff the capability to query the operational state (UP or DOWN) of storage devices.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2201	S-DSS-21270	B1	The STMGT CI shall provide the operations staff the capability to display information about archive storage devices, including current status, current operation, # operations completed, # errors reported, time/date of last error.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2203	S-DSS-21274	6A	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.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2275	S-DSS-30100	B0	The DDIST CI shall provide operations staff the capability to change the Priority Information for a queued  Distribution Request.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2276	S-DSS-30110	B1	The DDIST CI shall provide the capability for operations staff to list Electronic Distribution Requests separately from Media Distribution Requests.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2277	S-DSS-30115	B0	The DDIST CI shall provide the capability for operations staff to list Distribution Requests according to Request Identifier and requestor.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2278	S-DSS-30125	B0	The DDIST CI shall provide the capability for operations staff to list Media Distribution Requests according to media type.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2280	S-DSS-30135	B0	The DDIST CI shall provide the capability for operations staff to list Distribution Requests according to distribution status.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2286	S-DSS-30162	A	The DDIST CI GUIs shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2293	S-DSS-30195	A	The DDIST CI shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2311	S-DSS-30430	B1	The DDIST CI shall provide the capability for the operations staff to manually enter the status (i.e. "waiting for shipment" or "shipped") of a physical media shipment.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2495	S-INS-00350	5B	The INGST CI shall accept an ingest Cancellation Request from authorized operations staff to cancel an ongoing ingest request, specifying the ingest Request Identifier.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2500	S-INS-00364	5B	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.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2612	S-INS-60410	A	The ICLHW CI shall provide maintenance and operations interfaces to support the function of System Maintenance.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2907	C-MSS-36010	IR1	The MSS Management Agent Service shall retrieve data from ECS managed objects in test or operational mode.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	2923	C-MSS-36110	B0	The MSS Management Agent Service shall provide an ECS master agent to coordinate and communicate with multiple ECS management subagents.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3142	C-MSS-60010	IR1	The MSS Fault Management Application Service shall provide the capability to create and display graphical representations of a given network topology consisting of the following:    a. routers   b. communication lines   c. hosts   d. peripherals   e. applications	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3146	C-MSS-60020	IR1	The MSS Fault Management Application Service shall provide the capability to define categories of faults.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3147	C-MSS-60030	B0	The MSS Fault Management Application Service shall provide the capability to assign faults to categories.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3148	C-MSS-60040	B0	The MSS Fault Management Application Service shall provide the capability to assign severity levels to faults.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3149	C-MSS-60050	B0	The MSS Fault Management Application Service shall be capable of specifying whether to enable or disable the logging of fault notifications for each fault category.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3150	C-MSS-60060	B0	The MSS Fault Management Application Service shall provide the capability to enable or disable the display of fault notifications received from a specific managed object based on fault category assigned to that fault.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3151	C-MSS-60070	B0	MSS shall provide the capability to log fault specific information based on fault category, when the fault is detected.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3152	C-MSS-60080	IR1	The MSS Fault Management Application Service shall have the capability to establish, view, modify and delete thresholds on performance metrics it measures.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3258	C-MSS-68000	IR1	The MSS performance management application service shall be capable of graphically displaying the operational state of managed objects through the MUI service.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3259	C-MSS-68010	IR1	The MSS performance management application service shall be capable of displaying M&O staff-selected performance statistics through the MUI in tabular and graphical formats.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3272	C-MSS-69030	A	The MSS performance management application service shall be capable of providing results of benchmark tests and results of predefined tests to the M&O staff for validation.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3283	C-MSS-70130	IR1	The MSS site Security Management Application Service shall provide a command line interface and a GUI for the management of the following security databases:  a. Authentication Database    b.  Authorization Database  c. Network Database	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3300	C-MSS-70510	A	The MSS site Security Management Application Service shall, upon the detection of a compromise, isolate the compromised input I/O, and the compromised area's output I/O until the compromise has been eliminated.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3343	C-MSS-76040	B0	The MSS Accountability Management Service shall be capable of reporting audit information to M&O staff via the MUI service.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3638	S-PLS-60630	A	The PLNHW CI shall provide maintenance interfaces to support the function of System Maintenance.	99-0729	08/25/1999  	No Data	
147	EOSD1703	5B Partial	The ECS shall provide maintenance and operations interfaces to the DAACs to support the functions of:  a. System Management  b. Science Algorithm Integration  c. Product Generation  d. Data Archive/Distribution  e. User Support Services  f. System Maintenance	3639	S-PLS-60640	A	The PLNHW CI shall provide operations interfaces to support the function of System Maintenance.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1094	C-CSS-60520	IR1	The CSS File Access Service shall support the File Transfer Protocol (FTP).	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1095	C-CSS-60530	A	The CSS File Access Service shall support the kerberized version of File Transfer Protocol (kftp) for secured file transfers.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1113	C-CSS-61050	IR1	The CSS Electronic Mail Service shall be accessible in interactive mode.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1614	S-DPS-40010	IR1	The AITTL CI shall have the capability to receive a Science Software Delivery from the SCF electronically via the network.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1615	S-DPS-40020	A	The AITTL CI shall have the capability to receive a Science Software Delivery from the Science Data Server.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1616	S-DPS-40030	A	The AITTL CI shall provide the operations staff with the capability to register a Subscription with the Data Server to be notified when a new Science Software Delivery is received.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1617	S-DPS-40040	A	The AITTL CI shall provide the operations staff with the capability to request transfer of the Science Software Delivery files from the Data Server to the local I&T area.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2005	S-DSS-03004	B0	The SDSRV CI shall be capable of receiving and managing the storage of Ancillary Data, as requested by valid Data Insert Requests.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2022	S-DSS-03308	B0	The SDSRV CI shall direct the transfer of data files, specified by valid Data Insert Requests, to the STMGT CI.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2130	S-DSS-20000	B0	The STMGT CI shall accept and store data files into the archive, as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2437	S-INS-00010	IR1	The INGST CI shall accept Network Ingest Requests to request automated electronic network ingest of a collection of Data.  The collection of Data shall describe one or more Data Granules.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2438	S-INS-00020	IR1	The INGST CI shall check the Network Ingest Request to verify that the date/time prior to which the data will remain available is a valid date/time.	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2442	S-INS-00060	IR1	The INGST CI shall report status to the provider of a Network Ingest Request for the following:  a. File transfer failure  b. File size discrepancies  c. Invalid Data Type Identifier  d. Missing required metadata  e. Metadata parameters out of range  f. Data conversion failure  g. Failure to archive data  h. Inability to transfer data within the specified time window  i. Missing required request information  j. Successful archive of the data	99-0729	08/25/1999  	No Data	
148	EOSD1750	Complete	The ECS shall receive data including the following types of supporting information from the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Science Software    b.  Instrument calibration data    c. Data transfer requests (science products, metadata and browse)    d. Data Quality/Instrument assessment    e. Instrument operations information    f. Ancillary data	2551	S-INS-00680	A	The INGST CI shall ingest Data, provided by an SCF into the LaRC DAAC using a file transfer protocol.	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	366	S-CLS-10290	A	The WKBCH CI shall provide users the capability to browse data in ECS supported visualization formats in a window during the data selection and acquisition process,	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	415	S-CLS-10750	A	The WKBCH CI shall provide users a search and results interface to search for and view Inventory information based on core metadata attributes.	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	1094	C-CSS-60520	IR1	The CSS File Access Service shall support the File Transfer Protocol (FTP).	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	1113	C-CSS-61050	IR1	The CSS Electronic Mail Service shall be accessible in interactive mode.	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	1136	C-CSS-61800	A	The CSS Electronic Mail Service shall provide the capability to send an electronic mail message non-interactively from an application.	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	1733	S-DPS-42700	IR1	The operations staff shall have the capability to enter and track discrepancy reports related to AI&T.	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	1736	S-DPS-42740	IR1	The operations staff shall report on the status of I&T-related discrepancy reports.	99-0729	08/25/1999  	No Data	
149	EOSD1760	Complete	The ECS shall send the following types of data to the ECS science community (TLs, TMs, PIs, and Co-Is):    a. Metadata   b. Browse data    c. Archived data	3022	C-MSS-40660	B0	The MSS configuration management application service at the SMC shall distribute change evaluation requests to designated organizations system-wide and record evaluation assignments and distribution status.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	911	C-CSS-21000	IR1	The CSS Security service shall provide an API to verify the identity of users.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	913	C-CSS-21010	A	The CSS Security service shall not transmit its authentication information in clear text across networks.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	914	C-CSS-21020	IR1	The CSS Security service shall provide the capability to create/modify/delete user accounts and privileges in the security registry.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	915	C-CSS-21030	IR1	The CSS Security service shall provide the capability to define/modify/delete group information in the security registry.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	930	C-CSS-21170	A	The CSS Security service shall provide an API to maintain the integrity of the data passing between processes by using checksums at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	931	C-CSS-21180	A	The CSS Security service shall provide an API to encrypt and send the data passing between processes at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	932	C-CSS-21190	A	The CSS Security service shall provide an API to receive and decrypt the data passing between processes at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	1086	C-CSS-60310	A	The CSS File Access Service shall support access control for the remote files.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	1095	C-CSS-60530	A	The CSS File Access Service shall support the kerberized version of File Transfer Protocol (kftp) for secured file transfers.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	1171	C-CSS-63050	A	The CSS Virtual Terminal shall support kerberized version of the telnet protocol for secure authentication of users.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	2746	C-ISS-02010	IR1	The ISS shall provide the capability to filter packets based on the port/socket of the  transport layer protocol.	99-0729	08/25/1999  	No Data	
150	EOSD1990	Complete	The ECS system shall employ security measures and techniques for all applicable security disciplines which are identified in the following documents:   a. Federal Information Security Act of  2002    b. NPD 1600.2A. c. NPR 2810.1A.	2749	C-ISS-02040	A	The ISS shall provide the capability to filter packets based upon network layer source and/or destination addresses.	99-0729	08/25/1999  	No Data	
151	EOSD2100	Complete	The ECS technical security policy planning shall be comprehensive and shall cover the following areas:     a. ECS communications, network access, and control,    b. Data protection controls   c. System access controls and account/privilege management and user session tailoring   d. Security audit trail generation   e. Security analysis and reporting    f. Risk management planning	930	C-CSS-21170	A	The CSS Security service shall provide an API to maintain the integrity of the data passing between processes by using checksums at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
151	EOSD2100	Complete	The ECS technical security policy planning shall be comprehensive and shall cover the following areas:     a. ECS communications, network access, and control,    b. Data protection controls   c. System access controls and account/privilege management and user session tailoring   d. Security audit trail generation   e. Security analysis and reporting    f. Risk management planning	931	C-CSS-21180	A	The CSS Security service shall provide an API to encrypt and send the data passing between processes at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
151	EOSD2100	Complete	The ECS technical security policy planning shall be comprehensive and shall cover the following areas:     a. ECS communications, network access, and control,    b. Data protection controls   c. System access controls and account/privilege management and user session tailoring   d. Security audit trail generation   e. Security analysis and reporting    f. Risk management planning	933	C-CSS-21210	A	The CSS Security service shall provide the capability to log audit information into security logs whenever authentication and authorization services are used.  The audit information will contain the following:  a. Date and time of the event  b. User name  c. Type of event  d. Success or failure of the event  e. Origin of the request	99-0729	08/25/1999  	No Data	
151	EOSD2100	Complete	The ECS technical security policy planning shall be comprehensive and shall cover the following areas:     a. ECS communications, network access, and control,    b. Data protection controls   c. System access controls and account/privilege management and user session tailoring   d. Security audit trail generation   e. Security analysis and reporting    f. Risk management planning	2767	C-ISS-02500	B0	The ISS-INHW CI networks shall support the use of network and transport layer filtering to control access from internal and external interfaces.	99-0729	08/25/1999  	No Data	
151	EOSD2100	Complete	The ECS technical security policy planning shall be comprehensive and shall cover the following areas:     a. ECS communications, network access, and control,    b. Data protection controls   c. System access controls and account/privilege management and user session tailoring   d. Security audit trail generation   e. Security analysis and reporting    f. Risk management planning	3280	C-MSS-70100	IR1	The MSS site Security Management Application Service shall provide the capability to set, maintain, and update access control information for ECS resources.	99-0729	08/25/1999  	No Data	
151	EOSD2100	Complete	The ECS technical security policy planning shall be comprehensive and shall cover the following areas:     a. ECS communications, network access, and control,    b. Data protection controls   c. System access controls and account/privilege management and user session tailoring   d. Security audit trail generation   e. Security analysis and reporting    f. Risk management planning	3282	C-MSS-70120	IR1	The MSS site Security Management Application service shall provide the mechanism, for each ECS host, to allow or deny incoming requests from specific hosts to services.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	83	C-MSS-75021	5B	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')	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	84	C-MSS-75022	5B	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.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	85	C-MSS-75023	5B	The MSS accountability management service shall use a value of Non-NASA User ('N') as the default value for the NASA User attribute.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	264	S-DSS-06600	5B	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.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	265	S-DSS-06601	5B	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.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	267	S-DSS-06603	5B	The SDSRV CI shall support access rules based upon the MSS User Profile roles of P, R, and N individually or in any combination.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	268	S-DSS-06604	5B	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.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	277	S-DSS-06613	5B	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'.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	278	S-DSS-06614	5B	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'.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	533	S-CLS-13380	B1	 The WKBCH CI shall send User Authentication Requests to  the SMC.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	534	S-CLS-13390	B1	The WKBCH CI shall  allow or deny the user system access based on User Validation Status returned from the SMC.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	930	C-CSS-21170	A	The CSS Security service shall provide an API to maintain the integrity of the data passing between processes by using checksums at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	931	C-CSS-21180	A	The CSS Security service shall provide an API to encrypt and send the data passing between processes at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	1358	S-DMS-20690	5B	The DDICT CI shall provide the capability to add a link between a Data Collection and its Information Manager.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	1467	S-DPS-20340	A	The PRONG CI shall restrict the ability to cancel a Data Processing Request to authorized sources.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	1544	S-DPS-21880	A	The PRONG CI shall provide a User Interface to authorized users.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	1670	S-DPS-41200	B0	The AITTL CI shall provide the capability (a) to restrict update access of the Science Software Archive Packages to the Data Server to authorized personnel and (b) to maintain a record of updates made.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	1869	S-DSS-00310	B1	The SDSRV CI shall provide the capability for authorized clients to submit Service Requests  batch mode.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2439	S-INS-00030	IR1	The INGST CI shall authenticate the provider of a Network Ingest Request as an authorized provider of data to be ingested.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2453	S-INS-00150	A	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.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2454	S-INS-00160	A	The INGST CI shall authenticate that the Hard Media Ingest Request is input by operations staff authorized to ingest hard media data.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2457	S-INS-00175	A	The INGST CI shall report Hard Media Ingest Request status to the MSS event log for the following:   a. Unauthorized hard media provider   b. Unauthorized operations staff	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2463	S-INS-00208	A	The INGST CI shall authenticate that the interactive science user entering a Network Ingest Request is authorized to request ingest of data.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2472	S-INS-00227	A	The INGST CI shall authenticate that the interactive science user entering a Document Ingest Request is authorized to request ingest of data.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2482	S-INS-00290	A	The INGST CI shall authenticate the User Identifier of operations staff requesting status on all ongoing Ingest Requests.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2488	S-INS-00317	A	The INGST CI shall authenticate the User Identifier of an application submitting an Ingest Request.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2496	S-INS-00355	B0	The INGST CI shall accept an ingest Suspension Request from authorized operations staff to suspend ongoing ingest request processing for a specified ingest Request Identifier, to suspend all ongoing ingest request processing from a specified External Data Provider, or to suspend all ongoing ingest request processing.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2497	S-INS-00357	B0	The INGST CI shall accept an ingest Resumption Request from authorized operations staff to resume ongoing ingest request processing for a specified ingest Request Identifier, to resume all ongoing ingest request processing from a specified External Data Provider, or to resume all ongoing ingest request processing.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2498	S-INS-00360	A	The INGST CI shall authenticate the User Identifier of operations staff submitting an ingest Cancellation Request.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2499	S-INS-00363	B0	The INGST CI shall authenticate the User Identifier of operations staff submitting an ingest Suspension Request or ingest Resumption Request.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2501	S-INS-00365	B0	The INGST CI shall accept an ingest Suspension Request from authorized applications to suspend ongoing ingest request processing for a specified Request Identifier, to suspend all ongoing ingest request processing from a specified External Data Provider, or to suspend all ongoing ingest request processing.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2502	S-INS-00367	B0	The INGST CI shall accept an ingest Resumption Request from authorized applications to resume ongoing ingest request processing for a specified Request Identifier, to resume all ongoing ingest request processing from a specified External Data Provider, or to resume all ongoing ingest request processing.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2503	S-INS-00369	A	The INGST CI shall authenticate the User Identifier of an application submitting an ingest Cancellation Request.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2504	S-INS-00370	B0	The INGST CI shall authenticate the User Identifier of an application submitting an ingest Suspension Request or ingest Resumption Request.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2506	S-INS-00390	A	The INGST CI shall authenticate the User Identifier of operations staff requesting to set thresholds for concurrent ingest processing.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2581	S-INS-02000	B0	The INGST CI shall interactively accept Document Scanning/Digitizing Requests from authorized operations staff for hard copy media to be ingested.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2582	S-INS-02010	B0	The INGST CI shall authenticate that the Document Scanning/Digitizing Request is input by operations staff authorized to ingest hard copy media.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2583	S-INS-02020	B0	The INGST CI shall verify that the External Data Provider specified in a Document Scanning/Digitizing Request is an authorized provider of hard copy media to be ingested.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	2674	S-IOS-00410	A	The capability  to add, delete, or modify  individual advertising data and service listings shall be limited to authorized users.	99-0729	08/25/1999  	No Data	
152	EOSD2400	5B Future	The ECS shall provide data protection suitable for moderate data integrity as defined in NIST SP 800-100.	3479	S-PLS-00050	A	The PLANG CI shall reject a Production Request if an unauthorized User Identifier is specified.	99-0729	08/25/1999  	No Data	
153	EOSD2430	Complete	ECS data base access and manipulation shall accommodate control of user access and update of security controlled data.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
153	EOSD2430	Complete	ECS data base access and manipulation shall accommodate control of user access and update of security controlled data.	2886	C-MSS-18060	B0	The Management Data Access Service shall provide the capability for an operator to access management data via a log browser.	99-0729	08/25/1999  	No Data	
153	EOSD2430	Complete	ECS data base access and manipulation shall accommodate control of user access and update of security controlled data.	3280	C-MSS-70100	IR1	The MSS site Security Management Application Service shall provide the capability to set, maintain, and update access control information for ECS resources.	99-0729	08/25/1999  	No Data	
153	EOSD2430	Complete	ECS data base access and manipulation shall accommodate control of user access and update of security controlled data.	3281	C-MSS-70110	A	The MSS site Security Management Application Service shall provide the capability to specify privileges for authorized users and user groups for access to ECS resources.	99-0729	08/25/1999  	No Data	
153	EOSD2430	Complete	ECS data base access and manipulation shall accommodate control of user access and update of security controlled data.	3366	C-MSS-90030	B0	The DBMS shall provide security access control based upon userid, role and privleges for the following:  a. database  b. database object  c. database operations	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9024	S-DPL-49010	7.22	The Data Pool Ingest Service shall checksum the configured percentage of browse and ancillary files (PH, QA, and DAP) from a given provider. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9025	S-DPL-49020	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9026	S-DPL-49030	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9027	S-DPL-49040	7.22	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).	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9028	S-DPL-49050	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9029	S-DPL-49060	7.22	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.  	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9030	S-DPL-49070	7.22	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).	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9031	S-DPL-49080	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9032	S-DPL-49090	7.22	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) 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9033	S-DPL-49100	7.22	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 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9034	S-DSS-11010	7.22	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)	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9035	S-DSS-11020	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9036	S-DSS-11030	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9037	S-OMS-15100	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9038	S-OMS-15110	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9039	S-OMS-15120	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9040	S-OMS-15130	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9041	S-OMS-15140	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9044	S-OMS-15170	7.22	The OMS CI shall allow DAAC operators to limit the number of verification failures before suspension of resources.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9045	S-OMS-15180	7.22	The OMS CI shall allow DAAC operators to limit the number of concurrent verifications.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9046	S-OMS-15190	7.22	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 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9047	S-DPL-49110	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9048	S-DPL-49120	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9049	S-DPL-49130	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9050	S-DPL-49140	7.22	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 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9051	S-DPL-49150	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9052	S-DPL-49160	7.22	The DPCV shall update the checksum verification time in the Data Pool database for each file whose checksum was successfully verified.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9053	S-DPL-49170	7.22	The DPCV shall record the checksum verification status in the Data Pool database for each file whose checksum failed verification.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9054	S-DPL-49180	7.22	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 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9055	S-DPL-49190	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9056	S-DSS-11040	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9057	S-DSS-11050	7.22	The ACVU shall be capable of being scheduled and run as a background process or being run on command-line by the DAAC operator.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9058	S-DSS-11060	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9059	S-DSS-11070	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9060	S-DSS-11080	7.22	The ACVU shall allow the DAAC operator to configure the maximum number of tape reads it will submit at one time.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9061	S-DSS-11090	7.22	The ACVU shall allow the DAAC operator to configure the maximum number of concurrent tapes that can be used for checksum verification.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9062	S-DSS-11100	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9063	S-DSS-11110	7.22	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.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9064	S-DSS-11120	7.22	The ACVU shall update the checksum status in the AIM Inventory database to specify failed in the case of checksum verification failure.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9065	S-DSS-11130	7.22	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. 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9066	S-DSS-11140	7.22	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 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9067	S-DSS-11150	7.22	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 	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9068	S-DSS-11160	7.22	The ACVU shall checkpoint its progress and be able to resume and complete a previous run that was interrupted, starting from the last checkpoint.	08-0412	09/25/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9080	S-DPL-49200	7.22	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.	08-0517	12/16/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9081	S-DSS-11170	7.22	The ACVU shall be able to checksum files at a rate of 200MB per minute.	08-0517	12/16/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	9082	S-DSS-11180	7.22	The ACVU shall not significantly impact the performance of other ECS subsystems.	08-0517	12/16/2008  		
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	2881	C-MSS-18042	B0	The MSS MDA shall have the capability to distinguish MSS log file records according to mode identifier.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	2882	C-MSS-18044	B0	The MSS MDA shall support a separate management database for each active mode.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	2883	C-MSS-18046	B0	The MSS MDA shall transfer MSS log file records to the appropriate management database based on the event's mode.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	2884	C-MSS-18048	B0	The MSS MDA shall transfer non-mode specific MSS log file records to all mode specific management databases.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	3373	C-MSS-90180	B0	The DBMS shall provide the following database backup capabilities:   a.  Entire database   b.  Incremental data   c.  User specified database items.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	3374	C-MSS-90190	B0	The DBMS shall provide capabilities for specifying frequency, time, and type of backups.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	3377	C-MSS-90230	B0	The DBMS shall provide a transaction roll backward capability to a specified time or state:  a.   Restore a database  b.   Restore all or operator selected database objects of any database	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	3378	C-MSS-90240	B0	The DBMS shall provide for automatic database recovery including a means to:  a.   automatically restore undamaged portions of a database and recover work in progress after a system or component failure   b.   achieve dynamic backout of database modifications, performed by a failing transaction, that does not affect separate, concurrent tasks	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	3379	C-MSS-90260	B0	The DBMS shall provide a capability to export, archival, and restore a database.	99-0729	08/25/1999  	No Data	
154	EOSD2440	Complete	ECS data base integrity including prevention of data loss and corruption shall be maintained.	3380	C-MSS-90280	B0	The DBMS shall provide the capability to issue and record a database checkpoint.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	279	S-DSS-06615	5B	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.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	923	C-CSS-21105	A	The CSS shall notify MSS upon the failure or success of each authentication request.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	933	C-CSS-21210	A	The CSS Security service shall provide the capability to log audit information into security logs whenever authentication and authorization services are used.  The audit information will contain the following:  a. Date and time of the event  b. User name  c. Type of event  d. Success or failure of the event  e. Origin of the request	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	1670	S-DPS-41200	B0	The AITTL CI shall provide the capability (a) to restrict update access of the Science Software Archive Packages to the Data Server to authorized personnel and (b) to maintain a record of updates made.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	1952	S-DSS-01425	B0	The SDSRV CI shall log, to the Event Log, those Service Requests that fail authorization, the service requested, and the identity of the requesting user.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	1956	S-DSS-01445	B0	The SDSRV CI shall log the following when archived data is inserted, updated, deleted, or accessed:  a. User Identifier  b. Data and time of the operation performed  c. The identity of the data	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	3338	C-MSS-76000	B0	The MSS accountability management service shall be capable of retrieving user activity data (user id, type of user activity, data items used (browsed, searched, or ordered), and date/time of activity) from records generated by the SDPS Data Server, Data Processing, and Client subsystems.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	3342	C-MSS-76030	B0	The MSS Accountability Management Service shall be capable of browsing, via the Management Data Access service, logged events, for each ECS host, indicating incoming access attempts via:  a.  telnet  b.  FTP  c.  rlogin  d.  finger.	99-0729	08/25/1999  	No Data	
156	EOSD2510	5B Partial	ECS shall maintain an audit trail of:  a. All accesses to security controlled data  b. Users/processes  requesting access to security controlled data  c. Data access/manipulation operations performed on security controlled data  d. Date and time of access to security controlled data  e. Unsuccessful access attempt to security controlled data by unauthorized users/processes	3381	C-MSS-90290	B0	The DBMS shall provide an audit trail of chronological activities in the database.	99-0729	08/25/1999  	No Data	
158	EOSD2555	Complete	The ECS shall maintain confidentiality of user product request and accounts.	3366	C-MSS-90030	B0	The DBMS shall provide security access control based upon userid, role and privleges for the following:  a. database  b. database object  c. database operations	99-0729	08/25/1999  	No Data	
159	EOSD2620	Complete	ECS shall disconnect an operator  after a predetermined number of unsuccessful attempts to access data.	923	C-CSS-21105	A	The CSS shall notify MSS upon the failure or success of each authentication request.	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2456	S-INS-00170	A	The INGST CI shall report Hard Media Ingest Request status to the submitting operations staff for the following:  a.      Media file transfer failure  b.      Invalid Data Type Identifier  c.      Missing required metadata  d.      Metadata parameters out of range  e.      Data conversion failure  f.      Failure to archive data  g.      Missing file describing media data to be ingested  h.      Unauthorized hard media provider  i.      Unauthorized operations staff  j.      Successful archive of data	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2457	S-INS-00175	A	The INGST CI shall report Hard Media Ingest Request status to the MSS event log for the following:   a. Unauthorized hard media provider   b. Unauthorized operations staff	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2464	S-INS-00209	A	The INGST CI shall report to the Error Log an unauthorized attempt to interactively request ingest of data.	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2466	S-INS-00220	A	The INGST CI shall report status to the interactive submitter of a Network Ingest Request for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Data conversion failure  g.      Failure to archive data  h.      Inability to transfer data within the specified time window  i.      Unauthorized science user  j.      Missing required request information  k.      Successful archive of the data	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2473	S-INS-00228	A	The INGST CI shall report to the Error Log an unauthorized attempt to interactively request ingest of document data.	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2475	S-INS-00230	A	The INGST CI shall report status to the interactive submitter of a Document Ingest Request for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Data conversion failure  g.      Failure to archive data  h.      Inability to transfer data within the specified time window  i.      Unauthorized science user  j.      Missing required request information  k.      Successful archive of the data	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2483	S-INS-00295	A	The INGST CI shall return an error status to the requester and log information in the Error Log if status is requested on  ongoing Ingest Requests from an unauthorized requester.	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2493	S-INS-00340	A	The INGST CI shall report status on processing of an Ingest Request to the Error Log for the following:  a.      File transfer failure  b.      File size discrepancy  c.      Invalid Data Type Identifier  d.      Missing required metadata  e.      Metadata parameters out of range  f.      Metadata extraction failure  g.      Data conversion failure  h.      Data reformatting failure  i.      Failure to archive data  j.      Inability to transfer data within the specified time window  k.      Missing required request information  l.      Unauthorized Ingest Request submitter  m.      Successful archive of the data	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2507	S-INS-00392	A	The INGST CI shall report status on ingest Cancellation Requests to the requesting operations staff  and to the Error Log for the following:  a.      Unauthorized requester  b.      Invalid ingest Request Identifier  c.      Unable to cancel specified Ingest Request	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2508	S-INS-00393	B0	The INGST CI shall report status on ingest Suspension Requests to the requesting operations staff and to the Error Log for the following:   a._Unauthorized requester    b._Invalid ingest Request Identifier    c._Unable to suspend specified Ingest Request(s)	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2509	S-INS-00394	B0	The INGST CI shall report status on ingest Resumption Requests to the requesting operations staff and to the Error Log for the following:  a. Unauthorized requester  b. Invalid ingest Request Identifier	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2510	S-INS-00395	A	The INGST CI shall report status on ingest threshold setup Requests to the requesting operations staff and to the Error Log for the following:  a.      Unauthorized requester  b.      Invalid ingest Request Identifier  c.      Unable to suspend specified Ingest Request(s)	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2511	S-INS-00396	A	The INGST CI shall report status on ingest Cancellation Requests to the requesting application and to the Error Log for the following:  a.      Unauthorized requester  b.      Invalid ingest Request Identifier  c.      Unable to suspend specified Ingest Request(s)  	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2512	S-INS-00397	B0	The INGST CI shall report status on ingest Suspension Requests to the requesting application and to the Error Log for the following:   a._Unauthorized requester    b._Invalid ingest Request Identifier    c._Unable to suspend specified Ingest Request(s)	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2513	S-INS-00398	B0	The INGST CI shall report status on ingest Resumption Requests to the requesting application and to the Error Log for the following:   a._Unauthorized requester   b._Invalid ingest Request Identifier	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2585	S-INS-02040	B0	The INGST CI shall report to the Error Log an unauthorized attempt to interactively request ingest of hard copy media.	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	2586	S-INS-02050	B0	The INGST CI shall report Document Scanning/Digitizing Request status to the submitting operations staff for the following:   a._Hard copy scanning/digitizing failure    b._Invalid Data Type Identifier   c._Missing required metadata   d._Metadata parameters out of range    e._Failure to archive data    f._Unauthorized hard copy media provider    g._Unauthorized operations staff    h._Successful archive of data	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	3290	C-MSS-70400	A	The MSS EMC Security Management Application Service shall have the capability to receive notifications of security events from the site Security Management Application Services.	99-0729	08/25/1999  	No Data	
160	EOSD2650	Complete	The ECS shall report detected security violations to the ESDIS Computer Security Official (CSO) or designee.	3293	C-MSS-70430	A	The MSS site Security Management Application Service shall provide the capability to designate a user or a group of users to receive a notification upon the detection of an intrusion.	99-0729	08/25/1999  	No Data	
161	EOSD2660	Complete	The ECS shall at all times maintain and comply with the security directives issued by the cognizant Security Official (CSO).	3284	C-MSS-70300	IR1	The MSS site Security Management Application Service shall have the capability to perform the following types of security tests:  a. password auditing  b. file system integrity checking  c. auditing of user privileges  d. auditing of resource access control information	99-0729	08/25/1999  	No Data	
161	EOSD2660	Complete	The ECS shall at all times maintain and comply with the security directives issued by the cognizant Security Official (CSO).	3285	C-MSS-70310	B0	The MSS site Security Management Application Service shall have the capability to perform security testing on a periodic and on an interactive basis.	99-0729	08/25/1999  	No Data	
161	EOSD2660	Complete	The ECS shall at all times maintain and comply with the security directives issued by the cognizant Security Official (CSO).	3286	C-MSS-70320	A	The MSS site Security Management Application Service shall have the capability to send the results of the tests to the EMC Security Management Application Service.	99-0729	08/25/1999  	No Data	
161	EOSD2660	Complete	The ECS shall at all times maintain and comply with the security directives issued by the cognizant Security Official (CSO).	3287	C-MSS-70330	A	The MSS EMC Security Management Application Service shall have the capability to request, support, coordinate and maintain security testing for sites.	99-0729	08/25/1999  	No Data	
161	EOSD2660	Complete	The ECS shall at all times maintain and comply with the security directives issued by the cognizant Security Official (CSO).	3288	C-MSS-70340	A	The MSS EMC Security Management Application Service shall have the capability to request security testing of the sites on a scheduled and an interactive basis	99-0729	08/25/1999  	No Data	
161	EOSD2660	Complete	The ECS shall at all times maintain and comply with the security directives issued by the cognizant Security Official (CSO).	3289	C-MSS-70350	A	The MSS EMC Security Management Application Service shall have the capability to receive the results of security tests performed at the sites.	99-0729	08/25/1999  	No Data	
162	EOSD2710	Complete	ECS shall report all detected computer viruses and actions taken to the cognizant Security Official (CSO).	3290	C-MSS-70400	A	The MSS EMC Security Management Application Service shall have the capability to receive notifications of security events from the site Security Management Application Services.	99-0729	08/25/1999  	No Data	
162	EOSD2710	Complete	ECS shall report all detected computer viruses and actions taken to the cognizant Security Official (CSO).	3293	C-MSS-70430	A	The MSS site Security Management Application Service shall provide the capability to designate a user or a group of users to receive a notification upon the detection of an intrusion.	99-0729	08/25/1999  	No Data	
162	EOSD2710	Complete	ECS shall report all detected computer viruses and actions taken to the cognizant Security Official (CSO).	3294	C-MSS-70440	B0	The MSS site Security Management Application Service shall provide the capability to notify designated M&O staff(s) upon the detection of an intrusion.	99-0729	08/25/1999  	No Data	
162	EOSD2710	Complete	ECS shall report all detected computer viruses and actions taken to the cognizant Security Official (CSO).	3305	C-MSS-70700	IR1	The MSS Security Management Application Service shall have the capability to generate intrusion reports on the following:  a. Login failures  b. Unauthorized access to ECS resources  c. Break-ins   d. Viruses and worms	99-0729	08/25/1999  	No Data	
162	EOSD2710	Complete	ECS shall report all detected computer viruses and actions taken to the cognizant Security Official (CSO).	3462	C-MSS-92700	B1	The MSS Report Generation Service shall be capable of generating a Security Compromise Report listing occurrences of login failures, unauthorized accesses, breakins, viruses and worms indicating time, cause, impact, resolution status, and results of security compromise risk analysis.	99-0729	08/25/1999  	No Data	
162	EOSD2710	Complete	ECS shall report all detected computer viruses and actions taken to the cognizant Security Official (CSO).	3464	C-MSS-92720	B1	The MSS Report Generation Service shall be capable of generating a Virus Detection Report containing statistics on detected viruses/worms in the selected network nodes and actions taken.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	1534	S-DPS-21560	A	If the resource fails during the execution of a PGE, the PRONG CI shall be capable of initiating the execution of the PGE without having to regenerate that PGE's input data.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	1535	S-DPS-21570	A	If a PGE fails abnormally during execution, the PRONG CI shall be capable of initiating the execution of the PGE without having to regenerate that PGE's input data.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	2603	S-INS-60150	IR1	The ICLHW CI shall have provision for Initialization, Recovery, and an orderly shutdown.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	3299	C-MSS-70500	A	The MSS EMC Security Management Application Service shall have the capability to coordinate with the site Security Management Application Services, via directives and instructions, the recovery from security compromises.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	3300	C-MSS-70510	A	The MSS site Security Management Application Service shall, upon the detection of a compromise, isolate the compromised input I/O, and the compromised area's output I/O until the compromise has been eliminated.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	3302	C-MSS-70520	IR1	The MSS EMC Security Management Application Service shall provide office automation support tools to enable the generation of directives and instructions for recovery from detected security events.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	3303	C-MSS-70530	A	The MSS EMC Security Management Application Service shall coordinate, as necessary via directives and instructions, the recovery from security events reported from a site.	99-0729	08/25/1999  	No Data	
163	EOSD2990	Complete	The ECS shall support the recovery from a system failure due to a loss in the integrity of the ECS data or a catastrophic violation of the security system.	3378	C-MSS-90240	B0	The DBMS shall provide for automatic database recovery including a means to:  a.   automatically restore undamaged portions of a database and recover work in progress after a system or component failure   b.   achieve dynamic backout of database modifications, performed by a failing transaction, that does not affect separate, concurrent tasks	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	817	C-CSS-01120	A	The CSS DOF Service shall provide mechanisms to shutdown a service gracefully, by allowing the servers to unregister the server information from the namespace.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	863	C-CSS-10580	B0	The CSS DCCI shall record log events, including scheduled and unscheduled system shutdowns and restarts for auditing purposes.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	959	C-CSS-24060	B0	The CSS Lifecycle Service shall respond to MSS Lifecycle commands to provide graceful shutdown services in the event of scheduled and unscheduled shutdowns.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	960	C-CSS-24065	B0	The CSS Lifecycle Service shall act as an intermediary during the client server connection phase.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	961	C-CSS-24070	A	The CSS Lifecycle Service shall provide a way to shutdown an application process.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	962	C-CSS-24075	B0	The CSS Lifecycle Service shall respond to MSS Lifecycle commands to provide shutdown services in the event of graceful, scheduled and unscheduled shutdowns.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	963	C-CSS-24080	B1	The CSS Lifecycle Service shall provide a way to suspend an application process.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	964	C-CSS-24090	B1	The CSS Lifecycle Service shall provide a way to resume a suspend application process.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	965	C-CSS-24100	A	The CSS Lifecycle Service shall provide the capability for server applications to activate an object (if it is not already running) and dispatch the incoming call to the object.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	1010	C-CSS-30160	B1	The Process Framework (PF) shall interface with the MSS Management Agent framework to enable suspension of an application and support graceful shutdown services in the event of scheduled and unscheduled shutdowns.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	1011	C-CSS-30170	B1	The Process Framework (PF) shall interface with the MSS Management Agent Framework and respond to commands to resume/restart an application.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	1747	S-DPS-60080	IR1	The SPRHW CI shall have provision for Initialization, Recovery, and an orderly shutdown.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	1801	S-DPS-70060	IR1	The AITHW CI shall have provision for Initialization, Recovery, and an orderly shutdown.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	2599	S-INS-04000	B0	The INGST CI shall provide a restart capability to restore previously established ingest sessions after a system failure.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	2600	S-INS-04010	B0	The INGST CI shall provide a restart capability to restore the interface with the external data providers after a system failure.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	2601	S-INS-04020	B0	The INGST CI shall provide a restart capability to restore previously accepted Ingest Requests after a system failure.  An accepted Ingest Request is defined as a request for which an acknowledgment of receipt has been returned to the external data provider.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	2602	S-INS-04030	B0	The INGST CI shall provide a restart capability, after a system failure, to resume request processing for previously accepted Ingest Requests.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	2603	S-INS-60150	IR1	The ICLHW CI shall have provision for Initialization, Recovery, and an orderly shutdown.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	3196	C-MSS-60500	IR1	The MSS EMC Fault Management Application Service shall coordinate the recovery from conditions of performance degradation and faults with the sites and external network service providers.	99-0729	08/25/1999  	No Data	
164	EOSD3000	Complete	The ECS  shall provide for security safeguards to cover unscheduled system shutdown (aborts) and subsequent restarts, as well as for scheduled system shutdown and operational startup.	3198	C-MSS-60520	B0	The MSS Fault Management Application Service shall provide the capability to allow the specification and execution of action routines in response to the notification of a fault.	99-0729	08/25/1999  	No Data	
165	EOSD3200	Complete	A minimum of one backup which is maintained in a separate physical location (i.e., different building) shall be maintained for ECS software and key data items (including security audit trails and logs).	852	C-CSS-03900	B0	The CSS-DCHW CI Enterprise Communications Server shall backup all software and security audit trails and logs.	99-0729	08/25/1999  	No Data	
165	EOSD3200	Complete	A minimum of one backup which is maintained in a separate physical location (i.e., different building) shall be maintained for ECS software and key data items (including security audit trails and logs).	853	C-CSS-03910	B0	The CSS-DCHW CI Local Communications Server shall backup all software and security audit trails and logs.	99-0729	08/25/1999  	No Data	
165	EOSD3200	Complete	A minimum of one backup which is maintained in a separate physical location (i.e., different building) shall be maintained for ECS software and key data items (including security audit trails and logs).	2844	C-MSS-04000	B0	The MSS-MHW CI Enterprise Monitoring Server shall maintain one backup of all software and security audit trails and logs in a separate physical location.	99-0729	08/25/1999  	No Data	
165	EOSD3200	Complete	A minimum of one backup which is maintained in a separate physical location (i.e., different building) shall be maintained for ECS software and key data items (including security audit trails and logs).	2845	C-MSS-04010	B0	The MSS-MHW CI Local Management Server shall maintain one backup of all software and security audit trails and logs in a separate physical location.	99-0729	08/25/1999  	No Data	
165	EOSD3200	Complete	A minimum of one backup which is maintained in a separate physical location (i.e., different building) shall be maintained for ECS software and key data items (including security audit trails and logs).	3373	C-MSS-90180	B0	The DBMS shall provide the following database backup capabilities:   a.  Entire database   b.  Incremental data   c.  User specified database items.	99-0729	08/25/1999  	No Data	
165	EOSD3200	Complete	A minimum of one backup which is maintained in a separate physical location (i.e., different building) shall be maintained for ECS software and key data items (including security audit trails and logs).	3374	C-MSS-90190	B0	The DBMS shall provide capabilities for specifying frequency, time, and type of backups.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	2885	C-MSS-18050	A	The MSS Management Data Access Service's shall utilize CSS Services to access/transfer management data.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	2886	C-MSS-18060	B0	The Management Data Access Service shall provide the capability for an operator to access management data via a log browser.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	2887	C-MSS-18070	B0	The MSS Management Data Access Service shall provide the capability to selectively access management data.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	2893	C-MSS-18270	B0	The MSS Management Data Access Service shall have the capability to schedule the archiving of log files at the site.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	2894	C-MSS-18280	B0	MSS shall have the capability to schedule the transfer of management data at the sites to the SMC.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	2897	C-MSS-18350	B0	The MSS Management Data Access Service shall provide the capability to load log files into the management database at the site.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	3222	C-MSS-66137	B1	The MSS Performance Management Application Service shall retain the calculated RMA statistics in a repository accessible for further analysis by the M&O Staff.	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	3369	C-MSS-90080	B0	The DBMS shall support mathematical operations to generate statistics from management data to include:  a. average  b. maximum  c. minimum  d. sum  e. count	99-0729	08/25/1999  	No Data	
167	EOSD3492	Complete	The ECS RMA data shall be maintained in a repository accessible for logistics analysis and other purposes.	3370	C-MSS-90120	B0	The DBMS shall be compatible with the ECS Fault and Performance Management Application Services to support the transfer of management events and data.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1460	S-DPS-20030	B0	The PRONG CI shall be capable of operating in a 24-hour a day, 7-day week mode.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1765	S-DPS-60410	B0	The SPRHW CI shall be capable of operating in a 24 hour per day, 7 days a week mode.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1768	S-DPS-60490	A	The SPRHW CI shall be capable of supporting system development without impact to normal operations.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1769	S-DPS-60500	A	The SPRHW CI shall be capable of supporting science software test without impact to normal operations.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1771	S-DPS-60525	A	SPRHW CI functions shall have an operational availability of .96 as a minimum and Mean Down Time of < 4 hours during times of staffed operation.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1803	S-DPS-70080	A	AITHW CI functions shall have an operational availability of .96 as a minimum and Mean Down Time of < 4 hours during times of staffed operation.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	1825	S-DPS-80011	A	The AQAHW CI functions shall have an operational availability of .96 as a minimum and a mean down time of <4 hours during times of staffed operation.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	2609	S-INS-60325	A	The ICLHW CI shall be configured to support the SDPS function of Metadata Ingest and Update's Availability  requirement of .96 and Mean Down Time requirement of 4 hours or less.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	2779	C-ISS-04055	A	The EOC Support LAN shall have an operational availability of at least 0.96 and shall have a mean down time of no greater than 4 hours during times of staffed operation, unless otherwise specified.	99-0729	08/25/1999  	No Data	
169	EOSD3700	EOC Partial	The ECS functions shall have an operational availability of 0.96 at a minimum (.998 design goal) and a MDT of four (4) hours or less (1.5 hour design goal), unless otherwise specified.	3635	S-PLS-60420	A	PLNHW CI functions shall have an operational availability of .96 as a minimum and Mean Down Time of < 4 hours during times of staffed operations.	99-0729	08/25/1999  	No Data	
173	EOSD4035	Complete	The ECS network shall have no single point of failure for functions associated with site-specific network databases and configuration data.	796	C-CSS-00020	A	The CSS services shall have no single point of failure for functions associated with DCE services and network databases.	99-0729	08/25/1999  		
173	EOSD4035	Complete	The ECS network shall have no single point of failure for functions associated with site-specific network databases and configuration data.	801	C-CSS-00100	A	The CSS Directory services shall maintain multiple copies of the namespace on different hosts to provide fault tolerance.	99-0729	08/25/1999  		
173	EOSD4035	Complete	The ECS network shall have no single point of failure for functions associated with site-specific network databases and configuration data.	802	C-CSS-00120	B0	The CSS Directory services shall provide capabilities supporting reconfiguration transparent to the user.	99-0729	08/25/1999  		
173	EOSD4035	Complete	The ECS network shall have no single point of failure for functions associated with site-specific network databases and configuration data.	2776	C-ISS-04020	A	Backups of all router configuration files shall be maintained at the local DAAC and the Network Management Facility (NMF).	99-0729	08/25/1999  		
173	EOSD4035	Complete	The ECS network shall have no single point of failure for functions associated with site-specific network databases and configuration data.	2825	C-MSS-00020	A	The MSS services shall have no single point of failure for functions associated with network databases and configuration data.	99-0729	08/25/1999  		
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2781	C-ISS-04070	A	The portion of the DAAC LAN supporting the SDPS function of archiving and distributing data shall contribute to the function's operational availability of 0.98 at a minimum and a mean down time of two (2) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2782	C-ISS-04080	A	The portion of the DAAC LAN supporting the SDPS function of User Interfaces to Client, Interoperability, Data Server, and Data Management (IMS) services at Individual DAAC Sites shall contribute to the function's operational availability of 0.993 at a minimum and a mean down time requirement of two (2) hours or less during times of staffed operations.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2783	C-ISS-04090	B1	The portion of the DAAC LAN supporting the SDPS function of  information searches on the ECS Directory shall contribute to the function's operational availability of 0.993 at a minimum and a mean down time of two (2) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2784	C-ISS-04102	B0	The portion of the EDC DAAC LAN supporting the SDPS function of Data Acquisition Request (DAR) Submittal including TOOs shall contribute to the function's operational availability of 0.993 at a minimum and mean down time of two (2) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2785	C-ISS-04110	A	The portion of the DAAC LAN supporting the SDPS function of metadata ingest and update shall contribute to the function's operational availability of 0.96 at a minimum and a mean down time of four (4) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2786	C-ISS-04120	B1	The portion of the DAAC LAN supporting the SDPS function of information searches on local holdings shall contribute to the function's operational availability of 0.96 at a minimum and a mean down time of four (4) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2787	C-ISS-04130	B1	The portion of the DAAC LAN supporting the SDPS function of local data order submission shall contribute to the function's operational availability of 0.96 at a minimum and a mean down time of four (4) hours or less during times of staffed operations.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2788	C-ISS-04140	B1	The portion of the DAAC LAN supporting the SDPS function of local data order submission across DAACs shall contribute to the function's operational availability of 0.96 at a minimum and a mean down time of four (4) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
174	EOSD4036	Complete	The ECS operational availability of individual network segments shall be consistent with the specified operational availability of the supported ECS functions.	2789	C-ISS-04150	A	The portion of the DAAC LAN supporting the SDPS function of Client, Interoperability, Data Management and Data Server (IMS) Data Base Management and Maintenance Interface shall contribute to the function's operational availability of 0.96 at a minimum and a mean down time of four (4) hours or less during times of staffed operation.	99-0729	08/25/1999  	No Data	
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	842	C-CSS-02068	A	The CSS-DCHCI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	1455	S-DMS-60410	Complete	The DMGHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	1750	S-DPS-60110	A	The SPRHW CI shall have a fault detection/fault isolation capability of major HWCI component failures without interfering with operations.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	1770	S-DPS-60520	A	The SPRHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	1804	S-DPS-70085	A	The AITHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	1826	S-DPS-80020	A	The AQAHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	1991	S-DSS-02046	A	The ACMHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2244	S-DSS-21825	A	The DRPHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2349	S-DSS-31015	A	The DIPHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2379	S-DSS-70080	A	The WKSHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2536	S-INS-00510	A	The INGST CI shall provide the capability to select Ingest History Log entries for viewing by the following parameters:    a.      Ingest start/stop dates and times  b.      External Data Provider  c.      Data Type Identifier  d.      Final Service Request Status  e.      Test or operational mode	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2589	S-INS-03200	B0	The INGST CI shall be capable of operating in an off-line (test) mode.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2590	S-INS-03210	B0	The INGST CI shall be capable of accessing test data sets when operating in off-line (test) mode.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2611	S-INS-60330	A	The ICLHW CI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2733	C-ISS-01200	A	The topology of the EOC LANs shall not inhibit the reconfiguration of FOS devices to support either operational or support functions.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2791	C-ISS-04160	A	The ISS elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2837	C-MSS-02068	A	The MSS-MHCI elements and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2872	C-MSS-16010	B0	MSS Monitor/Control Service shall communicate via ECS management protocol with the Management Agent Service in test or operational mode.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	2907	C-MSS-36010	IR1	The MSS Management Agent Service shall retrieve data from ECS managed objects in test or operational mode.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	3101	C-MSS-56050	B1	 The MSS Mode Management Service shall provide fault detection and isolation capabilities for each independently executing mode.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	3158	C-MSS-60150	IR1	The MSS Fault Management Application Service shall have the capability to receive fault notifications from the Management Agent Service.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	3167	C-MSS-60230	B0	The MSS Fault Management Application Service shall have the capability of generating a notification within a maximum of five minutes of fault detection.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	3190	C-MSS-60380	IR1	The MSS Fault Management Application Service at the sites shall isolate, locate, and identify faults, identify subsystem, equipment and software faults, and identify the nature of the faults detected within its site.	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	3191	C-MSS-60390	B0	The MSS Fault Management Application Service at the sites shall, for faults detected within its site, isolate, locate, and identify faults to the level of:   a. subsystem   b. equipment   c. software	99-0729	08/25/1999  		
175	EOSD4100	Complete	The ECS network segments and components shall include the on-line (operational mode) and off-line (test mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	3636	S-PLS-60450	A	The PLNHW CI elements and components shall include the on-line (operational mode) and off-line (test-mode) fault detection and isolation capabilities required to achieve the specified operational availability requirements.	99-0729	08/25/1999  		
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	197	S-DMS-30387	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	198	S-DMS-30388	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	202	S-DMS-30399	5B	The GTWAY CI shall return Integrated Browse Results to the V0 IMS using protocols defined in the V0/ECS ICD	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	233	S-DMS-40600	5B	The GDS-ECS Component of the ASTGW CI shall receive Product Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	240	S-DMS-40609	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1384	S-DMS-30396	5B	The GTWAY CI shall receive Integrated Browse Requests from the V0 IMS, using protocols defined in the V0/ECS ICD.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1416	S-DMS-40320	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1417	S-DMS-40325	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1422	S-DMS-40410	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1423	S-DMS-40420	5B	The GDS-ECS Component of the ASTGW CI shall send Price Estimates to the ASTER GDS using protocols defined in the ASTER GDS ICD.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1424	S-DMS-40435	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1425	S-DMS-40440	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1426	S-DMS-40470	5B	The GDS-ECS Component of the ASTGW CI shall receive Browse Requests from the ASTER GDS, using protocols defined in the ASTER GDS ICD.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1427	S-DMS-40480	5B	The GDS-ECS Component of the ASTGW CI shall send Browse Results to the ASTER GDS using protocols defined in the ASTER GDS ICD.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1428	S-DMS-40490	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1429	S-DMS-40500	5B	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.	99-0729	08/25/1999  	No Data	
181	EOSD5250	5A 5B  Partial	The ECS shall enable access to configuration controlled applications programming interfaces (APIs) that permit development of DAAC-unique value added services and products.  The interfaces include:       a. V0-ECS Gateway     b. SIPS Gateway     c. Search and Order Gateway   d. Order-only Gateway	1458	S-DPS-20010	A	The PRONG CI shall be developed with configuration-controlled Application Programming Interfaces (APIs) to support the development and integration of DAAC value-added processing.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2745	C-ISS-02000	IR1	The ISS shall provide connection oriented transport services as specified by the TCP protocol referenced in RFC 793.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2747	C-ISS-02020	IR1	The ISS shall provide connectionless transport services as specified by the UDP protocol referenced in RFC 768.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2748	C-ISS-02030	IR1	The ISS shall provide network layer services as specified by the Internet Protocol (IP) suite referenced in RFC 791.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2750	C-ISS-02050	IR1	The ISS shall provide ICMP network layer service as specified by RFC 792.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2751	C-ISS-02060	IR1	The ISS shall provide network layer services in compliance with one or more of the following  protocols as appropriate to the type of the physical network supported.  a. IP over Ethernet as specified in RFCs 894, 895, 826 (ARP), 903 (RARP)  b. IP over FDDI as specified in RFC 1188, 1390 (ARP, RARP)  c. IP over HiPPI as specified in RFC 1374 (includes ARP, RARP)  	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2769	C-ISS-02520	IR1	The ISS shall provide services based on the Open Shortest Path First (OSPF) protocol referenced in RFC 1583 to route traffic between the source and destination nodes, maintain route databases, and exchange routing information between networks.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2770	C-ISS-02522	B0	The ISS shall have the capability to provide services based on the Border Gateway Protocol-4 (BGP-4) referenced in RFC 1583 to route traffic between the source and destination nodes, maintain route databases, and exchange routing information between networks.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2773	C-ISS-02530	IR1	The ISS shall provide services based on the Routing Information Protocol (RIP) referenced in RFC  1058 to route network traffic between the source and destination nodes.	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2804	C-ISS-20000	B0	The ISS shall provide LANs at the following Release B sites:  a. GSFC DAAC; b. GSFC EOC; c. EDC DAAC; d. LaRC DAAC; f. GSFC SMC; j. NSIDC DAAC	99-0729	08/25/1999  	No Data	
182	ESN-0003	Complete	The ECS shall interface with collocated DAAC networks to enable researchers on existing networks (TCP/IP) to gain access to data and ECS services in a transparent manner to the underlying differences between the networks.	2805	C-ISS-20010	B1	The ISS shall provide LANs at the JPL and ORNL DAACs.	99-0729	08/25/1999  	No Data	
183	ESN-0006	Complete	The ECS shall interface with EMSn and ESSn.	2795	C-ISS-11020	B0	The ISS shall interface with NSI at GSFC, LaRC, EDC, and NSIDC to provide DAAC access to science users in accordance with current document "Interface Requirements Document between EOSDIS Core System (ECS) and the NASA Science Internet (NSI), 505-41-17".	99-0729	08/25/1999  	No Data	
183	ESN-0006	Complete	The ECS shall interface with EMSn and ESSn.	2799	C-ISS-11195	B0	The ISS shall provide for connectivity with EBnet at the following ECS sites:     a. GSFC DAAC     b. GSFC EOC     c. GSFC SMC     d. LaRC DAAC       h. NSIDC DAAC     i.  EDC DAAC	99-0729	08/25/1999  	No Data	
183	ESN-0006	Complete	The ECS shall interface with EMSn and ESSn.	2820	C-ISS-21020	B1	The ISS shall interface with NSI at JPL and ORNL to provide DAAC access to science users in accordance with current document "Interface Requirements Document between EOSDIS Core System (ECS) and the NASA Science Internet (NSI), 505-41-17".	99-0729	08/25/1999  	No Data	
183	ESN-0006	Complete	The ECS shall interface with EMSn and ESSn.	2822	C-ISS-21195	B1	The ISS shall provide for connectivity with EBnet at the JPL DAAC.	99-0729	08/25/1999  	No Data	
184	ESN-0080	Complete	The ECS shall support data exchange via the EMSn for inter-site data transmission between DAACs.	2729	C-ISS-01080	IR1	The ISS shall reuse the V0 WAN and LAN links in order to provide connectivity between V0 network nodes and V1 network nodes and to provide interoperability between the systems.	99-0729	08/25/1999  	No Data	
184	ESN-0080	Complete	The ECS shall support data exchange via the EMSn for inter-site data transmission between DAACs.	2799	C-ISS-11195	B0	The ISS shall provide for connectivity with EBnet at the following ECS sites:     a. GSFC DAAC     b. GSFC EOC     c. GSFC SMC     d. LaRC DAAC       h. NSIDC DAAC     i.  EDC DAAC	99-0729	08/25/1999  	No Data	
184	ESN-0080	Complete	The ECS shall support data exchange via the EMSn for inter-site data transmission between DAACs.	2822	C-ISS-21195	B1	The ISS shall provide for connectivity with EBnet at the JPL DAAC.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	797	C-CSS-00022	B0	CSS shall provide an independent DCE cell at each DAAC site.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	798	C-CSS-00023	B0	CSS shall provide an independent DCE cell at the SMC site.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	799	C-CSS-00030	A	The CSS services shall be extensible in its design to provide capability for growth and enhancement.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2764	C-ISS-02390	B0	The ISS-INHW CI LANs at the DAAC sites shall be designed in a manner that allows a. Nodes to be added to any given LAN segment. b. Additional LAN segments to be added to the LAN.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2765	C-ISS-02400	B	The ISS-INHW CI EOC Operational LAN shall be able to support 230 network devices without redesign.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2766	C-ISS-02410	B	The ISS-INHW CI EOC Operational LAN shall be able to support peak data rates of up to 48 Mbps without redesign.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2809	C-ISS-20090	B0	The ISS LANs at the GSFC, GSFC EOC, GSFC SMC, EDC, LaRC, and NSIDC DAACs shall be capable of supporting twice the R-B network traffic load estimates without redesign.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2810	C-ISS-20095	B1	The ISS LANs at JPL and ORNL DAACs shall be capable of supporting twice the R-B network traffic load estimates without redesign.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2811	C-ISS-20100	B0	The ISS LANs shall be designed in a manner that allows  a. Nodes to be added to any given LAN segment.; b. Additional LAN segments to be added to the LAN.	99-0729	08/25/1999  	No Data	
185	ESN-0240	Complete	The ECS shall be extensible in its network design to provide capability for growth and enhancement.	2826	C-MSS-00030	A	The MSS services shall be extensible in its design to provide capability for growth and  enhancement.	99-0729	08/25/1999  	No Data	
186	ESN-0280	Complete	The ECS shall provide file transfer service  and as a minimum shall include the capability to transfer the following data  types:  a. Unstructured Text  b. Binary Unstructured  c. Binary Sequential  d. Sequential Text	1093	C-CSS-60510	IR1	The CSS File Access Service shall be capable of transferring ASCII and binary files.	99-0729	08/25/1999  	No Data	
186	ESN-0280	Complete	The ECS shall provide file transfer service  and as a minimum shall include the capability to transfer the following data  types:  a. Unstructured Text  b. Binary Unstructured  c. Binary Sequential  d. Sequential Text	1097	C-CSS-60610	IR1	The CSS File Access Service shall allow selection of the file type (ASCII or binary) when utilizing the ftp access service.	99-0729	08/25/1999  	No Data	
187	ESN-0290	Complete	The ECS file transfer service shall be available in interactive and non-interactive services.	1086	C-CSS-60310	A	The CSS File Access Service shall support access control for the remote files.	99-0729	08/25/1999  	No Data	
187	ESN-0290	Complete	The ECS file transfer service shall be available in interactive and non-interactive services.	1087	C-CSS-60320	A	The CSS File Access Service shall provide location independent naming for the remote files.	99-0729	08/25/1999  	No Data	
187	ESN-0290	Complete	The ECS file transfer service shall be available in interactive and non-interactive services.	1091	C-CSS-60500	IR1	The CSS File Access Service shall provide functionality for interactive and non-interactive transfer of files (send and receive) between two host systems.	99-0729	08/25/1999  	No Data	
188	ESN-0340	Complete	The ECS shall interoperate and exchange messages and data with  external SMTP mail systems.	856	C-CSS-10510	B0	The CSS DCCI shall accept Electronic Mail Service requests from the User.	99-0729	08/25/1999  	No Data	
188	ESN-0340	Complete	The ECS shall interoperate and exchange messages and data with  external SMTP mail systems.	1110	C-CSS-61010	A	The CSS Electronic Mail Service shall interoperate and exchange messages with external mail systems based on SMTP and X.400 protocols.	99-0729	08/25/1999  	No Data	
188	ESN-0340	Complete	The ECS shall interoperate and exchange messages and data with  external SMTP mail systems.	1115	C-CSS-61070	B0	The CSS Electronic Mail Service shall provide store and forward services capable of supporting mail systems based on SMTP and X.400.	99-0729	08/25/1999  	No Data	
189	ESN-0345	Complete	The ECS shall be capable of transparently transmitting Multi-purpose Internet Mail Extensions (MIME) messages.	1111	C-CSS-61020	A	The CSS Electronic Mail Service shall be capable of sending and receiving the Multi-purpose Internet Mail Extensions (MIME) messages.	99-0729	08/25/1999  	No Data	
189	ESN-0345	Complete	The ECS shall be capable of transparently transmitting Multi-purpose Internet Mail Extensions (MIME) messages.	1136	C-CSS-61800	A	The CSS Electronic Mail Service shall provide the capability to send an electronic mail message non-interactively from an application.	99-0729	08/25/1999  	No Data	
189	ESN-0345	Complete	The ECS shall be capable of transparently transmitting Multi-purpose Internet Mail Extensions (MIME) messages.	1137	C-CSS-61810	A	The CSS Electronic Mail Service shall allow attaching multiple text or binary files to the mail message.	99-0729	08/25/1999  	No Data	
190	ESN-0350	Complete	The ECS Electronic Messaging Service, shall be capable of exchanging binary data.	1137	C-CSS-61810	A	The CSS Electronic Mail Service shall allow attaching multiple text or binary files to the mail message.	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	855	C-CSS-10500	B0	The CSS DCCI shall accept virtual terminal service request from the User.	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	859	C-CSS-10540	B0	The CSS DCCI shall provide virtual terminal service to the User.	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	1167	C-CSS-63000	IR1	The CSS Virtual Terminal shall provide a virtual device which hides the physical terminal characteristics and handling conventions from both the operator and the server host.	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	1168	C-CSS-63010	IR1	The CSS Virtual Terminal shall provide means to enhance characteristics of the basic virtual device by mutual agreement between the two communicating parties (option negotiations).	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	1169	C-CSS-63020	IR1	The CSS Virtual Terminal shall be based on industry standard and accepted protocols (telnet and ktelnet).	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	1170	C-CSS-63040	IR1	The CSS Virtual Terminal shall provide guest access to non-registered users to log into the ECS guest server.	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	1171	C-CSS-63050	A	The CSS Virtual Terminal shall support kerberized version of the telnet protocol for secure authentication of users.	99-0729	08/25/1999  	No Data	
191	ESN-0370	Complete	The ECS shall provide interactive virtual terminal services.	1172	C-CSS-63060	A	The CSS Virtual Terminal shall support X applications.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4044	C-CSS-30400	5B	The Registry Service shall maintain a collection of attribute-value pairs.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4045	C-CSS-30410	5B	The Registry Service shall support attributes of a hierarchical nature.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4046	C-CSS-30420	5B	The Registry Service shall allow a list of values to be associated with an attribute.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4047	C-CSS-30430	5B	The Registry Service shall support the string data type for values.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4048	C-CSS-30440	5B	The Registry Service shall support  multiple labeled Attribute Trees.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4049	C-CSS-30450	5B	The Registry Service shall allow a new attribute to be added to an Attribute Tree.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4050	C-CSS-30460	5B	The Registry Service shall allow a single mode to be associated with an Attribute Tree.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4051	C-CSS-30470	5B	The Registry Service shall allow an Attribute Tree to be copied to create a new Attribute Tree.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4052	C-CSS-30480	5B	The Registry Service shall provide access to the Registry via a mode-specific Registry Server.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4053	C-CSS-30490	5B	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.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4054	C-CSS-30510	5B	The Registry Service shall allow a description to be associated with each attribute.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4055	C-CSS-30520	5B	The Registry Service shall allow a change description to be associated with each value. 	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4056	C-CSS-30530	5B	The Registry Service maintenance shall be performed via a GUI which communicates directly with the Registry database.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4057	C-CSS-30540	5B	The Registry Service shall allow an application to obtain the value or values for an attribute by supplying the attribute path.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4058	C-CSS-30550	5B	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. 	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4059	C-CSS-30560	5B	The Registry shall allow indirect specification of a value by specifying an Attribute Path prefixed with an @ as the value of an attribute.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4060	C-CSS-30570	5B	The Registry Server shall accept the Registry Database SQL server name, username, password, and mode at startup.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4061	C-CSS-30580	5B	The Registry Service shall allow subtrees and individual attributes to be marked as privileged.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4062	C-CSS-30590	5B	The Registry Service shall have the capability to support multiple drops concurrently.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4063	C-CSS-30600	5B	The Registry Service shall allow any subtree of an Attribute Tree to be moved to another location within the same or another Attribute Tree.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4064	C-CSS-30610	5B	The Registry Service shall allow any tree node or attribute within an Attribute Tree to be renamed.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4065	C-CSS-30620	5B	The Registry Service shall allow any subtree of an Attribute Tree to be deleted.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4066	C-CSS-30630	5B	The Registry Service shall allow any subtree of an Attribute Tree to be replicated to another location within the same or another Attribute Tree.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4067	C-CSS-30140	5B	The Process Framework Configuration File mechanism shall fetch parameters from the Registry Service.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4068	C-CSS-30150	5B	The Process Framework Configuration File mechanism shall read parameters from a .CFG file if present, otherwise parameters will be read from the Registry.	99-0914	02/27/1999  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	4476	C-CSS-30495	5B	The Registry Service shall allow multiple Registry Servers to run in a mode to provide redundancy of the Registry Service.	00-0420	04/24/2000  		
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	805	C-CSS-01000	A	The CSS DOF Service shall provide a standards-based Interface Definition Language (IDL) and language mappings to at least C and C++ (limited) languages.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	806	C-CSS-01010	A	The CSS DOF provided IDL shall support versioning of the interface supporting minor and major versions.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	807	C-CSS-01020	A	The IDL supported minor versioning shall be upward compatible that requires no changes in the client software to communicate with the new implementation.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	808	C-CSS-01030	A	The CSS Services shall provide Process-to-Process Communication Services to support the passing of the general error status as a parameter in calls between the clients and servers automatically.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	809	C-CSS-01040	A	The CSS DOF Service shall provide the capability to marshal and unmarshal the arguments and the returned value transparently while making a remote procedure call including common standard formats and user-defined formats.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	810	C-CSS-01050	A	The CSS DOF Service shall provide the capability to marshal and unmarshal standard types to/from a common standard format.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	811	C-CSS-01060	A	The CSS DOF Service shall provide the capability to define marshaling and unmarshaling routines for user defined types.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	812	C-CSS-01070	A	The CSS DOF Service shall support Process-to-Process Communication services by providing server APIs  to register/unregister services in the namespaces (in different administrative domains) under different views including:  a. server  b. group  c. profile.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	813	C-CSS-01080	A	The CSS DOF Service shall provide server APIs  to register/unregister different implementations of an interface in the namespace.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	814	C-CSS-01090	A	The CSS DOF Service shall provide server APIs to register/unregister individual objects implementing an interface in the namespace.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	815	C-CSS-01100	A	The CSS DOF Service shall provide server APIs to register their services using different protocols in the namespace.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	816	C-CSS-01110	A	The CSS DOF Service shall provide server APIs to register their services with the local endpoint mapper with the proper port number.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	817	C-CSS-01120	A	The CSS DOF Service shall provide mechanisms to shutdown a service gracefully, by allowing the servers to unregister the server information from the namespace.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	818	C-CSS-01130	A	The CSS DOF Service shall provide server APIs to limit the maximum number of threads to use in servicing the requests concurrently.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	819	C-CSS-01140	A	The CSS DOF Service shall provide client APIs to bind to services (registered in the local namespace as well as remote namespaces) by using any of the following information to achieve location transparency of services.  a. a service name  b. an interface name  c. an object name  d. a host name and communication protocol  e. an object reference	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	820	C-CSS-01150	A	The CSS DOF Service shall return gracefully by throwing an exception or returning an error code when it can not retrieve the binding information or can not resolve a binding.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	821	C-CSS-01160	A	The CSS DOF Service shall provide client APIs to specify a confidence level of the binding information as follows:  a. a low confidence level indicating the use of a local cache to obtain binding information  b. a medium confidence level indicating the DOF to get the binding information from any of the directory replicas.  c. a high confidence level indicating the DOF to get the binding information from the master copy of the directory services.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	822	C-CSS-01170	A	The CSS DOF Service shall provide APIs to set/get the authentication service type to be used between the server and the client.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	823	C-CSS-01180	A	The CSS DOF Service shall provide APIs to set/get authorization service type to be used between the client and the server.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	824	C-CSS-01190	A	The CSS DOF Service shall provide APIs to maintain the integrity of the data to be passed between the client and the server.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	825	C-CSS-01200	A	The CSS DOF Service shall provide APIs to maintain the privacy of the data passed between the client and the server by encrypting and decrypting the data.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	826	C-CSS-01210	A	The CSS DOF Service shall provide APIs to set the identity of a given principal to a given process.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	827	C-CSS-01220	A	The CSS DOF shall support the TCP and UDP communication protocols to communicate between the servers and the clients.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	885	C-CSS-10810	B0	The CSS DCCI shall accept lifecycle commands request from MSS.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	886	C-CSS-10820	B0	The CSS DCCI shall accept mode request from MSS.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	939	C-CSS-22000	A	The CSS Message service shall provide an API for senders to send messages to receivers asynchronously without waiting for the receivers to receive it.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	940	C-CSS-22010	A	The CSS Message service shall provide an API for senders to send messages to receivers in a deferred synchronously manner through an intermediary where by they can contact the intermediary at a latter time to receive the result.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	941	C-CSS-22040	A	The CSS Message Service shall provide an API for the sender to designate multiple receivers for asynchronous messages.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	942	C-CSS-22050	A	The CSS Message Service shall support multiple message queues so different groups of processes can use different message queues.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	943	C-CSS-22060	A	The CSS Message Service shall purge a message from the message queue after an application specified time and an application specified number of tries irrespective of its delivery to the receivers.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	944	C-CSS-22065	A	The CSS Message Service shall log event messages to the MSS management agents whenever the message service could not deliver a message to any receiver in the time period set by the sender of the message.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	945	C-CSS-22070	A	The CSS Message Service shall store undeliverable messages and retrieve and transmit them later.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	946	C-CSS-22080	B0	The CSS Message Service shall provide an API for the receiver to register interest in receiving messages from a certain sender.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	947	C-CSS-22090	A	The CSS Message Service shall provide the capability to locate and send (push model) the messages to receivers.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	948	C-CSS-22100	A	The CSS Message Service shall provide a non blocking API for the receiver to contact the message queue and get (pull model) the message.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	949	C-CSS-22110	A	The CSS Message service shall support guaranteed delivery of the message to the receiver.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	950	C-CSS-22120	A	The CSS Message service shall provide an API for the sender of the message to get the acknowledgment information the message service receives from the receivers.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	951	C-CSS-22130	A	The CSS Message service shall associate the receiver to a returned value and maintain that information locally until the sender requests that information.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	952	C-CSS-22140	A	The CSS Message Service shall provide an API for the sender of the message to receive return information stored at the message queue.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	953	C-CSS-22150	A	The CSS Message Service shall defer sending a message to a receiver, if the receiver is not active, and should try sending the message periodically with an application set interval of time and an application specified number of tries until the receiver is active.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	956	C-CSS-24010	B0	The CSS Lifecycle Service shall provide a generic instantiation capability that creates a new object for a client.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	957	C-CSS-24020	B0	The CSS Lifecycle Service shall provide an API that accepts state initialization information.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	958	C-CSS-24040	B0	The CSS Lifecycle Service shall provide an API that returns an object invocation handle.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	986	C-CSS-26010	A	The CSS Thread Service shall allow the option that each invocation of a server operation to run as a distinct thread.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	987	C-CSS-26040	A	The CSS Thread Service shall provide an API that synchronizes the access of shared data between concurrent threads.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	998	C-CSS-30010	A	The Process Framework shall accept at start up time process configuration information that it makes available to the application.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	999	C-CSS-30020	A	The Process Framework shall also accept process configuration information via the command line.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1000	C-CSS-30030	A	The Process Framework shall give precedence to the variables defined on the command line over those defined in the configuration file.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1001	C-CSS-30040	A	The Process Framework shall exit with an error status if the mode of operation and the configuration file name are not provided on the command line.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1002	C-CSS-30050	A	The Process Framework shall provide the ability for a process to get the following information:  a. Mode of operation  b. Executable name  c. Process ID  d. Application ID  e. Program ID  f. Major Version  g. Minor Version	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1003	C-CSS-30060	A	The Process Framework shall provide interfaces to the underlying distributed architecture to set the following naming parameters:  a. Short name for server  b. Profile name  c. Group name  	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1004	C-CSS-30070	A	The Process Framework shall provide interfaces to the underlying distributed architecture including:  a. Message Passing  b. Management Agent Framework  c. Server Request Framework  d. Scheduled File Transfer (FTP)	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1006	C-CSS-30090	A	The Process Framework shall provide an interface to the underlying distributed architecture to set the communications protocol policy  	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1007	C-CSS-30100	A	The Process Framework shall provide an interface to the underlying distributed architecture to set the host policy  	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1008	C-CSS-30110	A	The Process Framework shall provide the ability to log errors and events for both client and server processes in support of Network Management Services provided by MSS.  	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1009	C-CSS-30130	B0	The Process Framework shall provide interfaces to the Server Request Framework (SRF).	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1012	C-CSS-30180	B0	The SRF shall support the synchronous processing of requests by the client to the server.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1013	C-CSS-30190	B0	The SRF shall support the asynchronous processing of requests by the client to the server.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1014	C-CSS-30200	B0	The SRF shall allow requests to be submitted by a client that then terminates while requests continue to run	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1015	C-CSS-30210	B0	The SRF shall allow the reestablishment of the request contexts by the client upon restart.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1016	C-CSS-30220	B0	The SRF shall allow a client to send a Cancel notification to a currently running request.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1017	C-CSS-30230	B0	The SRF shall allow the client to obtain the current priority of an executing request thread.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1018	C-CSS-30240	B0	The SRF shall allow a client to alter the execution priority of a request's thread.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1019	C-CSS-30250	B0	The SRF shall allow the client to obtain a unique request identifier for each request submitted such that the identifier may be used to reference the request in the future.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1020	C-CSS-30260	B0	The SRF shall support the use of application defined status messages that may be posted by the server to inform the client of request progress.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1021	C-CSS-30270	B0	The SRF shall support the use of application defined result messages that are used to communicate the results of a request back to the client.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1022	C-CSS-30280	B0	The SRF shall support callback functions for statuses.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1023	C-CSS-30290	B0	The SRF shall support callback functions for request completion.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1024	C-CSS-30300	B0	The SRF shall allow a client to send a Suspend request signal to the server on a per request basis.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1025	C-CSS-30310	B0	The SRF shall allow a client to send a Resume request signal to the server on a per request basis.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1026	C-CSS-30320	B0	The SRF shall allow an executing request to block waiting on a Resume signal.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1027	C-CSS-30330	B0	The SRF shall support the explicit acknowledgment by the server application back to the client of a request.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1028	C-CSS-30340	B0	The SRF shall support a time-out on an explicit request acknowledgment.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1029	C-CSS-30350	B0	The SRF shall support automatic request restart on a per request basis.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1030	C-CSS-30360	B0	The SRF shall support automatic request restart on a per operation basis.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1031	C-CSS-30370	B0	The SRF shall support the ability to obtain a request's current state. (In progress, complete, etc.)	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1032	C-CSS-30380	B0	The SRF shall allow arbitrary objects to be passed as arguments in requests.	99-0729	08/25/1999  	No Data	
192	ESN-0450	Complete	The ECS shall provide process-to-process communication service.	1033	C-CSS-30390	B0	The SRF shall allow executing requests to determine if the server is available.	99-0729	08/25/1999  	No Data	
194	ESN-0510	Complete	The ECS directory function shall be able to respond to requests for information concerning named objects, either physical or logical, so as to support communications with those objects.	893	C-CSS-20000	A	The CSS Directory service shall provide the basic functionality to save and retrieve information into the local namespace:  a. Create/Delete/Get context (key)  b. List context.  c. Set/Get attributes.  d. Create/Delete attributes.  e. List attributes.  f. Set/Get attribute information.	99-0729	08/25/1999  	No Data	
194	ESN-0510	Complete	The ECS directory function shall be able to respond to requests for information concerning named objects, either physical or logical, so as to support communications with those objects.	894	C-CSS-20010	A	The CSS shall provide implementations of industry standard directory services, such as DNS, X.500, and CDS.	99-0729	08/25/1999  	No Data	
194	ESN-0510	Complete	The ECS directory function shall be able to respond to requests for information concerning named objects, either physical or logical, so as to support communications with those objects.	903	C-CSS-20085	A	The CSS Directory Service shall interact with the Security Service to provide principal based security to the entries in the CDS namespace and an enhanced host based security for the entries in the GDS namespace.	99-0729	08/25/1999  	No Data	
194	ESN-0510	Complete	The ECS directory function shall be able to respond to requests for information concerning named objects, either physical or logical, so as to support communications with those objects.	906	C-CSS-20120	A	The CSS Directory service shall provide a mechanism to communicate with both X.500 and DNS naming services in resolving lookups.	99-0729	08/25/1999  	No Data	
194	ESN-0510	Complete	The ECS directory function shall be able to respond to requests for information concerning named objects, either physical or logical, so as to support communications with those objects.	907	C-CSS-20130	A	The CSS Directory Service shall provide namespaces that are compatible with the existing NASA X.500 and DNS directory services.	99-0729	08/25/1999  	No Data	
197	ESN-0610	Complete	The ECS  shall include multiple  Directory  Service Agents (DSAs) which shall be collectively responsible for holding or retrieving all directory information which is needed by ECS.	897	C-CSS-20030	A	The CSS Directory Service shall provide the capability to partition the namespace and distribute and maintain them at different hosts on the network.	99-0729	08/25/1999  	No Data	
197	ESN-0610	Complete	The ECS  shall include multiple  Directory  Service Agents (DSAs) which shall be collectively responsible for holding or retrieving all directory information which is needed by ECS.	898	C-CSS-20040	A	The CSS Directory Service shall provide the capability to replicate partitions of the namespace on different hosts.	99-0729	08/25/1999  	No Data	
197	ESN-0610	Complete	The ECS  shall include multiple  Directory  Service Agents (DSAs) which shall be collectively responsible for holding or retrieving all directory information which is needed by ECS.	899	C-CSS-20050	A	The CSS Directory service shall provide multiple directory agents which cooperate among themselves through referral and chaining to perform directory operations.	99-0729	08/25/1999  	No Data	
197	ESN-0610	Complete	The ECS  shall include multiple  Directory  Service Agents (DSAs) which shall be collectively responsible for holding or retrieving all directory information which is needed by ECS.	900	C-CSS-20060	A	The CSS Directory service shall provide a way to denote the relative root of the namespace.	99-0729	08/25/1999  	No Data	
197	ESN-0610	Complete	The ECS  shall include multiple  Directory  Service Agents (DSAs) which shall be collectively responsible for holding or retrieving all directory information which is needed by ECS.	2804	C-ISS-20000	B0	The ISS shall provide LANs at the following Release B sites:  a. GSFC DAAC; b. GSFC EOC; c. EDC DAAC; d. LaRC DAAC; f. GSFC SMC; j. NSIDC DAAC	99-0729	08/25/1999  	No Data	
197	ESN-0610	Complete	The ECS  shall include multiple  Directory  Service Agents (DSAs) which shall be collectively responsible for holding or retrieving all directory information which is needed by ECS.	2805	C-ISS-20010	B1	The ISS shall provide LANs at the JPL and ORNL DAACs.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2817	C-ISS-20180	B0	The ISS shall receive diagnostic test requests from the MSS.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2819	C-ISS-20200	B0	The ISS shall send diagnostic test requests to the MSS.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2858	C-MSS-12080	IR1	The MSS MUI Service shall  provide a capability for applications to alert the M&O Staff	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2862	C-MSS-12120	IR1	The MSS MUI Service shall provide a capability for the operator to browse MIB values.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2864	C-MSS-12140	IR1	The MSS MUI Service shall provide the capability for an application to register and unregister managed objects.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2869	C-MSS-14030	IR1	The MSS Map/Collection Service shall provide a capability to define a hierarchical relationship between maps and sub-maps (i.e., a graphical hierarchical tree)	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2871	C-MSS-16005	IR1	The ECS management protocol shall be the SNMP standard as specified in RFC 1157.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2879	C-MSS-16100	IR1	The MSS Monitor/Control Service shall perform the following protocol test on managed network nodes:  a. IP test  b. TCP test  c. SNMP test  d. UDP test  e. ICMP test	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2903	C-MSS-20010	IR1	The MSS Discovery Service shall discover (via network protocol) new instances of managed objects.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2906	C-MSS-20040	IR1	The MSS Discovery Service shall update the object database after the Discovery Service receives a request to register/unregister a managed object.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	2923	C-MSS-36110	B0	The MSS Management Agent Service shall provide an ECS master agent to coordinate and communicate with multiple ECS management subagents.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3142	C-MSS-60010	IR1	The MSS Fault Management Application Service shall provide the capability to create and display graphical representations of a given network topology consisting of the following:    a. routers   b. communication lines   c. hosts   d. peripherals   e. applications	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3154	C-MSS-60110	IR1	The MSS Fault Management Application Service shall be capable of receiving fault notifications.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3164	C-MSS-60200	IR1	The MSS Fault Management Application Service shall have the capability to generate the following types of notifications for detected faults :   a. a change in the color of an icon on a display   b. a message in a pop-up notification window   c. logging the following fault information to a disk log file:    1.  fault type    2.  date and time of occurrence of the fault    3.  identification of the source of the notification (e.g. IP address, process name, etc.)    4.  fault data received with the notification    5.  operator-defined descriptive text   d. audible alert	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3186	C-MSS-60350	A	The MSS Fault Management Application Service shall have the capability to periodically execute diagnostic tests in order to isolate, characterize and identify a fault.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3195	C-MSS-60420	A	The MSS Fault Management Application Service shall interface with the MSS Configuration Management Application Service and schedule a change in the configuration of the site when such a change in the configuration of the site is deemed necessary to recover from a fault.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3198	C-MSS-60520	B0	The MSS Fault Management Application Service shall provide the capability to allow the specification and execution of action routines in response to the notification of a fault.	99-0729	08/25/1999  	No Data	
198	ESN-0620	Complete	The ECS shall include a network management function to monitor and control the local ECS networks.	3204	C-MSS-66001	B0	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components      a. network components         1.  routers         2.  links         3.  bridges         4.  gateways      b. hosts      c. operating systems      d. peripherals      e. databases     f. ECS applications.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2817	C-ISS-20180	B0	The ISS shall receive diagnostic test requests from the MSS.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2819	C-ISS-20200	B0	The ISS shall send diagnostic test requests to the MSS.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2850	C-MSS-12005	IR1	The MSS Management User Interface (MUI) Service shall be compatible with the ECS management framework.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2863	C-MSS-12130	IR1	The MSS MUI Service shall provide the capability for the M&O Staff to register and unregister managed objects.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2869	C-MSS-14030	IR1	The MSS Map/Collection Service shall provide a capability to define a hierarchical relationship between maps and sub-maps (i.e., a graphical hierarchical tree)	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2871	C-MSS-16005	IR1	The ECS management protocol shall be the SNMP standard as specified in RFC 1157.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2879	C-MSS-16100	IR1	The MSS Monitor/Control Service shall perform the following protocol test on managed network nodes:  a. IP test  b. TCP test  c. SNMP test  d. UDP test  e. ICMP test	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2903	C-MSS-20010	IR1	The MSS Discovery Service shall discover (via network protocol) new instances of managed objects.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2906	C-MSS-20040	IR1	The MSS Discovery Service shall update the object database after the Discovery Service receives a request to register/unregister a managed object.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	3142	C-MSS-60010	IR1	The MSS Fault Management Application Service shall provide the capability to create and display graphical representations of a given network topology consisting of the following:    a. routers   b. communication lines   c. hosts   d. peripherals   e. applications	99-0729	08/25/1999  	No Data	
199	ESN-0640	Complete	The ECS shall include  management functions at each ECS site, for the management of ECS network equipment or gateways.	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	914	C-CSS-21020	IR1	The CSS Security service shall provide the capability to create/modify/delete user accounts and privileges in the security registry.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	915	C-CSS-21030	IR1	The CSS Security service shall provide the capability to define/modify/delete group information in the security registry.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2746	C-ISS-02010	IR1	The ISS shall provide the capability to filter packets based on the port/socket of the  transport layer protocol.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2804	C-ISS-20000	B0	The ISS shall provide LANs at the following Release B sites:  a. GSFC DAAC; b. GSFC EOC; c. EDC DAAC; d. LaRC DAAC; f. GSFC SMC; j. NSIDC DAAC	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2805	C-ISS-20010	B1	The ISS shall provide LANs at the JPL and ORNL DAACs.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2871	C-MSS-16005	IR1	The ECS management protocol shall be the SNMP standard as specified in RFC 1157.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	2986	C-MSS-40120	XT	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. 	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3195	C-MSS-60420	A	The MSS Fault Management Application Service shall interface with the MSS Configuration Management Application Service and schedule a change in the configuration of the site when such a change in the configuration of the site is deemed necessary to recover from a fault.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3208	C-MSS-66010	IR1	The MSS performance management application service shall be capable of monitoring ECS component protocol stack performance parameters defined in IETF RFC 1213.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3216	C-MSS-66090	B0	The MSS Performance Management Application Service shall have the capability to collect the following performance information about communication protocol stacks on managed devices:   a. number of transport layer messages received with errors   b. number of transport layer messages requiring retransmission   c. number of transport layer messages received that could not be delivered   d. number of network layer messages received with errors   e. number of network layer messages received that could not be delivered   f. number of network layer messages that were discarded	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3280	C-MSS-70100	IR1	The MSS site Security Management Application Service shall provide the capability to set, maintain, and update access control information for ECS resources.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3281	C-MSS-70110	A	The MSS site Security Management Application Service shall provide the capability to specify privileges for authorized users and user groups for access to ECS resources.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3282	C-MSS-70120	IR1	The MSS site Security Management Application service shall provide the mechanism, for each ECS host, to allow or deny incoming requests from specific hosts to services.	99-0729	08/25/1999  	No Data	
200	ESN-0650	Complete	The ECS shall perform the following network management functions for each protocol  stack implemented in  any ECS element, and each communications facility:  a. Network Configuration Management  b. Network Fault Management  c. Network Performance Management  d. Network Security Management	3283	C-MSS-70130	IR1	The MSS site Security Management Application Service shall provide a command line interface and a GUI for the management of the following security databases:  a. Authentication Database    b.  Authorization Database  c. Network Database	99-0729	08/25/1999  	No Data	
201	ESN-0690	6B Partial	The ECS shall be capable of reconfiguration  transparent to network  users.	796	C-CSS-00020	A	The CSS services shall have no single point of failure for functions associated with DCE services and network databases.	99-0729	08/25/1999  	No Data	
201	ESN-0690	6B Partial	The ECS shall be capable of reconfiguration  transparent to network  users.	801	C-CSS-00100	A	The CSS Directory services shall maintain multiple copies of the namespace on different hosts to provide fault tolerance.	99-0729	08/25/1999  	No Data	
201	ESN-0690	6B Partial	The ECS shall be capable of reconfiguration  transparent to network  users.	802	C-CSS-00120	B0	The CSS Directory services shall provide capabilities supporting reconfiguration transparent to the user.	99-0729	08/25/1999  	No Data	
201	ESN-0690	6B Partial	The ECS shall be capable of reconfiguration  transparent to network  users.	817	C-CSS-01120	A	The CSS DOF Service shall provide mechanisms to shutdown a service gracefully, by allowing the servers to unregister the server information from the namespace.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2753	C-ISS-02110	B0	The ISS-INHW CI physical components, and services shall have the capability to be monitored via SNMP agents.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2850	C-MSS-12005	IR1	The MSS Management User Interface (MUI) Service shall be compatible with the ECS management framework.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2868	C-MSS-14020	IR1	The MSS Map/Collection Service shall provide a capability to define maps and objects.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2869	C-MSS-14030	IR1	The MSS Map/Collection Service shall provide a capability to define a hierarchical relationship between maps and sub-maps (i.e., a graphical hierarchical tree)	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2871	C-MSS-16005	IR1	The ECS management protocol shall be the SNMP standard as specified in RFC 1157.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2879	C-MSS-16100	IR1	The MSS Monitor/Control Service shall perform the following protocol test on managed network nodes:  a. IP test  b. TCP test  c. SNMP test  d. UDP test  e. ICMP test	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2903	C-MSS-20010	IR1	The MSS Discovery Service shall discover (via network protocol) new instances of managed objects.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2906	C-MSS-20040	IR1	The MSS Discovery Service shall update the object database after the Discovery Service receives a request to register/unregister a managed object.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	2923	C-MSS-36110	B0	The MSS Management Agent Service shall provide an ECS master agent to coordinate and communicate with multiple ECS management subagents.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3208	C-MSS-66010	IR1	The MSS performance management application service shall be capable of monitoring ECS component protocol stack performance parameters defined in IETF RFC 1213.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3210	C-MSS-66030	IR1	The MSS performance management application service shall be capable of receiving managed object definitions for each managed object.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3211	C-MSS-66040	IR1	The MSS performance management application service shall be capable of specifying which available performance metrics are to be gathered from each individual managed object.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3212	C-MSS-66050	IR1	The MSS performance management application service shall be capable of requesting performance data from each individual managed object:  a. at configurable intervals  b. on demand.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3213	C-MSS-66060	IR1	The MSS performance management application service shall be capable of receiving requested performance data from ECS components.	99-0729	08/25/1999  	No Data	
203	ESN-0740	Complete	The ECS network management service shall  retrieve  performance/fault data about local ECS network protocol stacks and equipment.	3216	C-MSS-66090	B0	The MSS Performance Management Application Service shall have the capability to collect the following performance information about communication protocol stacks on managed devices:   a. number of transport layer messages received with errors   b. number of transport layer messages requiring retransmission   c. number of transport layer messages received that could not be delivered   d. number of network layer messages received with errors   e. number of network layer messages received that could not be delivered   f. number of network layer messages that were discarded	99-0729	08/25/1999  	No Data	
204	ESN-0750	Complete	The ECS network management component at each DAAC shall provide capabilities for the extraction, tabulation, and display to the operator of network performance data.	3228	C-MSS-66171	B0	The MSS performance management application service shall log ECS performance data pertaining to ECS network components, ECS applications and operating system resources.	99-0729	08/25/1999  	No Data	
204	ESN-0750	Complete	The ECS network management component at each DAAC shall provide capabilities for the extraction, tabulation, and display to the operator of network performance data.	3229	C-MSS-66180	IR1	The MSS performance management application service shall have the capability to generate the following types of statistics for a configurable period of time for performance data stored in the Management Database:  a. average  b. median  c. maximum  d. minimum  e. ratios  f. rates  g. standard deviations.	99-0729	08/25/1999  	No Data	
204	ESN-0750	Complete	The ECS network management component at each DAAC shall provide capabilities for the extraction, tabulation, and display to the operator of network performance data.	3240	C-MSS-66260	IR1	The MSS performance management application service shall provide queries that generate performance statistics from performance data stored in the Management Database.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	888	C-CSS-10840	B0	The CSS DCCI shall have the capability to send processing status to MSS.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	889	C-CSS-10860	B0	The CSS DCCI shall have the capability to send detected hardware and software  fault information to MSS.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	891	C-CSS-10880	B0	The CSS DCCI shall have the capability to send resource utilization data to MSS.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	2977	C-MSS-40000	B0	The MSS configuration management application service at each site shall track the following items at the site by name and identifier:  a. ECS subsystems, networks, and configured system and network devices such as workstations, servers, and routers    b. ECS releases and site baselines    c. ECS hardware and software resources designated as configuration items  d. specifications asscoiated with configuration items    e. technical documentation and test materials  f. scientific algorithms, including software, data and test materials (DAACs only)	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3142	C-MSS-60010	IR1	The MSS Fault Management Application Service shall provide the capability to create and display graphical representations of a given network topology consisting of the following:    a. routers   b. communication lines   c. hosts   d. peripherals   e. applications	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3164	C-MSS-60200	IR1	The MSS Fault Management Application Service shall have the capability to generate the following types of notifications for detected faults :   a. a change in the color of an icon on a display   b. a message in a pop-up notification window   c. logging the following fault information to a disk log file:    1.  fault type    2.  date and time of occurrence of the fault    3.  identification of the source of the notification (e.g. IP address, process name, etc.)    4.  fault data received with the notification    5.  operator-defined descriptive text   d. audible alert	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3165	C-MSS-60210	A	The MSS Fault Management Application Service shall maintain a list of external service providers, M&O operators, and applications to be notified in the event that a specified fault is detected.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3166	C-MSS-60220	B0	The MSS Fault Management Application Service shall have the capability to send the notification of a fault to registered recipients.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3167	C-MSS-60230	B0	The MSS Fault Management Application Service shall have the capability of generating a notification within a maximum of five minutes of fault detection.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3178	C-MSS-60300	B0	The MSS Fault Management Application Service shall provide the capability to verify connectivity between selected pairs of hosts on the ESN.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3179	C-MSS-60301	B0	The MSS Fault Management Application Service shall provide the capability to identify routes between selected pairs of hosts on the EBnet.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3190	C-MSS-60380	IR1	The MSS Fault Management Application Service at the sites shall isolate, locate, and identify faults, identify subsystem, equipment and software faults, and identify the nature of the faults detected within its site.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3201	C-MSS-60600	IR1	The MSS Fault Management Application Service shall have the capability to generate, on an interactive and on a scheduled basis, reports on performance/error data that it has been configured to collect.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3202	C-MSS-60610	B0	The MSS Fault Management Application Service shall have the capability to build histories for different types of errors and events detected, for the purpose of analysis.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3258	C-MSS-68000	IR1	The MSS performance management application service shall be capable of graphically displaying the operational state of managed objects through the MUI service.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3259	C-MSS-68010	IR1	The MSS performance management application service shall be capable of displaying M&O staff-selected performance statistics through the MUI in tabular and graphical formats.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3260	C-MSS-68020	IR1	The MSS performance management application service shall be capable of printing M&O staff-selected performance statistics.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3267	C-MSS-68090	B0	The MSS Performance Management Application Service shall have the capability to generate reports from collected management data.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3306	C-MSS-70710	IR1	The MSS Security Management Application Service shall have the capability to generate reports from collected management data.	99-0729	08/25/1999  	No Data	
205	ESN-0760	Completel	The ECS network management  function at each DAAC shall  provide, on an interactive basis,  network configuration, fault and performance information.	3348	C-MSS-77080	B0	The MSS Accountability Management Service shall have the capability to generate reports from collected management data.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	2750	C-ISS-02050	IR1	The ISS shall provide ICMP network layer service as specified by RFC 792.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	2879	C-MSS-16100	IR1	The MSS Monitor/Control Service shall perform the following protocol test on managed network nodes:  a. IP test  b. TCP test  c. SNMP test  d. UDP test  e. ICMP test	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	3212	C-MSS-66050	IR1	The MSS performance management application service shall be capable of requesting performance data from each individual managed object:  a. at configurable intervals  b. on demand.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	3213	C-MSS-66060	IR1	The MSS performance management application service shall be capable of receiving requested performance data from ECS components.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	3215	C-MSS-66080	IR1	The MSS performance management application service shall be capable of retrieving the following data for all network component interfaces:  a. operational status  b. type  c. speed  d. octets in/out  e. packets in/out  f. discards in/out  g. errors in/out	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	3259	C-MSS-68010	IR1	The MSS performance management application service shall be capable of displaying M&O staff-selected performance statistics through the MUI in tabular and graphical formats.	99-0729	08/25/1999  	No Data	
206	ESN-0780	Complete	The ECS network elements, shall have the capability to report, periodically and on an interactive basis , network statistics to the ECS network management function, including  the following information:  a. Network reset and restart indications  b. Outages and CRC errors  c. Performance statistics	3260	C-MSS-68020	IR1	The MSS performance management application service shall be capable of printing M&O staff-selected performance statistics.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2903	C-MSS-20010	IR1	The MSS Discovery Service shall discover (via network protocol) new instances of managed objects.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2907	C-MSS-36010	IR1	The MSS Management Agent Service shall retrieve data from ECS managed objects in test or operational mode.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	2923	C-MSS-36110	B0	The MSS Management Agent Service shall provide an ECS master agent to coordinate and communicate with multiple ECS management subagents.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	3142	C-MSS-60010	IR1	The MSS Fault Management Application Service shall provide the capability to create and display graphical representations of a given network topology consisting of the following:    a. routers   b. communication lines   c. hosts   d. peripherals   e. applications	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	3146	C-MSS-60020	IR1	The MSS Fault Management Application Service shall provide the capability to define categories of faults.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	3163	C-MSS-60190	IR1	The MSS Fault Management Application Service shall use the Logging Services to record each detected fault.	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	3215	C-MSS-66080	IR1	The MSS performance management application service shall be capable of retrieving the following data for all network component interfaces:  a. operational status  b. type  c. speed  d. octets in/out  e. packets in/out  f. discards in/out  g. errors in/out	99-0729	08/25/1999  	No Data	
207	ESN-0790	Complete	The ECS shall include the following configuration management functions:  a. Collect information describing the state of the network subsystem and its communications resources,  b. Exercise control over the configuration, parameters, and resources of the subsystem,  and over the information collected  c. Store the configuration information collected, and   d. Display the configuration information  e. Register all configuration modifications	3219	C-MSS-66121	B0	The MSS performance management application service shall be capable of determining the operational state of all network components, hosts, and peripherals to be:      a. on-line      b. off-line      c. in test mode      d. In maintenance,      e. in simulation mode.	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2851	C-MSS-12010	IR1	The MSS Management User Interface (MUI) Service shall provide a graphical user interface that is OSF/MOTIF compliant	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2854	C-MSS-12040	IR1	The MSS MUI Service shall provide a capability for an application to add/delete a symbol and to modify a symbol's shape, color and position	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2868	C-MSS-14020	IR1	The MSS Map/Collection Service shall provide a capability to define maps and objects.	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2869	C-MSS-14030	IR1	The MSS Map/Collection Service shall provide a capability to define a hierarchical relationship between maps and sub-maps (i.e., a graphical hierarchical tree)	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	3160	C-MSS-60162	B0	The MSS SMC Trouble Ticket Application Service shall have the capability to exchange notifications of detected faults and degradation of performance with:  a. EBnet  b. NSI  c. ASTER	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	3164	C-MSS-60200	IR1	The MSS Fault Management Application Service shall have the capability to generate the following types of notifications for detected faults :   a. a change in the color of an icon on a display   b. a message in a pop-up notification window   c. logging the following fault information to a disk log file:    1.  fault type    2.  date and time of occurrence of the fault    3.  identification of the source of the notification (e.g. IP address, process name, etc.)    4.  fault data received with the notification    5.  operator-defined descriptive text   d. audible alert	99-0729	08/25/1999  	No Data	
208	ESN-0800	Complete	The ECS shall be capable of displaying  the local network configuration status related to each system locally, and for all systems at the SMC.	3258	C-MSS-68000	IR1	The MSS performance management application service shall be capable of graphically displaying the operational state of managed objects through the MUI service.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3142	C-MSS-60010	IR1	The MSS Fault Management Application Service shall provide the capability to create and display graphical representations of a given network topology consisting of the following:    a. routers   b. communication lines   c. hosts   d. peripherals   e. applications	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3146	C-MSS-60020	IR1	The MSS Fault Management Application Service shall provide the capability to define categories of faults.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3147	C-MSS-60030	B0	The MSS Fault Management Application Service shall provide the capability to assign faults to categories.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3148	C-MSS-60040	B0	The MSS Fault Management Application Service shall provide the capability to assign severity levels to faults.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3149	C-MSS-60050	B0	The MSS Fault Management Application Service shall be capable of specifying whether to enable or disable the logging of fault notifications for each fault category.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3150	C-MSS-60060	B0	The MSS Fault Management Application Service shall provide the capability to enable or disable the display of fault notifications received from a specific managed object based on fault category assigned to that fault.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3151	C-MSS-60070	B0	MSS shall provide the capability to log fault specific information based on fault category, when the fault is detected.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3153	C-MSS-60100	IR1	The MSS Fault Management Application Service shall have the capability to poll for the detection of fault/performance information.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3154	C-MSS-60110	IR1	The MSS Fault Management Application Service shall be capable of receiving fault notifications.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3155	C-MSS-60120	IR1	The MSS Fault Management Application Service shall have the capability to define the frequency with which polling is done for the detection of fault/performance information.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3158	C-MSS-60150	IR1	The MSS Fault Management Application Service shall have the capability to receive fault notifications from the Management Agent Service.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3164	C-MSS-60200	IR1	The MSS Fault Management Application Service shall have the capability to generate the following types of notifications for detected faults :   a. a change in the color of an icon on a display   b. a message in a pop-up notification window   c. logging the following fault information to a disk log file:    1.  fault type    2.  date and time of occurrence of the fault    3.  identification of the source of the notification (e.g. IP address, process name, etc.)    4.  fault data received with the notification    5.  operator-defined descriptive text   d. audible alert	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3178	C-MSS-60300	B0	The MSS Fault Management Application Service shall provide the capability to verify connectivity between selected pairs of hosts on the ESN.	99-0729	08/25/1999  	No Data	
209	ESN-0810	Complete	The ECS shall provide the following fault management functions:  a. Detect the occurrence of  faults, and  b. Control the collection of fault information	3179	C-MSS-60301	B0	The MSS Fault Management Application Service shall provide the capability to identify routes between selected pairs of hosts on the EBnet.	99-0729	08/25/1999  	No Data	
210	ESN-0815	Complete	The ECS shall provide a network analyzer capability to troubleshoot network problems and to use in network planning.	3204	C-MSS-66001	B0	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components      a. network components         1.  routers         2.  links         3.  bridges         4.  gateways      b. hosts      c. operating systems      d. peripherals      e. databases     f. ECS applications.	99-0729	08/25/1999  	No Data	
210	ESN-0815	Complete	The ECS shall provide a network analyzer capability to troubleshoot network problems and to use in network planning.	3228	C-MSS-66171	B0	The MSS performance management application service shall log ECS performance data pertaining to ECS network components, ECS applications and operating system resources.	99-0729	08/25/1999  	No Data	
210	ESN-0815	Complete	The ECS shall provide a network analyzer capability to troubleshoot network problems and to use in network planning.	3271	C-MSS-69020	A	The MSS performance management application service shall be capable of performing operational benchmark tests.	99-0729	08/25/1999  	No Data	
210	ESN-0815	Complete	The ECS shall provide a network analyzer capability to troubleshoot network problems and to use in network planning.	3272	C-MSS-69030	A	The MSS performance management application service shall be capable of providing results of benchmark tests and results of predefined tests to the M&O staff for validation.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	889	C-CSS-10860	B0	The CSS DCCI shall have the capability to send detected hardware and software  fault information to MSS.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	890	C-CSS-10870	B0	The CSS DCCI shall have the capability to send event notification to MSS.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	989	C-CSS-28000	IR1	CSS Event Logger Service shall provide capability to record event and history data to a application specific log file.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	994	C-CSS-28040	IR1	CSS Event Logger Service shall accept and record the event type information. (Type of the event: fault, performance)	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2858	C-MSS-12080	IR1	The MSS MUI Service shall  provide a capability for applications to alert the M&O Staff	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2894	C-MSS-18280	B0	MSS shall have the capability to schedule the transfer of management data at the sites to the SMC.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2903	C-MSS-20010	IR1	The MSS Discovery Service shall discover (via network protocol) new instances of managed objects.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
211	ESN-0830	Complete	The ECS shall have the capability to detect and report communications related errors and events.	3166	C-MSS-60220	B0	The MSS Fault Management Application Service shall have the capability to send the notification of a fault to registered recipients.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	989	C-CSS-28000	IR1	CSS Event Logger Service shall provide capability to record event and history data to a application specific log file.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	990	C-CSS-28010	IR1	CSS Event Logger Service shall accept and record event time (when the event was generated, obtained from the Time Service) information.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	991	C-CSS-28020	IR1	CSS Event Logger Service shall accept and record the application information (name and version of the calling application).	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	992	C-CSS-28025	A	CSS Event Logger Service shall support predetermined event importance indicators that provide different levels of information on event severities in support of MSS Network Management and Reporting Services.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	993	C-CSS-28030	IR1	CSS Event Logger Service shall accept and record event message information.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	994	C-CSS-28040	IR1	CSS Event Logger Service shall accept and record the event type information. (Type of the event: fault, performance)	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	995	C-CSS-28070	IR1	CSS Event Logger Service shall record the operator/principle information that is relevant for the generated event.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	996	C-CSS-28080	IR1	CSS Event Logger Service shall record the environment information for the generated event.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2858	C-MSS-12080	IR1	The MSS MUI Service shall  provide a capability for applications to alert the M&O Staff	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2870	C-MSS-14040	IR1	The MSS Map/Collection Service shall propagate events associated with objects up the hierarchical tree	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2871	C-MSS-16005	IR1	The ECS management protocol shall be the SNMP standard as specified in RFC 1157.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2904	C-MSS-20020	IR1	The MSS Discovery Service shall detect missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	2923	C-MSS-36110	B0	The MSS Management Agent Service shall provide an ECS master agent to coordinate and communicate with multiple ECS management subagents.	99-0729	08/25/1999  	No Data	
212	ESN-0840	Complete	The ECS shall have communications error reporting, event logging and generation of alerts.	3164	C-MSS-60200	IR1	The MSS Fault Management Application Service shall have the capability to generate the following types of notifications for detected faults :   a. a change in the color of an icon on a display   b. a message in a pop-up notification window   c. logging the following fault information to a disk log file:    1.  fault type    2.  date and time of occurrence of the fault    3.  identification of the source of the notification (e.g. IP address, process name, etc.)    4.  fault data received with the notification    5.  operator-defined descriptive text   d. audible alert	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	990	C-CSS-28010	IR1	CSS Event Logger Service shall accept and record event time (when the event was generated, obtained from the Time Service) information.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	992	C-CSS-28025	A	CSS Event Logger Service shall support predetermined event importance indicators that provide different levels of information on event severities in support of MSS Network Management and Reporting Services.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	993	C-CSS-28030	IR1	CSS Event Logger Service shall accept and record event message information.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	994	C-CSS-28040	IR1	CSS Event Logger Service shall accept and record the event type information. (Type of the event: fault, performance)	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	995	C-CSS-28070	IR1	CSS Event Logger Service shall record the operator/principle information that is relevant for the generated event.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	996	C-CSS-28080	IR1	CSS Event Logger Service shall record the environment information for the generated event.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2858	C-MSS-12080	IR1	The MSS MUI Service shall  provide a capability for applications to alert the M&O Staff	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2859	C-MSS-12090	IR1	The MSS MUI Service shall  provide a capability for applications to establish a dialog session with the M&O Staff	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2864	C-MSS-12140	IR1	The MSS MUI Service shall provide the capability for an application to register and unregister managed objects.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2866	C-MSS-12180	IR1	The MSS MUI Service shall provide the capability for an application to display on-line help windows	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
213	ESN-0900	Complete	The ECS shall detect the following errors and events:  a. Communications hardware errors  b. Protocol errors  c. Performance degradation conditions  d. Telecommunications errors and failures	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	989	C-CSS-28000	IR1	CSS Event Logger Service shall provide capability to record event and history data to a application specific log file.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	990	C-CSS-28010	IR1	CSS Event Logger Service shall accept and record event time (when the event was generated, obtained from the Time Service) information.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	991	C-CSS-28020	IR1	CSS Event Logger Service shall accept and record the application information (name and version of the calling application).	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	992	C-CSS-28025	A	CSS Event Logger Service shall support predetermined event importance indicators that provide different levels of information on event severities in support of MSS Network Management and Reporting Services.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	993	C-CSS-28030	IR1	CSS Event Logger Service shall accept and record event message information.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	994	C-CSS-28040	IR1	CSS Event Logger Service shall accept and record the event type information. (Type of the event: fault, performance)	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	995	C-CSS-28070	IR1	CSS Event Logger Service shall record the operator/principle information that is relevant for the generated event.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	996	C-CSS-28080	IR1	CSS Event Logger Service shall record the environment information for the generated event.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2852	C-MSS-12020	IR1	The MSS  MUI Service shall have the capability to respond to  keyboard and mouse input devices	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2853	C-MSS-12030	IR1	The MSS MUI Service shall provide a capability for the M&O Staff to add/delete a symbol and to modify a symbol's shape, color and position	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2854	C-MSS-12040	IR1	The MSS MUI Service shall provide a capability for an application to add/delete a symbol and to modify a symbol's shape, color and position	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2855	C-MSS-12050	IR1	The MSS MUI Service shall provide a capability for the M&O Staff to add, delete, and modify text strings	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2856	C-MSS-12060	IR1	The MSS MUI Service shall provide a capability for an application to add, delete, and modify text strings	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2857	C-MSS-12070	IR1	The MSS MUI Service shall have the capability to provide options and methods to the M&O Staff for screen configuration changes (color, symbol placement, etc) and for retaining the changes from session to session	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2858	C-MSS-12080	IR1	The MSS MUI Service shall  provide a capability for applications to alert the M&O Staff	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2859	C-MSS-12090	IR1	The MSS MUI Service shall  provide a capability for applications to establish a dialog session with the M&O Staff	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2860	C-MSS-12100	IR1	The MSS MUI Service shall provide a capability for the M&O Staff to load and unload vendor or ECS defined MIB.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2861	C-MSS-12110	IR1	The MSS MUI Service shall provide a capability for applications to load and unload vendor or ECS defined MIB.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2862	C-MSS-12120	IR1	The MSS MUI Service shall provide a capability for the operator to browse MIB values.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2863	C-MSS-12130	IR1	The MSS MUI Service shall provide the capability for the M&O Staff to register and unregister managed objects.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2864	C-MSS-12140	IR1	The MSS MUI Service shall provide the capability for an application to register and unregister managed objects.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2866	C-MSS-12180	IR1	The MSS MUI Service shall provide the capability for an application to display on-line help windows	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2890	C-MSS-18200	B0	The MSS shall provide the capability for an application via APIs to log event information.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2891	C-MSS-18220	A	MSS shall provide the capability for an application via APIs to alter tables and fields in the management database.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2892	C-MSS-18260	B0	The MSS Management Data Access Service shall have the capability to schedule the transfer and loading log files into the management database at the site.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2893	C-MSS-18270	B0	The MSS Management Data Access Service shall have the capability to schedule the archiving of log files at the site.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2894	C-MSS-18280	B0	MSS shall have the capability to schedule the transfer of management data at the sites to the SMC.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	3149	C-MSS-60050	B0	The MSS Fault Management Application Service shall be capable of specifying whether to enable or disable the logging of fault notifications for each fault category.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	3150	C-MSS-60060	B0	The MSS Fault Management Application Service shall provide the capability to enable or disable the display of fault notifications received from a specific managed object based on fault category assigned to that fault.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	3152	C-MSS-60080	IR1	The MSS Fault Management Application Service shall have the capability to establish, view, modify and delete thresholds on performance metrics it measures.	99-0729	08/25/1999  	No Data	
214	ESN-0910	Complete	The ECS communications fault management shall provide the capability to perform the following functions both locally and at the SMC:  a. Set, view, and change alert threshold values  b. Enable and disable alert notifications (alarms) within a system  c. Enable and disable event reports within a system  d. Manage error and event logging files	3156	C-MSS-60130	IR1	The MSS Fault Management Application Service shall provide the capability to detect the following types of faults, errors and events:   a. communications software version mismatch errors   b. communication software configuration errors   c. the following errors in communications:    1.  host not reachable    2.  router not reachable    3. errors and failures of communication links   d. Errors in the communications protocols supported     e. degradation of performance due to established thresholds being exceeded   f. Peripherals   g. Databases   h. Applications:    1.  process missing (Application or COTS product)    2.  process in a loop    3.  process failed	99-0729	08/25/1999  	No Data	
215	ESN-0920	Complete	The ECS shall provide a set of utilities to perform diagnostic and testing functions for purposes of communications fault isolation.	3182	C-MSS-60310	IR1	The MSS Fault Management Application Service shall provide utilities to perform diagnostics and testing of the following for the purpose of fault isolation:   a. connectivity between pairs of ECS hosts and ECS routers   b. ability to reach hosts and routers   c. availability of network services at hosts	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	966	C-CSS-25010	A	The CSS Time Service shall adjust the time kept by the operating system at every node.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	967	C-CSS-25020	A	The CSS Time Service shall provide the functionality to obtain timestamps that are based on Coordinated Universal Time (UTC).	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	968	C-CSS-25030	A	The CSS Time Service shall provide an API to retrieve timestamp information.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	969	C-CSS-25040	A	The CSS Time Service shall provide an API for converting between binary timestamps that use different time structures.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	970	C-CSS-25050	A	The CSS Time Service shall provide an API for converting between binary timestamps and ASCII representations.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	971	C-CSS-25060	A	The CSS Time Service shall provide an API for converting between UTC time and local time.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	972	C-CSS-25070	A	The CSS Time Service shall provide an API for manipulating binary timestamps.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	973	C-CSS-25080	A	The CSS Time Service shall provide an API for comparing two binary time values.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	974	C-CSS-25090	A	The CSS Time Service shall provide an API for calculating binary time values.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	975	C-CSS-25100	A	The CSS Time Service shall provide an API for obtaining time zone information.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	976	C-CSS-25110	A	The CSS Time Service shall utilize a UTC based time provider.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	977	C-CSS-25120	A	The CSS Time Service shall provide the utilities required to synchronize system time across all components.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	978	C-CSS-25130	A	The CSS Time Service shall have the capability to synchronize its time to one or more external time sources.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	979	C-CSS-25140	A	The CSS Time Service shall maintain an accuracy of 500 milliseconds within all ECS distributed components.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	980	C-CSS-25155	A	The CSS TIME service shall provide a simulated time value based on a delta time value and the current absolute time.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	981	C-CSS-25165	A	The CSS time service shall provide a simulated time given an absolute time value	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	983	C-CSS-25175	A	The CSS time service shall accept delta or absolute time value to be used for simulated time from the cell directory service or a string	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	984	C-CSS-25180	A	The CSS time service shall provide an API for obtaining the current time.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	990	C-CSS-28010	IR1	CSS Event Logger Service shall accept and record event time (when the event was generated, obtained from the Time Service) information.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	991	C-CSS-28020	IR1	CSS Event Logger Service shall accept and record the application information (name and version of the calling application).	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	992	C-CSS-28025	A	CSS Event Logger Service shall support predetermined event importance indicators that provide different levels of information on event severities in support of MSS Network Management and Reporting Services.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	993	C-CSS-28030	IR1	CSS Event Logger Service shall accept and record event message information.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	994	C-CSS-28040	IR1	CSS Event Logger Service shall accept and record the event type information. (Type of the event: fault, performance)	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	995	C-CSS-28070	IR1	CSS Event Logger Service shall record the operator/principle information that is relevant for the generated event.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	996	C-CSS-28080	IR1	CSS Event Logger Service shall record the environment information for the generated event.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	2886	C-MSS-18060	B0	The Management Data Access Service shall provide the capability for an operator to access management data via a log browser.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	2887	C-MSS-18070	B0	The MSS Management Data Access Service shall provide the capability to selectively access management data.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	2888	C-MSS-18072	B1	The MSS Management Data Access Service shall have the capability to chain management events to their ancestor management events.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	2889	C-MSS-18074	B1	The MSS Management Data Access Service event chaining tool shall provide user access via the MDA user interface.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	2896	C-MSS-18340	B0	The MSS Management Data Access Service shall provide the capability for an operator to selectively read a record from a log file	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	3202	C-MSS-60610	B0	The MSS Fault Management Application Service shall have the capability to build histories for different types of errors and events detected, for the purpose of analysis.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	3230	C-MSS-66181	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of system errors and events for system analysis and trending.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	3231	C-MSS-66182	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of operational status, performance of resources and maintenance activities for system analysis and trending.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	3273	C-MSS-69100	B1	The MSS Performance Trending Service shall have the capability to save and retrieve data from the management database for long and short term trending.	99-0729	08/25/1999  	No Data	
216	ESN-1000	Complete	The ECS network management function shall have the capability to build histories for different types of errors and events, and the capability to analyze errors and recommend corrective action wherever practical.	3277	C-MSS-69150	B1	The MSS Performance Trending Service shall have the capability to perform short and long term trending by system, site and element.	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	2754	C-ISS-02200	B0	The ISS-INHW CI LAN Analysis Equipment shall provide protocol analysis through the transport layer for all ISS LAN protocols and interconnection protocols to MANs/WANs.	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	2755	C-ISS-02210	B0	The ISS-INHW CI LAN Analysis Equipment shall include a Communications line monitor.	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	2756	C-ISS-02220	B0	The ISS-INHW CI communications line monitor shall  store and display up to 10,000 bytes of data sent and received over any of the communications lines at rates of 10Mbits/sec to 100Mbits/sec.	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	2757	C-ISS-02230	B0	The ISS-INHW CI communications line monitor shall  support the protocols used within and interconnecting the ECS.	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	2758	C-ISS-02250	B0	The ISS-INHW CI LAN Analysis Equipment shall have the capability to analyze IP, Internet, and FDDI packet.	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	2879	C-MSS-16100	IR1	The MSS Monitor/Control Service shall perform the following protocol test on managed network nodes:  a. IP test  b. TCP test  c. SNMP test  d. UDP test  e. ICMP test	99-0729	08/25/1999  	No Data	
217	ESN-1010	Complete	The ECS shall provide, for selective use as a debugging aid, the capability to perform packet tracing of its supported protocols.	3183	C-MSS-60320	B0	The MSS Fault Management Application Service shall provide, for selective use as a debugging aid, the capability to perform packet tracing of protocols used in ECS.	99-0729	08/25/1999  	No Data	
218	ESN-1030	Complete	The ECS shall  perform periodic testing of  alternate communication  capabilities to verify that they are operational.	2879	C-MSS-16100	IR1	The MSS Monitor/Control Service shall perform the following protocol test on managed network nodes:  a. IP test  b. TCP test  c. SNMP test  d. UDP test  e. ICMP test	99-0729	08/25/1999  	No Data	
218	ESN-1030	Complete	The ECS shall  perform periodic testing of  alternate communication  capabilities to verify that they are operational.	3184	C-MSS-60330	B0	The MSS Fault Management Application Service at each site shall have the capability to perform periodic testing of all ECS communication links at that site to verify that they are operational.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	3219	C-MSS-66121	B0	The MSS performance management application service shall be capable of determining the operational state of all network components, hosts, and peripherals to be:      a. on-line      b. off-line      c. in test mode      d. In maintenance,      e. in simulation mode.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	3220	C-MSS-66130	IR1	The MSS performance management application service shall be capable of receiving operational state change notifications from network components, hosts, applications, and peripherals.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	3233	C-MSS-66190	IR1	The MSS performance management application service shall provide a configurable number of thresholds for each performance metric.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	3234	C-MSS-66200	IR1	The MSS EMC performance management application service shall be capable of creating a list of suggested initial threshold values for each performance metric.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	3237	C-MSS-66230	IR1	The MSS performance management application service shall allow each performance metric threshold to be configurable.	99-0729	08/25/1999  	No Data	
219	ESN-1060	Complete	The ECS network performance management function shall provide the capability to evaluate the performance of ECS networks  resources and interconnection activities.	3238	C-MSS-66240	IR1	The MSS performance management application service shall be capable of evaluating each performance metric against defined thresholds.	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3256	C-MSS-67000	B0	The MSS performance management application service shall be capable of extracting values of performance metrics gathered for a specified managed objects over a configurable period of time from the Management Database.	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3257	C-MSS-67010	B0	The MSS performance management application service shall be capable of generating a graph of the extracted performance metric values.	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3273	C-MSS-69100	B1	The MSS Performance Trending Service shall have the capability to save and retrieve data from the management database for long and short term trending.	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3274	C-MSS-69105	B1	The MSS Performance Trending Service shall have the capability to generate the following types of trend analysis:  a. time series analysis  b. analysis of variance including multiple analysis of variance  c. correlation analysis  d. regression analysis including non-linear and multiple regression	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3275	C-MSS-69110	B1	The MSS Performance Trending Service shall provide the capability to select parameters for trend analysis.	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3276	C-MSS-69120	B1	The MSS Performance Trending Service shall have the capability to output trend data in textual and graphical formats.	99-0729	08/25/1999  	No Data	
220	ESN-1065	Completel	The ECS network performance management function shall include trend analysis for prediction of loading and bottlenecks/delays.	3277	C-MSS-69150	B1	The MSS Performance Trending Service shall have the capability to perform short and long term trending by system, site and element.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2850	C-MSS-12005	IR1	The MSS Management User Interface (MUI) Service shall be compatible with the ECS management framework.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2851	C-MSS-12010	IR1	The MSS Management User Interface (MUI) Service shall provide a graphical user interface that is OSF/MOTIF compliant	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2887	C-MSS-18070	B0	The MSS Management Data Access Service shall provide the capability to selectively access management data.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2896	C-MSS-18340	B0	The MSS Management Data Access Service shall provide the capability for an operator to selectively read a record from a log file	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2897	C-MSS-18350	B0	The MSS Management Data Access Service shall provide the capability to load log files into the management database at the site.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2907	C-MSS-36010	IR1	The MSS Management Agent Service shall retrieve data from ECS managed objects in test or operational mode.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2920	C-MSS-36080	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS Host systems	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2922	C-MSS-36100	B0	The MSS Management Agent Service shall provide proxy agents for ECS network devices and applications that cannot be managed via SNMP.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	2923	C-MSS-36110	B0	The MSS Management Agent Service shall provide an ECS master agent to coordinate and communicate with multiple ECS management subagents.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3229	C-MSS-66180	IR1	The MSS performance management application service shall have the capability to generate the following types of statistics for a configurable period of time for performance data stored in the Management Database:  a. average  b. median  c. maximum  d. minimum  e. ratios  f. rates  g. standard deviations.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3239	C-MSS-66250	IR1	The MSS performance management application service shall record an event in the local History Log whenever a threshold is crossed.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3240	C-MSS-66260	IR1	The MSS performance management application service shall provide queries that generate performance statistics from performance data stored in the Management Database.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3241	C-MSS-66270	IR1	The MSS performance management application service shall store generated performance statistics.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3259	C-MSS-68010	IR1	The MSS performance management application service shall be capable of displaying M&O staff-selected performance statistics through the MUI in tabular and graphical formats.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3260	C-MSS-68020	IR1	The MSS performance management application service shall be capable of printing M&O staff-selected performance statistics.	99-0729	08/25/1999  	No Data	
221	ESN-1070	Complete	The ECS shall provide the capability to perform the following functions:  a. Generate/collect network statistics  b. Control collection/generation of network statistics	3369	C-MSS-90080	B0	The DBMS shall support mathematical operations to generate statistics from management data to include:  a. average  b. maximum  c. minimum  d. sum  e. count	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2871	C-MSS-16005	IR1	The ECS management protocol shall be the SNMP standard as specified in RFC 1157.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2907	C-MSS-36010	IR1	The MSS Management Agent Service shall retrieve data from ECS managed objects in test or operational mode.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	2919	C-MSS-36070	IR1	The MSS Management Agent Service shall provide an ECS management agent for network devices	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	3233	C-MSS-66190	IR1	The MSS performance management application service shall provide a configurable number of thresholds for each performance metric.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	3237	C-MSS-66230	IR1	The MSS performance management application service shall allow each performance metric threshold to be configurable.	99-0729	08/25/1999  	No Data	
222	ESN-1090	Complete	The ECS shall provide the capability to control the communications performance parameters of the network.	3238	C-MSS-66240	IR1	The MSS performance management application service shall be capable of evaluating each performance metric against defined thresholds.	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2729	C-ISS-01080	IR1	The ISS shall reuse the V0 WAN and LAN links in order to provide connectivity between V0 network nodes and V1 network nodes and to provide interoperability between the systems.	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2751	C-ISS-02060	IR1	The ISS shall provide network layer services in compliance with one or more of the following  protocols as appropriate to the type of the physical network supported.  a. IP over Ethernet as specified in RFCs 894, 895, 826 (ARP), 903 (RARP)  b. IP over FDDI as specified in RFC 1188, 1390 (ARP, RARP)  c. IP over HiPPI as specified in RFC 1374 (includes ARP, RARP)  	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2769	C-ISS-02520	IR1	The ISS shall provide services based on the Open Shortest Path First (OSPF) protocol referenced in RFC 1583 to route traffic between the source and destination nodes, maintain route databases, and exchange routing information between networks.	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2770	C-ISS-02522	B0	The ISS shall have the capability to provide services based on the Border Gateway Protocol-4 (BGP-4) referenced in RFC 1583 to route traffic between the source and destination nodes, maintain route databases, and exchange routing information between networks.	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2771	C-ISS-02524	B0	The ISS shall have the capability to provide protocol bridging services between network segments.	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2772	C-ISS-02526	B0	The ISS shall provide protocol termination services in network devices.	99-0729	08/25/1999  	No Data	
223	ESN-1140	Complete	The ECS shall provide protocol translation, termination, bridging and routing.	2773	C-ISS-02530	IR1	The ISS shall provide services based on the Routing Information Protocol (RIP) referenced in RFC  1058 to route network traffic between the source and destination nodes.	99-0729	08/25/1999  	No Data	
224	ESN-1170	Complete	The ECS shall provide necessary translation within supported file transfer.	1094	C-CSS-60520	IR1	The CSS File Access Service shall support the File Transfer Protocol (FTP).	99-0729	08/25/1999  	No Data	
224	ESN-1170	Complete	The ECS shall provide necessary translation within supported file transfer.	1112	C-CSS-61040	IR1	The CSS Electronic Mail Service shall provide translation between SMTP and X.400 protocol.	99-0729	08/25/1999  	No Data	
225	ESN-1180	Complete	The ECS shall interoperate with ESSn to provide user access to ECS.	2795	C-ISS-11020	B0	The ISS shall interface with NSI at GSFC, LaRC, EDC, and NSIDC to provide DAAC access to science users in accordance with current document "Interface Requirements Document between EOSDIS Core System (ECS) and the NASA Science Internet (NSI), 505-41-17".	99-0729	08/25/1999  	No Data	
225	ESN-1180	Complete	The ECS shall interoperate with ESSn to provide user access to ECS.	2820	C-ISS-21020	B1	The ISS shall interface with NSI at JPL and ORNL to provide DAAC access to science users in accordance with current document "Interface Requirements Document between EOSDIS Core System (ECS) and the NASA Science Internet (NSI), 505-41-17".	99-0729	08/25/1999  	No Data	
226	ESN-1206	Complete	The ECS network capacity and performance shall be consistent with the specified capacity and performance requirements of the ECS functions.	2764	C-ISS-02390	B0	The ISS-INHW CI LANs at the DAAC sites shall be designed in a manner that allows a. Nodes to be added to any given LAN segment. b. Additional LAN segments to be added to the LAN.	99-0729	08/25/1999  	No Data	
226	ESN-1206	Complete	The ECS network capacity and performance shall be consistent with the specified capacity and performance requirements of the ECS functions.	2766	C-ISS-02410	B	The ISS-INHW CI EOC Operational LAN shall be able to support peak data rates of up to 48 Mbps without redesign.	99-0729	08/25/1999  	No Data	
226	ESN-1206	Complete	The ECS network capacity and performance shall be consistent with the specified capacity and performance requirements of the ECS functions.	2806	C-ISS-20050	B1	The ISS shall provide sufficient local area network bandwidth at the JPL DAAC to support data transfer between and among physical nodes provided in accordance with the Release B network I/O sizing listed in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2 and A-3).	99-0729	08/25/1999  	No Data	
226	ESN-1206	Complete	The ECS network capacity and performance shall be consistent with the specified capacity and performance requirements of the ECS functions.	2807	C-ISS-20070	B1	The ISS shall provide sufficient local area network bandwidth at the ORNL DAAC to support data transfer between and among physical nodes in accordance with the  Release B network I/O sizing listed in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2 and A-3).	99-0729	08/25/1999  	No Data	
226	ESN-1206	Complete	The ECS network capacity and performance shall be consistent with the specified capacity and performance requirements of the ECS functions.	2808	C-ISS-20080	B0	The ISS shall provide sufficient local area network bandwidth at the NSIDC DAAC to support data transfer between and among physical nodes in accordance with the Release B network sizing listed in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2 and A-3).	99-0729	08/25/1999  	No Data	
226	ESN-1206	Complete	The ECS network capacity and performance shall be consistent with the specified capacity and performance requirements of the ECS functions.	2818	C-ISS-20190	B0	The ISS-INHW CI shall contribute to the response time and performance requirements specified in Reference Table:  A/B Service Performance Response Time Budgets by Subsystem (Table E-8.2).	99-0729	08/25/1999  	No Data	
227	ESN-1207	Complete	The ECS network capacity and performance shall be capable of expansion to be consistent with the specified capacity and performance growth requirements of the ECS functions.	2765	C-ISS-02400	B	The ISS-INHW CI EOC Operational LAN shall be able to support 230 network devices without redesign.	99-0729	08/25/1999  	No Data	
227	ESN-1207	Complete	The ECS network capacity and performance shall be capable of expansion to be consistent with the specified capacity and performance growth requirements of the ECS functions.	2809	C-ISS-20090	B0	The ISS LANs at the GSFC, GSFC EOC, GSFC SMC, EDC, LaRC, and NSIDC DAACs shall be capable of supporting twice the R-B network traffic load estimates without redesign.	99-0729	08/25/1999  	No Data	
227	ESN-1207	Complete	The ECS network capacity and performance shall be capable of expansion to be consistent with the specified capacity and performance growth requirements of the ECS functions.	2810	C-ISS-20095	B1	The ISS LANs at JPL and ORNL DAACs shall be capable of supporting twice the R-B network traffic load estimates without redesign.	99-0729	08/25/1999  	No Data	
227	ESN-1207	Complete	The ECS network capacity and performance shall be capable of expansion to be consistent with the specified capacity and performance growth requirements of the ECS functions.	2811	C-ISS-20100	B0	The ISS LANs shall be designed in a manner that allows  a. Nodes to be added to any given LAN segment.; b. Additional LAN segments to be added to the LAN.	99-0729	08/25/1999  	No Data	
227	ESN-1207	Complete	The ECS network capacity and performance shall be capable of expansion to be consistent with the specified capacity and performance growth requirements of the ECS functions.	2818	C-ISS-20190	B0	The ISS-INHW CI shall contribute to the response time and performance requirements specified in Reference Table:  A/B Service Performance Response Time Budgets by Subsystem (Table E-8.2).	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2745	C-ISS-02000	IR1	The ISS shall provide connection oriented transport services as specified by the TCP protocol referenced in RFC 793.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2747	C-ISS-02020	IR1	The ISS shall provide connectionless transport services as specified by the UDP protocol referenced in RFC 768.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2748	C-ISS-02030	IR1	The ISS shall provide network layer services as specified by the Internet Protocol (IP) suite referenced in RFC 791.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2750	C-ISS-02050	IR1	The ISS shall provide ICMP network layer service as specified by RFC 792.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2751	C-ISS-02060	IR1	The ISS shall provide network layer services in compliance with one or more of the following  protocols as appropriate to the type of the physical network supported.  a. IP over Ethernet as specified in RFCs 894, 895, 826 (ARP), 903 (RARP)  b. IP over FDDI as specified in RFC 1188, 1390 (ARP, RARP)  c. IP over HiPPI as specified in RFC 1374 (includes ARP, RARP)  	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2757	C-ISS-02230	B0	The ISS-INHW CI communications line monitor shall  support the protocols used within and interconnecting the ECS.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2769	C-ISS-02520	IR1	The ISS shall provide services based on the Open Shortest Path First (OSPF) protocol referenced in RFC 1583 to route traffic between the source and destination nodes, maintain route databases, and exchange routing information between networks.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2770	C-ISS-02522	B0	The ISS shall have the capability to provide services based on the Border Gateway Protocol-4 (BGP-4) referenced in RFC 1583 to route traffic between the source and destination nodes, maintain route databases, and exchange routing information between networks.	99-0729	08/25/1999  	No Data	
228	ESN-1340	Complete	The ECS shall provide support for TCP/IP communications protocols and services to external interfaces as required by the IRDs.	2773	C-ISS-02530	IR1	The ISS shall provide services based on the Routing Information Protocol (RIP) referenced in RFC  1058 to route network traffic between the source and destination nodes.	99-0729	08/25/1999  	No Data	
229	ESN-1350	Complete	The ECS LANs shall provide physical devices and the corresponding medium access control (MAC) protocol compatible with ISO and ANSI standards.	2752	C-ISS-02100	B0	The ISS-INHW CI  shall use physical devices and Medium Access Control protocols compatible with the following standards: a. IEEE 802.2 (Logical Link Control) b. IEEE 802.3 (MAC for Ethernet) c.  ANSI X3.183, X3.210, X3.218, X3.222 (HiPPI) d. ANSI X3T9.5 (MAC for FDDI).	99-0729	08/25/1999  	No Data	
229	ESN-1350	Complete	The ECS LANs shall provide physical devices and the corresponding medium access control (MAC) protocol compatible with ISO and ANSI standards.	2757	C-ISS-02230	B0	The ISS-INHW CI communications line monitor shall  support the protocols used within and interconnecting the ECS.	99-0729	08/25/1999  	No Data	
229	ESN-1350	Complete	The ECS LANs shall provide physical devices and the corresponding medium access control (MAC) protocol compatible with ISO and ANSI standards.	2758	C-ISS-02250	B0	The ISS-INHW CI LAN Analysis Equipment shall have the capability to analyze IP, Internet, and FDDI packet.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	913	C-CSS-21010	A	The CSS Security service shall not transmit its authentication information in clear text across networks.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	914	C-CSS-21020	IR1	The CSS Security service shall provide the capability to create/modify/delete user accounts and privileges in the security registry.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	915	C-CSS-21030	IR1	The CSS Security service shall provide the capability to define/modify/delete group information in the security registry.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	918	C-CSS-21060	A	The CSS Security Service shall provide an API to accept server keys (i.e. passwords) associated with services interactively at the startup of a service.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	919	C-CSS-21070	A	The CSS Security Service shall provide an API to store server keys associated with servers to a disk file.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	920	C-CSS-21080	A	The CSS Security Service shall provide an API to retrieve the server keys associated with services from a disk file at startup time to authenticate the service.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	922	C-CSS-21100	IR1	The CSS Security service shall provide an API to challenge the client/server to authenticate itself at the following three levels.  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	924	C-CSS-21110	A	The CSS Security service shall provide the functionality to authenticate the principal before checking whether the principal is authorized to access a service/resources.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	925	C-CSS-21120	A	The CSS Security service shall provide an API to check the authorization privileges of principals to access/control services/resources.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	926	C-CSS-21130	A	The CSS Security Service shall provide an API to define the permission schema associated with a server/resource.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	927	C-CSS-21140	A	The CSS Security Service shall provide an API to create and maintain the ACLs associated with the server/resource in a database.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	928	C-CSS-21150	A	The CSS Security Service shall provide an API to save/retrieve the ACL database onto persistent store.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	929	C-CSS-21160	A	The CSS Security service shall provide the following APIs to MSS security management applications to retrieve/modify the access control lists associated with the ECS services/resources.  a. to identify the permissions available to a principal  b. to identify all the ACL managers protecting an object  c. to get the printable representation of the permissions  d. to locate the server with the writable copy of the ACL  e. to read an ACL  f. to write an ACL  g. to test if the calling principal has some permissions  h. to test if another principal has some permissions.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	930	C-CSS-21170	A	The CSS Security service shall provide an API to maintain the integrity of the data passing between processes by using checksums at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	935	C-CSS-21222	B0	CSS shall provide authentication service to reference cell objects and processes, located within a remote DAAC cell.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	936	C-CSS-21223	B0	CSS shall provide authentication service to reference cell objects and processes, located within the SMC cell.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	937	C-CSS-21225	A	The CSS Security service shall provide a name based authorization capability.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	1005	C-CSS-30080	A	The Process Framework shall provide interfaces to the underlying distributed infrastructure to set the following security parameters:  a. Server principal name  b. Keytab file name  c. ACL database filename	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	2746	C-ISS-02010	IR1	The ISS shall provide the capability to filter packets based on the port/socket of the  transport layer protocol.	99-0729	08/25/1999  	No Data	
230	ESN-1380	Complete	The ECS shall provide countermeasures for the following security threats related to data communications:  a. Modification of data (i.e., manipulation) while in transit over the network  b. Disclosure of  authentication information  c. Impersonation of authentication credentials or authorization privileges.	2749	C-ISS-02040	A	The ISS shall provide the capability to filter packets based upon network layer source and/or destination addresses.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	822	C-CSS-01170	A	The CSS DOF Service shall provide APIs to set/get the authentication service type to be used between the server and the client.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	825	C-CSS-01200	A	The CSS DOF Service shall provide APIs to maintain the privacy of the data passed between the client and the server by encrypting and decrypting the data.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	826	C-CSS-01210	A	The CSS DOF Service shall provide APIs to set the identity of a given principal to a given process.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	832	C-CSS-01280	B0	The CSS Security Service shall provide for a security service ACL manager facility.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	864	C-CSS-10600	B0	The CSS DCCI shall accept User authentication request from CLS.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	866	C-CSS-10620	B0	The CSS DCCI shall provide User authentication response to CLS .	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	868	C-CSS-10640	B0	The CSS DCCI shall accept User authorization request from IOS.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	870	C-CSS-10660	B0	The CSS DCCI shall provide User authorization response to IOS .	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	872	C-CSS-10680	B0	The CSS DCCI shall accept User authorization request from DMS.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	874	C-CSS-10700	B0	The CSS DCCI shall provide User authorization response to DMS.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	905	C-CSS-20110	A	The CSS Directory service shall determine which naming service to use from a given context.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	912	C-CSS-21005	A	The CSS Security service shall provide the functionality to get a unique session key for each client session.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	913	C-CSS-21010	A	The CSS Security service shall not transmit its authentication information in clear text across networks.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	917	C-CSS-21050	A	The CSS Security Service shall provide an API to refresh login contexts before they expire.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	918	C-CSS-21060	A	The CSS Security Service shall provide an API to accept server keys (i.e. passwords) associated with services interactively at the startup of a service.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	919	C-CSS-21070	A	The CSS Security Service shall provide an API to store server keys associated with servers to a disk file.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	920	C-CSS-21080	A	The CSS Security Service shall provide an API to retrieve the server keys associated with services from a disk file at startup time to authenticate the service.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	921	C-CSS-21090	A	The CSS Security Service shall provide an API to change the identity of an application process through server keys.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	922	C-CSS-21100	IR1	The CSS Security service shall provide an API to challenge the client/server to authenticate itself at the following three levels.  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	923	C-CSS-21105	A	The CSS shall notify MSS upon the failure or success of each authentication request.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	924	C-CSS-21110	A	The CSS Security service shall provide the functionality to authenticate the principal before checking whether the principal is authorized to access a service/resources.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	925	C-CSS-21120	A	The CSS Security service shall provide an API to check the authorization privileges of principals to access/control services/resources.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	926	C-CSS-21130	A	The CSS Security Service shall provide an API to define the permission schema associated with a server/resource.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	927	C-CSS-21140	A	The CSS Security Service shall provide an API to create and maintain the ACLs associated with the server/resource in a database.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	928	C-CSS-21150	A	The CSS Security Service shall provide an API to save/retrieve the ACL database onto persistent store.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	929	C-CSS-21160	A	The CSS Security service shall provide the following APIs to MSS security management applications to retrieve/modify the access control lists associated with the ECS services/resources.  a. to identify the permissions available to a principal  b. to identify all the ACL managers protecting an object  c. to get the printable representation of the permissions  d. to locate the server with the writable copy of the ACL  e. to read an ACL  f. to write an ACL  g. to test if the calling principal has some permissions  h. to test if another principal has some permissions.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	930	C-CSS-21170	A	The CSS Security service shall provide an API to maintain the integrity of the data passing between processes by using checksums at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	931	C-CSS-21180	A	The CSS Security service shall provide an API to encrypt and send the data passing between processes at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	932	C-CSS-21190	A	The CSS Security service shall provide an API to receive and decrypt the data passing between processes at the following three levels:  a. connect level  b. request level  c. packet level	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	935	C-CSS-21222	B0	CSS shall provide authentication service to reference cell objects and processes, located within a remote DAAC cell.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	936	C-CSS-21223	B0	CSS shall provide authentication service to reference cell objects and processes, located within the SMC cell.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	937	C-CSS-21225	A	The CSS Security service shall provide a name based authorization capability.	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	1005	C-CSS-30080	A	The Process Framework shall provide interfaces to the underlying distributed infrastructure to set the following security parameters:  a. Server principal name  b. Keytab file name  c. ACL database filename	99-0729	08/25/1999  	No Data	
231	ESN-1400	5A Partial	The ECS shall provide the following security functions and services :  a. Authentication  b. Access (authorization) control  c. Data confidentiality	2767	C-ISS-02500	B0	The ISS-INHW CI networks shall support the use of network and transport layer filtering to control access from internal and external interfaces.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	989	C-CSS-28000	IR1	CSS Event Logger Service shall provide capability to record event and history data to a application specific log file.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	990	C-CSS-28010	IR1	CSS Event Logger Service shall accept and record event time (when the event was generated, obtained from the Time Service) information.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	991	C-CSS-28020	IR1	CSS Event Logger Service shall accept and record the application information (name and version of the calling application).	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	992	C-CSS-28025	A	CSS Event Logger Service shall support predetermined event importance indicators that provide different levels of information on event severities in support of MSS Network Management and Reporting Services.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	993	C-CSS-28030	IR1	CSS Event Logger Service shall accept and record event message information.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	994	C-CSS-28040	IR1	CSS Event Logger Service shall accept and record the event type information. (Type of the event: fault, performance)	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	995	C-CSS-28070	IR1	CSS Event Logger Service shall record the operator/principle information that is relevant for the generated event.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	996	C-CSS-28080	IR1	CSS Event Logger Service shall record the environment information for the generated event.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	2907	C-MSS-36010	IR1	The MSS Management Agent Service shall retrieve data from ECS managed objects in test or operational mode.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	2918	C-MSS-36060	IR1	The MSS Management Agent Service shall provide an ECS management agent that is configurable to include:  a. Community to respond to and set attributes  b. Agent location & contact person  c. Traps to send   d. Events to log & log file name	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	3282	C-MSS-70120	IR1	The MSS site Security Management Application service shall provide the mechanism, for each ECS host, to allow or deny incoming requests from specific hosts to services.	99-0729	08/25/1999  	No Data	
232	ESN-1430	Complete	The ECS shall provide the following security event functions:   a. Event detection    b. Event reporting   c. Event logging	3342	C-MSS-76030	B0	The MSS Accountability Management Service shall be capable of browsing, via the Management Data Access service, logged events, for each ECS host, indicating incoming access attempts via:  a.  telnet  b.  FTP  c.  rlogin  d.  finger.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	532	S-CLS-13370	A	The WKBCH CI shall provide users an interface for user authentication.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	533	S-CLS-13380	B1	 The WKBCH CI shall send User Authentication Requests to  the SMC.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	534	S-CLS-13390	B1	The WKBCH CI shall  allow or deny the user system access based on User Validation Status returned from the SMC.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	535	S-CLS-13400	B0	 The WKBCH CI shall obtain user authentication information from  the user.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	536	S-CLS-13410	A	The WKBCH CI shall display the results of user validation to the user if user validation is denied.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	934	C-CSS-21220	B0	The CSS Security Service shall provide a mechanism to authenticate client/server applications.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	937	C-CSS-21225	A	The CSS Security service shall provide a name based authorization capability.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1225	C-CSS-65010	B0	The MOJO Gateway shall perform authentication of a user using the DCE security service for login requests.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1226	C-CSS-65020	B0	The MOJO Gateway shall inform users of authentication failure or success via messages to the WKBCH CI.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1383	S-DMS-30395	Complete	The GTWAY CI shall receive authentication information with each request from the Version 0 Client using Version 0 protocols.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1401	S-DMS-31240	Complete	The GTWAY CI shall request user profile information from the MSS based on the authenticator information.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1452	S-DMS-42130	5B	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.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1453	S-DMS-42140	5B	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.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	1952	S-DSS-01425	B0	The SDSRV CI shall log, to the Event Log, those Service Requests that fail authorization, the service requested, and the identity of the requesting user.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	2688	S-IOS-00685	B1	The ADSRV CI shall validate user authorization requests with CSS.	99-0729	08/25/1999  	No Data	
233	IMS-0040	Complete	The ECS shall authenticate the  user.	3330	C-MSS-75130	B0	The Accountability Service shall have the capability to send user registration information to the CLS.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	4567	C-MSS-75440	5BP	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   	00-1097	11/22/2000  		
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	324	S-CLS-01615	A	The DESKT CI shall provide users the capability to set preferences (e.g. desired view, mode of opening container object, sort based on alphabetical, modification, size, type of object either in ascending or descending order, and confirmation for delete.)	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	473	S-CLS-12510	A	The WKBCH CI shall provide the user a capability to view their User Profile.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	474	S-CLS-12520	A	The WKBCH CI shall provide the capability for a user to  modify their User Profile information.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	535	S-CLS-13400	B0	 The WKBCH CI shall obtain user authentication information from  the user.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	538	S-CLS-13450	A	Where the User Profile specifies defaults for parameters which are applicable to an ECS Service Request, the user interface shall employ these defaults to assist the user in the formulation of a new request (e.g., by displaying them as default values).	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	541	S-CLS-13475	B0	The WKBCH CI shall provide capability for user to create a user preference that can house the following types of information:  user electronic address, data distribution media, data distribution address, user expertise level, default query parameters, terminal characteristics, and technical specialty.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	644	S-CLS-15900	B0	 The WKBCH CI shall support multiple addresses for product requests,  which include mailing address, billing address and shipping address.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	1260	C-CSS-65310	B0	The MOJO Gateway shall forward the user profile request to the MSS user profile server.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	1262	C-CSS-65330	B0	The MOJO Gateway shall send the user profile information and status  to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	1264	C-CSS-65350	B0	The MOJO Gateway shall forward the user profile update request to  the MSS user profile server.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	3313	C-MSS-75001	B0	The MSS accountability management service shall provide the capability to maintain a user profile database that stores the following information for each registered user:     a.  Name     b.  User ID     c.  Password information      1.  password      2.  password expiration date      d.  Assigned privileges     e.  Mailing address     f.  Telephone number     g.  Product shipping address     h.  E-mail address     i.  Organization (optional)   j.  Project affiliation(s) (optional)      1.  project name      2.  project principal investigator     k.  User group     l.  Account information      1.  creation date      2.  expiration date     m.  Restrictions      1.  time of day      2.  location      3.  type of service   n. Billing address   o. Payment method	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	3317	C-MSS-75025	B0	The MSS Accountability Management Service shall be capable of receiving requests for user profile data from ECS applications.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	3319	C-MSS-75035	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to ECS applications	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	3325	C-MSS-75105	B0	The  Accountability Service shall have the capability to receive user registration requests from the CLS.	99-0729	08/25/1999  	No Data	
234	IMS-0050	Complete	The ECS shall provide the capability for users to define and modify the following user profile   information:  a. User electronic address  b. Data distribution address  c. Technical specialty	3327	C-MSS-75115	B0	The Accountability Service shall have the capability to receive requests for user profile updates from the CLS.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4494	S-CLS-00500	5BP	The DESKT CI shall provide a capability to accept the ECS user registration message using protocols as defined in the ECS/V0 ICD.      	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4495	S-CLS-00505	5BP	The DESKT CI shall provide a capability to accept the ECS user password change message using protocols as defined in the ECS/V0 ICD.        	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4496	S-CLS-00510	5BP	The DESKT CI shall send the user registration message to the MCI user registration service using ECS protocols.      	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4497	S-CLS-00515	5BP	The DESKT CI shall send the user password change message to the MCI user registration service using ECS protocols.        	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4498	S-CLS-00520	5BP	The DESKT CI shall send the user registration result to the V0 EDG client using protocols as defined in the ECS/V0 ICD.      	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4499	S-CLS-00525	5BP	The DESKT CI shall send the user password change result to the V0 EDG client using protocols as defined in the ECS/V0 ICD.        	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4500	S-DMS-24098	5BP	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.        	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4501	C-MSS-75400	5BP	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.           	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4502	C-MSS-75405	5BP	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.              	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4503	C-MSS-75410	5BP	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.                	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4504	C-MSS-75415	5BP	Upon successful user registration, the MCI user registration service shall create a new user account with basic search and order privileges.            	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4505	C-MSS-75420	5BP	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.               	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4506	C-MSS-75425	5BP	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.           	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4507	C-MSS-75430	5BP	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.      	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	4508	C-MSS-75435	5BP	The MCI shall provide a capability to embed a DAAC-specific configurable preamble into the e-mail messages sent to the user.  	00-0662	06/26/2000  		
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	515	S-CLS-13090	B0	The WKBCH CI shall perform  registration of new users from user supplied and default information.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	516	S-CLS-13110	B0	The WKBCH CI shall provide registered  users  with the capability to view their user account priorities, and authorized user services.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	537	S-CLS-13420	A	The WKBCH CI shall provide a User Registration Request  to create a new ECS user account.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	686	S-CLS-18070	A	The WKBCH CI shall acquire request registration approval, user account priorities, and authorized user services from the MSS when new ECS users accounts are requested.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3313	C-MSS-75001	B0	The MSS accountability management service shall provide the capability to maintain a user profile database that stores the following information for each registered user:     a.  Name     b.  User ID     c.  Password information      1.  password      2.  password expiration date      d.  Assigned privileges     e.  Mailing address     f.  Telephone number     g.  Product shipping address     h.  E-mail address     i.  Organization (optional)   j.  Project affiliation(s) (optional)      1.  project name      2.  project principal investigator     k.  User group     l.  Account information      1.  creation date      2.  expiration date     m.  Restrictions      1.  time of day      2.  location      3.  type of service   n. Billing address   o. Payment method	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3314	C-MSS-75010	B0	The MSS accountability management service shall be capable of receiving user profile records entered by M&O personnel.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3315	C-MSS-75015	B0	The MSS accountability management service shall provide the capability for M&O Staff to modifying and delete user profile records.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3316	C-MSS-75020	B0	The MSS Accountability Management Service shall create a new user account whenever a new record is added to the user profile database.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3318	C-MSS-75030	B0	The MSS Accountability Management Service shall be capable of receiving requests for user profile data from M&O operators.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3319	C-MSS-75035	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to ECS applications	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3320	C-MSS-75040	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to M&O operators.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3322	C-MSS-75052	B0	The MSS shall provide the user with registration approval  results when new ECS user accounts are requested.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3325	C-MSS-75105	B0	The  Accountability Service shall have the capability to receive user registration requests from the CLS.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3328	C-MSS-75120	B0	The Accountability Service shall have the capability to receive user registration status requests from the CLS.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3330	C-MSS-75130	B0	The Accountability Service shall have the capability to send user registration information to the CLS.	99-0729	08/25/1999  	No Data	
235	IMS-0060	Complete	The ECS shall allow the user to request registration approval.	3331	C-MSS-75135	B0	The Accountability Service shall have the capability to send user registration status to the CLS.	99-0729	08/25/1999  	No Data	
236	IMS-0070	Complete	The ECS shall provide the user with initial system access procedures.	517	S-CLS-13115	B0	The WKBCH CI shall provide registered  users  with the capability  to request changes to their user account priorities and authorized user services.	99-0729	08/25/1999  	No Data	
236	IMS-0070	Complete	The ECS shall provide the user with initial system access procedures.	518	S-CLS-13120	A	The WKBCH CI shall provide users with initial system access procedures.	99-0729	08/25/1999  	No Data	
236	IMS-0070	Complete	The ECS shall provide the user with initial system access procedures.	519	S-CLS-13130	A	The WKBCH CI shall provide users Priority Information.	99-0729	08/25/1999  	No Data	
236	IMS-0070	Complete	The ECS shall provide the user with initial system access procedures.	655	S-CLS-16040	A	The WKBCH CI shall provide users with initial  authorized services.	99-0729	08/25/1999  	No Data	
236	IMS-0070	Complete	The ECS shall provide the user with initial system access procedures.	3313	C-MSS-75001	B0	The MSS accountability management service shall provide the capability to maintain a user profile database that stores the following information for each registered user:     a.  Name     b.  User ID     c.  Password information      1.  password      2.  password expiration date      d.  Assigned privileges     e.  Mailing address     f.  Telephone number     g.  Product shipping address     h.  E-mail address     i.  Organization (optional)   j.  Project affiliation(s) (optional)      1.  project name      2.  project principal investigator     k.  User group     l.  Account information      1.  creation date      2.  expiration date     m.  Restrictions      1.  time of day      2.  location      3.  type of service   n. Billing address   o. Payment method	99-0729	08/25/1999  	No Data	
237	IMS-0085	Complete	The ECS shall provide unregistered users access to unrestricted ECS services.	407	S-CLS-10670	A	The WKBCH CI shall provide unregistered users the capability to browse public Advertisements.	99-0729	08/25/1999  	No Data	
237	IMS-0085	Complete	The ECS shall provide unregistered users access to unrestricted ECS services.	656	S-CLS-16050	A	The WKBCH CI shall identify unregistered users to ECS as such when performing the DCE login using a DCE login identifier reserved for that purpose by the SMC.	99-0729	08/25/1999  	No Data	
238	IMS-0090	Complete	The ECS shall be accessible to users via  network link.	630	S-CLS-15710	A	The WKBCH CI shall provide users access to ECS services via a network link.	99-0729	08/25/1999  	No Data	
238	IMS-0090	Complete	The ECS shall be accessible to users via  network link.	804	C-CSS-00510	A	The CSS shall support a transparent RPC mechanism to provide access to ECS data and services to the clients at the DAACs and SCFs.	99-0729	08/25/1999  	No Data	
238	IMS-0090	Complete	The ECS shall be accessible to users via  network link.	2691	S-IOS-00730	A	The ADSRV CI shall allow advertisements of services that can be accessed via the WWW.	99-0729	08/25/1999  	No Data	
238	IMS-0090	Complete	The ECS shall be accessible to users via  network link.	2795	C-ISS-11020	B0	The ISS shall interface with NSI at GSFC, LaRC, EDC, and NSIDC to provide DAAC access to science users in accordance with current document "Interface Requirements Document between EOSDIS Core System (ECS) and the NASA Science Internet (NSI), 505-41-17".	99-0729	08/25/1999  	No Data	
238	IMS-0090	Complete	The ECS shall be accessible to users via  network link.	2820	C-ISS-21020	B1	The ISS shall interface with NSI at JPL and ORNL to provide DAAC access to science users in accordance with current document "Interface Requirements Document between EOSDIS Core System (ECS) and the NASA Science Internet (NSI), 505-41-17".	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	402	S-CLS-10630	B1	The WKBCH CI shall provide science users a Training Option that consists of simulated user sessions for identifying, searching for , and obtaining data and services.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	479	S-CLS-12570	B0	The WKBCH CI  shall provide users interactive user sessions.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	497	S-CLS-12860	B1	The WKBCH CI shall provide a Web interface with a command language.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	521	S-CLS-13170	B1	The WKBCH CI shall provide users the capability to initiate user sessions with service providers.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	522	S-CLS-13180	B1	The WKBCH CI shall provide users the capability to suspend user sessions with service providers.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	523	S-CLS-13190	B1	The WKBCH CI shall provide users the capability to resume suspended user sessions with service providers.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	526	S-CLS-13220	B0	The WKBCH CI shall provide users the capability to issue single sequential Service Requests within the context of a  user session.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	657	S-CLS-16080	A	The DESKT CI shall provide, but not limited to, prompts, dialog boxes, select lists, and information boxes to support interactive sessions.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	658	S-CLS-16085	A	The DESKT shall support a client-server interface.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	794	S-CLS-19300	5B	The WKBCH CI DAR Tool shall provide an HTML tutorial for training users in the  use of the DAR Tool.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	1228	C-CSS-65040	B0	The MOJO Gateway shall perform DCE logout on behalf of a user's logout request.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	1229	C-CSS-65050	B0	The MOJO Gateway shall perform automatic DCE logout of a user after a configurable period of idle time.	99-0729	08/25/1999  	No Data	
239	IMS-0100	Complete	The ECS shall support:  a. Interactive sessions  b. Simulated sessions for training purposes	1432	S-DMS-40900	5B	The ASTGW CI shall support multiple Service Requests.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	498	S-CLS-12870	B1	The WKBCH CI shall support a web interface that provides users system access from local and remote terminals.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	531	S-CLS-13300	B0	The WKBCH CI shall provide users the capability to access text information as plain text documents for  terminals.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	741	S-CLS-19184	B0	The WKBCH CI shall support a web interface that provides users system access through one of the following Web browsers that they have installed on their workstation or personal computer at a minimum:  a.  Netscape (Version 4.06)  b.  Microsoft Explorer (Version 4.X or higher)  	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	744	S-CLS-19190	4PY	The WKBCH CI shall send user requests to the MOJO Gateway as messages, which include:  a)  Length of message  b)  Session ID  c)  Request type  d)  Server UR  e)  Other data as required to process the request	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	750	S-CLS-19200	4PY	The WKBCH CI shall accept user request responses from the MOJO Gateway as messages, which include:  a)  Length of       message  b)  Session ID  c)  Request type  d) Result information (request dependent information, e.g., status/status code, notifications, error messages, or data ).	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	754	S-CLS-19205	5B	The WKBCH CI shall convert the MOJO Gateway  messages into information/data for user display.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1228	C-CSS-65040	B0	The MOJO Gateway shall perform DCE logout on behalf of a user's logout request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1231	C-CSS-65070	B0	The MOJO Gateway shall receive search requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., SEARCH)  d)  Server Universal Reference.  e)  other data as required by the SDSRV to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1235	C-CSS-65110	B0	The MOJO Gateway shall receive browse requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., BROWSE)  d)  A list of externalized Universal References for granules for which browse data is requested.  e)  other data as required by the SDSRV to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1239	C-CSS-65150	B0	The MOJO Gateway shall receive acquire requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., ACQUIRE)  d)  A list of externalized Universal References for granules to be acquired  e)  other data as required by the SDSRV to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1243	C-CSS-65180	B0	The MOJO Gateway shall receive order creation requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., ORDER or REQUEST)  d)  other data as required from the Order Tracking Server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1246	C-CSS-65197	B0	The MOJO Gateway shall send the order creation results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1247	C-CSS-65200	B0	The MOJO Gateway shall receive order status requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., ORDER STATUS)  d)  Other data as required from the Order Tracking Server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1250	C-CSS-65218	B0	The MOJO Gateway shall send the order status results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1254	C-CSS-65250	B0	The MOJO Gateway shall send the price estimate to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1255	C-CSS-65260	B1	The MOJO Gateway shall receive service requests  from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request Type   d)  Server UR  e)  Other data as required from the specified server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1258	C-CSS-65277	B1	The MOJO Gateway shall send the service results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1259	C-CSS-65300	B0	The MOJO Gateway shall receive user profile requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., USER PROFILE RETRIEVAL)  d)  Other data as required from the MSS user profile server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1263	C-CSS-65340	B0	The MOJO Gateway shall receive user profile update requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., USER PROFILE UPDATE)  d)  Other data as required from the MSS user profile server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1266	C-CSS-65365	B0	The MOJO Gateway shall send the updated user profile information and status to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1267	C-CSS-65385	B0	The MOJO Gateway shall receive subscription requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Request type (i.e., subscription request)  c)  Session ID  d)  other data as required from subscription server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1270	C-CSS-65395	B0	The MOJO Gateway shall send the subscription request result to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1271	C-CSS-65398	B0	The MOJO Gateway shall receive advertising query requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., ADVERTISING QUERY)  d)  Other data as required from the advertising server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1272	C-CSS-65400	B0	The MOJO Gateway shall forward the advertising query request to the ADSRV CI.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1274	C-CSS-65405	B0	The MOJO Gateway shall send the advertising query results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1275	C-CSS-65408	B0	The MOJO Gateway shall receive data dictionary query requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., data dictionary query)  d)  Server UR  e)  Other data as required by the data dictionary server to process the request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1278	C-CSS-65430	B0	The MOJO Gateway shall send the data dictionary query results to the WKBCH CI as a  message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1279	C-CSS-65510	B0	The MOJO Gateway shall receive a MOJO session validation request from the WKBCH CI.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1280	C-CSS-65520	B0	The MOJO Gateway shall have the capability to  process a  MOJO session validation request.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1288	C-CSS-65590	B0	The MOJO Gateway shall accept and process lifecycle commands from the MSS.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1293	C-CSS-65625	B0	The MOJO Gateway shall send the valid status code and xAR results or the invalid status code to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
240	IMS-0110	Complete	The ECS user interface shall support access to ECS services from the personal computers and workstations of the general user community, without requiring them to install ECS client software.	1299	C-CSS-65660	B0	The MOJO Gateway shall receive a xAR query from the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	282	S-CLS-00010	A	The DESKT CI shall provide a GUI interface with a multiple window display.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	283	S-CLS-00020	A	The DESKT CI shall provide a GUI interface with buttons and pull down menus.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	284	S-CLS-00030	A	The DESKT CI shall provide a GUI interface with consistent use of non-standard keys.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	285	S-CLS-00040	A	The DESKT CI shall provide a GUI interface with minimal use of non-standard keys.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	286	S-CLS-00050	A	The DESKT CI shall provide a GUI interface with standardized use of commands and terminology across screens.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	287	S-CLS-00060	B1	The WKBCH CI shall provide users with automatic acronym expansion, which can be enabled and disabled interactively.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	288	S-CLS-00080	A	The DESKT CI shall provide a GUI interface for users with self-explanatory error messages either through the  Message/Error Dialogs or through message area.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	289	S-CLS-00090	A	The DESKT CI shall provide a GUI interface with  random movement of a cursor through the screen.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	290	S-CLS-00100	A	The DESKT CI shall provide a GUI interface with  context-sensitive help.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	291	S-CLS-00110	A	The DESKT CI shall provide an mechanism to have help information made available to users and include a general introductory description of EOSDIS and its services.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	292	S-CLS-00120	A	The DESKT CI shall provide for a common default color scheme for the user interface which may be customized by the user.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	293	S-CLS-00130	A	The DESKT CI shall provide for a standard ordering of menu items for the user interface.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	294	S-CLS-00140	A	The DESKT CI shall provide a standard widget set for building a user interface, e.g. TimeEntry Widget, TimeInterval Widget, TextField, Integer TextField, Real TextField, Listbox, Double Selection List Box, and Utilities like SetFont.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	295	S-CLS-00150	A	The DESKT CI shall provide container desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	296	S-CLS-00160	A	The DESKT CI shall provide document desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	297	S-CLS-00170	A	The DESKT CI shall provide application desktop  objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	298	S-CLS-00180	A	The DESKT CI shall provide users the capability to execute software associated with a desktop object.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	299	S-CLS-00190	A	The DESKT CI shall provide users the capability to create desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	300	S-CLS-00200	A	The DESKT CI shall provide users the capability to destroy desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	301	S-CLS-00210	A	The DESKT CI shall provide users the capability to open desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	302	S-CLS-00230	A	The DESKT CI shall provide users the capability to copy a desktop object.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	303	S-CLS-00250	A	The DESKT CI shall provide users the capability to move  desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	304	S-CLS-00290	A	The DESKT CI shall provide users the capability to bind a service to a desktop object.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	305	S-CLS-00300	A	The DESKT CI shall provide users the capability to invoke any service bound to a desktop object.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	306	S-CLS-00330	A	The DESKT CI shall provide users the capability to add desktop objects to container objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	307	S-CLS-00340	A	The DESKT CI shall provide users the capability to remove desktop objects from container objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	308	S-CLS-00345	A	The DESKT CI shall provide users the capability to undo the last removal of desktop objects from container objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	310	S-CLS-00380	A	The DESKT CI shall provide users the capability to display the objects contained in container objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	311	S-CLS-00390	A	The DESKT CI shall provide the capability to iconically represent desktop objects, allow single or multiple icons to be selected, and highlight icons when selected.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	312	S-CLS-00400	A	The DESKT CI shall provide the capability to textually represent desktop objects.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	313	S-CLS-01280	A	The WKBCH CI shall provide a GUI interface to data dictionary with associations between attributes (e.g., between instruments and geophysical parameters) portrayed.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	314	S-CLS-01480	A	The DESKT CI shall utilize an X-windows windowing interface for the GUI.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	317	S-CLS-01500	A	The DESKT CI user interface shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User INterface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	318	S-CLS-01505	B0	The DESKT CI user interface shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	319	S-CLS-01507	A	The DESKT CI user interface shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	321	S-CLS-01600	A	The DESKT CI shall provide users the capability to resize windows.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	322	S-CLS-01605	A	The DESKT CI shall provide users the capability to select different default screen font sizes.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	323	S-CLS-01610	A	The DESKT CI shall provider users with the option of selecting among four icon sizes (i.e. tiny, small, medium and large).	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	324	S-CLS-01615	A	The DESKT CI shall provide users the capability to set preferences (e.g. desired view, mode of opening container object, sort based on alphabetical, modification, size, type of object either in ascending or descending order, and confirmation for delete.)	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	325	S-CLS-01625	A	The DESKT CI shall provide the capability to drag and drop desktop objects to perform functions like move, copy and to invoke related applications.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	326	S-CLS-01627	A	The DESKT CI shall provide a mechanism to save the screen location of all programs it is managing.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	403	S-CLS-10642	A	The DESKT CI shall provide for an unregistered user to find out how to register through Help.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	418	S-CLS-10780	A	The WKBCH CI shall list Dependent Valid Values to assist users in formulating Search Requests.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	469	S-CLS-12070	B0	The WKBCH CI shall provide a GUI interface with capability to save and restore the contents of   data search and order forms.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	470	S-CLS-12110	B1	The WKBCH CI shall provide a GUI interface with a command language.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	472	S-CLS-12500	B1	The WKBCH CI shall provide users an interface to APIs for use in non-interactive remote user sessions.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	484	S-CLS-12710	B1	The WKBCH CI shall save user states for restoring interrupted sessions.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	492	S-CLS-12810	B1	The WKBCH CI shall provide a Web interface with  minimal and consistent use of non-standard keys.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	493	S-CLS-12820	B1	The WKBCH CI shall provide a Web interface with capability to save and restore the contents of a menu or form.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	494	S-CLS-12830	B1	The WKBCH CI shall provide a Web interface with standardized use of commands and terminology across screens.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	495	S-CLS-12840	B1	The WKBCH CI shall provide a Web interface with self-explanatory, meaningful error messages.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	496	S-CLS-12850	B1	The WKBCH CI shall provide a Web interface with availability of a menu tree diagram.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	497	S-CLS-12860	B1	The WKBCH CI shall provide a Web interface with a command language.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	498	S-CLS-12870	B1	The WKBCH CI shall support a web interface that provides users system access from local and remote terminals.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	499	S-CLS-12903	A	The WKBCH CI shall provide users a capability to save documents at his local workstation.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	500	S-CLS-12906	A	The WKBCH CI shall provide users a capability to print documents at his local workstation.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	528	S-CLS-13240	B1	The WKBCH CI shall provide users the capability to individually suspend and restore the Service Requests within a  user session after interruption.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	530	S-CLS-13270	A	The WKBCH CI shall provide a GUI interface with Valid Value lists for all variables.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	563	S-CLS-13680	B1	The WKBCH CI shall allow users to access the Data Dictionary Service.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	592	S-CLS-14000	B1	The WKBCH CI shall provide a user interface that indicates changes in status of an iconified window (e.g., additional results inserted into window).	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	593	S-CLS-14010	B1	The WKBCH CI shall prompt the user to save his/her edits when the user quits the editing of workbench objects (e.g., a Result Set or a Guide document), if there are any unsaved edits.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	594	S-CLS-14020	A	The WKBCH CI shall display Dependent Valid Values associated with search screens to show current Valid Values, as the parameterization of the search is changed.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	606	S-CLS-14440	B0	The WKBCH CI DAR Tool shall provide users the capability to save and retrieve the DAR parameters of any of their previously submitted DARs.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	613	S-CLS-14520	B1	For WKBCH CI screens requiring user input, optional fields shall be distinguished from mandatory fields.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	615	S-CLS-14560	A	The WKBCH CI shall provide access to the lists of the Valid Values for data elements, where the data element has an enumerated set of values as a constraint.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	629	S-CLS-15690	A	The DESKT CI shall utilize the Motif widget set for providing GUI interfaces.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	688	S-CLS-18090	B0	The WKBCH CI interface to access communications networks shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	689	S-CLS-18100	A	The WKBCH CI interface to access communications networks shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	697	S-CLS-18170	A	The WKBCH CI interface to access communications networks shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	708	S-CLS-19116	4PY	The WKBCH CI DAR Tool shall provide a selection list for all DAR parameters having an enumerated set of values during DAR formulation.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	709	S-CLS-19117	B0	The WKBCH CI DART shall have the capability to store DAR configuration parameters on the user's local storage and permit users to restore these saved parameters on demand.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	720	S-CLS-19130	4PY	The WKBCH CI DAR Tool shall provide:  1. context sensitive help  2. general help at a window level	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	738	S-CLS-19174	5B	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.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	739	S-CLS-19176	5B	The WKBCH CI DAR Tool shall allow the user to delete:  1) a xAR search  2) xAR search results.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	742	S-CLS-19186	4PY	The WKBCHCI DAR Tool shall have a common look and feel within the interface and  with other ECS user interfaces (i.e., JEST) as defined by the ECS User Interface  Style Guide.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	782	S-CLS-19263	5A	The WKBCH CI DAR Tool shall support the save and restore of search criteria and  search results.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	783	S-CLS-19264	5A	The WKBCH CI DAR Tool shall automatically save:  1) a xAR search submitted by the user,  2) the corresponding xAR search results and have the capability to correlate the   search request with the corresponding search results.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	785	S-CLS-19270	4PY	The WKBCH CI DAR Tool screen shall distinguish optional fields from mandatory fields.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	1283	C-CSS-65540	B0	The MOJO Gateway shall determine invalid requests and send error messages for them to the WKBCH CI.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	1284	C-CSS-65550	B0	The MOJO Gateway shall inform the user if a valid request for ECS data or services fails by sending failure messages to the WKBCH CI.	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	1366	S-DMS-20910	Complete	The DDICT CI shall provide access to the lists of the Valid Values for data elements, where the data element has an enumerated set of values as a constraint	99-0729	08/25/1999  	No Data	
241	IMS-0120	Complete	The ECS shall ensure standard use of keys across custom ECS GUIs.	1367	S-DMS-20930	Complete	The DDICT CI shall export Dependent Valid Values to the V0 IMS.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	3970	C-CSS-40425	5B	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.	99-0768	08/25/1999  		
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	168	S-CLS-20090	5B	The ODFRM CI shall reject any ASTER L1B on-demand product order from an unauthorized user.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	533	S-CLS-13380	B1	 The WKBCH CI shall send User Authentication Requests to  the SMC.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	534	S-CLS-13390	B1	The WKBCH CI shall  allow or deny the user system access based on User Validation Status returned from the SMC.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	633	S-CLS-15760	B0	The WKBCH CI shall restrict users' access to data and services for  which the users lack sufficient priviledges.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	719	S-CLS-19129	4PY	The WKBCH CI DART shall have the capability to verify user access privilege and to obtain a User ID on determination of a valid access privilege at each launch of the DART.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	740	S-CLS-19182	4PY	The WKBCH CI DAR Tool shall allow users that are not authorized for DAR submission to use the DAR Tool to construct DARs, but will not allow them to submit these DARs to the ASTER GDS.  	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	934	C-CSS-21220	B0	The CSS Security Service shall provide a mechanism to authenticate client/server applications.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	937	C-CSS-21225	A	The CSS Security service shall provide a name based authorization capability.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	1225	C-CSS-65010	B0	The MOJO Gateway shall perform authentication of a user using the DCE security service for login requests.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	1226	C-CSS-65020	B0	The MOJO Gateway shall inform users of authentication failure or success via messages to the WKBCH CI.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	1228	C-CSS-65040	B0	The MOJO Gateway shall perform DCE logout on behalf of a user's logout request.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	1306	S-DMS-00200	Complete	The LIMGR CI shall forward to and the ECS-V0 Gateways the identification of the user on whose behalf a service request is being executed.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
242	IMS-0130	5B Partial	The ECS shall verify that a user is authorized to access a particular ECS service before providing the service to the user.	1918	S-DSS-00860	A	The SDSRV CI shall inform a client that a requested service is not accessible if the client attempts to access services outside their access level.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	314	S-CLS-01480	A	The DESKT CI shall utilize an X-windows windowing interface for the GUI.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	317	S-CLS-01500	A	The DESKT CI user interface shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User INterface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	318	S-CLS-01505	B0	The DESKT CI user interface shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	319	S-CLS-01507	A	The DESKT CI user interface shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	578	S-CLS-13830	B1	The WKBCH CI DAR Tool shall have the capability to display instrument and AM-1 spacecraft activities chronologically on a schedule timeline.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	579	S-CLS-13850	B1	The WKBCH CI DAR Tool shall provide detailed help on the ASTER instrument and parameters during DAR formulation and submittal.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	581	S-CLS-13870	B0	The WKBCH CI DAR Tool shall provide visualizations of a single view swath for the ASTER sensors, based on user selection, as a reference aid to the creation of an area of interest for a DAR.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	582	S-CLS-13880	B0	The WKBCH CI DAR Tool shall provide instrument specific default settings for the  ASTER instrument configuration parameters.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	583	S-CLS-13890	B0	The WKBCH CI shall provide users the capability to view Valid Values for  DAR Parameters.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	586	S-CLS-13940	B1	The WKBCH CI DAR Tool shall allow the user to search for ASTER xAR status resulting in a display with the following information:  a. Date and time of DAR submittal  b. Sensor name  c. Data acquisition request ID  d. Request status  e. Implementation schedule  f. If rejection, then the reason for the rejection.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	591	S-CLS-13990	B1	The WKBCH CI DAR Tool shall provide users the capability to view the resulting selection area on a map when a latitude/longitude selection is made during DAR formulation and xAR Search creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	602	S-CLS-14400	B0	The WKBCH CI DAR Tool shall update the DAR date/time fields after the following  information has been selected via the timeline display:  a.  repeat interval  b.  acquisition window  c.  xAR lifetime	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	603	S-CLS-14410	B0	The WKBCH CI DAR Tool shall update the timeline display during DAR formulation when the user  provides the following information:  a.  repeat interval  b.  acquisition window  c.  xAR lifetime.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	604	S-CLS-14420	B0	The WKBCH CI DAR Tool shall synchronize geographic selection criteria for DARs so that selection of an area on a DAR map display will be translated into latitude/longitude coordinates in a DAR submission window.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	605	S-CLS-14430	B0	The WKBCH CI DAR Tool shall synchronize geographic selection criteria for DARs so that typing latitude/longitude coordinates in a DAR submission window will be graphically displayed as a bounded area on a DAR map display.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	606	S-CLS-14440	B0	The WKBCH CI DAR Tool shall provide users the capability to save and retrieve the DAR parameters of any of their previously submitted DARs.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	607	S-CLS-14442	B0	The WKBCH CI DAR Tool shall provide the capability to create a new DAR by editing the parameters of a previously submitted DAR.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	610	S-CLS-14490	B1	The WKBCH CI DAR Tool shall synchronize time-related data for a xAR Search Request so that a date/time range typed in a Search Request window will be graphically displayed as a time range in a Search Request timeline window.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	688	S-CLS-18090	B0	The WKBCH CI interface to access communications networks shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	689	S-CLS-18100	A	The WKBCH CI interface to access communications networks shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	691	S-CLS-18110	B0	The WKBCH CI interface to access databases that may be geographically dispersed shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	692	S-CLS-18120	A	The WKBCH CI interface to access databases that may be geographically dispersed shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	693	S-CLS-18130	B0	The WKBCH CI interface to access multi-disciplinary directories and inventories shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	694	S-CLS-18140	A	The WKBCH CI interface to access multidisciplinary directories and inventories shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	695	S-CLS-18150	B0	The WKBCH CI interface to access heterogeneous data sets shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Guidance for Web-Based Applications (March 1997) and determined by human factors' analysis based on this document.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	696	S-CLS-18160	A	The WKBCH CI interface to access heterogeneous data sets shall provide for user effectiveness and satisfaction as defined by the overarching principles in the ECS User Interface Style Guide (January 1996) and determined by human factors' analysis based on the Guide.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	697	S-CLS-18170	A	The WKBCH CI interface to access communications networks shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	698	S-CLS-18180	A	The WKBCH CI interface to access databases that may be geographically dispersed shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	699	S-CLS-18190	A	The WKBCH CI interface to access multi-disciplinary directories and inventories shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	700	S-CLS-18200	A	The WKBCH CI interface to access heterogeneous data sets shall have a common look and feel within the interface and with other ECS user interfaces as defined by the ECS User Interface Style Guide (January 1996) and the ECS HTML Developer's Guide (Version 1.1, 1997) and determined by human factors' analysis based on the Guides.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	701	S-CLS-19101	4PY	The WKBCH CI DART shall have the capability to create and edit an ASTER DAR with parameters identified in the ECS to ASTER GDS ICD.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	702	S-CLS-19102	4PY	The WKBCH CI DART shall have the capability for users to interactively set observation timing parameters via a GUI or by keyboard entry on a forms-based screen.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	703	S-CLS-19103	4PY	The WKBCH CI DAR Tool shall have the capability for users to specify single or multiple observation times on the DAR Tool temporal GUI.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	706	S-CLS-19108	5B	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.  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	711	S-CLS-19119	4PY	The WKBCH CI DAR Tool shall provide the capability for users to interactively enter, edit, and delete latitude/longitude coordinates in an Area of Interest (AOI) polygon.  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	713	S-CLS-19123	4PY	The WKBCH CI DAR Tool shall provide the capability for users to change the following information which controls the timeline display:  a.  the number of increments  b.  the units of increments (years or months).	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	714	S-CLS-19124	4PY	The WKBCH CI DAR Tool shall provide the capability for the user to interactively  select the instrument mode, gain settings, and bands.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	715	S-CLS-19125	4PY	The WKBCH CI DART shall have the capability (in a manner that is meaningful and tailorable by the user) to save, delete, move, and copy locally stored DAR configuration parameters.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	716	S-CLS-19126	4PY	The WKBCH CI DART shall automatically update the information in spatial, temporal, and forms-based GUI displays, when the user changes the existing dependent information (parameters); Reference Document: DAR Submit Tool GUI Dependencies and Interactions.      	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	717	S-CLS-19127	5B	The WKBCH CI DAR Tool shall allow an ECS user to display the results of xAR Searches on spatial and textual-based displays.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	718	S-CLS-19128	B0	The WKBCH CI DART submission screens requiring user input shall distinguish optional fields from mandatory fields.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	720	S-CLS-19130	4PY	The WKBCH CI DAR Tool shall provide:  1. context sensitive help  2. general help at a window level	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	722	S-CLS-19135	5B	The WKBCH CI DAR Tool shall provide references to sources of climatology information, including: cloud climatology probabilities, seasonal snow and ice cover, and major ecosystem regions.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	723	S-CLS-19136	4PY	The WKBCH CI DAR Tool shall have the capability to show or hide overlays or backgrounds to or from the map on a geographic display.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	724	S-CLS-19137	4PY	The WKBCH CI DAR Tool spatial display shall provide the capability to display the following geographic projections:  1.  Geographical (Plate Carree)  2.  Universal Transverse Mercator  3.  Polar Stereographic  4.  Lambert Conformal Conic  5.  Space Oblique Mercator  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	725	S-CLS-19139	5B	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).  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	728	S-CLS-19142	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	730	S-CLS-19153	4PY	The WKBCH CI DAR Tool spatial display shall have the capability to display the latitude/longitude coordinates of any point on a geographical display selected by the user's pointing device.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	731	S-CLS-19154	4PY	The WKBCH CI DAR Tool shall be able to calculate and display to the user the size (in square km) of any user-specified polygonal area on a geographical display.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	733	S-CLS-19156	4PY	The WKBCH CI DAR Tool help system shall provide ASTER-specific help messages that instruct users how to change the instrument parameter settings for the three ASTER telescopes in their DARs.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	737	S-CLS-19166	4PY	The WKBCH CI DAR Tool shall have the capability to provide a meaningful error message to users based on the receipt of an error code from ECS network components or services or the ASTER GDS.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	741	S-CLS-19184	B0	The WKBCH CI shall support a web interface that provides users system access through one of the following Web browsers that they have installed on their workstation or personal computer at a minimum:  a.  Netscape (Version 4.06)  b.  Microsoft Explorer (Version 4.X or higher)  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	742	S-CLS-19186	4PY	The WKBCHCI DAR Tool shall have a common look and feel within the interface and  with other ECS user interfaces (i.e., JEST) as defined by the ECS User Interface  Style Guide.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	745	S-CLS-19191	4PY	The WKBCH CI DAR Tool shall provide users the option to display latitude/longitude pairs as symbols, displayed in their proper geo-location on the map used to select areas of interest when constructing a DAR.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	746	S-CLS-19192	4PY	The WKBCH CI DAR Tool shall provide users the option to display a series of latitude/longitude pairs as connected lines, displayed in their proper geo-location on top of the map used to select areas of interest when constructing a DAR.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	747	S-CLS-19194	5B	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  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	748	S-CLS-19196	4PY	The WKBCH CI DAR Tool spatial selection function shall allow users to select and add geographic areas of interest as a polygon during DAR formulation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	749	S-CLS-19198	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	751	S-CLS-19201	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	752	S-CLS-19202	4PY	The WKBCH CI DAR Tool spatial selection function shall support the selection of  polygons on the spatial map by the simple connection of points selected by the user.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	753	S-CLS-19204	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	755	S-CLS-19206	B0	The WKBCH CI DAR Tool spatial selection function shall allow users to highlight  an AOI to distinguish it from overlapping AOIs.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	756	S-CLS-19208	4PY	The WKBCH CI DAR Tool spatial selection function shall allow the user to stop a  current web transaction relating to spatial map server connections and downloads  and upon termination of the web transaction, the spatial map reverts to its previous state.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	757	S-CLS-19210	4PY	The WKBCH CI DAR Tool spatial map shall support the display of a base map and additional map overlays.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	758	S-CLS-19212	4PY	The WKBCH CI DAR Tool spatial map function shall support the following zoom capabilities:  a) zoom by window:  zoom to a user defined area drawn interactively on a map using a rubberbanding box  b) zoom in:  zoom in on the map center point by a pre-defined zoom factor  c) zoom out:  zoom out from the map center point by a pre-defined zoom factor  d) zoom by percent:  zoom in or out on the map center by a percentage.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	759	S-CLS-19214	4PY	The WKBCH CI DAR Tool spatial map shall support the following pan capabilities:  a) point-and-click:  click on any point within the map to make that point the map center point   b) drag-and-release: drag a map point to a new position within the map area to  effect a corresponding pan.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	760	S-CLS-19216	4PY	The WKBCH CI DAR Tool spatial map shall support the reset of the map scale and pan to a zoom factor of 1 (100%) and a pan center of 0 degrees lat. and 0 degrees long. with a single user action.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	761	S-CLS-19218	4PY	The WKBCH CI DAR Tool shall allow the user to see the current zoom area in relation to the whole earth and use this display to pan the zoom window to another area on the earth.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	762	S-CLS-19220	4PY	The WKBCH CI DAR Tool spatial map shall respond appropriately (resize) to window resizing events.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	763	S-CLS-19222	4PY	The WKBCH CI DAR Tool spatial map shall allow selection of projections via a select list.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	764	S-CLS-19224	4PY	The WKBCH CI DAR Tool spatial map shall allow control of overlay resources to include, at a minimum, the following:  a) color  b) line style  c) line thickness	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	765	S-CLS-19226	4PY	The WKBCH CI DAR Tool spatial map shall allow the user to control overlay sequences that are being displayed.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	766	S-CLS-19228	4PY	The WKBCH CI DAR Tool spatial map shall support the display of a latitude/longitude grid which includes the annotation of user selected latitude/longitude intervals.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	767	S-CLS-19230	4PY	The WKBCH CI DAR Tool spatial map shall support user customization of the latitude/longitude grid to include, at a minimum:  a) the grid size in the following increments: 5, 10, 15, 20, 25, 30, 45, 60, 90  b) the showing/hiding of latitude/longitude annotations  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	768	S-CLS-19232	4PY	The WKBCH CI DAR Tool spatial map shall support the display of the following data, at a minimum:  a) current projection  b) zoom factor/percentage  c) cursor location in latitude/longitude coordinates.  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	769	S-CLS-19234	5B	The WKBCH CI DAR Tool xAR Status function shall allow the user to highlight or hide a xAR geographic AOI within the viewing window.  	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	770	S-CLS-19236	5B	The WKBCH CI DAR Tool xAR Status function shall support the display of xAR acquired scenes overlaid with the xAR AOI.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	771	S-CLS-19238	5B	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	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	772	S-CLS-19240	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	773	S-CLS-19241	5B	The WKBCH CI DAR Tool acquired scenes viewing function shall support the highlighting or hiding of acquired scenes within the viewing window.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	774	S-CLS-19242	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	775	S-CLS-19244	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	776	S-CLS-19246	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	777	S-CLS-19254	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	779	S-CLS-19258	4PY	The WKBCH CI DAR Tool shall provide users the capability to select from a list of values for DAR parameters that have a distinct set of values.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	780	S-CLS-19260	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	781	S-CLS-19262	5B	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	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	785	S-CLS-19270	4PY	The WKBCH CI DAR Tool screen shall distinguish optional fields from mandatory fields.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	786	S-CLS-19272	4PY	The WKBCH CI DAR Tool shall ensure that only those gain settings appropriate to  the selected sensor(s) can be enabled by the user during DAR creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	787	S-CLS-19274	4PY	The WKBCH CI  DAR Tool shall disable the entry of minimum and maximum look angles and specific look angles when the user enters a specific view swath during DAR creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	788	S-CLS-19276	4PY	The WKBCH CI DAR Tool shall disable the entry of Minimum and Maximum Look Angles  and Specific View Swath when the user enters a Specific Look Angle during DAR creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	789	S-CLS-19278	4PY	The WKBCH CI DAR Tool shall ensure that when Implementation Urgency is set to 'Yes', that xAR lifetime start and end days do not exceed a total of 18 days during DAR creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	790	S-CLS-19280	4PY	The WKBCH CI DAR Tool shall ensure that when Ground Campaign is set to 'Yes", that the tool does not permit users to set 'Allow Cross-Track Fragmentation' to 'Yes' during DAR creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	791	S-CLS-19282	B0	The WKBCH CI DAR Tool shall ensure that when the Avoid Clouds Flag is set to 'No', that the tool does not permit users to enter Cloud Coverage settings during DAR creation.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	792	S-CLS-19296	5B	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.	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	793	S-CLS-19298	5B	The WKBCH CI DAR Tool temporal selection function shall support the textual selection of temporal ranges in support of DAR creation and xAR searches	99-0729	08/25/1999  	No Data	
243	IMS-0150	5B Partial	The ECS shall supply a user interface for access to the following services:    a. User registration	794	S-CLS-19300	5B	The WKBCH CI DAR Tool shall provide an HTML tutorial for training users in the  use of the DAR Tool.	99-0729	08/25/1999  	No Data	
244	IMS-0170	Complete	The ECS user interface shall be designed so that restructuring of the ECS data bases shall not result in the need for changes to the ECS user interface.	501	S-CLS-12910	A	The user interface shall not require changes as a result of restructuring any of the data bases provided by the SDSRV CI.	99-0729	08/25/1999  	No Data	
244	IMS-0170	Complete	The ECS user interface shall be designed so that restructuring of the ECS data bases shall not result in the need for changes to the ECS user interface.	508	S-CLS-12980	A	The user interface shall not require changes as a result of restructuring any of the data bases provided by the DDICT CI.	99-0729	08/25/1999  	No Data	
244	IMS-0170	Complete	The ECS user interface shall be designed so that restructuring of the ECS data bases shall not result in the need for changes to the ECS user interface.	509	S-CLS-12990	A	The user interface shall not require changes as a result of restructuring any of the data bases provided by the ADSRV CI.	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	324	S-CLS-01615	A	The DESKT CI shall provide users the capability to set preferences (e.g. desired view, mode of opening container object, sort based on alphabetical, modification, size, type of object either in ascending or descending order, and confirmation for delete.)	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	538	S-CLS-13450	A	Where the User Profile specifies defaults for parameters which are applicable to an ECS Service Request, the user interface shall employ these defaults to assist the user in the formulation of a new request (e.g., by displaying them as default values).	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	539	S-CLS-13460	B1	The WKBCH CI shall provide users the capability to create a Session Profile for each user session.  The Session Profile shall be able to contain any of the parameters which are in the User Profile and which may apply as defaults to ECS Service Requests.	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	540	S-CLS-13470	B1	The WKBCH CI shall employ the defaults specified in the MSS user Profile to assist the user in the formulation of a new request in the context of a user session (e.g., by displaying them as default values in the respective input fields).	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	541	S-CLS-13475	B0	The WKBCH CI shall provide capability for user to create a user preference that can house the following types of information:  user electronic address, data distribution media, data distribution address, user expertise level, default query parameters, terminal characteristics, and technical specialty.	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	3317	C-MSS-75025	B0	The MSS Accountability Management Service shall be capable of receiving requests for user profile data from ECS applications.	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	3318	C-MSS-75030	B0	The MSS Accountability Management Service shall be capable of receiving requests for user profile data from M&O operators.	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	3319	C-MSS-75035	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to ECS applications	99-0729	08/25/1999  	No Data	
245	IMS-0180	Complete	The ECS shall extract relevant data from the user profile information and use as default values.	3320	C-MSS-75040	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to M&O operators.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	1073	C-CSS-40420	5B	The SBSRV shall validate upon submission of a subscription that the subscription references a user ID associated with a MSS user profile.	00-0737	07/19/2000  		
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	4851	S-OMS-01170	SY3	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.	02-1045	12/04/2002  		
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	4852	S-OMS-01180	SY3	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.	02-1045	12/04/2002  		
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	83	C-MSS-75021	5B	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')	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	84	C-MSS-75022	5B	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.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	85	C-MSS-75023	5B	The MSS accountability management service shall use a value of Non-NASA User ('N') as the default value for the NASA User attribute.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	264	S-DSS-06600	5B	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.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	265	S-DSS-06601	5B	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.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	267	S-DSS-06603	5B	The SDSRV CI shall support access rules based upon the MSS User Profile roles of P, R, and N individually or in any combination.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	268	S-DSS-06604	5B	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.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	269	S-DSS-06605	5B	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).	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	271	S-DSS-06607	5B	The SDSRV CI shall use the MSS based NASAUSER attribute when evaluating granule access rules.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	272	S-DSS-06608	5B	The SDSRV CI shall send to the MSS Accountability Service a request for User Profile information including the NASAUser attribute.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	273	S-DSS-06609	5B	The SDSRV CI shall receive User Profile information, including the NASAUser attribute, from the MSS Accountability Service.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	274	S-DSS-06610	5B	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").	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	275	S-DSS-06611	5B	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.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	276	S-DSS-06612	5B	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').	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	277	S-DSS-06613	5B	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'.	99-0729	08/25/1999  	No Data	
246	IMS-0212	5B Future	The ECS shall have the capability to restrict access of data at the granule level to only DAAC operations and instrument team members.	278	S-DSS-06614	5B	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'.	99-0729	08/25/1999  	No Data	
247	IMS-0216	5B Future	The ECS shall provide the capability for DAAC operations staff and Instrument Team members to designate which granules have restricted access.	266	S-DSS-06602	5B	The SDSRV CI shall provide a command line interface for modifying the QA Time range associated with a specific ESDT.	99-0729	08/25/1999  	No Data	
247	IMS-0216	5B Future	The ECS shall provide the capability for DAAC operations staff and Instrument Team members to designate which granules have restricted access.	270	S-DSS-06606	5B	The SDSRV CI shall provide a command line interface for changing the QA independent access permissions of a specific ESDT.	99-0729	08/25/1999  	No Data	
247	IMS-0216	5B Future	The ECS shall provide the capability for DAAC operations staff and Instrument Team members to designate which granules have restricted access.	280	S-DSS-06616	5B	The SDSRV CI shall assign a null value to the QA time range when a new ESDT is installed.	99-0729	08/25/1999  	No Data	
247	IMS-0216	5B Future	The ECS shall provide the capability for DAAC operations staff and Instrument Team members to designate which granules have restricted access.	281	S-DSS-06617	5B	The SDSRV CI shall assign a null value to the ESDT specific access permission when a new ESDT is installed.	99-0729	08/25/1999  	No Data	
248	IMS-0220	Complete	The ECS shall store, maintain and provide data management services for ECS directory and inventory data.	1331	S-DMS-20015	Complete	The DDICT CI shall maintain a mapping between Data Collections and the location of Data Collections in ECS.	99-0729	08/25/1999  	No Data	
248	IMS-0220	Complete	The ECS shall store, maintain and provide data management services for ECS directory and inventory data.	1341	S-DMS-20250	Complete	The DDICT CI shall store, maintain and provide data management services for ECS data dictionary entries.	99-0729	08/25/1999  	No Data	
248	IMS-0220	Complete	The ECS shall store, maintain and provide data management services for ECS directory and inventory data.	1344	S-DMS-20300	Complete	The DDICT CI shall provide a database administration utility for on-line, full backup of the Data Dictionary database.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1342	S-DMS-20255	Complete	The DDICT CI shall provide a database administration utility to allow operators to control user access at a table, column, and row level for read, insert, update, and delete operations.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1343	S-DMS-20260	Complete	The DDICT CI shall support an administration utility for performance monitoring of the Data Dictionary DBMS for system disk, memory, CPU and Input/Output utilization.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1344	S-DMS-20300	Complete	The DDICT CI shall provide a database administration utility for on-line, full backup of the Data Dictionary database.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1345	S-DMS-20320	Complete	The DDICT CI shall provide a database administration utility for manual recovery of Data Dictionary data from system and media failures.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1346	S-DMS-20340	Complete	The DDICT CI shall provide a database administration utility for data import.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1347	S-DMS-20350	Complete	The DDICT CI shall provide a database administration utility for data export.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1348	S-DMS-20530	Complete	The DDICT CI shall support batch information management capabilities to add data dictionary entries.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1349	S-DMS-20540	Complete	The DDICT CI shall support batch information management capabilities to update data dictionary entries.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1893	S-DSS-00550	A	The SDSRV CI shall provide the capability for operations staff to view the Metadata Database Schema.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1894	S-DSS-00560	A	The SDSRV CI shall provide the capability for operations staff to create the Metadata Database Schema.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1895	S-DSS-00570	A	The SDSRV CI shall provide the capability for operations staff to update the Metadata Database Schema.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1897	S-DSS-00610	A	The SDSRV CI shall provide the capability for operations staff to delete the Metadata Database Schema.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1907	S-DSS-00800	B0	The SDSRV CI shall provide tools to monitor and tune the performance of the Metadata Database when such tools are supplied by the database vendor.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1922	S-DSS-00905	B0	The SDSRV CI shall provide tools for the incremental backup of the Metadata Database.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	1993	S-DSS-02500	A	The SDSRV CI shall provide the capability to implement services for new data types, including data insert services, search services, and data distribution services.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2658	S-IOS-00100	A	The ADSRV CI shall support an administration utility for performance monitoring of database query processing.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2659	S-IOS-00110	A	The ADSRV CI shall support an administration utility for performance tuning.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2660	S-IOS-00130	A	The ADSRV CI shall support an administration utility for on-line full backup and restoration of advertising service data.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2661	S-IOS-00140	A	The ADSRV CI shall support an administration utility for on-line incremental backup and restoration of advertising service data.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2662	S-IOS-00150	A	ADSRV CI shall support an administration utility for manual recovery of advertising service data from media and system failures.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2663	S-IOS-00160	A	The ADSRV CI shall support an administration utility for automatic recovery of advertising service data from system failures.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2664	S-IOS-00170	A	The ADSRV CI shall support a data administration utility for data import.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	2665	S-IOS-00180	A	The ADSRV CI shall support a data administration utility for data export.	99-0729	08/25/1999  	No Data	
249	IMS-0240	Complete	The ECS shall provide data base administration utilities for:  a. Modifying the data base schema  b. Performance monitoring  c. Performance tuning  d. Administration of user access control  e. On-line backup  f. On-line recovery  g. Export/import of data	3232	C-MSS-66183	B1	The MSS Performance Management Application Service shall have the capability to monitor the performance of ECS relational and object oriented database servers.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1070	C-CSS-40390	B0	The Subscription Service shall provide a mechanism that allows the Subscription Service to be restarted and any requests that were in progress be restarted	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1350	S-DMS-20550	Complete	The DDICT CI shall support batch information management capabilities to delete data dictionary entries.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1357	S-DMS-20640	Complete	The DDICT CI shall support the restart of database administration and maintenance activities which are unintentionally interrupted through system software or hardware failure, without loss of information.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1854	S-DSS-00158	B0	The SDSRV CI shall provide the capability to restructure the Metadata Database in order to support database maintenance activities.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1919	S-DSS-00900	A	The SDSRV CI shall support the interruption of a data base administrative or maintenance activity and its restart without loss of information.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1920	S-DSS-00901	A	The SDSRV CI shall provide tools for database backup and restore.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	1921	S-DSS-00902	A	The SDSRV CI shall provide a database management capability that maintains database integrity during concurrent user interactions.	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	2655	S-IOS-00060	A	ADSRV CI internal data base management queries shall be expressed in standard query language (SQL).	99-0729	08/25/1999  	No Data	
250	IMS-0250	Complete	The ECS shall provide the following maintenance of the ECS data bases:  a. Capability to restructure the data base  b. Capability to interrupt a maintenance session and restart the session without loss of information	2670	S-IOS-00330	A	The ADSRV CI shall support the interruption of any administrative or maintenance activity and its restart without loss of database information.	99-0729	08/25/1999  	No Data	
251	IMS-0290	Complete	The ECS internal data base management queries shall be expressed in a standard query language.	2655	S-IOS-00060	A	ADSRV CI internal data base management queries shall be expressed in standard query language (SQL).	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	1356	S-DMS-20610	Complete	 The DDICT CI shall log all insertions, updates and deletions of data dictionary entries.	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	1435	S-DMS-41011	5B	The ASTGW CI shall log the startup of the ASTGW servers.	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	1436	S-DMS-41012	5B	The ASTGW CI shall log the shutdown of the ASTGW servers.	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	2666	S-IOS-00220	A	The ADSRV CI shall log all information write, update and delete activities to the MSS.	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	2886	C-MSS-18060	B0	The Management Data Access Service shall provide the capability for an operator to access management data via a log browser.	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	2890	C-MSS-18200	B0	The MSS shall provide the capability for an application via APIs to log event information.	99-0729	08/25/1999  	No Data	
252	IMS-0300	Complete	The ECS shall maintain a log of all information update activity.	2897	C-MSS-18350	B0	The MSS Management Data Access Service shall provide the capability to load log files into the management database at the site.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	5794	S-DPL-21100	SY2	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).	08-0426	09/29/2008  		
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	414	S-CLS-10730	B0	The WKBCH CI shall provide users the capability to search data dictionary information to obtain the precise definitions of terms used within ECS.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	614	S-CLS-14530	B0	The WKBCH CI shall provide users access to Data Definitions of the following information at a minimum :   a._Earth Science Data Types and services descriptions   b._core metadata attribute definitions   c._valid values   d._synonyms for valid values   e._product specific metadata	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	617	S-CLS-14580	B1	The WKBCH CI shall provide users a consistent view of data dictionary entries based on the value given for an attribute.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	618	S-CLS-14590	B1	The WKBCH CI shall have the capability to send to the Data Dictionary CI, data dictionary information requests consisting of any combination of the following: Data Collection Types, Core Metadata attributes, and Product Specific Metadata.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	619	S-CLS-14600	B1	The WKBCH CI shall have the capability to receive from the Data Dictionary CI, data dictionary information consisting of any combination of the following : Data Collection Types, Core Metadata attributes, and Product Specific Metadata.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	690	S-CLS-18105	B0	The WKBCH CI shall ensure that the following calendar transitions are handled completely and accurately:  a. New Year  b. New Decade  c. New Century  d. Leap Year.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1326	S-DMS-20005	Complete	The DDICT CI shall provide Data Dictionary entries with the following information:   a._Data Collection descriptions   b._core metadata attribute definitions   c._valid values   d._synonyms for valid values   e._product specific metadata	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1334	S-DMS-20080	Complete	The DDICT CI shall allow only one definition of an ECS core metadata attribute that will be used by all data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1335	S-DMS-20110	Complete	The DDICT CI shall define a data dictionary context including all data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1336	S-DMS-20130	Complete	The DDICT CI shall accept  search requests consisting of any combination of the following:  Data Collections, Core and Product Specific Metadata attribute domains and definitions.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1338	S-DMS-20140	Complete	The DDICT CI shall send the results of a search to the originator.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1339	S-DMS-20160	Complete	The DDICT CI shall have the capability to accept new Data Dictionary Entries from the SDSRV CI Data Server.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1348	S-DMS-20530	Complete	The DDICT CI shall support batch information management capabilities to add data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1349	S-DMS-20540	Complete	The DDICT CI shall support batch information management capabilities to update data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1350	S-DMS-20550	Complete	The DDICT CI shall support batch information management capabilities to delete data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1351	S-DMS-20560	Complete	The DDICT CI shall support batch information management capabilities to retrieve data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1352	S-DMS-20570	Complete	The DDICT CI shall support interactive information management capabilities to add data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1353	S-DMS-20580	Complete	The DDICT CI shall support interactive information management capabilities to update data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1354	S-DMS-20590	Complete	The DDICT CI shall support interactive information management capabilities to delete data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1355	S-DMS-20600	Complete	The DDICT CI shall support interactive information management capabilities to retrieve data dictionary entries.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1357	S-DMS-20640	Complete	The DDICT CI shall support the restart of database administration and maintenance activities which are unintentionally interrupted through system software or hardware failure, without loss of information.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	2047	S-DSS-04360	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule in accordance with the Release B data model.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	2048	S-DSS-04365	B0	The SDSRV CI shall maintain Collection Metadata, for standard products, containing key organizations and personnel for all product-related DAACs, ADCs, and ODCs.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	2057	S-DSS-04390	A	Standard Product related Metadata at the Data Server shall include Metadata associated with static subsetted, subsampled, and summary products.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	2059	S-DSS-04420	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Instrument Engineering Data.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	2063	S-DSS-04490	B1	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related reference documentation.	99-0729	08/25/1999  	No Data	
253	IMS-0320	Complete	The ECS Standard Product related metadata shall contain:    a. Identifiers for locating products in the ECS archive by granule    b. Key organizations and personnel for all product-related DAACs, ADCs, and ODCs    c. Granule-specific information	2701	S-IOS-00860	A	The ADSRV CI shall have the capability to contain advertisements that include key organizations and personnel for all product-related DAACs, ADCs, and ODCs.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2050	S-DSS-04372	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Navigation Data, including Spacecraft Orbit and Attitude Data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2051	S-DSS-04374	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Browse Data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2052	S-DSS-04375	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Ancillary Data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2053	S-DSS-04378	B0	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related QA and validation Data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2058	S-DSS-04400	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Calibration Data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2059	S-DSS-04420	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Instrument Engineering Data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2060	S-DSS-04450	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related Production History Data, including data generation software and its associated parameters and input data.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2061	S-DSS-04470	A	The SDSRV CI shall store and maintain Granult Inventory Metadata that identifies the data production facility for the product.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2062	S-DSS-04480	A	The SDSRV CI shall store and maintain Granule Inventory Metadata that references granule-related QA Statistics.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2301	S-DSS-30270	6A	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.	99-0729	08/25/1999  	No Data	
254	IMS-0330	Complete	The ECS metadata shall provide a cross reference that relates science data to the following:  a. Calibration data, navigation data, and instrument engineering data  b. Processing algorithms used for data generation  c. Software used for data generation  d. Parameters used for data generation  e. Input data used for data generation  f. The DAAC at which the data was processed  g. QA Data.	2303	S-DSS-30280	6A	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.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	4015	C-CSS-40285	5P	The Subscription Service shall treat a request to insert an event as a request to replace the event if the event already exists	99-0872	09/22/1999  		
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	151	C-CSS-40276	5P	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	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	152	C-CSS-40277	5P	The Subscription Service shall be able to re-execute a replacement command whether or not a previous replacement command succeeded or failed.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	153	C-CSS-40278	5P	The Subscription Service shall return failure notification to the SDSRV CI if an event update is not successful.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	154	C-CSS-40279	5P	The Subscription Service shall pass replace event information in  an  ADSRV CI advertisement, using the ADSRV CI delete and insert interfaces .	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	155	C-CSS-40281	5P	The Subscription Service shall accept and process  advertisement failure notification from the ADSRV CI for ADSRV CI delete and insert interfaces.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	156	C-CSS-40283	5P	The Subscription Service shall preserve any existing subscriptions against events being replaced.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	177	S-DMS-20161	5B	The DDICT CI shall have the capability to accept updated data dictionary entries from the SDSRV CI Data Server.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	320	S-CLS-01570	A	The WKBCH CI shall allow users to enter User Comments in a comments window directly accessible from any open ECS application window on the users desktop.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	450	S-CLS-11100	B1	The WKBCH CI shall accept from the users, user feedback information on product data quality assessment and output it to the DAAC originating the data.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	1358	S-DMS-20690	5B	The DDICT CI shall provide the capability to add a link between a Data Collection and its Information Manager.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	1365	S-DMS-20890	Complete	The DDICT CI shall maintain Valid Values for data elements, where the data element has an enumerated set of values as a constraint.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	1857	S-DSS-00165	A	The SDSRV CI shall update Granule Inventory Metadata as specified by valid Update Metadata Requests.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	1917	S-DSS-00850	A	The SDSRV CI shall utilize a CSS authorization service to verify that a user is authorized to access DSS services and resources.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2027	S-DSS-03750	A	The SDSRV CI shall provide a Data Type Description for each data type listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2029	S-DSS-03780	A	The SDSRV CI shall specify the Attributes and associated Valid Values for the data type in each Data Type Description.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2067	S-DSS-04570	A	The SDSRV CI shall provide the operations staff the capability to add Granule Inventory Metadata for any specified data granules in a special privileged mode.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2068	S-DSS-04580	B1	The SDSRV CI shall provide the operations staff the capability to delete all Granule Inventory Metadata for any specified data granules, in a special privileged mode.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2073	S-DSS-04590	A	The SDSRV CI shall provide the operations staff the capability to modify all Granule Inventory Metadata for any specified data granules in a special privileged mode.	99-0729	08/25/1999  	No Data	
255	IMS-0350	Complete	The ECS shall provide the capability for authorized personnel to add, delete, or modify ECS metadata entries, individually or in groups.	2667	S-IOS-00230	A	The ADSRV CI shall provide the capability  to add, delete, or modify individual Advertisements.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	3973	S-DSS-06127	6B	The SDSRV CI shall provide operations staff with the ability to install Platform, Sensor, Campaign, Instrument, Analysis Source, Contact, and Discipline Topic Keyword attributes by installing the Collection Reference Descriptor.	99-0768	08/25/1999  		
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	3974	S-DSS-06128	6B	The SDSRV CI shall provide operations staff with the ability to update Platform, Sensor, Campaign, Instrument, Analysis Source, Contact, and Discipline Topic Keyword attributes by updating the Collection Reference Descriptor.	99-0768	08/25/1999  		
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	3975	S-DSS-06129	6B	The SDSRV CI shall provide the operations staff with functionality in the SDSRV Operations Gui to install the collection reference descriptor.	99-0768	08/25/1999  		
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	3976	S-DSS-06130	6B	The SDSRV CI shall provide the operations staff with functionality in the SDSRV Operations Gui to update the collection reference descriptor.	99-0768	08/25/1999  		
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	1	S-DSS-06131	5P	The SDSRV CI shall provide operations staff with the capability to update ESDTs. 	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	2	S-DSS-06100	5P	The SDSRV CI shall update ESDTs using the updated version of the ESDT files provided by operations staff.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	3	S-DSS-06101	5P	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	4	S-DSS-06102	5P	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	5	S-DSS-06103	5P	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	6	S-DSS-06104	5P	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	7	S-DSS-06105	5P	The SDSRV CI shall send additional services to the ADSRV CI when an ESDT is updated by adding services.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	8	S-DSS-06106	5P	The SDSRV CI shall send additional events to SBSRV when an ESDT is updated by adding events.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	9	S-DSS-06107	5P	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	10	S-DSS-06108	5P	The SDSRV CI shall provide operations staff with functionality in the SDSRV Operations GUI to install updated ESDTs.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	11	S-DSS-06109	5P	The SDSRV CI shall recover from and process the resubmittal of a partially completed ESDT update.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	12	S-DSS-06110	5P	The SDSRV CI shall prohibit the use of an ESDT that has partially completed ESDT update in any other service calls.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	13	S-DSS-06111	5P	The SDSRV CI shall validate the updated descriptor as part of the Update ESDT process.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	14	S-DSS-06112	5P	The SDSRV CI shall determine the changes to the updated descriptor as part of the ESDT Update process.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	15	S-DSS-06113	5P	The SDSRV CI shall notify operations staff if there are no differences in a descriptor as part of the ESDT process.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	16	S-DSS-06114	5P	The SDSRV CI shall disable all other services during the ESDT Update process.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	17	S-DSS-06115	5P	The SDSRV CI shall only accept ESDT update requests when the SDSRV is operating in a maintenance mode.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	77	S-DMS-24100	5P	The DDICT CI shall accept a request to update collection and inventory metadata when an ESDT is updated by adding collection metadata.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	78	S-DMS-24110	5P	The DDICT CI shall accept a request to update collection and inventory metadata when an ESDT is updated by adding inventory metadata.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	105	S-DMS-24120	5P	The DDICT CI shall accept the resubmittal of a previously failed update request.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	106	S-IOS-00420	5P	The ADSRV CI shall preserve existing advertisements when updating collection metadata.    	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	136	S-IOS-00430	5P	The ADSRV CI shall treat a duplicate add request for service advertisement data as a replace request.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	137	S-IOS-00440	5P	The ADSRV CI shall accept the resubmittal of a previously failed update request.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	138	S-DSS-06120	5B	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	139	S-DSS-06121	5B	The SDSRV CI shall maintain a list of attributes that can not be updated through the ESDT update process.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	140	S-DSS-06122	5B	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	141	S-DSS-06123	5B	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	142	S-DSS-06124	5B	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	143	S-DSS-06125	5B	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.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	144	S-DSS-06126	5B	The SDSRV CI shall send a command to the ADSRV CI to replace services when an ESDT is updated by updating the service signature.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	177	S-DMS-20161	5B	The DDICT CI shall have the capability to accept updated data dictionary entries from the SDSRV CI Data Server.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	1895	S-DSS-00570	A	The SDSRV CI shall provide the capability for operations staff to update the Metadata Database Schema.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	2027	S-DSS-03750	A	The SDSRV CI shall provide a Data Type Description for each data type listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
256	IMS-0355	5B Partial	The ECS metadata shall be expandable to include additional attributes which are identified during the mission and deemed useful for data search.	2029	S-DSS-03780	A	The SDSRV CI shall specify the Attributes and associated Valid Values for the data type in each Data Type Description.	99-0729	08/25/1999  	No Data	
257	IMS-0356	Future	The ECS shall provide a mechanism to forward EOSDIS directory entries in the appropriate format to the Global Change Master Directory.	2024	S-DSS-03365	A	The SDSRV CI shall supply metadata on collections to the global master change directory in directory interchange format.	99-0729	08/25/1999  	No Data	
257	IMS-0356	Future	The ECS shall provide a mechanism to forward EOSDIS directory entries in the appropriate format to the Global Change Master Directory.	2667	S-IOS-00230	A	The ADSRV CI shall provide the capability  to add, delete, or modify individual Advertisements.	99-0729	08/25/1999  	No Data	
488	IMS-0410	5B	The ECS shall provide a DAAC-configurable, data set-specific Guide URL in the metadata.	4485	S-DSS-01625	5BP	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.     .   	00-0151	05/24/2000  		
488	IMS-0410	5B	The ECS shall provide a DAAC-configurable, data set-specific Guide URL in the metadata.	4486	S-DSS-01630	5BP	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.     	00-0151	05/24/2000  		
488	IMS-0410	5B	The ECS shall provide a DAAC-configurable, data set-specific Guide URL in the metadata.	4487	S-DSS-01635	5BP	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.     	00-0151	05/24/2000  		
488	IMS-0410	5B	The ECS shall provide a DAAC-configurable, data set-specific Guide URL in the metadata.	4490	S-DMS-24080	5BP	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.     	00-0151	05/24/2000  		
488	IMS-0410	5B	The ECS shall provide a DAAC-configurable, data set-specific Guide URL in the metadata.	4491	S-DMS-24085	5BP	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.     	00-0151	05/24/2000  		
488	IMS-0410	5B	The ECS shall provide a DAAC-configurable, data set-specific Guide URL in the metadata.	4492	S-DMS-24090	5BP	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.      	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4485	S-DSS-01625	5BP	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.     .   	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4486	S-DSS-01630	5BP	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.     	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4487	S-DSS-01635	5BP	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.     	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4488	S-DSS-01640	5BP	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.  	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4489	S-DSS-01645	5BP	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  	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4490	S-DMS-24080	5BP	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.     	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4491	S-DMS-24085	5BP	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.     	00-0151	05/24/2000  		
489	IMS-0420	5B	The ECS shall provide to the user, the Guide URL along with data distribution information. This shall be part of the DAAC configurable portion of the data distribution information.	4492	S-DMS-24090	5BP	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.      	00-0151	05/24/2000  		
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	5632	S-DPL-41230	SY3	The DPIU shall populate the Data Pool inventory and warehouse from the XML file.	08-0426	09/29/2008  		
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	5794	S-DPL-21100	SY2	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).	08-0426	09/29/2008  		
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	7795	S-DPL-46450	72	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.]	08-0426	09/29/2008  		
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	415	S-CLS-10750	A	The WKBCH CI shall provide users a search and results interface to search for and view Inventory information based on core metadata attributes.	99-0729	08/25/1999  	No Data	
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	1852	S-DSS-00145	A	The SDSRV CI shall maintain Granule Inventory Metadata for each stored data granule as follows  a.  the Granule ID;  b.  the Logical File Location for each of the granule's constituent file(s)  c.  the Checksum for each of the granule's constituent file(s)  d.  the date and time of storage  e.  all user-searchable metadata for that granule	99-0729	08/25/1999  	No Data	
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	1885	S-DSS-00450	A	The SDSRV CI shall provide Advertisements that indicate the types of data available from the Data Server.	99-0729	08/25/1999  	No Data	
261	IMS-0430	Complete	The ECS shall maintain an on-line inventory with information that individually describes each granule of EOSDIS data, where granule refers to the minimum traceable logical unit of data stored in the archives, as defined by the instrument science team.	1886	S-DSS-00460	A	The SDSRV CI shall provide Advertisements that indicate the services available from the Data Server.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	1339	S-DMS-20160	Complete	The DDICT CI shall have the capability to accept new Data Dictionary Entries from the SDSRV CI Data Server.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	1853	S-DSS-00155	B0	The SDSRV CI shall provide storage for the metadata associated with all data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	2019	S-DSS-03292	B0	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.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	2020	S-DSS-03295	B0	The SDSRV CI shall verify that scientist-provided data and metadata, specified by a valid Data Insert Request, complies with ESDIS approved standards for metadata and file content.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	2021	S-DSS-03305	B0	The SDSRV CI shall store Granule Inventory Metadata, specified by valid Data Insert Request, into the Metadata Database.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	2026	S-DSS-03370	B0	The SDSRV CI shall perform consistency and correctness checks for the  metadata, specified in each valid Data Insert Request.	99-0729	08/25/1999  	No Data	
263	IMS-0450	Complete	The ECS shall accept and validate new and updated metadata for all ECS archive   data which has been inserted at a DAAC.	2066	S-DSS-04530	A	The SDSRV CI shall validate updated Granule Inventory Metadata, specified by Update Metadata Requests, and reject the request if the request fails validation.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	8658	S-DPL-00315	7.21	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.]  	08-0262	06/09/2008  		
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	8659	S-DSS-45211	7.21	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.]  	08-0262	06/09/2008  		
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	329	S-CLS-10005	B0	The WKBCH CI shall provide the capability for users to compose Search Requests based on core metadata attributes.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	330	S-CLS-10010	B1	The WKBCH CI shall provide the capability for users to compose Search Requests based on product specific  attributes.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	405	S-CLS-10650	A	The WKBCH CI shall provide the user the capability to identify Data and services provided by ECS.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	410	S-CLS-10700	A	The WKBCH CI shall provide the user the capability to locate non-ECS data and services interoperable with ECS.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	411	S-CLS-10710	A	The WKBCH CI shall provide the registered user the capability to obtain ECS data and services.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	412	S-CLS-10720	A	Registered users  shall be able to obtain ECS data and services via their corresponding interfaces in the WKBCH CI, provided that the users are authorized for the specific services and/or data.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	418	S-CLS-10780	A	The WKBCH CI shall list Dependent Valid Values to assist users in formulating Search Requests.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	468	S-CLS-11290	B1	The WKBCH CI shall provide a capability to  translate user input Search Criteria into ECS internal query language.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	501	S-CLS-12910	A	The user interface shall not require changes as a result of restructuring any of the data bases provided by the SDSRV CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	626	S-CLS-15670	A	The WKBCH CI shall provide an interface for users to issue data searches and requests using the V0 IMS protocol.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	744	S-CLS-19190	4PY	The WKBCH CI shall send user requests to the MOJO Gateway as messages, which include:  a)  Length of message  b)  Session ID  c)  Request type  d)  Server UR  e)  Other data as required to process the request	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	750	S-CLS-19200	4PY	The WKBCH CI shall accept user request responses from the MOJO Gateway as messages, which include:  a)  Length of       message  b)  Session ID  c)  Request type  d) Result information (request dependent information, e.g., status/status code, notifications, error messages, or data ).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	754	S-CLS-19205	5B	The WKBCH CI shall convert the MOJO Gateway  messages into information/data for user display.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1075	C-CSS-46000	A	The UR mechanism shall allow clients to access ECS object instances, without actually having the instance by providing each object instance with it's own UR.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1078	C-CSS-46030	A	The UR mechanism shall support multiple redundant instances for a UR.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1079	C-CSS-46040	A	The UR mechanism shall provide a way for an external entity, like a person, or an office automation package, to transport the mechanism.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1080	C-CSS-46050	A	The UR mechanism shall provide some human readable information about the object in the external representation.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1081	C-CSS-46060	A	The UR mechanism shall make sure that the external representation is validated so that erroneous ECS object instance are not created.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1083	C-CSS-46080	A	The UR mechanism shall allow a client to have a UR for an encapsulated abstract base class.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1084	C-CSS-46090	A	The UR mechanism shall allow additional concrete specializations of abstract base class to be added without client modification.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1230	C-CSS-65060	B0	The MOJO Gateway shall be capable of distinguishing each request received from users via WKBCH CI messages.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1231	C-CSS-65070	B0	The MOJO Gateway shall receive search requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., SEARCH)  d)  Server Universal Reference.  e)  other data as required by the SDSRV to process the request.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1232	C-CSS-65080	B0	The MOJO Gateway shall forward the search request to the server specified in the WKBCH CI request message.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1233	C-CSS-65090	B0	The MOJO Gateway shall package the search results into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Search results information (e.g., status, notifications, or data).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1234	C-CSS-65100	B0	The MOJO Gateway shall send the search results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1236	C-CSS-65120	B0	The MOJO Gateway shall forward the browse request to the server specified in the WKBCH CI request message Universal Reference(s).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1237	C-CSS-65130	B0	The MOJO Gateway shall package the browse results into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Browse results information (e.g., status, notifications, and data).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1238	C-CSS-65140	B0	The MOJO Gateway shall send the browse results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1240	C-CSS-65160	B0	The MOJO Gateway shall forward the acquire request to the server specified in the WKBCH CI request message Universal Reference(s).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1241	C-CSS-65170	B0	The MOJO Gateway shall package the acquire results into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Acquire results information (e.g., status, notifications, and data)	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1242	C-CSS-65175	B0	The MOJO Gateway shall send the acquire results to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1244	C-CSS-65190	B0	The MOJO Gateway shall forward the order creation requests to the MSS Management Software CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1245	C-CSS-65194	B0	The MOJO Gateway shall package the order creation results into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Order creation results information (e.g., status, notifications, or data).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1248	C-CSS-65210	B0	The MOJO Gateway shall forward the order status requests to the MSS Management Software CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1249	C-CSS-65214	B0	The MOJO Gateway shall package the order status results into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Order status results information (e.g., status, notifications, or data).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1251	C-CSS-65220	B0	The MOJO Gateway shall receive price estimate requests from the WKBCH CI as a message, which includes:  a)  Length of message  b)  Session ID  c)  Request type (i.e., PRICE ESTIMATE)  d)  Other data as required from the Price Estimate Server to process the request.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1252	C-CSS-65230	B0	The MOJO Gateway shall forward the price estimate request to the MSS Management Software CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1253	C-CSS-65240	B0	The MOJO Gateway shall package the price estimate into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Price estimate information (e.g., price estimate or status).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1256	C-CSS-65270	B1	The MOJO Gateway shall forward service requests to the server specified in the message from the WKBCH CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1261	C-CSS-65320	B0	The MOJO Gateway shall package the user profile into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  User profile information (i.e., profile information and status).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1262	C-CSS-65330	B0	The MOJO Gateway shall send the user profile information and status  to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1265	C-CSS-65360	B0	The MOJO Gateway shall package the user profile updates into a message for the WKBCH CI which includes:  a)  Length of message  b)  Session ID  c)  Updated user profile information (i.e., profile information and status)  d)  Status (ok, not ok).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1268	C-CSS-65390	B0	The MOJO Gateway shall forward the subscription request to the CSS DCCI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1272	C-CSS-65400	B0	The MOJO Gateway shall forward the advertising query request to the ADSRV CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1273	C-CSS-65403	B0	The MOJO Gateway shall package the advertising query results into a message for the WKBCH CI, which includes:  a)  Length of message  b)  Session ID  c)  advertisement information (data or service).	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1276	C-CSS-65410	B1	The MOJO Gateway shall forward the data dictionary query request to the DDICT CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1281	C-CSS-65530	B0	The MOJO Gateway shall package the MOJO session validation result into a message for the WKBCH CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1282	C-CSS-65535	B0	The MOJO Gateway shall send the session validation results to the WKBCH CI.	99-0729	08/25/1999  	No Data	
266	IMS-0550	Complete	The ECS shall allow a user to locate and identify desired data without detailed knowledge of the system:  a. Architecture  b. Data Base management system  c. Data Base structure  d. Query languages  e. Data formats	1298	C-CSS-65655	B0	The MOJO Gateway shall send the status code to the WKBCH CI as a message.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4607	S-DSS-00186	BP	The SDSRV shall support the definition of predefined spatial extents to aid in spatial searching.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4608	S-DSS-00187	BP	The SDSRV shall provide capabilities to populate the SDSRV DsMdOrbitPolygons table with polygon definitions for an instrument.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4609	S-DSS-00188	BP	The SDSRV shall support predefined spatial extents that are associated with a specific instrument and platform.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4610	S-DSS-00189	BP	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.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4611	S-DSS-00190	BP	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.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4612	S-DSS-00192	BP	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.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4613	S-DSS-00193	BP	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	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4614	S-DSS-00194	BP	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.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	4615	S-DSS-00195	BP	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.	01-0147	02/21/2001  		
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	355	S-CLS-10190	B1	The WKBCH CI shall provide the capability for users to compose searches across multiple data sets for coincident occurrences of data in space, time, or any other searchable core Metadata attribute(s).	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	432	S-CLS-10910	A	The  WKBCH CI shall  provide users the capability to transparently search across any combination of Data Servers for stored EOSDIS Data Granules.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	433	S-CLS-10920	B1	The WKBCH CI shall provide users the capability to search inventory based on any combination of the inventory product specific metadata attributes.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	434	S-CLS-10930	B0	The WKBCH CI shall provide users the capability to search inventory  based on any combination of the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	471	S-CLS-12480	B0	The WKBCH CI shall provide the capability to request browse and order services available for the granules in the inventory search results.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	1858	S-DSS-00170	A	The SDSRV CI shall accept and process Search Requests to search the Granule Inventory Metadata for the data types listed in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	2076	S-DSS-04660	A	The SDSRV CI shall, as a result of processing a valid Search Request, provide the requesting client access to the matching search attributes and the Universal Reference for each data granule found during the search.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	2077	S-DSS-04690	A	The SDSRV CI shall process Search Requests for searches on either Core Granule Inventory Metadata or Product-Specific Granule Inventory Metadata, or a combination of both.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	2079	S-DSS-04710	A	The SDSRV CI shall notify the requesting client that no data granules were found, in the event that no data granules match the search criteria specified in a valid Search Request.	99-0729	08/25/1999  	No Data	
267	IMS-0610	Complete	The ECS shall provide the capability to search the data inventory which describes each granule of EOSDIS data.	2653	S-IOS-00030	A	The ADSRV CI shall contain and maintain information that describes ECS data and services in addition to external provider data and services.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	168	S-CLS-20090	5B	The ODFRM CI shall reject any ASTER L1B on-demand product order from an unauthorized user.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	3997	S-CLS-20002	5B	The ODFRM CI shall accept one ASTER L1A or L1B granule ID as input to a DEM on-demand product order	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	3998	S-CLS-20004	5B	The ODFRM CI shall accept one GDS  L1A granule ID as input to an on-demand product order for a non-standard L1B Product.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	3999	S-CLS-20005	5B	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.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4012	S-CLS-20185	5B	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.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4014	S-CLS-20195	5B	The ODFRM CI shall provide a user login prompt	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4017	S-DMS-30413	5B	The GTWAY CI shall have the capability to process ftp push Product Requests.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4018	S-DMS-30414	5B	The GTWAY CI shall receive ftp Product Requests from the V0 IMS, using protocols defined in the V0/ECS ICD.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4019	S-DMS-30415	5B	The GTWAY CI shall send ftp push Product Requests to the SDSRV CI.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4020	S-DMS-30416	5B	The GTWAY CI shall receive ftp push Product Request Results from the SDSRV CI.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4021	S-DMS-30417	5B	The GTWAY CI shall return ftp push Product Request Results to the V0 IMS using protocols defined in the V0/ECS ICD.	99-0872	09/22/1999  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4178	S-DMS-30442	6A	The GTWAY CI shall process Inventory Search Requests against non-science collections.	00-0174	02/23/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4179	S-DMS-30443	6A	The GTWAY CI shall submit product orders for non-science data to the SDSRV CI.	00-0174	02/23/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4268	C-MSS-75085	5B	The MSS accountability management service shall only allow read-access of User Profiles at the DAACs.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4269	C-MSS-75086	5B	The MSS accountability management service shall replicate User Profiles from the SMC to the DAACs.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4270	C-MSS-75087	5B	The MSS accountability management service shall be capable of identifying the homeDAAC of an operator accessing the user profile database.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4271	C-MSS-75088	5B	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.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4272	C-MSS-75089	5B	The MSS accountability management service shall allow User Profile updates at the SMC only by DAAC personnel from the assigned User Profile homeDAAC.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4273	C-MSS-75095	5B	The MSS accountability management service shall allow the SMC operator to approve user profile registration requests on behalf of any DAAC.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4274	C-MSS-75096	5B	The MSS accountability management service shall allow the SMC operator to perform user profile updates on behalf of any DAAC.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4275	C-MSS-75097	5B	The MSS accountability management service shall be able to identify and recover from a loss of replicate transactions.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4276	C-MSS-75098	5B	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.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4277	C-MSS-75099	5B	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.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4278	C-MSS-75100	5B	The MSS accountability management service shall alert the DAAC operations staff when replication-related servers fail.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4279	C-MSS-75101	5B	The MSS accountability management service shall disable a user's account when the account has been disabled at the user's designated homeDAAC.	00-0096	02/07/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4477	S-DMS-30431	6A	The GTWAY CI shall always return a configurable set of attributes in the inventory search results that are required by the V0 client.	00-0434	04/26/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4479	S-DMS-30379	5BP	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.	00-0518	05/17/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4480	S-DMS-30380	5BP	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.	00-0518	05/17/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4481	S-DMS-30382	5BP	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.	00-0518	05/17/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4482	S-DMS-30383	5BP	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.	00-0518	05/17/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4483	S-DMS-30385	5BP	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.	00-0518	05/17/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4484	S-DMS-30386	5BP	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.	00-0518	05/17/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4493	S-DMS-24095	5BP	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.    	00-0151	05/24/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4523	S-DSS-06750	6B	The SDSRV CI shall provide a capability to return the inventory search results in one or more data chunks of a specified size.	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4524	S-DSS-06752	6B	The SDSRV CI shall provide a capability to accept a chunk size to be used in packaging the inventory search results into data chunks.	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4525	S-DSS-06754	6B	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. 	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4526	S-DSS-06756	6B	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. 	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4527	S-DSS-06758	6B	The SDSRV CI shall use a default chunk size in packaging the inventory search results if no chunk size is provided by the client.	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4528	S-DSS-06760	6B	The SDSRV CI shall allow the default chunk size to be a configurable parameter. 	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4530	S-DSS-06764	6B	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.	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4531	S-DSS-06766	6B	The SDSRV CI shall provide a capability to turn off inventory result-set chunking.	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4532	S-DMS-33040	6B	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. 	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	4533	S-DMS-33041	6B	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.	00-0745	07/25/2000  		
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	56	S-PLS-04095	5B	 The PLANG CI shall register all on-demand product requests with the ECS order tracking database as on-demand orders and requests.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	57	S-PLS-04096	5B	 The PLANG CI shall initialize the status of an ASTER higher level ODPR request as "Queued".	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	58	S-PLS-04097	5B	 The PLANG CI shall initialize the status of a DEM request as "Queued".	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	73	S-PLS-04098	5B	 The PLANG CI shall initialize the status of an L1B request as "Queued".	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	109	S-DMS-20937	5B	The DDICT CI shall send ECS Core and Product Specific Attribute definitions to the V0 IMS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	157	S-CLS-20000	5B	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	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	158	S-CLS-20200	5B	The ODFRM CI shall accept one or more GDS ASTER L1A granule IDs as input to an L1B on-demand product order.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	159	S-CLS-20010	5B	The ODFRM CI shall accept as input from the user ASTER on-demand processing parameter values.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	160	S-CLS-20030	5B	The ODFRM CI shall apply the same ASTER on-demand processing parameters for all granules in an ASTER on-demand product order.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	161	S-CLS-20040	5B	The ODFRM CI shall display valid values for ASTER on-demand processing parameters that have a limited set of values.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	162	S-CLS-20050	5B	The ODFRM CI shall display default values for ASTER on-demand processing parameters and apply them if the user does not override these values.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	163	S-CLS-20060	5B	The ODFRM CI shall send the on-demand product request to the ODPRM CI using ODPRMs DCE client I/F	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	164	S-CLS-20070	5B	The ODFRM CI shall allow the user to specify media distribution options for any ASTER on-demand product orders except ASTER L1B.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	165	S-CLS-20190	5B	The ODFRM CI shall allow the media distribution options to be configurable by a DAAC operator.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	166	S-CLS-20180	5B	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.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	167	S-CLS-20080	5B	The ODFRM CI shall verify all user inputs relating to ASTER on-demand processing and return the status of that input to the user.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	169	S-CLS-20100	5B	The ODFRM CI shall assign configurable priorities to all on-demand product orders.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	174	S-CLS-20160	5B	The ODFRM CI shall submit all on-demand DEM product orders to an ECS operator after getting the OrderId from the ODPRM.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	175	S-CLS-20170	5B	The ODFRM CI shall send an email notification to the user upon submission of the ASTER on-demand product order.	99-0872	09/22/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	186	S-DMS-20936	5P	The DDICT CI shall send AM-1 ECS Core and Product Specific Attributes with the Dependent Valid Values exported to the V0 IMS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	187	S-DMS-20938	5P	The DDICT CI shall send AM-1 ECS Core and Product Specific Attribute definitions to the V0 IMS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	190	S-DMS-30370	Complete	The GTWAY CI shall accept Landsat 7 Product Specific Attributes as search criteria in an Inventory Search Request.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	191	S-DMS-30371	5B	The GTWAY CI shall accept ECS Core and/or Product Specific Attributes in an Inventory Search Request.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	192	S-DMS-30373	Complete	The GTWAY CI shall send Landsat 7 Product Specific Attributes in the Inventory Search Results.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	193	S-DMS-30376	5B	The GTWAY CI shall send ECS Core and/or Product Specific Attributes in the Inventory Search Results.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	194	S-DMS-30378	Complete	The GTWAY CI shall send the maximum cost of Landsat 7 Level 0R floating scenes in the packaging information returned with an Inventory Search Result.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	195	S-DMS-30381	Complete	The GTWAY CI shall read Landsat 7 Level 0R fixed scene price estimates from a configuration parameter to include in the packaging information returned with an Inventory Search Result.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	196	S-DMS-30384	5B	The GTWAY CI shall have the capability to process V0 Integrated Browse Requests.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	197	S-DMS-30387	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	198	S-DMS-30388	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	199	S-DMS-30389	5B	The GTWAY CI shall calculate the Price Estimate for Landsat 7 Level 0R floating scenes.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	200	S-DMS-30397	5B	The GTWAY CI shall send Integrated Browse Requests to the SDSRV CI.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	201	S-DMS-30398	5B	The GTWAY CI shall receive Integrated Browse Results from the SDSRV CI.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	202	S-DMS-30399	5B	The GTWAY CI shall return Integrated Browse Results to the V0 IMS using protocols defined in the V0/ECS ICD	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	203	S-DMS-30409	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	204	S-DMS-30412	5B	The GTWAY CI shall send Landsat 7 Level 0R floating scene subsetting parameters included in a Product Request to the SDSRV.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	206	S-DMS-30432	6A	The GTWAY CI shall accept requests for Inventory Search Results without spatial or temporal attributes using V0 protocols defined in the V0/ECS ICD.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	207	S-DMS-30433	6A	The GTWAY CI shall process requests for Inventory Search Requests against ECS collections containing granules without spatial or temporal metadata.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	208	S-DMS-30434	6A	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	209	S-DMS-30435	6A	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	210	S-DMS-30436	6A	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	211	S-DMS-30437	6A	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	212	S-DMS-30438	6A	The GTWAY CI shall process requests specifying that the DEFAULT set of granule level attributes shall be included in the Inventory Search Results.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	213	S-DMS-30439	6A	The GTWAY CI shall allow DAAC operators to configure the granule level attributes included in the default list.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	214	S-DMS-30440	6A	The GTWAY CI shall process requests specifying that the FULL set of granule level attributes shall be included in the Inventory Search Results. 	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	215	S-DMS-30441	6A	The GTWAY CI shall process requests specifying the set of granule level attributes that shall be included in the Inventory Search Results.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	249	S-DMS-42190	5B	The GTWAY CI shall accept a granule ID in an Inventory Search Request.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	250	S-DMS-42200	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	251	S-DMS-42210	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	252	S-DMS-42220	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	253	S-DMS-42230	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	254	S-DMS-42240	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	255	S-DMS-42260	5B	The GTWAY CI shall send Landsat 7 Level 0R BAND subsetting parameters included in a Product Request to the SDSRV.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	256	S-DMS-42270	5B	The GTWAY CI shall send Landsat 7 Level 0R non-image subsetting parameters included in a Product Request to the SDSRV.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	257	S-DMS-42280	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	258	S-DMS-42290	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	259	S-DMS-42300	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	260	S-DMS-20934	5B	The DDICT CI shall send ECS Core and Product Specific Attributes with the Dependent Valid Values exported to the V0 IMS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	622	S-CLS-15630	A	The WKBCH CI shall have the capability to send  Requests for Guide data to the ESDIS V0 IMS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	623	S-CLS-15640	A	The WKBCH CI shall have the capability to receive Guide Request Results from the ESDIS V0 IMS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	624	S-CLS-15650	B0	The WKBCH CI shall determine the appropriate ECS GTWAY to send requests for ECS products.  	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	678	S-CLS-18000	A	The WKBCH CI shall have the capability to send  Inventory Search Requests using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	679	S-CLS-18010	A	The WKBCH CI shall have the capability to receive  Inventory Search Request Results using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	680	S-CLS-18020	A	The WKBCH CI shall have the capability to send Directory Search Requests using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	681	S-CLS-18030	A	The WKBCH CI shall have the capability to receive Directory Search Requests results using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	682	S-CLS-18040	A	The WKBCH CI shall have the capability to send Browse Search Requests using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	683	S-CLS-18045	A	The WKBCH CI shall have the capability to receive  Browse Search Requests Results using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	684	S-CLS-18050	A	The WKBCH CI shall have the capability to send Product Requests using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1314	S-DMS-01010	5B	The LIMGR CI shall log all Service requests initiated during a session.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1336	S-DMS-20130	Complete	The DDICT CI shall accept  search requests consisting of any combination of the following:  Data Collections, Core and Product Specific Metadata attribute domains and definitions.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1377	S-DMS-30350	Complete	The ECS-V0 Component of the GTWAY CI shall have the capability to send Product Requests to the Version 0 IMS using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1378	S-DMS-30368	Complete	The GTWAY CI shall have the capability to process V0 Inventory Search Requests.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1379	S-DMS-30372	Complete	The GTWAY CI shall send directory search results to the Version 0 Client using Version 0 protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1380	S-DMS-30374	Complete	The GTWAY CI shall receive directory search requests from the Version 0 Client using Version 0 protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1381	S-DMS-30375	Complete	The GTWAY CI shall send inventory search results to the Version 0 Client using Version 0 protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1382	S-DMS-30392	Complete	The GTWAY CI shall receive inventory search requests from the Version 0 Client using Version 0 protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1383	S-DMS-30395	Complete	The GTWAY CI shall receive authentication information with each request from the Version 0 Client using Version 0 protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1384	S-DMS-30396	5B	The GTWAY CI shall receive Integrated Browse Requests from the V0 IMS, using protocols defined in the V0/ECS ICD.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1385	S-DMS-30404	Complete	The GTWAY CI shall have the capability to process V0 Product Requests.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1386	S-DMS-30406	Complete	The GTWAY CI shall receive Product Requests from the Version 0 IMS using Version 0 protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1387	S-DMS-30408	Complete	The GTWAY CI shall have the capability to send Product Request acknowledgements to the V0 Client using Version 0 system protocols.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1388	S-DMS-30540	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1390	S-DMS-30550	5B	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.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1396	S-DMS-31015	5B	The ECS-V0 Component of the GTWAY CI shall log when an external connection to the LPDS has been established.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1397	S-DMS-31016	5B	The ECS-V0 Component of the GTWAY CI shall log when the component service request has been submitted to the LPDS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	1398	S-DMS-31017	5B	The ECS-V0 Component of the GTWAY CI shall log when the request to the LPDS has been successfully returned.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	2657	S-IOS-00080	A	The ADSRV CI shall provide a capability to access Advertisements for ECS and non-ECS data and services.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	2676	S-IOS-00510	A	The ADSRV CI shall report Accountability Management Data (such as searches, advertisement submissions, etc.) to the MSS.	99-0729	08/25/1999  	No Data	
268	IMS-0625	5A 5B 6A 6B	The ECS shall support V0 requests for    a. Access to ECS inventory metadata (including ECS core and product specific metadata attributes) and browse data    b. Ordering of data products    c. User profile information    d. Production history    e. Science software    f.  ancillary information     g. DAAC-configurable, dataset-specific disclaimers provided as part of an inventory search result	3524	S-PLS-00604	B0	The PLANG CI shall be able to access advertisements for ECS and non-ECS data and services from the IOS.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	333	S-CLS-10030	A	The WKBCH CI shall provide graphical aids to assist users in formulating Search Requests.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	334	S-CLS-10040	A	The WKBCH CI shall allow users to specify geographic reference parameters (i.e., sets of coordinates) as metadata search criteria.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	335	S-CLS-10050	A	The WKBCH CI shall support  query of  geographic Metadata by  data element content criteria specified in Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	337	S-CLS-10060	A	The WKBCH CI shall support a minimum bounding rectangle criteria for query of geographic Metadata by text input.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	338	S-CLS-10062	B1	The WKBCH CI shall support a minimum bounding rectangle criteria for query of geographic Metadata by graphical input.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	340	S-CLS-10070	B1	The WKBCH CI shall support point-and-radius criteria for query of geographic Metadata by graphical input.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	343	S-CLS-10080	B0	The WKBCH CI shall support up to four sided polygons coordinate criteria for query of geographic Metadata by text and graphical input.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	344	S-CLS-10082	B1	The WKBCH CI shall support polygonal coordinate criteria for query of geographic Metadata by text and graphical input.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	346	S-CLS-10100	A	The WKBCH CI shall support phrase matching criteria for query of alpha-numeric non-geographic guide Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	347	S-CLS-10110	A	The WKBCH CI shall support an exact word matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	348	S-CLS-10120	A	The WKBCH CI shall support character set (string) matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	349	S-CLS-10130	B1	The WKBCH CI shall provide users the capability to use boolean operators to relate query parameters for geographic and non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	350	S-CLS-10140	B1	The WKBCH CI shall support wildcard construct (prefix, embedded, suffix)  matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	351	S-CLS-10150	B1	The WKBCH CI shall support character range matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	352	S-CLS-10160	B1	The WKBCH CI shall support logical and boolean operators  matching criteria for query of alpha-numeric  non-geographic ( non-spatial ) Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	353	S-CLS-10170	B1	The WKBCH CI shall support min/max range Search Criteria for query of  numerical non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	354	S-CLS-10180	B1	The WKBCH CI shall support any combination with logical and boolean operators of exact word match, exact phrase match, character set, wildcard, character range, and min/max range as Search Criteria for query of  non-geographic Metadata.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	418	S-CLS-10780	A	The WKBCH CI shall list Dependent Valid Values to assist users in formulating Search Requests.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	433	S-CLS-10920	B1	The WKBCH CI shall provide users the capability to search inventory based on any combination of the inventory product specific metadata attributes.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	434	S-CLS-10930	B0	The WKBCH CI shall provide users the capability to search inventory  based on any combination of the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	666	S-CLS-17060	A	The WKBCH CI shall support the selection of metadata using "and" and "or" boolean operators.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	667	S-CLS-17070	A	The WKBCH CI shall support the selection of metadata using relational operators for spatial and temporal search parameters.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	1336	S-DMS-20130	Complete	The DDICT CI shall accept  search requests consisting of any combination of the following:  Data Collections, Core and Product Specific Metadata attribute domains and definitions.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	1337	S-DMS-20134	Complete	The DDICT CI shall accept search requests in a parameter = value format.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	2689	S-IOS-00690	B1	The ADSRV CI shall accept Search Requests in a format compatible with the Earth Science Query Language.	99-0729	08/25/1999  	No Data	
271	IMS-0630	Complete	The ECS shall provide the capability to select metadata for retrieval by:  a. Boolean operators  b. Relational operators  c. Attribute values  d. Combinations thereof	2693	S-IOS-00770	A	The ADSRV CI shall be able to provide attributes of the Advertisements to be selected by a Search Request or an Advertisement Request.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4607	S-DSS-00186	BP	The SDSRV shall support the definition of predefined spatial extents to aid in spatial searching.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4608	S-DSS-00187	BP	The SDSRV shall provide capabilities to populate the SDSRV DsMdOrbitPolygons table with polygon definitions for an instrument.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4609	S-DSS-00188	BP	The SDSRV shall support predefined spatial extents that are associated with a specific instrument and platform.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4610	S-DSS-00189	BP	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.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4611	S-DSS-00190	BP	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.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4612	S-DSS-00192	BP	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.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4613	S-DSS-00193	BP	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	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4614	S-DSS-00194	BP	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.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	4615	S-DSS-00195	BP	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.	01-0147	02/21/2001  		
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	102	S-DSS-00181	5B	The SDSRV CI shall provide spatial search constraints based upon LLBOX spatial extents.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	103	S-DSS-00182	5B	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).	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	104	S-DSS-00183	5B	The SDSRV CI shall provide storage of LLBOX spatial extents.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	107	S-DSS-00184	5B	The SDSRV CI shall support LLBOX search constraints that cross the +180 degrees to -180 degrees longitude discontinuity.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	108	S-DSS-00185	5B	The SDSRV CI shall support LLBOX interpretation of existing Metadata stored with the BoundingRectangle datatype.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	145	S-DSS-00171	5B	The SDSRV CI shall provide spatial searching with polygonal search areas.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	146	S-DSS-00172	5B	The SDSRV CI shall  provide storage of polygonal (store Gpolygon) spatial extents.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	147	S-DSS-00173	5B	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.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	148	S-DSS-00174	5B	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.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	149	S-DSS-00175	5B	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.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	262	S-DSS-00177	5B	The SDSRV CI shall assume orient polygon points are in a clockwise direction when inserting and distributing polygon metadata data.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	329	S-CLS-10005	B0	The WKBCH CI shall provide the capability for users to compose Search Requests based on core metadata attributes.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	330	S-CLS-10010	B1	The WKBCH CI shall provide the capability for users to compose Search Requests based on product specific  attributes.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	334	S-CLS-10040	A	The WKBCH CI shall allow users to specify geographic reference parameters (i.e., sets of coordinates) as metadata search criteria.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	335	S-CLS-10050	A	The WKBCH CI shall support  query of  geographic Metadata by  data element content criteria specified in Metadata.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	336	S-CLS-10055	B0	The WKBCH CI shall allow users to query geographic metadata using attribute values based on WRS.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	337	S-CLS-10060	A	The WKBCH CI shall support a minimum bounding rectangle criteria for query of geographic Metadata by text input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	338	S-CLS-10062	B1	The WKBCH CI shall support a minimum bounding rectangle criteria for query of geographic Metadata by graphical input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	340	S-CLS-10070	B1	The WKBCH CI shall support point-and-radius criteria for query of geographic Metadata by graphical input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	341	S-CLS-10075	B0	The WKBCH CI shall support point criteria for query of geographic Metadata by text input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	342	S-CLS-10076	B0	The WKBCH CI shall support point criteria for query of geographic Metadata by graphical input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	343	S-CLS-10080	B0	The WKBCH CI shall support up to four sided polygons coordinate criteria for query of geographic Metadata by text and graphical input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	344	S-CLS-10082	B1	The WKBCH CI shall support polygonal coordinate criteria for query of geographic Metadata by text and graphical input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	345	S-CLS-10090	B1	The WKBCH CI shall support  query of  geographic Metadata by  geographic name by text input.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	349	S-CLS-10130	B1	The WKBCH CI shall provide users the capability to use boolean operators to relate query parameters for geographic and non-geographic Metadata.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	355	S-CLS-10190	B1	The WKBCH CI shall provide the capability for users to compose searches across multiple data sets for coincident occurrences of data in space, time, or any other searchable core Metadata attribute(s).	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	433	S-CLS-10920	B1	The WKBCH CI shall provide users the capability to search inventory based on any combination of the inventory product specific metadata attributes.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	434	S-CLS-10930	B0	The WKBCH CI shall provide users the capability to search inventory  based on any combination of the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	605	S-CLS-14430	B0	The WKBCH CI DAR Tool shall synchronize geographic selection criteria for DARs so that typing latitude/longitude coordinates in a DAR submission window will be graphically displayed as a bounded area on a DAR map display.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	611	S-CLS-14500	B0	Geographic selection criteria for a Search Request shall be synchronized so that selection of an area on a Search Request map display will be translated into lat/lon coordinates in a Search Request submissions window.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	612	S-CLS-14510	B1	The WKBCH CI shall synchronize geographic selection criteria for a Search so that typed lat/long coordinates in a Search Request submission window will be graphically displayed as a blocked out area on a Search Request map display.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	648	S-CLS-15940	B0	The WKBCH CI shall provide users the capability to search for global granules.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	725	S-CLS-19139	5B	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).  	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	774	S-CLS-19242	5B	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.	99-0729	08/25/1999  	No Data	
272	IMS-0640	5B Partial	The ECS shall provide the capability to query geographic metadata by any of the following criteria at a minimum:    a. Geographic reference    b.  Minimum bounding rectangle    c.  Point and radius    d.  Polygon    e.   Any combination that allows for specification of multiple, distinct geographic areas	775	S-CLS-19244	5B	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.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	346	S-CLS-10100	A	The WKBCH CI shall support phrase matching criteria for query of alpha-numeric non-geographic guide Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	347	S-CLS-10110	A	The WKBCH CI shall support an exact word matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	348	S-CLS-10120	A	The WKBCH CI shall support character set (string) matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	349	S-CLS-10130	B1	The WKBCH CI shall provide users the capability to use boolean operators to relate query parameters for geographic and non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	350	S-CLS-10140	B1	The WKBCH CI shall support wildcard construct (prefix, embedded, suffix)  matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	351	S-CLS-10150	B1	The WKBCH CI shall support character range matching criteria for query of alpha-numeric non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	352	S-CLS-10160	B1	The WKBCH CI shall support logical and boolean operators  matching criteria for query of alpha-numeric  non-geographic ( non-spatial ) Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	353	S-CLS-10170	B1	The WKBCH CI shall support min/max range Search Criteria for query of  numerical non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	354	S-CLS-10180	B1	The WKBCH CI shall support any combination with logical and boolean operators of exact word match, exact phrase match, character set, wildcard, character range, and min/max range as Search Criteria for query of  non-geographic Metadata.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	355	S-CLS-10190	B1	The WKBCH CI shall provide the capability for users to compose searches across multiple data sets for coincident occurrences of data in space, time, or any other searchable core Metadata attribute(s).	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	418	S-CLS-10780	A	The WKBCH CI shall list Dependent Valid Values to assist users in formulating Search Requests.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	1336	S-DMS-20130	Complete	The DDICT CI shall accept  search requests consisting of any combination of the following:  Data Collections, Core and Product Specific Metadata attribute domains and definitions.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	1337	S-DMS-20134	Complete	The DDICT CI shall accept search requests in a parameter = value format.	99-0729	08/25/1999  	No Data	
273	IMS-0650	Complete	The ECS shall query non-geographic metadata by any of the following criteria:  a. Exact word match  b. Min/max range search  c. And combinations of the above with Logical and Boolean operators	2689	S-IOS-00690	B1	The ADSRV CI shall accept Search Requests in a format compatible with the Earth Science Query Language.	99-0729	08/25/1999  	No Data	
274	IMS-0660	Complete	The ECS shall provide inventory metadata search based on any combination of the core metadata and where applicable dataset-specific inventory metadata attributes.	433	S-CLS-10920	B1	The WKBCH CI shall provide users the capability to search inventory based on any combination of the inventory product specific metadata attributes.	99-0729	08/25/1999  	No Data	
274	IMS-0660	Complete	The ECS shall provide inventory metadata search based on any combination of the core metadata and where applicable dataset-specific inventory metadata attributes.	434	S-CLS-10930	B0	The WKBCH CI shall provide users the capability to search inventory  based on any combination of the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
274	IMS-0660	Complete	The ECS shall provide inventory metadata search based on any combination of the core metadata and where applicable dataset-specific inventory metadata attributes.	649	S-CLS-15950	B1	The WKBCH CI shall provide users the capability to set thresholds for the number of results returned from a query.	99-0729	08/25/1999  	No Data	
274	IMS-0660	Complete	The ECS shall provide inventory metadata search based on any combination of the core metadata and where applicable dataset-specific inventory metadata attributes.	1336	S-DMS-20130	Complete	The DDICT CI shall accept  search requests consisting of any combination of the following:  Data Collections, Core and Product Specific Metadata attribute domains and definitions.	99-0729	08/25/1999  	No Data	
274	IMS-0660	Complete	The ECS shall provide inventory metadata search based on any combination of the core metadata and where applicable dataset-specific inventory metadata attributes.	2077	S-DSS-04690	A	The SDSRV CI shall process Search Requests for searches on either Core Granule Inventory Metadata or Product-Specific Granule Inventory Metadata, or a combination of both.	99-0729	08/25/1999  	No Data	
275	IMS-0680	Complete	The ECS shall provide data order capabilities integrated with metadata search capabilities.	358	S-CLS-10220	B0	The WKBCH CI shall allow users to formulate a Product Request based on the results of searching the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
275	IMS-0680	Complete	The ECS shall provide data order capabilities integrated with metadata search capabilities.	359	S-CLS-10225	B1	The WKBCH CI shall allow users to formulate a Product Request based on the results of searching the inventory product specific metadata attributes.	99-0729	08/25/1999  	No Data	
275	IMS-0680	Complete	The ECS shall provide data order capabilities integrated with metadata search capabilities.	471	S-CLS-12480	B0	The WKBCH CI shall provide the capability to request browse and order services available for the granules in the inventory search results.	99-0729	08/25/1999  	No Data	
275	IMS-0680	Complete	The ECS shall provide data order capabilities integrated with metadata search capabilities.	2681	S-IOS-00600	A	The ADSRV CI shall provide the clients with a binding to the advertisement which can be used to issue Service Requests to the selected service or use the reference to the service in a Universal Reference	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	191	S-DMS-30371	5B	The GTWAY CI shall accept ECS Core and/or Product Specific Attributes in an Inventory Search Request.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	193	S-DMS-30376	5B	The GTWAY CI shall send ECS Core and/or Product Specific Attributes in the Inventory Search Results.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	196	S-DMS-30384	5B	The GTWAY CI shall have the capability to process V0 Integrated Browse Requests.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	200	S-DMS-30397	5B	The GTWAY CI shall send Integrated Browse Requests to the SDSRV CI.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	201	S-DMS-30398	5B	The GTWAY CI shall receive Integrated Browse Results from the SDSRV CI.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	202	S-DMS-30399	5B	The GTWAY CI shall return Integrated Browse Results to the V0 IMS using protocols defined in the V0/ECS ICD	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	366	S-CLS-10290	A	The WKBCH CI shall provide users the capability to browse data in ECS supported visualization formats in a window during the data selection and acquisition process,	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	370	S-CLS-10330	A	The WKBCH CI shall provide users the capability of displaying 8-bit raster images.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	371	S-CLS-10340	A	The WKBCH CI shall provide users the capability of displaying 24-bit raster images.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	373	S-CLS-10360	A	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in table format.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	374	S-CLS-10370	A	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in text format.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	375	S-CLS-10380	A	The WKBCH CI shall provide users the capability to produce an animation loop.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	385	S-CLS-10470	B1	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in vector graphic format.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	551	S-CLS-13580	B1	The WKBCH CI shall provide users the capability to graphically represent data availability for product(s) vs. time.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	552	S-CLS-13590	B1	The WKBCH CI shall provide users the capability to graphically view the temporal extent of Data Granules.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	566	S-CLS-13710	A	The WKBCH CI shall provide users the capability to display on a coverage map the geographic coverage of Data Granules.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	1384	S-DMS-30396	5B	The GTWAY CI shall receive Integrated Browse Requests from the V0 IMS, using protocols defined in the V0/ECS ICD.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	1388	S-DMS-30540	5B	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.	99-0729	08/25/1999  	No Data	
276	IMS-0690	5B Partial	The ECS shall provide the capability to visualize browse data and metadata to facilitate the data selection and ordering process.	1390	S-DMS-30550	5B	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.	99-0729	08/25/1999  	No Data	
502	IMS-0700	5B	The ECS shall be able to provide the science data granule in response to an integrated browse request.	4569	S-DSS-07105	5BP	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. 	00-1110	12/04/2000  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4683	S-SSS-10010	SY3	The NSBRV CI shall allow operators to enter bundling orders.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4686	S-SSS-10040	SY3	The NSBRV CI shall require the operator to associate the userid of a registered ECS user with a bundling order. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4687	S-SSS-10050	SY3	The NSBRV CI shall allow the operator to enter an expiration date for a bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4688	S-SSS-10055	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4689	S-SSS-10070	SY3	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). 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4690	S-SSS-10080	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4691	S-SSS-10090	SY3	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.)	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4692	S-SSS-10100	SY3	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).   	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4693	S-SSS-10110	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4694	S-SSS-10120	SY3	The NSBRV CI shall allow the operator to select a valid ECS physical media type for the bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4695	S-SSS-10125	SY3	The NSBRV CI shall allow the operator to select ftp push or ftp pull as media types for a bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4696	S-SSS-10130	SY3	The NSBRV CI shall allow the operator to enter the distribution options that are valid for the selected media type into a bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4697	S-SSS-10140	SY3	The NSBRV CI shall require the operator to enter all distribution options into a bundling order that are mandatory for the selected media type.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4698	S-SSS-10150	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4700	S-SSS-10170	SY3	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.]	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4701	S-SSS-10175	SY3	The NSBRV CI shall allow operators to configure a default value for the minimum bundle granule count.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4702	S-SSS-10180	SY3	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].	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4703	S-SSS-10190	SY3	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.] 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4704	S-SSS-10195	SY3	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]. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4705	S-SSS-10200	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4706	S-SSS-10210	SY3	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']	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4707	S-SSS-10212	SY3	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. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4708	S-SSS-10220	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4709	S-SSS-10230	SY3	The NSBRV CI shall allow an operator to filter a list of bundling orders by user ID, media type, and current status.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4710	S-SSS-10240	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4711	S-SSS-10250	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4712	S-SSS-10260	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4713	S-SSS-10270	SY3	The NSBRV CI shall allow an operator to select a bundling order from a displayed list of bundling orders for modification.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4714	S-SSS-10280	SY3	The NSBRV CI shall allow the operator to update the userid associated with an existing bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4715	S-SSS-10285	SY3	The NSBRV CI shall propagate an update to the userid of bundling order to all the subscriptions associated with that bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4716	S-SSS-10290	SY3	The NSBRV CI shall allow the operator to update the expiration date associated with an existing bundling order. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4717	S-SSS-10300	SY3	The NSBRV CI shall allow the operator to update the e-mail address associated with an existing bundling order. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4718	S-SSS-10310	SY3	The NSBRV CI shall allow the operator to update the userstring associated with an existing bundling order. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4719	S-SSS-10320	SY3	The NSBRV CI shall allow the operator to update the distribution priority associated with an existing bundling order. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4720	S-SSS-10330	SY3	The NSBRV CI shall allow the operator to modify the media type and distribution options associated with an existing bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4721	S-SSS-10340	SY3	The NSBRV CI shall allow the operator to modify the bundle completion criteria associated with an existing bundling order.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4722	S-SSS-10345	SY3	The NSBRV CI shall ask the operator to confirm the modifications to a bundling order before saving them.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4723	S-SSS-10350	SY3	The NSBRV CI shall preserve the id of a bundling order when it is updated.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4727	S-SSS-10380	SY3	The NSBRV CI shall consider all subscriptions associated with a cancelled bundling order as cancelled.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4728	S-SSS-10390	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4729	S-SSS-10391	SY3	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. 	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4730	S-SSS-10392	SY3	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).	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4731	S-SSS-10394	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4738	S-SSS-10430	SY3	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.]	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4739	S-SSS-10440	SY3	The NSBRV CI command line interface shall permit the viewing of media subscriptions.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4740	S-SSS-10450	SY3	The NSBRV CI command line interface shall permit the editing of media subscriptions.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4741	S-OMS-05010	SY3	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]	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4742	S-OMS-05040	SY3	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.	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	4743	S-OMS-05050	SY3	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]	02-1045	12/04/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5402	S-SSS-00010	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5403	S-SSS-00015	SY2	The NSBRV CI shall store subscription information persistently. 	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5404	S-SSS-00020	SY2	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).	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5405	S-SSS-00030	SY2	The NSBRV CI shall not permit an operator to enter subscriptions for events that are not valid SDSRV events.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5406	S-SSS-00040	SY2	The NSBRV CI shall require an operator to associate a valid ECS userid with a subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5407	S-SSS-00050	SY2	The NSBRV CI shall allow an operator to associate an expiration date with a subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5408	S-SSS-00065	SY2	The NSBRV CI shall assign a unique identification to each subscription.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5409	S-SSS-00066	SY2	The NSBRV CI shall not evaluate subscriptions against ECS events which occur after the expiration date of the subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5410	S-SSS-00070	SY2	The NSBRV CI shall allow the operator to qualify a subscription spatially by specifying one of the following criteria:    a. LLBOX  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5411	S-SSS-00072	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5412	S-SSS-00074	SY2	The NSBRV CI shall allow spatial qualification of a subscription where the underlying ESDT has a gpolygon spatial search type.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5413	S-SSS-00076	SY2	The NSBRV CI shall allow spatial qualification of a subscription where the underlying ESDT has a bounding rectangle spatial search type.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5414	S-SSS-00078	SY2	The NSBRV CI shall allow spatial qualification of a subscription where the underlying ESDT has an orbit spatial search type.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5415	S-SSS-00079	SY2	The NSBRV CI shall not permit an operator to enter a spatial qualification criterion for an ESDT that does not have spatial coverage metadata.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5416	S-SSS-00080	SY2	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.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5417	S-SSS-00082	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5418	S-SSS-00084	SY2	The NSBRV CI shall not permit an operator to enter a temporal qualification criterion for an ESDT that does not have temporal coverage metadata.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5419	S-SSS-00090	SY2	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  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5420	S-SSS-00100	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5421	S-SSS-00110	SY2	The NSBRV CI shall allow the operator to qualify a subscription by values of the following measured parameter attributes:     a. QAPercentCloudCover  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5422	S-SSS-00112	SY2	The NSBRV CI  shall accept a string value as a qualifier for core, product specific, or measured parameter attributes of type string. 	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5423	S-SSS-00113	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5424	S-SSS-00114	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5425	S-SSS-00115	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5426	S-SSS-00116	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5427	S-SSS-00117	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5428	S-SSS-00120	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5429	S-SSS-00122	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5431	S-SSS-00126	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5432	S-SSS-00130	SY2	The NSBRV shall consider a granule to qualify for a subscription if it meets all of the subscription's qualification criteria.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5433	S-SSS-00160	SY2	The NSBRV CI shall allow an email notification action to be associated with a subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5434	S-SSS-00162	SY2	The NSBRV CI shall require the operator to enter one 'to' address for the email notification action.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5435	S-SSS-00164	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5436	S-SSS-00180	SY2	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).	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5437	S-SSS-00185	SY2	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).	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5438	S-SSS-00190	SY2	The NSBRV CI shall allow the operator to specify a userstring to be included in the message text for each email notification.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5439	S-SSS-00200	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5440	S-SSS-00220	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5441	S-SSS-00230	SY2	The NSBRV CI shall embed all selected inventory metadata information in the email text, in parameter=value format, one parameter per line.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5442	S-SSS-00235	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5443	S-SSS-00260	SY2	The NSBRV CI shall allow a distribution action to be associated with a subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5444	S-SSS-00270	SY2	The NSBRV CI shall require the operator to associate the userid of a registered ECS user with a distribution action.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5445	S-SSS-00275	SY2	The NSBRV CI shall provide the userid of the registered ECS user associated with the subscription as the default userid for the distribution action.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5446	S-SSS-00280	SY2	The NSBRV CI shall allow the operator to associate an email address with a distribution action.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5447	S-SSS-00285	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5448	S-SSS-00290	SY2	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.)	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5449	S-SSS-00300	SY2	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).   	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5450	S-SSS-00305	SY2	The NSBRV CI shall provide the distribution priority in the user profile of the userid associated with the subscription as the default distribution priority.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5451	S-SSS-00310	SY2	The NSBRV CI shall allow the operator to select FtpPush distribution.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5452	S-SSS-00320	SY2	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  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5453	S-SSS-00330	SY2	The NSBRV CI shall allow the operator to select FtpPull distribution.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5454	S-SSS-00340	SY2	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  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5455	S-SSS-00380	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5456	S-SSS-00384	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5457	S-SSS-00390	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5458	S-SSS-00395	SY2	The NSBRV CI shall process the action queue in first-in, first-out order.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5459	S-SSS-00440	SY2	The NSBRV CI shall retain information about completed actions, and the completion times associated with each, for an operator-configurable amount of time.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5460	S-SSS-00443	SY2	The NSBRV CI shall process the event queue in first-in first-out order.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5461	S-SSS-00444	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5462	S-SSS-00450	SY2	The NSBRV CI shall allow the operator to update the userid associated with a subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5463	S-SSS-00455	SY2	The NSBRV CI shall allow the operator to update the expiration date associated with a subscription. 	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5464	S-SSS-00460	SY2	The NSBRV CI shall allow the operator to add, modify,or delete qualifications associated with a subscription. 	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5465	S-SSS-00470	SY2	The NSBRV CI shall allow the operator to add, modify, or delete actions associated with an existing subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5466	S-SSS-00480	SY2	The NSBRV CI shall preserve the subscription id when a subscription is updated.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5467	S-SSS-00490	SY2	The NSBRV CI shall allow the operator to suspend an individual subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5468	S-SSS-00520	SY2	The NSBRV CI shall not evaluate a suspended subscription against ECS events which occur after the subscription is suspended.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5469	S-SSS-00530	SY2	The NSBRV CI shall process normally any actions associated with a suspended subscription which were already queued at the time the subscription was suspended.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5470	S-SSS-00540	SY2	The NSBRV CI shall allow the operator to resume a subscription which has been suspended.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5471	S-SSS-00545	SY2	The NSBRV CI shall preserve the subscription id when a subscription is suspended or resumed.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5472	S-SSS-00550	SY2	The NSBRV CI shall allow the operator to cancel an individual subscription.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5473	S-SSS-00560	SY2	The NSBRV CI shall not evaluate a cancelled subscription against ECS events which occur after the subscription is cancelled.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5474	S-SSS-00570	SY2	The NSBRV CI shall process normally any actions associated with a cancelled subscription which were already queued at the time the subscription was cancelled.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5475	S-SSS-00590	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5476	S-SSS-00600	SY2	The NSBRV CI shall allow the operator to filter the subscription list by user id, collection name, and current status.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5477	S-SSS-00610	SY2	The NSBRV CI shall allow the operator to sort the subscription list by subscription id, user id, collection name, expiration date, and current status.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5478	S-SSS-00620	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5479	S-SSS-00630	SY2	The NSBRV CI shall provide the capability to persistently store information regarding which ECS events are valid for placing subscriptions.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5480	S-SSS-00640	SY2	The NSBRV CI shall allow the operator to display the list of valid ECS events upon which subscriptions may be placed.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5481	S-SSS-00650	SY2	The NSBRV CI shall allow the operator to filter the event list by collection name, version id, and event type.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5482	S-SSS-00660	SY2	The NSBRV CI shall allow the operator to sort the event list by collection name, version id, and event type.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5483	S-SSS-00680	SY2	The NSBRV CI shall automatically update its database of valid ECS events when an ESDT is installed in the SDSRV inventory.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5484	S-SSS-00690	SY2	The NSBRV CI shall automatically update its database of valid ECS events when an ESDT is removed from the SDSRV inventory.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5485	S-SSS-00700	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5486	S-SSS-00710	SY2	At startup time, the NSBRV CI shall allow the operator to specify the number of concurrently operating event handling processes to run.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5487	S-SSS-00715	SY2	The NSBRV CI shall allow the operator to start additional event handling processes as needed.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5488	S-SSS-00720	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5489	S-SSS-00730	SY2	The NSBRV CI shall allow the graceful shutdown of an event handling process.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5490	S-SSS-00740	SY2	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  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5491	S-SSS-00750	SY2	At startup time, the NSBRV CI shall allow the operator to specify the number of concurrently operating action handling processes to run.  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5492	S-SSS-00755	SY2	The NSBRV CI shall allow the operator to start additional action handling processes as needed.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5493	S-SSS-00760	SY2	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.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5494	S-SSS-00770	SY2	The NSBRV CI shall allow the graceful shutdown of an action handling process.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5495	S-SSS-00780	SY2	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  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5496	S-SSS-00785	SY2	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   	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5497	S-SSS-00810	SY2	The NSBRV CI shall provide an interface such that externally-developed software can be substituted for the NSBRV GUI to insert subscriptions.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5498	S-SSS-00830	SY2	The NSBRV CI shall support warm start after a fault such that no event, subscription, triggered event, or action is lost.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5499	S-SSS-00835	SY2	The NSBRV CI shall retry an operation if it encounters a retriable error (such as database deadlock).	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5500	S-SSS-00840	SY2	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  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5501	S-SSS-00850	SY2	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)  	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5502	S-SSS-00860	SY2	The NSBRV CI event queue handling processes shall generate a default name for the event handling log file. 	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5503	S-SSS-00865	SY2	he NSBRV CI action queue handling processes shall generate a default name for the action handling log file. 	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5504	S-SSS-00870	SY2	The NSBRV CI shall append output to a log file if the log file already exists.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5505	S-SSS-00880	SY2	The NSBRV CI shall create the log file if the log file does not already exist.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	5506	S-SSS-00890	SY2	The NSBRV CI shall be able to operate in multiple modes concurrently.	02-1088	12/18/2002  		
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	365	S-CLS-10280	B1	The WKBCH CI shall provide users the capability to create, cancel, renew, update and list the contents of Subscriptions, including standing requests.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	437	S-CLS-10960	A	The WKBCH CI shall provide the capability for users to generate orders for ECS data to be distributed on a one-time basis.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	438	S-CLS-10970	B1	The WKBCH CI shall provide the capability for the user to request standard product software and associated documentation to be distributed on-line.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	453	S-CLS-11140	B1	The WKBCH CI shall provide the capability for users to update Distribution Requests prior to the shipment of Data.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	463	S-CLS-11250	B1	The WKBCH CI shall provide a capability to submit Subscription Requests for the distribution of ECS data.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	464	S-CLS-11260	B1	The WKBCH CI shall provide the capability for users to update Subscriptions for the distribution of ECS data.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	570	S-CLS-13750	B1	The WKBCH CI shall provide users the capability to submit Subscription Requests which request a periodic search for new documents meeting user specified search conditions.  All search conditions supported by the document search user interface shall be allowed in this context.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	571	S-CLS-13760	B1	The WKBCH CI shall provide users the capability to issue a Subscription Request for revisions of a given document.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	572	S-CLS-13770	B1	The WKBCH CI shall provide users the capability to issue a Subscription Request for new documents, based on topical keywords.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	595	S-CLS-14030	B1	The WKBCH CI shall provide users the capability to retrieve any previously saved Product Request parameters into a new Product Request, edit the parameters, save the modified parameters, and/or submit the new Product Request.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	601	S-CLS-14250	B1	The WKBCH CI shall provide users the capability to issue a Status Request to determine the status of any active Service Request.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1036	C-CSS-40060	A	The Subscription Service shall provide the capability to perform the following actions on behalf of the client : data acquire, search, and data production requests.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1044	C-CSS-40170	B0	The Subscription Service shall accept Subscription Update Requests to update stored Subscriptions by changing the event or the action.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1050	C-CSS-40230	B0	The Subscription Service shall validate that Subscription Update Requests specify a valid Subscription UR and a valid replacement Subscription.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1051	C-CSS-40260	B0	The Subscription Service shall periodically report on new events for timer-based Subscriptions.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1053	C-CSS-40272	B0	The Subscription Service shall accept requests from subscribers to update existing subscriptions.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1066	C-CSS-40350	B0	The Subscription Service shall allow events to be triggered asynchronously.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1958	S-DSS-01476	B0	The SDSRV CI shall submit requests to the Subscription Service to register a subscribable event.	99-0729	08/25/1999  	No Data	
278	IMS-0740	Complete SY2	The ECS shall provide the capability to generate and update requests for one-time orders or standing orders for the ECS to distribute the following archive holdings, Standard Products, and Standard Product software.	1959	S-DSS-01478	B0	The SDSRV CI shall submit requests to the Subscription Service to register a subscribable event with qualifiers.	99-0729	08/25/1999  	No Data	
279	IMS-0750	Complete	The ECS shall provide the capability for the user to order Standard Product software in accordance with EOSDIS distribution criteria.	438	S-CLS-10970	B1	The WKBCH CI shall provide the capability for the user to request standard product software and associated documentation to be distributed on-line.	99-0729	08/25/1999  	No Data	
279	IMS-0750	Complete	The ECS shall provide the capability for the user to order Standard Product software in accordance with EOSDIS distribution criteria.	439	S-CLS-10980	B1	The WKBCH CI shall provide the capability for the user to request standard product software and associated documentation to be distributed off-line (i.e., media).	99-0729	08/25/1999  	No Data	
280	IMS-0770	Complete	The ECS shall allow users to formulate a data order based on any combination of the inventory core metadata attributes and geophysical parameters.	4328	S-PLS-04330	5B	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.	00-0178	02/23/2000  		
280	IMS-0770	Complete	The ECS shall allow users to formulate a data order based on any combination of the inventory core metadata attributes and geophysical parameters.	358	S-CLS-10220	B0	The WKBCH CI shall allow users to formulate a Product Request based on the results of searching the inventory core metadata attributes.	99-0729	08/25/1999  	No Data	
280	IMS-0770	Complete	The ECS shall allow users to formulate a data order based on any combination of the inventory core metadata attributes and geophysical parameters.	359	S-CLS-10225	B1	The WKBCH CI shall allow users to formulate a Product Request based on the results of searching the inventory product specific metadata attributes.	99-0729	08/25/1999  	No Data	
280	IMS-0770	Complete	The ECS shall allow users to formulate a data order based on any combination of the inventory core metadata attributes and geophysical parameters.	1071	C-CSS-40400	B0	The Subscription Service shall allow subscribers to qualify a subscribable event based on a set of attributes specified by the event producer.	99-0729	08/25/1999  	No Data	
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4793	S-OMS-00010	SY3	The Order Management Service shall accept data distribution requests.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4794	S-OMS-00100	SY3	The Order Management Service shall require that a data distribution request specify a set of distribution options.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4795	S-OMS-00110	SY3	The Order Management Service shall accept any valid combination of electronic or physical media distribution options that are supported by ECS.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4802	S-OMS-00170	SY3	The Order Management Service shall accept an optional UserString parameter of a maximum length of 255 characters for a distribution request.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4803	S-OMS-00180	SY3	The Order Management Service shall accept an optional PRIORITY parameter for a distribution request that specifies one of the ECS priorities.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4804	S-OMS-00190	SY3	The Order Management Service shall accept an optional DDISTNOTIFYTYPE parameter for a distribution request that specifies the ECS notification policy MAIL.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4805	S-OMS-00200	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4806	S-OMS-00210	SY3	The Order Management Service shall require that a data distribution request specify the list of granules to be distributed by the request. 	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4807	S-OMS-00220	SY3	The Order Management Service shall require that the list of granules to be distributed include at least one granule. 	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4808	S-OMS-00230	SY3	The Order Management Service shall allow the list of granules to be distributed to include ECS granule UR strings. 	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4809	S-OMS-00240	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4810	S-OMS-00250	SY3	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 	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4815	S-OMS-00295	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4819	S-OMS-00325	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4839	S-OMS-01060	SY3	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]	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4840	S-OMS-01070	SY3	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]	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4842	S-OMS-01080	SY3	The Order Manager shall validate the size of a request against request size limits in terms of number of granules.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4843	S-OMS-01090	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4844	S-OMS-01100	SY3	The Order Manager shall allow operators to configure request size limits in GB by media type.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4847	S-OMS-01130	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4850	S-OMS-01160	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4851	S-OMS-01170	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4852	S-OMS-01180	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4854	S-OMS-01200	SY3	The Order Manager shall exclude from validation granules that have been flagged as failed.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4878	S-OMS-01430	SY3	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.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4883	S-OMS-01480	SY3	Client applications shall be able to submit data distribution requests whether the Order Manager is currently operating or not.	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4884	S-OMS-02010	SY3	The Order Management Service shall provide a command line utility for submitting data distribution requests. [OSS]	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	4885	S-OMS-02015	SY3	The Order Management Service Command Line Utility shall accept MSS user ID, order ID and request ID as optional parameters. [OSS]	02-1045	12/04/2002  		
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	632	S-CLS-15750	A	The WKBCH CI shall provide users confirmation or rejection of their data requests.	99-0729	08/25/1999  	No Data	
281	IMS-0780	Complete	The ECS shall accept and validate from the ECS users requests for  ECS archival data products.	638	S-CLS-15840	A	Confirmation or rejection of product requests shall contain requestor identification, request identification, request status, and the reason for rejection if rejected.	99-0729	08/25/1999  	No Data	
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	4249	C-CSS-40500	6A	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.	00-0174	02/23/2000  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	4250	C-CSS-30640	6A	The Registry shall store distribution options information. 	00-0174	02/23/2000  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	4251	C-CSS-30650	6A	The Registry shall provide an API to retrieve information that is hierarchically structured, containing dependencies between values. 	00-0174	02/23/2000  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5706	S-DPL-00500	SY3	The Data Pool FTP service shall provide a data compression capability upon data download.	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5707	S-DPL-00510	SY3	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 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5708	S-DPL-00520	SY3	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. 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5709	S-DPL-00530	SY3	The data compression options supported by the Data Pool FTP service shall be operator configurable. 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5711	S-DPL-00550	SY3	The Data Pool FTP service shall log the length of time it takes for transferring each data file. 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5712	S-DPL-05700	SY3	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.	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5713	S-DPL-05705	SY3	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 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5714	S-DPL-05710	SY3	The data compression options supported by the Data Pool Web access service shall be programmer configurable.	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5715	S-DPL-05720	SY3	The Data Pool Web access service shall not provide Unix or gzip compression option  for Browse and metadata files. 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5716	S-DPL-05725	SY3	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. 	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5717	S-DPL-05730	SY3	a. The Data Pool Web access service shall allow users to choose specific compression option explicitly for each download activity.	02-1098	12/18/2002  		
282	IMS-0785	6A Future	ECS shall allow users to request a compression format in which ECS archival data formats are to be distributed.	5718	S-DPL-00540	SY3	The Data Pool FTP log shall indicate whether or not compression was used for each data file transferred. 	02-1098	12/18/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4794	S-OMS-00100	SY3	The Order Management Service shall require that a data distribution request specify a set of distribution options.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4795	S-OMS-00110	SY3	The Order Management Service shall accept any valid combination of electronic or physical media distribution options that are supported by ECS.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4796	S-OMS-00120	SY3	The Order Management Service shall require that a data distribution request specify a single media type.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4803	S-OMS-00180	SY3	The Order Management Service shall accept an optional PRIORITY parameter for a distribution request that specifies one of the ECS priorities.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4806	S-OMS-00210	SY3	The Order Management Service shall require that a data distribution request specify the list of granules to be distributed by the request. 	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4808	S-OMS-00230	SY3	The Order Management Service shall allow the list of granules to be distributed to include ECS granule UR strings. 	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4809	S-OMS-00240	SY3	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.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4951	S-OMS-01500	SY3	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.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4952	S-OMS-01502	SY3	The Order Management Service shall include provisions for removing actions from the database whose completion date/time exceeds a maximum age.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4953	S-OMS-01505	SY3	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.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4954	S-OMS-01506	SY3	The Order Management Service shall include provisions for removing notifications from the database whose sent date/time exceeds a maximum age.	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	4955	S-OMS-01510	SY3	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]	02-1045	12/04/2002  		
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	440	S-CLS-10990	A	The WKBCH CI shall provide users the capability to specify the content of Product Requests which shall contain the Requester Identification, Data set identifier, Distribution instructions, and media requirements.	99-0729	08/25/1999  	No Data	
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	636	S-CLS-15830	B0	The WKBCH CI shall provide the capability for the users to compose Data Distribution Instructions for Product Requests that contain requester identification, data type, data set identifier, data formats, and distribution and media instructions.	99-0729	08/25/1999  	No Data	
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	637	S-CLS-15835	B1	The WKBCH CI shall provide the capability for users to compose Data Distribution Instructions for Product Requests that contain data set subsetting instructions, request priority, suggested earliest start time, and suggested latest completion time.	99-0729	08/25/1999  	No Data	
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	1834	S-DSS-00015	A	The SDSRV CI shall insure that each Data Request includes a User Identifier, a Request Priority, and a Data Identifier.	99-0729	08/25/1999  	No Data	
283	IMS-0810	Complete	The ECS shall support product orders, to retrieve specified data from the archive and distribute it, containing the following information:    a. Requester identification    b. Data type    c. Data set identifier    d. Data set subsetting instructions    e. Data formats    f. Distribution instructions, including media and data compression requirements    g. Request priority	1970	S-DSS-01865	B0	The SDSRV CI shall provide Priority Information for each Data Distribution Request to the DDIST CI.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	2305	S-DSS-30345	6A	The DDIST CI shall send to the requesting client a Distribution Nofification that describes the reason for the unsuccessful completion of a Distribution Request.	99-1175	12/01/1999  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4792	C-DMS-39040	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4804	S-OMS-00190	SY3	The Order Management Service shall accept an optional DDISTNOTIFYTYPE parameter for a distribution request that specifies the ECS notification policy MAIL.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4805	S-OMS-00200	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4816	S-OMS-00300	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4817	S-OMS-00310	SY3	The Order Management Service shall return a fatal error if a distribution request fails validation.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4818	S-OMS-00320	SY3	The Order Management Service shall return a retriable error if a distribution request cannot be saved in the database.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4826	S-OMS-01033	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4827	S-OMS-01034	SY3	The Order Manager shall include in a user notification the data distribution request information of the request to which the notification pertains.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4828	S-OMS-01035	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4829	S-OMS-01036	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4832	S-OMS-03280	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4833	S-OMS-03290	SY3	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.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4836	S-OMS-01045	SY3	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]	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	4838	S-OMS-01055	SY3	The Order Manager shall allow operators to resume the queuing and dispatching of e-mail notification requests if it was suspended.	02-1045	12/04/2002  		
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	443	S-CLS-11010	B1	The WKBCH CI shall automatically provide the capability to confirm or reject a Data Request.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	454	S-CLS-11150	B1	The WKBCH CI shall provide product delay notification to users to notify them when products will not be distributed within the estimated time.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	632	S-CLS-15750	A	The WKBCH CI shall provide users confirmation or rejection of their data requests.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	638	S-CLS-15840	A	Confirmation or rejection of product requests shall contain requestor identification, request identification, request status, and the reason for rejection if rejected.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	1041	C-CSS-40140	A	The Subscription Service shall provide the capability for Subscriptions to notify users via email or directly to a program interface.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	1844	S-DSS-00095	IR1	The SDSRV CI shall return a Reject Notification including the reason for rejection if a Service Request fails validation.	99-0729	08/25/1999  	No Data	
284	IMS-0820	Complete	The ECS shall provide to the user product order information to confirm or reject an order, which contains the following information:  a. Requester identification  b. Request identification  c. If rejection, then the reason for the rejection	1937	S-DSS-01212	B1	The SDSRV CI shall accept and process Status Requests, for the status of any specified Data Request, and provide Data Request Status to the requesting client as a result.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4761	C-CSS-30770	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4762	C-CSS-30780	SY3	The Registry Service shall provide capabilities to retrieve ASTER On-Demand processing options information for ASTER L1A or ASTER L1B by ESDT shortname/version.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4763	S-DMS-33510	SY3	The GTWAY CI shall retrieve ASTER On-Demand processing option information, from the Registry by ASTER L1A or L1B shortname and version.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4764	S-DMS-33520	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4765	S-DMS-33530	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4766	S-DMS-33540	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4767	S-DMS-33550	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4768	S-DMS-33560	SY3	The GTWAY CI shall provide the capability to receive product request messages from the V0 Client containing ASTER on-demand processing request information.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4769	S-DMS-33570	SY3	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	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4770	S-DMS-33580	SY3	The GTWAY CI shall submit on-demand processing request messages to the PLANG CI	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4771	S-DMS-33590	SY3	The GTWAY CI shall break up product requests on a per-granule basis.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4772	S-DMS-33610	SY3	The GTWAY CI shall flag the Order Tracking requests for on-demand product orders to indicate that they are on-demand request type.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4773	S-DMS-33620	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	4774	S-DMS-33630	SY3	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.	02-0980	11/13/2002  		
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	157	S-CLS-20000	5B	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	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	158	S-CLS-20200	5B	The ODFRM CI shall accept one or more GDS ASTER L1A granule IDs as input to an L1B on-demand product order.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	159	S-CLS-20010	5B	The ODFRM CI shall accept as input from the user ASTER on-demand processing parameter values.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	160	S-CLS-20030	5B	The ODFRM CI shall apply the same ASTER on-demand processing parameters for all granules in an ASTER on-demand product order.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	161	S-CLS-20040	5B	The ODFRM CI shall display valid values for ASTER on-demand processing parameters that have a limited set of values.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	162	S-CLS-20050	5B	The ODFRM CI shall display default values for ASTER on-demand processing parameters and apply them if the user does not override these values.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	163	S-CLS-20060	5B	The ODFRM CI shall send the on-demand product request to the ODPRM CI using ODPRMs DCE client I/F	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	164	S-CLS-20070	5B	The ODFRM CI shall allow the user to specify media distribution options for any ASTER on-demand product orders except ASTER L1B.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	165	S-CLS-20190	5B	The ODFRM CI shall allow the media distribution options to be configurable by a DAAC operator.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	166	S-CLS-20180	5B	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.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	167	S-CLS-20080	5B	The ODFRM CI shall verify all user inputs relating to ASTER on-demand processing and return the status of that input to the user.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	168	S-CLS-20090	5B	The ODFRM CI shall reject any ASTER L1B on-demand product order from an unauthorized user.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	169	S-CLS-20100	5B	The ODFRM CI shall assign configurable priorities to all on-demand product orders.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	174	S-CLS-20160	5B	The ODFRM CI shall submit all on-demand DEM product orders to an ECS operator after getting the OrderId from the ODPRM.	99-0729	08/25/1999  	No Data	
286	IMS-0922	5B Future	The ECS shall provide support for the construction and submittal of On-Demand Production requests for processing of ASTER data, which contain the following information:  a. Requester identification  b. Science Software input requirements  c. L1A or L1B data set  d. Resulting product type  e. Processing parameters  f.  ECS distribution options	175	S-CLS-20170	5B	The ODFRM CI shall send an email notification to the user upon submission of the ASTER on-demand product order.	99-0729	08/25/1999  	No Data	
309	IMS-1500	Complete	The ECS shall provide the tools to support user preparation or automated generation of metadata, for example, directory and inventory entries.	467	S-CLS-11285	B1	The WKBCH CI shall provide users the capability to create documents in HTML format.	99-0729	08/25/1999  	No Data	
309	IMS-1500	Complete	The ECS shall provide the tools to support user preparation or automated generation of metadata, for example, directory and inventory entries.	2667	S-IOS-00230	A	The ADSRV CI shall provide the capability  to add, delete, or modify individual Advertisements.	99-0729	08/25/1999  	No Data	
311	IMS-1510	Complete	The ECS data visualization capabilities shall be portable and execute on  ECS supported workstations and appropriate ECS facility computers.	315	S-CLS-01490	A	The DESKT CI executables shall run on the following hosts:  a. SGI IRIX 5.3  b. HP UX 9.05  c. SUN Solaris 2.4  d. IBM RS/6000 AIX 3.2.5	99-0729	08/25/1999  	No Data	
311	IMS-1510	Complete	The ECS data visualization capabilities shall be portable and execute on  ECS supported workstations and appropriate ECS facility computers.	316	S-CLS-01492	B0	The DESKT CI executables shall run on the following hosts:  a. DEC Digital Unix 4.0  b. HP UX 10.01  c. SGI IRIX 6.2 (64 bit)  d. IBM RS/6000 AIX 4.1	99-0729	08/25/1999  	No Data	
311	IMS-1510	Complete	The ECS data visualization capabilities shall be portable and execute on  ECS supported workstations and appropriate ECS facility computers.	376	S-CLS-10390	A	The WKBCH CI binaries that run on ECS supported workstations shall be publicly available.	99-0729	08/25/1999  	No Data	
311	IMS-1510	Complete	The ECS data visualization capabilities shall be portable and execute on  ECS supported workstations and appropriate ECS facility computers.	377	S-CLS-10393	A	The DESKT CI binaries that run on ECS supported workstations shall be publicly available.	99-0729	08/25/1999  	No Data	
311	IMS-1510	Complete	The ECS data visualization capabilities shall be portable and execute on  ECS supported workstations and appropriate ECS facility computers.	627	S-CLS-15680	A	The WKBCH CI executables shall run on the following hosts:  a. SGI IRIX 5.3  b. HP UX 9.05  c. SUN Solaris 2.4  d. IBM RS/6000 AIX 3.2.5	99-0729	08/25/1999  	No Data	
311	IMS-1510	Complete	The ECS data visualization capabilities shall be portable and execute on  ECS supported workstations and appropriate ECS facility computers.	628	S-CLS-15682	B0	The WKBCH CI executables shall run on the following hosts:  a. DEC Digital Unix 4.0  b. HP UX 10.01  c. SGI IRIX 6.2 (64 bit)  d. IBM RS/6000 AIX 4.1	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	362	S-CLS-10245	B1	The WKBCH CI shall provide users the capability to view subsetted, subsampled, and summarized data in conjunction with displayed associated inventory information.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	373	S-CLS-10360	A	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in table format.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	374	S-CLS-10370	A	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in text format.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	395	S-CLS-10570	A	The WKBCH CI shall produce visualizations of images needed for QA, validation, Algorithm development, calibration functions, parameter verification and anomaly detection.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	396	S-CLS-10580	A	The WKBCH CI shall produce visualizations of multi-dimensional arrays needed for QA, Validation, Algorithm development, calibration functions, parameter verification and anomaly detection.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	397	S-CLS-10590	A	The WKBCH CI shall produce visualizations of tables of numbers needed for QA, Validation, Algorithm development, calibration functions, parameter verification and anomaly detection.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	556	S-CLS-13620	B0	The WKBCH CI shall provide the capability to visualize ECS HDF-EOS formatted data as continuous forward animation.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	558	S-CLS-13630	B0	The WKBCH CI shall provide the capability to visualize ECS HDF-EOS formatted data as single-step forward animation.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	559	S-CLS-13640	B0	The WKBCH CI shall provide  the capability to visualize ECS HDF-EOS formatted data as single-step backward animation.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	560	S-CLS-13650	B0	The WKBCH CI shall provide  the capability to visualize ECS HDF-EOS formatted data as oscillating animation (i.e., continuous forward then continuous backward, alternating throughout the loop until user-directed termination).	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	561	S-CLS-13660	B0	The WKBCH CI shall provide users the capability to change the minimum/maximum values of the color tables for visualization of ECS HDF-EOS formatted data.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	562	S-CLS-13670	B0	The WKBCH CI shall provide users the capability to modify color palettes for visualization of ECS HDF-EOS formatted data.	99-0729	08/25/1999  	No Data	
312	IMS-1520	Complete	The ECS shall provide data visualization tools to assist the investigators to perform the following functions:  a. QA/Validation of generated products  b. Science Software development  c. Calibration functions, parameter verification, and anomaly detection  d. View subsetted data whenever associated inventory information is displayed	590	S-CLS-13980	B0	The WKBCH CI shall provide a legend describing the display of ECS HDF-EOS formatted data, in each window.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	369	S-CLS-10320	B0	The WKBCH CI shall provide users the option to display Latitude/Longitude pairs as symbols, displayed in their proper geolocation on all visualizations produced by the WKBCH CI.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	370	S-CLS-10330	A	The WKBCH CI shall provide users the capability of displaying 8-bit raster images.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	371	S-CLS-10340	A	The WKBCH CI shall provide users the capability of displaying 24-bit raster images.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	372	S-CLS-10350	A	The WKBCH CI shall provide users the option to display a series of Latitude/Longitude pairs (i.e., a vector) as lines, displayed in their proper geolocation on top of all visualizations produced by the WKBCH CI.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	373	S-CLS-10360	A	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in table format.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	374	S-CLS-10370	A	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in text format.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	375	S-CLS-10380	A	The WKBCH CI shall provide users the capability to produce an animation loop.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	378	S-CLS-10400	A	The WKBCH CI shall provide users the option to display a series of visualizations as an animation.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	384	S-CLS-10460	B1	The WKBCH CI shall provide users Lat/Long lists for the production of built-in vector overlays as part of the application.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	385	S-CLS-10470	B1	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in vector graphic format.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	556	S-CLS-13620	B0	The WKBCH CI shall provide the capability to visualize ECS HDF-EOS formatted data as continuous forward animation.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	558	S-CLS-13630	B0	The WKBCH CI shall provide the capability to visualize ECS HDF-EOS formatted data as single-step forward animation.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	559	S-CLS-13640	B0	The WKBCH CI shall provide  the capability to visualize ECS HDF-EOS formatted data as single-step backward animation.	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	560	S-CLS-13650	B0	The WKBCH CI shall provide  the capability to visualize ECS HDF-EOS formatted data as oscillating animation (i.e., continuous forward then continuous backward, alternating throughout the loop until user-directed termination).	99-0729	08/25/1999  	No Data	
313	IMS-1530	Complete	The ECS shall provide the capability to visualize data in raster formats and to visualize animated products.	685	S-CLS-18060	A	The WKBCH CI shall provide users the capability to display an animation.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	379	S-CLS-10410	A	The WKBCH CI shall provide the capability of generating and displaying ECS HDF-EOS formatted data as a two-dimensional color scatter plot.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	381	S-CLS-10430	A	The WKBCH CI shall provide the capability of displaying two-dimensional data arrays as pseudocolor images.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	386	S-CLS-10480	B1	The WKBCH CI shall provide the capability of generating and displaying ECS HDF-EOS formatted data as a series of lineplots.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	387	S-CLS-10490	B1	The WKBCH CI shall provide the capability of displaying a horizontal or vertical profile through a pseudo-color image.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	388	S-CLS-10500	B1	The WKBCH CI shall provide the capability of displaying multi-dimensional arrays of data as a series of two-dimensional pseudo-color images.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	555	S-CLS-13615	B1	The WKBCH CI shall provide the capability of generating and displaying ECS HDF-EOS formatted data as a three-dimensional color plot.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	557	S-CLS-13625	B1	The WKBCH CI shall provide the capability of generating and displaying ECS HDF-EOS formatted data as a three-dimensional surface diagram.	99-0729	08/25/1999  	No Data	
314	IMS-1540	Complete	The ECS shall provide the capability to generate:    a. Two-dimensional plots (x-y plots, scatter plots, profiles, histograms)    b.  Contour plots	647	S-CLS-15920	B0	The Client Visualization Tool shall support display of multiple images.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	380	S-CLS-10420	A	The WKBCH CI shall provide the capability of selecting different color palettes for the pseudocolor visualizations.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	382	S-CLS-10440	A	The WKBCH CI shall provide the capability of zooming and panning pseudocolor visualizations of data.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	383	S-CLS-10450	A	The WKBCH CI shall provide the capability of zooming and panning raster images.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	389	S-CLS-10510	B1	The WKBCH CI shall provide the capability of importing color palettes.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	390	S-CLS-10520	B1	The WKBCH CI shall provide the capability for modifying the color palette.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	391	S-CLS-10530	B1	The WKBCH CI shall provide the capability of modifying the pseudo-color mapping by changing the min/max values associated with that color.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	392	S-CLS-10540	B1	The WKBCH CI shall provide the capability of modifying the pseudocolor mapping by adaptive equalization.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	561	S-CLS-13660	B0	The WKBCH CI shall provide users the capability to change the minimum/maximum values of the color tables for visualization of ECS HDF-EOS formatted data.	99-0729	08/25/1999  	No Data	
315	IMS-1550	Complete	The ECS shall provide capabilities for image manipulation (e.g., pan, zoom, color, contrast).	562	S-CLS-13670	B0	The WKBCH CI shall provide users the capability to modify color palettes for visualization of ECS HDF-EOS formatted data.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	393	S-CLS-10550	B1	The WKBCH CI shall provide users the capability of calculating summarizing statistics of  multi-dimensional arrays of EOS data.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	394	S-CLS-10560	B1	The WKBCH CI shall provide the capability of calculating summarizing statistics of user-selected columns from tables of values of EOS data.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1631	S-DPS-40700	A	The data visualization capability of the AITTL CI shall include the capability to display data in hexadecimal, octal, decimal, or ASCII form.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1632	S-DPS-40710	A	The data visualization capability of the AITTL CI shall include the capability to display data as a two- or three-dimensional image.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1633	S-DPS-40720	A	The data visualization capability of the AITTL CI shall include the capability to display data as a two- or three-dimensional plot.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1634	S-DPS-40730	A	The data visualization capability of the AITTL CI shall include the capability to compare data and to display the differences as a two- or three-dimensional image or plot.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1635	S-DPS-40740	A	The data visualization capability of the AITTL CI shall include the capability to produce and play a "movie loop" of data in two- or three-dimensional image or plot form.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1636	S-DPS-40750	A	The data visualization capability of the AITTL CI shall include the capability to display two-dimensional slice of a three-dimensional image or plot.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1637	S-DPS-40760	A	The data visualization capability of the AITTL CI shall include the capability to rotate a three-dimensional image or plot about an axis.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1638	S-DPS-40770	A	The data visualization capability of the AITTL CI shall provide the operations staff with the option to specify the color table for new or existing image displays.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1639	S-DPS-40780	A	The data visualization capability of the AITTL CI shall provide the operations staff with the option to specify the axis limits for new or existing plot displays.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1640	S-DPS-40790	A	The data visualization capability of the AITTL CI shall provide the operations staff with the option to specify the parameter assigned to each axis in new or existing plot or image displays.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1641	S-DPS-40800	A	The data visualization capability of the AITTL CI shall include the capability to display simultaneously multiple views of the same or different data in different windows.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1642	S-DPS-40810	A	The data visualization capability of the AITTL CI shall include the capability to save any plot, image, or hex/decimal/octal/ASCII dump to a file.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1643	S-DPS-40820	A	The data visualization capability of the AITTL CI shall include feature enhancement capabilities, including but not limited to (1) histogram equalization and (2) edge enhancement.	99-0729	08/25/1999  	No Data	
316	IMS-1570	Complete	The ECS shall provide data visualization statistical analysis capabilities.	1644	S-DPS-40830	A	The data visualization capability of the AITTL CI shall include the capability to read ASCII, binary, or HDF files.	99-0729	08/25/1999  	No Data	
317	IMS-1590	Complete	The ECS shall provide capabilities for sizing and positioning the cursor by:  a. Earth coordinates  b. Image coordinates  c. Instrument scan-line coordinated	368	S-CLS-10310	B0	The WKBCH CI shall provide users the capability of positioning the cursor by entering  an image X,Y coordinate.	99-0729	08/25/1999  	No Data	
317	IMS-1590	Complete	The ECS shall provide capabilities for sizing and positioning the cursor by:  a. Earth coordinates  b. Image coordinates  c. Instrument scan-line coordinated	398	S-CLS-10600	B0	The WKBCH CI shall display the Latitude and Longitude coordinates of the cursor, when the cursor is inside an EOS Grid array.	99-0729	08/25/1999  	No Data	
317	IMS-1590	Complete	The ECS shall provide capabilities for sizing and positioning the cursor by:  a. Earth coordinates  b. Image coordinates  c. Instrument scan-line coordinated	399	S-CLS-10610	B0	The WKBCH CI shall provide users the capability of positioning the cursor by entering a Latitude/Longitude value.	99-0729	08/25/1999  	No Data	
317	IMS-1590	Complete	The ECS shall provide capabilities for sizing and positioning the cursor by:  a. Earth coordinates  b. Image coordinates  c. Instrument scan-line coordinated	400	S-CLS-10615	B0	The WKBCH CI shall provide users the capability of positioning the cursor by entering  instrument scan line.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4258	C-MSS-75090	5B	The MSS accountability management service shall replicate GDS Order Status from the DAACs to the SMC.	00-0105	02/07/2000  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4259	C-MSS-75091	5B	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.	00-0105	02/07/2000  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4260	C-MSS-75092	5B	The MSS accountability management service shall allow manual GDS Order Status updates only by DAAC personnel from the processing DAAC.	00-0105	02/07/2000  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4261	C-MSS-75093	5B	The MSS accountability management service shall allow automated GDS Order Status updates.	00-0105	02/07/2000  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4262	C-MSS-75094	5B	The MSS accountability management service shall allow GDS Order Status read-access at the SMC.	00-0105	02/07/2000  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4870	S-OMS-01360	SY3	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	02-1045	12/04/2002  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4871	S-OMS-01370	SY3	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  	02-1045	12/04/2002  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4872	S-OMS-01380	SY3	The Order Manager shall generate a default name for the log file compatible with ECS log file names.	02-1045	12/04/2002  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4873	S-OMS-01390	SY3	The Order Manager shall append output to the log file if it already exists.	02-1045	12/04/2002  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	4874	S-OMS-01400	SY3	The Order Manager shall create the log file if it does not already exist.	02-1045	12/04/2002  		
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	86	C-MSS-75046	5B	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	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	87	C-MSS-75047	5B	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	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	88	C-MSS-75056	5B	The MSS accountability management service shall provide the capability to identify on demand processing orders and requests.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	89	C-MSS-75058	5B	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.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	90	C-MSS-75059	5B	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.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	91	C-MSS-75061	5B	The MSS accountability management service shall be able to track the status of an ASTER L1B order and its requests.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	92	C-MSS-75062	5B	The MSS accountability management service shall provide an interface for an operator to mark an ASTER on demand request as "canceled" or "aborted".	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	93	C-MSS-75063	5B	The MSS accountability management service shall provide the ability to identify whether a user has the privilege to order ASTER L1B products.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	94	C-MSS-75065	5B	The MSS accountability management service shall provide an ECS wide unique order ID for each Cross-DAAC GDS order.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	97	C-MSS-75068	5B	The MSS accountability management service shall provide an ECS wide unique request ID for each Cross-DAAC GDS request.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	98	C-MSS-75075	5B	The MSS accountability management service shall be able to create an order with a pre-existing order/request ID.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	99	C-MSS-75076	5B	The MSS accountability management service shall be able to create an order/request with a foreign home DAAC value.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	101	C-MSS-75055	5B	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	1947	S-DSS-01400	B0	The SDSRV CI shall provide the capability to log, to the Event Log, the completion of each Service Request.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	1950	S-DSS-01415	B0	The SDSRV CI shall log, to the Event Log, failures to successfully complete Service Requests, and shall log the reason for such failures.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	1952	S-DSS-01425	B0	The SDSRV CI shall log, to the Event Log, those Service Requests that fail authorization, the service requested, and the identity of the requesting user.	99-0729	08/25/1999  	No Data	
318	IMS-1646	Complete	The ECS shall provide a record of data orders for the purposes of maintaining a full and complete history of all data orders.	1953	S-DSS-01430	B0	The SDSRV CI shall provide the capability to log, to the Event Log, the initiation of each Service Request.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4258	C-MSS-75090	5B	The MSS accountability management service shall replicate GDS Order Status from the DAACs to the SMC.	00-0105	02/07/2000  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4259	C-MSS-75091	5B	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.	00-0105	02/07/2000  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4260	C-MSS-75092	5B	The MSS accountability management service shall allow manual GDS Order Status updates only by DAAC personnel from the processing DAAC.	00-0105	02/07/2000  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4261	C-MSS-75093	5B	The MSS accountability management service shall allow automated GDS Order Status updates.	00-0105	02/07/2000  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4262	C-MSS-75094	5B	The MSS accountability management service shall allow GDS Order Status read-access at the SMC.	00-0105	02/07/2000  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4870	S-OMS-01360	SY3	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	02-1045	12/04/2002  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4871	S-OMS-01370	SY3	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  	02-1045	12/04/2002  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4872	S-OMS-01380	SY3	The Order Manager shall generate a default name for the log file compatible with ECS log file names.	02-1045	12/04/2002  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4873	S-OMS-01390	SY3	The Order Manager shall append output to the log file if it already exists.	02-1045	12/04/2002  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	4874	S-OMS-01400	SY3	The Order Manager shall create the log file if it does not already exist.	02-1045	12/04/2002  		
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	86	C-MSS-75046	5B	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	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	87	C-MSS-75047	5B	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	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	88	C-MSS-75056	5B	The MSS accountability management service shall provide the capability to identify on demand processing orders and requests.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	89	C-MSS-75058	5B	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.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	90	C-MSS-75059	5B	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.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	91	C-MSS-75061	5B	The MSS accountability management service shall be able to track the status of an ASTER L1B order and its requests.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	92	C-MSS-75062	5B	The MSS accountability management service shall provide an interface for an operator to mark an ASTER on demand request as "canceled" or "aborted".	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	93	C-MSS-75063	5B	The MSS accountability management service shall provide the ability to identify whether a user has the privilege to order ASTER L1B products.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	94	C-MSS-75065	5B	The MSS accountability management service shall provide an ECS wide unique order ID for each Cross-DAAC GDS order.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	97	C-MSS-75068	5B	The MSS accountability management service shall provide an ECS wide unique request ID for each Cross-DAAC GDS request.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	98	C-MSS-75075	5B	The MSS accountability management service shall be able to create an order with a pre-existing order/request ID.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	99	C-MSS-75076	5B	The MSS accountability management service shall be able to create an order/request with a foreign home DAAC value.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	101	C-MSS-75055	5B	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1314	S-DMS-01010	5B	The LIMGR CI shall log all Service requests initiated during a session.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1315	S-DMS-01014	Complete	The LIMGR CI shall log when the request to the ECS-V0 Gateway has been successfully returned.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1316	S-DMS-01016	Complete	The LIMGR CI shall log when  a connection to the ECS-V0 Gateway has been established.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1359	S-DMS-20865	Complete	The  DDICT CI shall log the initiation of all requests received by the DDICT CI.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1360	S-DMS-20866	Complete	The  DDICT CI shall log the startup of the DDICT servers.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1361	S-DMS-20867	Complete	The  DDICT CI shall log the shutdown of the DDICT servers.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1362	S-DMS-20868	Complete	The  DDICT CI shall log when a service request is activated from the queue.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1363	S-DMS-20869	Complete	The  DDICT CI shall log when a request has been successfully completed and the status is about to be returned to the client.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1364	S-DMS-20870	Complete	The  DDICT CI shall log the initiation of a DDICT CI session.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1393	S-DMS-31010	Complete	The GTWAY CI shall log the initiation of all requests.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1396	S-DMS-31015	5B	The ECS-V0 Component of the GTWAY CI shall log when an external connection to the LPDS has been established.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1397	S-DMS-31016	5B	The ECS-V0 Component of the GTWAY CI shall log when the component service request has been submitted to the LPDS.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1398	S-DMS-31017	5B	The ECS-V0 Component of the GTWAY CI shall log when the request to the LPDS has been successfully returned.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1399	S-DMS-31040	Complete	The GTWAY CI shall log a message upon successful completion of all requests.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1437	S-DMS-41013	5B	The ASTGW CI shall log when a service request is activated from the queue.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1438	S-DMS-41014	5B	The GDS-ECS component of the ASTGW CI shall log when a service request has been successfully decomposed into its component requests.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1439	S-DMS-41015	5B	The ECS-GDS component of the ASTGW CI shall log when an external connection to the ASTER GDS server has been established.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1440	S-DMS-41016	5B	The ECS-GDS component of the ASTGW CI shall log when the component service request has been submitted to the ASTER GDS server.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1441	S-DMS-41017	5B	The ECS-GDS component of the ASTGW CI shall log when the results from the ASTER GDS server have been successfully returned.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1442	S-DMS-41018	5B	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.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1839	S-DSS-00057	B1	The SDSRV CI shall maintain, for each entry in the Service Request List, an indicator that determines whether the associated Service Request is being processed or is waiting to be processed.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1872	S-DSS-00331	B1	The SDSRV CI shall record the User Identifier of the science investigator associated with a Service Request, to be used for accounting purposes.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1927	S-DSS-01090	B1	The SDSRV CI shall maintain a Service Request List that lists received Service Requests, associated Priority Information, and all other information required to process each request.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1934	S-DSS-01170	B1	The SDSRV CI shall provide the capability to monitor resource utilization on a client basis.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1949	S-DSS-01410	B1	The SDSRV CI shall log the suspension of the processing of a Service Request or the suspension of a client session.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1951	S-DSS-01420	B1	The SDSRV CI shall log the resumption of a previously suspended Service Request or client session.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	1970	S-DSS-01865	B0	The SDSRV CI shall provide Priority Information for each Data Distribution Request to the DDIST CI.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2102	S-DSS-05730	B0	The SDSRV CI shall provide the capability to associate multiple DAR identifiers with any ingested ASTER data granule.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2276	S-DSS-30110	B1	The DDIST CI shall provide the capability for operations staff to list Electronic Distribution Requests separately from Media Distribution Requests.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2277	S-DSS-30115	B0	The DDIST CI shall provide the capability for operations staff to list Distribution Requests according to Request Identifier and requestor.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2278	S-DSS-30125	B0	The DDIST CI shall provide the capability for operations staff to list Media Distribution Requests according to media type.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2280	S-DSS-30135	B0	The DDIST CI shall provide the capability for operations staff to list Distribution Requests according to distribution status.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2882	C-MSS-18044	B0	The MSS MDA shall support a separate management database for each active mode.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2883	C-MSS-18046	B0	The MSS MDA shall transfer MSS log file records to the appropriate management database based on the event's mode.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2884	C-MSS-18048	B0	The MSS MDA shall transfer non-mode specific MSS log file records to all mode specific management databases.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2885	C-MSS-18050	A	The MSS Management Data Access Service's shall utilize CSS Services to access/transfer management data.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2887	C-MSS-18070	B0	The MSS Management Data Access Service shall provide the capability to selectively access management data.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2892	C-MSS-18260	B0	The MSS Management Data Access Service shall have the capability to schedule the transfer and loading log files into the management database at the site.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2893	C-MSS-18270	B0	The MSS Management Data Access Service shall have the capability to schedule the archiving of log files at the site.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	2894	C-MSS-18280	B0	MSS shall have the capability to schedule the transfer of management data at the sites to the SMC.	99-0729	08/25/1999  	No Data	
319	IMS-1650	Complete	The ECS operations data shall contain information on:    a. System utilization     b. Outstanding data distribution requests 	3256	C-MSS-67000	B0	The MSS performance management application service shall be capable of extracting values of performance metrics gathered for a specified managed objects over a configurable period of time from the Management Database.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	246	S-DMS-41019	5B	The ASTGW CI shall log when a successful user authentication has taken place.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	247	S-DMS-41021	5B	The ASTGW CI shall log when an unsuccessful user authentication has taken place.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1393	S-DMS-31010	Complete	The GTWAY CI shall log the initiation of all requests.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1399	S-DMS-31040	Complete	The GTWAY CI shall log a message upon successful completion of all requests.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1433	S-DMS-40910	B1	The ASTGW CI shall log the initiation of a session.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1434	S-DMS-40920	B1	The ASTGW CI shall log the termination of a session.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1437	S-DMS-41013	5B	The ASTGW CI shall log when a service request is activated from the queue.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1438	S-DMS-41014	5B	The GDS-ECS component of the ASTGW CI shall log when a service request has been successfully decomposed into its component requests.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1440	S-DMS-41016	5B	The ECS-GDS component of the ASTGW CI shall log when the component service request has been submitted to the ASTER GDS server.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1441	S-DMS-41017	5B	The ECS-GDS component of the ASTGW CI shall log when the results from the ASTER GDS server have been successfully returned.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1442	S-DMS-41018	5B	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.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	1880	S-DSS-00376	B1	The SDSRV CI shall provide User Accounting Information to the System Management Subsystem, using MSS application program interfaces.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	2895	C-MSS-18330	B0	MSS shall provide the capability for an applications to append records to a log file.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	2921	C-MSS-36090	B0	The MSS Management Agent Service shall provide an extensible ECS management agent for ECS applications	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	3291	C-MSS-70410	B0	The MSS SMC Security Management Application Service shall have the capability to receive security audit trails from the site Security Management Application Services.	99-0729	08/25/1999  	No Data	
320	IMS-1665	Complete	The ECS shall log services usage by each user (to include user name, service identification, date/time stamp) for later reporting and determination of access patterns.	3437	C-MSS-92420	B1	The MSS Report Generation Service shall be capable of generating a User Activity Audit Report tracing a user's activity during a logon including products requested and files accessed.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	1307	S-DMS-00520	5B	The LIMGR CI shall log the failure of a request.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	1400	S-DMS-31051	Complete	The GTWAY CI shall log errors.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	1443	S-DMS-41051	5B	The ASTGW CI shall log the failure of a request.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2675	S-IOS-00490	A	The ADSRV CI shall send detected hardware and software fault information to MSS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2924	C-MSS-36215	B0	The Management Agent Service shall have the capability to receive event notification from the CLS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2927	C-MSS-36310	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the IOS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2934	C-MSS-36360	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the DMS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2941	C-MSS-36410	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the PLS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2948	C-MSS-36460	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the DPS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2956	C-MSS-36510	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the INS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2963	C-MSS-36560	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the DSS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	2971	C-MSS-36710	B0	The Management Agent Service shall have the capability to receive detected hardware and software fault information from the CSS.	99-0729	08/25/1999  	No Data	
321	IMS-1760	Complete	The ECS shall  raise the following detected hardware faults:  a. Processors  b. Network interfaces  c. Storage devices	3191	C-MSS-60390	B0	The MSS Fault Management Application Service at the sites shall, for faults detected within its site, isolate, locate, and identify faults to the level of:   a. subsystem   b. equipment   c. software	99-0729	08/25/1999  	No Data	
322	IMS-1780	6B Partial	The ECS shall respond to each user session operation within the time period specified in Table 6-1 with the specified rate of operations.	2126	S-DSS-10300	B1	The Document Data Server shall complete a search for a guide document by a single keyword in not exceeding 8 seconds.	99-0729	08/25/1999  	No Data	
322	IMS-1780	6B Partial	The ECS shall respond to each user session operation within the time period specified in Table 6-1 with the specified rate of operations.	2127	S-DSS-10305	B1	The Document Data Server shall complete a directory search using a single keyword in a period not to exceed 8 seconds.	99-0729	08/25/1999  	No Data	
322	IMS-1780	6B Partial	The ECS shall respond to each user session operation within the time period specified in Table 6-1 with the specified rate of operations.	2128	S-DSS-10306	B1	The Document Data Server shall complete a directory search using multiple keywords in a period not to exceed 13 seconds.	99-0729	08/25/1999  	No Data	
322	IMS-1780	6B Partial	The ECS shall respond to each user session operation within the time period specified in Table 6-1 with the specified rate of operations.	2129	S-DSS-10310	B1	The Document Data Server shall complete a keyword search on a 1000 page document of not exceeding 3 seconds.	99-0729	08/25/1999  	No Data	
322	IMS-1780	6B Partial	The ECS shall respond to each user session operation within the time period specified in Table 6-1 with the specified rate of operations.	2671	S-IOS-00340	A	The ADSRV CI shall perform a single keyword attribute directory search in not exceeding the time specified in Appendix E in the current version of 304-CD-005.	99-0729	08/25/1999  	No Data	
322	IMS-1780	6B Partial	The ECS shall respond to each user session operation within the time period specified in Table 6-1 with the specified rate of operations.	2672	S-IOS-00345	B0	The ADSRV CI shall perform multiple keyword attributes directory search in not exceeding the time specified in Reference Table:  A/B Service Performance Response Time Budgets by Subsystem (Table E-8.2).	99-0729	08/25/1999  	No Data	
325	IMS-1800	Complete	The ECS design and implementation shall have the flexibility to accommodate 100% expansion in query processing and metadata storage capacity without major changes to the hardware and software design.	1457	S-DMS-60500	Complete	The DMGHW CI shall accommodate 100% expansion in processing and storage capacity without major changes to the hardware and software design.	99-0729	08/25/1999  	No Data	
325	IMS-1800	Complete	The ECS design and implementation shall have the flexibility to accommodate 100% expansion in query processing and metadata storage capacity without major changes to the hardware and software design.	2232	S-DSS-21510	B1	The STMGT CI shall have the capability to expand its storage capacity by 200% with no change to its architecture or design.	99-0729	08/25/1999  	No Data	
325	IMS-1800	Complete	The ECS design and implementation shall have the flexibility to accommodate 100% expansion in query processing and metadata storage capacity without major changes to the hardware and software design.	2238	S-DSS-21770	A	The DRPHW CI shall be capable of providing of 200 percent expansion in capacity without architecture or design change.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3977	S-TKS-00256	TK5a	The SDP Toolkit shall contain tools which perform inquiries to point structures.  These tools will return information about:  number of levels, number of records in a level, number of fields in a level, information about the defined spatial and temporal extent of point structures, and information about defined attributes of point structures.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3978	S-TKS-00260	TK5a	The SDP Toolkit shall contain tools for the definition of and access to swath structures.  These structures will be based on standard HDF structures and will also be known as HDF-EOS swath structures.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3979	S-TKS-00264	TK5a	The SDP Toolkit shall contain tools which perform inquiries to swath structures.  These tools will return information about:  dimensions, geolocation relations, geolocation and data mappings, geolocation and data fields, number and name of attributes, and defined region and time period.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3980	S-TKS-00280	TK5a	The SDP Toolkit shall contain tools for the definition of and access to grid structures.  These structures will be based on standard HDF structures and will also be known as HDF-EOS grid structures.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3981	S-TKS-00253	TK5a	The SDP Toolkit shall contain tools which access point structures.  These tools will create, open, close, attach, or detach to existing point structures.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3982	S-TKS-00254	TK5a	The SDP Toolkit shall contain tools to define the level within a point structure and to define the link between two levels within a point structure.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3983	S-TKS-00255	TK5a	The SDP Toolkit shall contain tools which read/write records and read/write attributes of point structures.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3984	S-TKS-00257	TK5a	The SDP Toolkit shall contain tools which subset point structures.  These tools will define a region or time period of interest within a point structure, and read the region or time period of interest.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3985	S-TKS-00261	TK5a	The SDP Toolkit shall contain tools which open an HDF file and create, read or write, attach or detach a swath structure within that file; and close the file.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3986	S-TKS-00262	TK5a	The SDP Toolkit shall contain tools which define:  swath data and geolocation dimensions, the mapping between geolocation and data dimensions, a new geolocation field, a new swath structure, a field compression method; and writes field metadata to geolocation or data fields.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3987	S-TKS-00263	TK5a	The SDP Toolkit shall contain tools which read/write data fields, read/write attributes within a swath, and set or retrieve fill values for a field.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3988	S-TKS-00265	TK5a	The SDP Toolkit shall contain tools which subset swath structures.  These tools will define, read, and extract a region of interest by latitude and longitude and define, read and extract a time period of interest.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3989	S-TKS-00281	TK5a	The SDP Toolkit shall contain tools which open an HDF file and create, read or write, attach or detach a grid structure within that file, and close the file.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3990	S-TKS-00282	TK5a	The SDP Toolkit shall contain tools which define:  origin of a grid, projection of a grid, pixel registration within a grid cell, data field within a grid, and a field compression method.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3991	S-TKS-00283	TK5a	The SDP Toolkit shall contain tools which read/write data, read/write attributes within a swath, and set and retrieve fill values for a field.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3992	S-TKS-00284	TK5a	The SDP Toolkit shall contain tools which perform inquiries to grid structures.  These tools will return information about:  data fields, dimensions, attributes, projection, geolocation, grid origin, and defined region.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3993	S-TKS-00285	TK5a	The SDP Toolkit shall contain tools which subset grid structures.  These tools will define and read a region of interest of a field or a vertical field, extract row/column for specified latitude/longitude pairs, extract field values for specified pixels, and perform bilinear interpolation for a grid field.	99-0764	08/25/1999  		
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	1515	S-DPS-21120	A	The PRONG CI shall create a Process Control File to provide information to the SDP Toolkit CI about the input data required to execute a PGE.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	1518	S-DPS-21130	A	The PRONG CI shall create a Process Control File to provide information to the SDP Toolkit CI about the output data generated from the executing PGE.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	1519	S-DPS-21140	A	The PRONG CI shall create a  mapping  of logical file handles to physical file handles in the Process Control File for the input data required to execute a PGE.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	1520	S-DPS-21150	A	The PRONG CI shall create a  mapping  of logical file handles to physical file handles in the Process Control File for the output data generated from the executing PGE.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3664	S-TKD-00190	IR1	The SDP Toolkit shall contain tools to open and close Science Data Processing Facility (SDPF), EOS Data and Operations System (EDOS)-generated Level 0 data sets or data sets from other sources as determined by the ESDIS Project.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3665	S-TKD-00200	IR1	The SDP Toolkit shall contain tools to read Consultative Committee on Space Data Systems (CCSDS)-format packetized data 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.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3666	S-TKD-00220	IR1	The SDP Toolkit shall include the capability to provide the first CCSDS packet after a given time.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3667	S-TKD-00225	B0	The SDP Toolkit shall return the number of Level 0 packets read to reach the Level 0 packet with the correct start time.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3668	S-TKD-00230	IR1	The SDP Toolkit shall contain tools to access the metadata located within Level 0 data files , (e.g., SDPF- and EDOS-generated header, accounting and quality information).	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3669	S-TKD-00235	IR1	The SDP Toolkit shall contain tools to access the ECS-internal metadata that is associated with the Level 0 data files provided to a PGE.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3670	S-TKD-00240	IR1	The SDP Toolkit shall provide tools to access SDPF-, EDOS-provided telemetry data, or access to data sets from other sources as determined by the ESDIS Project.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3671	S-TKD-00252	B0	The SDP Toolkit shall contain tools for the definition of and access to point structures.  These structures will be based on standard HDF structures and will also be known as HDF-EOS point structures.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3672	S-TKD-00253	B0	The SDP Toolkit shall contain tools which access point structures.  These tools will create, open, close, attach, or detach to existing point structures.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3673	S-TKD-00254	B0	The SDP Toolkit shall contain tools to define the level within a point structure and to define the link between two levels within a point structure.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3674	S-TKD-00255	B0	The SDP Toolkit shall contain tools which read/write records and read/write attributes of point structures.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3675	S-TKD-00256	B0	The SDP Toolkit shall contain tools which perform inquiries to point structures.  These tools will return information about:  number of levels, number of records in a level, number of fields in a level, information about the defined spatial and temporal extent of point structures, and information about defined attributes of point structures.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3676	S-TKD-00257	B0	The SDP Toolkit shall contain tools which subset point structures.  These tools will define a region or time period of interest within a point structures, and read the region or time period of interest.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3677	S-TKD-00260	B0	The SDP Toolkit shall contain tools for the definition of and access to swath structures.  These structures will be based on standard HDF structures and will also be known as HDF-EOS swath structures.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3678	S-TKD-00261	B0	The SDP Toolkit shall contain tools which open an HDF file and create, read or write, attach or detach a swath structure within that file; and close the file.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3679	S-TKD-00262	B0	The SDP Toolkit shall contain tools which define:  swath data and geolocation dimensions, the mapping between geolocation and data dimensions, a new geolocation field, a new swath structure, a field compression method; and writes field metadata to geolocation or data fields.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3680	S-TKD-00263	B0	The SDP Toolkit shall contain tools which read/write data fields, read/write attributes within a swath, and sets or retrieves fill values for a field.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3681	S-TKD-00264	B0	The SDP Toolkit shall contain tools which perform inquiries to swath structures.  These tools will return information about:  dimensions, geolocation relations, geolocation and data mappings, geolocation and data fields, number and name of attributes, and defined region and time period.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3682	S-TKD-00265	B0	The SDP Toolkit shall contain tools which subset swath structures.  These tools will define, read, and extract a region of interest by latitude and longitude; and define, read and extract a time period of interest.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3683	S-TKD-00270	IR1	The SDP Toolkit shall contain tools that select data items within an HDF file, and read the selected data item, and optionally rewrite the HDF file with changes made to the data item.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3684	S-TKD-00271	IR1	The SDP Toolkit shall contain tools that list the contents of HDF files, and verify that the files are legal HDF files.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3685	S-TKD-00272	B0	The SDP Toolkit shall support tiling of SDSs within HDF-EOS files by setting up a data structure with an arbitrary number of internal tiles, reading and writing data tiles to that structure.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3686	S-TKD-00280	B0	The SDP Toolkit shall contain tools for the definition of and access to grid structures.  These structures will be based on standard HDF structures and will also be known as HDF-EOS grid structures.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3687	S-TKD-00281	B0	The SDP Toolkit shall contain tools which open an HDF file and create, read or write, attach or detach a grid structure within that file; and close the file.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3688	S-TKD-00282	B0	The SDP Toolkit shall contain tools which define:  origin of a grid, projection of a grid, pixel registration within a grid cell, data field within a grid, and a field compression method.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3689	S-TKD-00283	B0	The SDP Toolkit shall contain tools which read/write data, read/write attributes within a swath, and set and retrieve fill values for a field.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3690	S-TKD-00284	B0	The SDP Toolkit shall contain tools which perform inquiries to grid structures.  These tools will return information about:  data fields, dimensions, attributes, projection, geolocation, grid origin, and defined region.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3691	S-TKD-00285	B0	The SDP Toolkit shall contain tools which subset grid structures.  These tools will define and read a region of interest of a field or a vertical field, extract row/column for specified latitude/longitude pairs, extract field values for specified pixels, and perform bilinear interpolation for a grid field.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3692	S-TKD-00286	B0	The SDP Toolkit shall allow a user to perform nested subsetting on non-geolocation dimensions of an HDF-EOS grid data structure.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3693	S-TKD-00290	IR1	The SDP toolkit shall contain tools that read from and write to metadata information contained in HDF files.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3694	S-TKD-00321	IR1	The SDP toolkit shall contain tools to read from and write to HDF files.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3695	S-TKD-00324	IR1	The SDP toolkit shall contain tools to convert a single instance of selected HDF datatypes into files in formats identified by the ESDIS project.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3696	S-TKD-00360	IR1	The SDP Toolkit shall contain tools to open and close generic files, including text and binary files. These generic files will be limited to those produced by an ECS approved language.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3818	S-TKS-00190	TK5	The SDP Toolkit shall contain tools to open and close Science Data Processing Facility (SDPF), EOS Data and Operations System (EDOS)-generated Level 0 data sets or data sets from other sources as determined by the ESDIS Project.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3819	S-TKS-00200	TK5	The SDP Toolkit shall contain tools to read Consultative Committee on Space Data Systems (CCSDS)-format packetized data 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.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3820	S-TKS-00220	TK5	The SDP Toolkit shall include the capability to provide the first CCSDS packet after a given time.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3821	S-TKS-00225	TK5b	The SDP Toolkit shall return the number of Level 0 packets read to reach the Level 0 packet with the correct start time.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3822	S-TKS-00230	TK5	The SDP Toolkit shall contain tools to access the metadata located within Level 0 data files , (e.g., SDPF- and EDOS-generated header, accounting and quality information).	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3823	S-TKS-00235	TK5	The SDP Toolkit shall contain tools to access the ECS-internal metadata that is associated with the Level 0 data files provided to a PGE.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3824	S-TKS-00240	TK5	The SDP Toolkit shall provide tools to access SDPF-, EDOS-provided telemetry data, or access to data sets from other sources as determined by the ESDIS Project.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3825	S-TKS-00270	TK5	The SDP Toolkit shall contain tools that select data items within an HDF file, and read the selected data item, and optionally rewrite the HDF file with changes made to the data item.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3826	S-TKS-00271	TK5	The SDP Toolkit shall contain tools that list the contents of HDF files, and verify that the files are legal HDF files.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3827	S-TKS-00272	TK5b	The SDP Toolkit shall support tiling of SDSs within HDF-EOS files by setting up a data structure with an arbitrary number of internal tiles and reading and writing data tiles to that structure.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3828	S-TKS-00286	TK5b	The SDP Toolkit shall allow a user to perform nested subsetting on non-geolocation dimensions of an HDF-EOS grid data structure.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3829	S-TKS-00290	TK5	The SDP toolkit shall contain tools that read from and write to metadata information contained in HDF files.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3830	S-TKS-00321	TK5	The SDP toolkit shall contain tools to read from and write to HDF files.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3831	S-TKS-00324	TK5	The SDP toolkit shall contain tools to convert a single instance of selected HDF datatypes into files in formats identified by the ESDIS project.	99-0729	08/25/1999  	No Data	
369	PGS-0970	Complete	The ECS shall provide file access subroutines that enforce compliance with the adopted standard ECS formats.	3832	S-TKS-00360	TK5	The SDP Toolkit shall contain tools to open and close generic files, including text and binary files. These generic files will be limited to those produced by an ECS approved language.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4606	S-PLS-04020	5B	The PLANG CI shall determine which profile to run based on the ESDT version of each L1B input granule.	00-1157	12/20/2000  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4781	S-PLS-05290	SY3	The PLANG CI shall notify the operator in the event that it is not able to properly create a DPR	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4782	S-PLS-05300	SY3	The PLANG CI shall accept an on-demand processing order message for multiple higher level ASTER product, from the GTWAY CI.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4783	S-PLS-05310	SY3	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.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4784	S-PLS-05320	SY3	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.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4785	S-PLS-05330	SY3	The PLANG CI shall respond to the GTWAY CI for On-Demand Requests within 3 seconds per granule ordered.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4786	S-PLS-05340	SY3	The PLANG CI shall not fail requests for which the DPR cannot be correctly created but retain the request for possible operator attention.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4787	S-PLS-05350	SY3	The PLANG CI shall, for orders received from the GTWAY CI, accept an order that includes an MSS OrderID and RequestID.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4788	S-PLS-05360	SY3	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.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	4789	S-PLS-05370	SY3	The PLANG CI shall assign configurable distribution priorities to all on-demand product orders.	02-0980	11/13/2002  		
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	1515	S-DPS-21120	A	The PRONG CI shall create a Process Control File to provide information to the SDP Toolkit CI about the input data required to execute a PGE.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	1518	S-DPS-21130	A	The PRONG CI shall create a Process Control File to provide information to the SDP Toolkit CI about the output data generated from the executing PGE.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	1519	S-DPS-21140	A	The PRONG CI shall create a  mapping  of logical file handles to physical file handles in the Process Control File for the input data required to execute a PGE.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	1520	S-DPS-21150	A	The PRONG CI shall create a  mapping  of logical file handles to physical file handles in the Process Control File for the output data generated from the executing PGE.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3779	S-TKD-01290	IR1	The SDP Toolkit shall provide tools to deliver runtime parameter data to the PGE.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3780	S-TKD-01291	IR1	The SDP Toolkit shall provide command tools to deliver runtime parameter data to the PGE's shell.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3781	S-TKD-01310	IR1	The SDP Toolkit shall provide tools for retrieving file metadata (also known as file attributes) that is associated with files staged by the Data Processing Subsystem.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3782	S-TKD-01311	IR1	The SDP Toolkit shall provide tools for performing PGE initialization and termination procedures to support PGE usage of the Toolkit.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3783	S-TKD-01312	IR1	The SDP Toolkit shall provide a command tool to facilitate the execution of a PGE and its' initialization and termination.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3784	S-TKD-01313	IR1	The SDP Toolkit shall provide a command tool to perform format checking on files containing Process Control information.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3785	S-TKD-01314	IR1	The SDP Toolkit shall provide a command tool for retrieving file metadata that is associated with files staged by the Data Processing Subsystem.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3786	S-TKD-01315	IR1	The SDP Toolkit shall provide a command tool to retrieve the number of physical file instances that are associated with a single logical file instance.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3787	S-TKD-01316	B0	The SDP Toolkit shall provide a function which returns the size of a file entered in the Process Control File.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3913	S-TKS-01290	TK5	The SDP Toolkit shall provide tools to deliver runtime parameter data to the PGE.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3914	S-TKS-01291	TK5	The SDP Toolkit shall provide command tools to deliver runtime parameter data to the PGE's shell.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3915	S-TKS-01310	TK5	The SDP Toolkit shall provide tools for retrieving file metadata (also known as file attributes) that is associated with files staged by the Data Processing Subsystem.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3916	S-TKS-01311	TK5	The SDP Toolkit shall provide tools for performing PGE initialization and termination procedures to support PGE usage of the Toolkit.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3917	S-TKS-01312	TK5	The SDP Toolkit shall provide a command tool to facilitate the execution of a PGE and its' initialization and termination.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3918	S-TKS-01313	TK5	The SDP Toolkit shall provide a command tool to perform format checking on files containing Process Control information.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3919	S-TKS-01314	TK5	The SDP Toolkit shall provide a command tool for retrieving file metadata that is associated with files staged by the Data Processing Subsystem.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3920	S-TKS-01315	TK5	The SDP Toolkit shall provide a command tool to retrieve the number of physical file instances that are associated with a single logical file instance.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3921	S-TKS-01316	TK5b	The SDP Toolkit shall provide a function which returns the size of a file entered in the Process Control File.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3945	S-DPS-21010	5B	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.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3946	S-DPS-21012	5B	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.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3947	S-DPS-21014	5B	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.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3948	S-DPS-21016	5B	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.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3949	S-DPS-21018	5B	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.	99-0729	08/25/1999  	No Data	
370	PGS-0980	Complete	The ECS shall provide job control routines that provide all required task parameters to the Standard Product software.	3956	S-DPS-27000	5B	The PRONG CI shall provide the user specified values for PGE runtime parameters when executing an On-Demand PGE.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	1521	S-DPS-21160	A	The PRONG CI shall create a Status Message File to be used by the SDP Toolkit CI to collect Toolkit status and error information about the execution of a PGE.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	1522	S-DPS-21170	A	The PRONG CI shall create User Status Message Files to be used by the SDP Toolkit CI during PGE execution if requested through the data defining the characteristics of the PGE.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	1523	S-DPS-21180	A	The PRONG CI shall allocate 1 shared memory attachment  to a PGE to support access to internal memory during execution.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3710	S-TKD-00580	IR1	The SDP Toolkit shall contain tools that can test for multi-level error/status conditions.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3711	S-TKD-00581	IR1	The SDP Toolkit shall provide an ordering for the multi-level error/status conditions thus enabling them to be used in conditional expressions.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3712	S-TKD-00582	IR1	The SDP Toolkit shall contain tools that allow the user to assert an error/status condition with a discrete severity level.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3715	S-TKD-00600	IR1	The SDP Toolkit shall contain tools for recording user and Toolkit-defined error and status reports to log files.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3845	S-TKS-00580	TK5	The SDP Toolkit shall contain tools that can test for multi-level error/status conditions.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3846	S-TKS-00581	TK5	The SDP Toolkit shall provide an ordering for the multi-level error/status conditions thus enabling them to be used in conditional expressions.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3847	S-TKS-00582	TK5	The SDP Toolkit shall contain tools that allow the user to assert an error/status condition with a discrete severity level.	99-0729	08/25/1999  	No Data	
371	PGS-0990	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying the system operators of conditions requiring their attention.	3850	S-TKS-00600	TK5	The SDP Toolkit shall contain tools for recording user and Toolkit-defined error and status reports to log files.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	1521	S-DPS-21160	A	The PRONG CI shall create a Status Message File to be used by the SDP Toolkit CI to collect Toolkit status and error information about the execution of a PGE.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	1522	S-DPS-21170	A	The PRONG CI shall create User Status Message Files to be used by the SDP Toolkit CI during PGE execution if requested through the data defining the characteristics of the PGE.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	1523	S-DPS-21180	A	The PRONG CI shall allocate 1 shared memory attachment  to a PGE to support access to internal memory during execution.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	1783	S-DPS-61045	A	The SPRHW CI shall provide local consoles for maintenance and operation.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3663	S-TKD-00180	IR1	All SDP Toolkit functions shall return error/status codes that can be detected and reported using error/status reporting tools.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3710	S-TKD-00580	IR1	The SDP Toolkit shall contain tools that can test for multi-level error/status conditions.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3713	S-TKD-00590	IR1	The SDP Toolkit shall support the following levels for error/status conditions: fatal error, general error, warning error, notice status, user-defined status, informational message status and success status.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3714	S-TKD-00591	IR1	The SDP Toolkit shall provide the means of associating an action message with one or more status conditions.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3716	S-TKD-00610	IR1	The SDP Toolkit shall contain tools to uniquely identify the software unit, science software program, product and production run in error and status messages.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3717	S-TKD-00620	IR1	The SDP Toolkit shall contain tools to identify the associated instrument within the error message codes.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3718	S-TKD-00630	IR1	The SDP Toolkit shall provide a tool for marking all user requested files and status logs for subsequent retrieval by the SCF.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3719	S-TKD-00631	IR1	The SDP Toolkit shall support a tool for transferring all report and status logs to an intermediate location.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3720	S-TKD-00632	IR1	The SDP Toolkit shall contain tools for integrating Commercial-off-the-Shelf (COTS) status messages into the Toolkit wherever the Toolkit uses that COTS software.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3721	S-TKD-00650	IR1	The SDP Toolkit shall contain tools to associate with error messages at least the following: what routine noted the error, error-type, pertinent variable data, and action taken.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3722	S-TKD-00660	IR1	The SDP Toolkit shall contain tools to allow science algorithms to enable error trapping mechanisms for non-processing relating signals, and to issue the appropriate signal handling routines to respond to these events.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3723	S-TKD-00661	IR1	The SDP Toolkit shall be capable of performing context-sensitive buffering of status message information in order to provide an optimal level of efficiency.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3724	S-TKD-00662	IR1	The SDP Toolkit shall prevent the proliferation of duplicate status messages from being recorded in the status log files.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3725	S-TKD-00663	IR1	The SDP Toolkit shall provide the tools to enable and disable status messaging for user-specified calls.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3726	S-TKD-00664	IR1	The SDP Toolkit shall provide the tools to ensure that user status codes are unique across the entire ECS system.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3817	S-TKS-00180	TK5	All SDP Toolkit functions shall return error/status codes that can be detected and reported using error/status reporting tools.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3845	S-TKS-00580	TK5	The SDP Toolkit shall contain tools that can test for multi-level error/status conditions.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3848	S-TKS-00590	TK5	The SDP Toolkit shall support the following levels for error/status conditions: fatal error, general error, warning error, notice status, user-defined status, informational message status and success status.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3849	S-TKS-00591	TK5	The SDP Toolkit shall provide the means of associating an action message with one or more status conditions.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3851	S-TKS-00610	TK5	The SDP Toolkit shall contain tools to uniquely identify the software unit, science software program, product and production run in error and status messages.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3852	S-TKS-00620	TK5	The SDP Toolkit shall contain tools to identify the associated instrument within the error message codes.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3853	S-TKS-00630	TK5	The SDP Toolkit shall provide a tool for marking all user requested files and status logs for subsequent retrieval by the SCF.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3854	S-TKS-00631	TK5	The SDP Toolkit shall support a tool for transferring all report and status logs to an intermediate location.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3855	S-TKS-00632	TK5	The SDP Toolkit shall contain tools for integrating Commercial-off-the-Shelf (COTS) status messages into the Toolkit wherever the Toolkit uses that COTS software.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3856	S-TKS-00650	TK5	The SDP Toolkit shall contain tools to associate with error messages at least the following: what routine noted the error, error-type, pertinent variable data, and action taken.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3857	S-TKS-00660	TK5	The SDP Toolkit shall contain tools to allow science algorithms to enable error trapping mechanisms for non-processing relating signals, and to issue the appropriate signal handling routines to respond to these events.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3858	S-TKS-00661	TK5	The SDP Toolkit shall be capable of performing context-sensitive buffering of status message information in order to provide an optimal level of efficiency.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3859	S-TKS-00662	TK5	The SDP Toolkit shall prevent the proliferation of duplicate status messages from being recorded in the status log files.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3860	S-TKS-00663	TK5	The SDP Toolkit shall provide the tools to enable and disable status messaging for user-specified calls.	99-0729	08/25/1999  	No Data	
372	PGS-1000	Complete	The ECS shall provide error logging subroutines for use by Standard Product software in notifying users of conditions requiring their attention.	3861	S-TKS-00664	TK5	The SDP Toolkit shall provide the tools to ensure that user status codes are unique across the entire ECS system.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3683	S-TKD-00270	IR1	The SDP Toolkit shall contain tools that select data items within an HDF file, and read the selected data item, and optionally rewrite the HDF file with changes made to the data item.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3705	S-TKD-00520	B0	The SDP Toolkit shall contain a tool for marking temporary files for deletion, enabling reuse of the logical file ID within the science software.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3706	S-TKD-00521	IR1	The SDP Toolkit shall contain a command tool for marking temporary files for deletion, enabling reuse of the logical file ID within the science software, while preserving the record of the defunct temporary file.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3707	S-TKD-00530	IR1	The SDP Toolkit shall create temporary file names such that each name is unique for a given DAAC.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3708	S-TKD-00531	IR1	SDP Toolkit shall contain a tool for creating "intermediate" files, whose longevity is determined by the user up to ECS defined limits, e.g., a temporary calibration file may be retained as an intermediate file from the last orbit's processing or a file kept for averaging purposes for several months.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3709	S-TKD-00535	IR1	The SDP Toolkit shall contain command tools for creating and retrieving intermediate and temporary file reference names at the level of the PGE's script.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3825	S-TKS-00270	TK5	The SDP Toolkit shall contain tools that select data items within an HDF file, and read the selected data item, and optionally rewrite the HDF file with changes made to the data item.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3840	S-TKS-00520	TK5	The SDP Toolkit shall contain a tool for marking temporary files for deletion, enabling reuse of the logical file ID within the science software.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3841	S-TKS-00521	TK5	The SDP Toolkit shall contain a command tool for marking temporary files for deletion, enabling reuse of the logical file ID within the science software, while preserving the record of the defunct temporary file.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3842	S-TKS-00530	TK5	The SDP Toolkit shall create temporary file names such that each name is unique for a given DAAC.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3843	S-TKS-00531	TK5	SDP Toolkit shall contain a tool for creating "intermediate" files, whose longevity is determined by the user up to ECS defined limits, e.g., a temporary calibration file may be retained as an intermediate file from the last orbit's processing or a file kept for averaging purposes for several months.	99-0729	08/25/1999  	No Data	
373	PGS-1010	Complete	The ECS shall provide mass storage allocation subroutines that provide Science Software with a means for dynamic allocation of storage for temporary files.	3844	S-TKS-00535	TK5	The SDP Toolkit shall contain command tools for creating and retrieving intermediate and temporary file reference names at the level of the PGE's script.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3995	S-TKS-00745	TK5a	The SDP Toolkit shall return the orbit number of a spacecraft for a given time.	99-0764	08/25/1999  		
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	1606	S-DPS-30675	B0	The PRONG CI shall use FDF 2800-byte block, binary EPHEM formatted EOS-AM definitive orbit data to replace EOS-AM onboard orbit data that cannot be repaired by FDF supplied interpolation subroutines.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	1607	S-DPS-30710	B0	The PRONG CI shall provide to the SDP Toolkit, metadata with the ephemeris data files for EOS-AM processing in the standard format for ephemeris files as defined by the SDP Toolkit.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3727	S-TKD-00680	IR1	Input to all relevant SDP Toolkit planetary body and spacecraft position access functions shall include spacecraft identification.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3728	S-TKD-00710	IR1	The SDP Toolkit shall use a single standard internal time in all ephemeris calculations.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3729	S-TKD-00720	IR1	The SDP Toolkit shall provide tools to return spacecraft position, velocity, attitude, and quaternion defining the rotation from spacecraft to Earth Centered Inertial reference frame for any given time or for a range of times, including provision for interpolation between state vectors.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3730	S-TKD-00740	IR1	SDP Toolkit shall have the capability to provide to the user quality information about position and attitude.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3731	S-TKD-00745	B0	The SDP Toolkit shall return the orbit number of a spacecraft for a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3732	S-TKD-00760	IR1	The SDP Toolkit shall contain tools that return local solar time for a given UTC time and position on the Earth's surface, as well as solar right ascension and declination.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3733	S-TKD-00770	IR1	The SDP Toolkit shall contain tools that return Greenwich Hour Angle for a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3734	S-TKD-00780	IR1	The SDP Toolkit shall contain tools that return a flag for the presence of a celestial body in the field of view.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3735	S-TKD-00800	IR1	The SDP Toolkit shall contain a tool that returns the Earth-Centered Inertial (ECI) vector from the Earth to the sun, moon, and planets at a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3736	S-TKD-00810	IR1	The SDP Toolkit shall contain a tool that returns the Satellite-Centered Inertial (SCI) vector from the Satellite to the sun, moon, and planets at a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3739	S-TKD-00860	IR1	The SDP Toolkit shall contain a tool to determine if a given point on the earth's surface is in day or in night.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3740	S-TKD-00870	IR1	The SDP Toolkit shall contain tools to access a land/sea classification database including coastal outlines.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3741	S-TKD-00900	IR1	The toolkit shall provide access to Greenwich Mean and Greenwich Apparent Sidereal Time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3742	S-TKD-00910	IR1	The SDP Toolkit shall provide a tool to transform a position and velocity vector between J2000 and true of date coordinate systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3743	S-TKD-00912	IR1	The SDP Toolkit shall provide a tool to transform a position and velocity vector between J2000 and mean of date coordinate systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3744	S-TKD-00914	IR1	The SDP Toolkit shall provide a tool to transform a position and velocity vector between mean of date and true of date coordinate systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3745	S-TKD-00916	IR1	The SDP Toolkit shall provide a tool to provide the angles of nutation in longitude and obliquity and their respective rates at a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3746	S-TKD-00930	IR1	Geographic information access tools in the SDP Toolkit shall be capable of handling the north and south pole singularities, e.g., such a way that no failures, such as division by zero or erratic results in terms of positions will occur on approaching or passing over the poles.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3760	S-TKD-01050	IR1	The SDP Toolkit shall provide the following lower level coordinate system bi-directional transformations:  a. spacecraft reference to orbital reference  b. Earth-Centered Inertial (ECI) to Earth-Centered Rotating (ECR)   c. ECR to geodeticd. ECI to spacecraft reference  e. ECI to orbital reference	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3761	S-TKD-01060	IR1	The SDP Toolkit shall provide the sub-satellite point and ground track velocity vector at any arbitrary time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3763	S-TKD-01080	IR1	The SDP Toolkit shall provide the latitude and longitude of the intersection of the earth reference ellipsoid with the instrument look vector in the spacecraft reference frame at an arbitrary time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3764	S-TKD-01083	IR1	The SDP Toolkit shall provide a tool to geolocate every pixel (with its own look angle).	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3765	S-TKD-01090	IR1	The SDP Toolkit shall provide a tool to determine a given point on earth is in an instrument field of view at any designated time. Parameters that determine instrument field-of-view relative to a platform are assumed to be supplied by instrument teams.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3766	S-TKD-01091	IR1	The SDP Toolkit shall provide the capability of determining the terrestrial zenith angle and azimuth of the look vector, as well as the vectors to any celestial body, at any specified latitude, longitude and altitude.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3767	S-TKD-01092	IR1	The SDP Toolkit shall provide the capability of determining the angle of refraction of the look vector, other vectors at the look point and the displacement of the ray at the look point due to refraction, under mean atmospheric conditions.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3768	S-TKD-01160	IR1	The SDP Toolkit shall contain time system transformation tools that return UTC and TAI (International Atomic Time) times and Julian Dates that are of the same precision as the spacecraft clock.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3769	S-TKD-01170	IR1	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  f. Global Positioning System (GPS)	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3770	S-TKD-01180	IR1	Where applicable, the SDP Toolkit time system transformation tools shall return ASCII times that are in Consultative Committee for Space Data Systems (CCSDS) standard time code formats.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3771	S-TKD-01190	IR1	The SDP Toolkit time system transformation tools shall have the capability of returning TAI time in seconds from the start of a specified epoch.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3772	S-TKD-01210	IR1	The SDP Toolkit shall assure that leap seconds are accounted for in all time and date conversion tools for binary formats, and leap days/years for ASCII formats.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3773	S-TKD-01215	IR1	The SDP Toolkit shall contain tools to convert UTC to UT1 and ephemeris times.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3774	S-TKD-01220	IR1	The SDP Toolkit shall contain provision to transform UTC and TAI to and from Julian Day formats, and to provide UT1 as a Julian Date, as well as a difference from UTC.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3788	S-TKD-01360	IR1	The SDP Toolkit shall provide access to ancillary data sets used by several instrument processing systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3790	S-TKD-01365	IR1	The SDP toolkit shall provide an interface that accepts simple searches for parameter values on a PARAMETER=VALUE basis and returns parameter values.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3794	S-TKD-01500	B0	The SDP toolkit shall support the bi-directional transformation between coordinates in the following projections:  a.  Cartesian ellipsoid reference frame and the Space Oblique Mercator  b.  Universal Transverse Mercator  c.  Polar Stereographic  d.  Goodes Interrupted Homolosine  e.  Integerized Sinusoidal Grid  f.  Lambert Confromal Conic  g.  Polyconic  h.  Transverse Mercator  i.  Hotin Oblique Mercator.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3795	S-TKD-01502	IR1	The SDP Toolkit geo-coordinate transformation tools shall support the transformation of multiple coordinate vectors in a single call.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3862	S-TKS-00680	TK5	Input to all relevant SDP Toolkit planetary body and spacecraft position access functions shall include spacecraft identification.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3863	S-TKS-00710	TK5	The SDP Toolkit shall use a single standard internal time in all ephemeris calculations.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3864	S-TKS-00720	TK5	The SDP Toolkit shall provide tools to return spacecraft position, velocity, attitude, and quaternion defining the rotation from spacecraft to Earth Centered Inertial reference frame for any given time or for a range of times, including provision for interpolation between state vectors.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3865	S-TKS-00740	TK5	SDP Toolkit shall have the capability to provide to the user quality information about position and attitude.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3866	S-TKS-00760	TK5	The SDP Toolkit shall contain tools that return local solar time for a given UTC time and position on the Earth's surface, as well as solar right ascension and declination.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3867	S-TKS-00770	TK5	The SDP Toolkit shall contain tools that return Greenwich Hour Angle for a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3868	S-TKS-00780	TK5	The SDP Toolkit shall contain tools that return a flag for the presence of a celestial body in the field of view.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3869	S-TKS-00800	TK5	The SDP Toolkit shall contain a tool that returns the Earth-Centered Inertial (ECI) vector from the Earth to the sun, moon, and planets at a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3870	S-TKS-00810	TK5	The SDP Toolkit shall contain a tool that returns the Satellite-Centered Inertial (SCI) vector from the Satellite to the sun, moon, and planets at a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3873	S-TKS-00860	TK5	The SDP Toolkit shall contain a tool to determine if a given point on the earth's surface is in day or in night.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3874	S-TKS-00870	TK5	The SDP Toolkit shall contain tools to access a land/sea classification database including coastal outlines.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3875	S-TKS-00900	TK5	The toolkit shall provide access to Greenwich Mean and Greenwich Apparent Sidereal Time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3876	S-TKS-00910	TK5	The SDP Toolkit shall provide a tool to transform a position and velocity vector between J2000 and true of date coordinate systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3877	S-TKS-00912	TK5	The SDP Toolkit shall provide a tool to transform a position and velocity vector between J2000 and mean of date coordinate systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3878	S-TKS-00914	TK5	The SDP Toolkit shall provide a tool to transform a position and velocity vector between mean of date and true of date coordinate systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3879	S-TKS-00916	TK5	The SDP Toolkit shall provide a tool to provide the angles of nutation in longitude and obliquity and their respective rates at a given time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3880	S-TKS-00930	TK5	Geographic information access tools in the SDP Toolkit shall be capable of handling the north and south pole singularities, e.g., such a way that no failures, such as division by zero or erratic results in terms of positions will occur on approaching or passing over the poles.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3894	S-TKS-01050	TK5	The SDP Toolkit shall provide the following lower level coordinate system bi-directional transformations:  a. spacecraft reference to orbital reference  b. Earth-Centered Inertial (ECI) to Earth-Centered Rotating (ECR)   c. ECR to geodeticd. ECI to spacecraft reference  e. ECI to orbital reference	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3895	S-TKS-01060	TK5	The SDP Toolkit shall provide the sub-satellite point and ground track velocity vector at any arbitrary time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3897	S-TKS-01080	TK5	The SDP Toolkit shall provide the latitude and longitude of the intersection of the earth reference ellipsoid with the instrument look vector in the spacecraft reference frame at an arbitrary time.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3898	S-TKS-01083	TK5	The SDP Toolkit shall provide a tool to geolocate every pixel (with its own look angle).	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3899	S-TKS-01090	TK5	The SDP Toolkit shall provide a tool to determine a given point on earth is in an instrument field of view at any designated time. Parameters that determine instrument field-of-view relative to a platform are assumed to be supplied by instrument teams.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3900	S-TKS-01091	TK5	The SDP Toolkit shall provide the capability of determining the terrestrial zenith angle and azimuth of the look vector, as well as the vectors to any celestial body, at any specified latitude, longitude and altitude.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3901	S-TKS-01092	TK5	The SDP Toolkit shall provide the capability of determining the angle of refraction of the look vector, other vectors at the look point and the displacement of the ray at the look point due to refraction, under mean atmospheric conditions.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3902	S-TKS-01160	TK5	The SDP Toolkit shall contain time system transformation tools that return UTC and TAI (International Atomic Time) times and Julian Dates that are of the same precision as the spacecraft clock.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3903	S-TKS-01170	TK5	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  f. Global Positioning System (GPS)	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3904	S-TKS-01180	TK5	Where applicable, the SDP Toolkit time system transformation tools shall return ASCII times that are in Consultative Committee for Space Data Systems (CCSDS) standard time code formats.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3905	S-TKS-01190	TK5	The SDP Toolkit time system transformation tools shall have the capability of returning TAI time in seconds from the start of a specified epoch.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3906	S-TKS-01210	TK5	The SDP Toolkit shall assure that leap seconds are accounted for in all time and date conversion tools for binary formats, and leap days/years for ASCII formats.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3907	S-TKS-01215	TK5	The SDP Toolkit shall contain tools to convert UTC to UT1 and ephemeris times.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3908	S-TKS-01220	TK5	The SDP Toolkit shall contain provision to transform UTC and TAI to and from Julian Day formats, and to provide UT1 as a Julian Date, as well as a difference from UTC.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3922	S-TKS-01360	TK5	The SDP Toolkit shall provide access to ancillary data sets used by several instrument processing systems.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3924	S-TKS-01365	TK5	The SDP toolkit shall provide an interface that accepts simple searches for parameter values on a PARAMETER=VALUE basis and returns parameter values.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3927	S-TKS-01500	TK5b	The SDP toolkit shall support the bi-directional transformation between coordinates in the following projections:  a.  Cartesian ellipsoid reference frame and the Space Oblique Mercator  b.  Universal Transverse Mercator  c.  Polar Stereographic  d.  Goodes Interrupted Homolosine  e.  Integerized Sinusoidal Grid  f.  Lambert Confromal Conic  g.  Polyconic  h.  Transverse Mercator  i.  Hotin Oblique Mercator.	99-0729	08/25/1999  	No Data	
374	PGS-1015	Complete	The ECS shall provide ancillary data access subroutines that provide Standard Product software access to ephemeris data (e.g., solar, lunar, and satellite   ephemeris ), Earth rotation data, and time and position measurement data.  These subroutines shall perform operations such as:  a. Interpolation  b. Extrapolation  c. Coordinate system conversion	3928	S-TKS-01502	TK5	The SDP Toolkit geo-coordinate transformation tools shall support the transformation of multiple coordinate vectors in a single call.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	381	S-CLS-10430	A	The WKBCH CI shall provide the capability of displaying two-dimensional data arrays as pseudocolor images.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	383	S-CLS-10450	A	The WKBCH CI shall provide the capability of zooming and panning raster images.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	385	S-CLS-10470	B1	The WKBCH CI shall provide users the capability to display ECS HDF-EOS formatted data in vector graphic format.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	387	S-CLS-10490	B1	The WKBCH CI shall provide the capability of displaying a horizontal or vertical profile through a pseudo-color image.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	388	S-CLS-10500	B1	The WKBCH CI shall provide the capability of displaying multi-dimensional arrays of data as a series of two-dimensional pseudo-color images.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	395	S-CLS-10570	A	The WKBCH CI shall produce visualizations of images needed for QA, validation, Algorithm development, calibration functions, parameter verification and anomaly detection.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	396	S-CLS-10580	A	The WKBCH CI shall produce visualizations of multi-dimensional arrays needed for QA, Validation, Algorithm development, calibration functions, parameter verification and anomaly detection.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3704	S-TKD-00510	IR1	The SDP Toolkit shall contain tools that support three types of Q/A data: (1) flags; (2) graphics files, which are output directly from science processes; and (3) data that is written in the same format as a standard product file.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3792	S-TKD-01410	IR1	The SDP Toolkit shall provide tools for producing graphics output from production software.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3793	S-TKD-01415	IR1	The SDP Toolkit shall provide tools for image processing; for map projections; correlations and registration; filters; contrast enhancement.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3796	S-TKD-01520	IR1	The SDP Toolkit shall provide a means of accessing commonly used mathematical and physical constants.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3839	S-TKS-00510	TK5	The SDP Toolkit shall contain tools that support three types of Q/A data: (1) flags; (2) graphics files, which are output directly from science processes; and (3) data that is written in the same format as a standard product file.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3925	S-TKS-01410	TK5	The SDP Toolkit shall provide tools for producing graphics output from production software.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3926	S-TKS-01415	TK5	The SDP Toolkit shall provide tools for image processing; for map projections; correlations and registration; filters; contrast enhancement.	99-0729	08/25/1999  	No Data	
376	PGS-1025	Complete	The ECS shall provide the capability to perform:    a. Data visualization	3929	S-TKS-01520	TK5	The SDP Toolkit shall provide a means of accessing commonly used mathematical and physical constants.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3651	S-TKD-00010	IR1	The interfaces provided by the SCF Toolkit functions to the science software shall either be identical to the interfaces provided by the SDP Toolkit functions to the science software, or they will be transparent emulations.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3652	S-TKD-00020	IR1	Calling sequences of SCF Toolkit functions and SDP Toolkit functions shall be identical.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3653	S-TKD-00040	IR1	Logical file paths referenced by SCF Toolkit functions and SDP Toolkit functions shall be identical, i.e., all file references shall be by logical file names.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3654	S-TKD-00090	IR1	The SCF Toolkit shall contain error/status handling and reporting capabilities identical to those available in the SDP Toolkit.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3655	S-TKD-00100	IR1	The SCF Toolkit shall contain versions that have been certified for each of the ECS approved computing platforms.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3656	S-TKD-00101	IR1	The SCF Toolkit shall exhibit its portability and adaptability by producing the same results (to an agreed upon tolerance) on each of the approved computing platforms.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3659	S-TKD-00140	IR1	The SCF Toolkit shall provide access to Level 0 data provided by science software developers and/or ESDIS.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3660	S-TKD-00141	IR1	The SCF Toolkit shall provide access to simulated orbit data for at least 1 day and 1 night (15 consecutive orbits).	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3661	S-TKD-00160	IR1	The ECS contractor shall provide an Algorithm Integration Team at each DAAC, whose function shall be to answer questions about the SCF and SDP Toolkits, PDPS design and operations concept, and the science software integration and test process.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3662	S-TKD-00170	IR1	A detailed user's guide for the SCF Toolkit shall be delivered, in both hardcopy and electronic versions, and shall include at a minimum detailed descriptions of the SDP Toolkit; all differences between the SCF and PDPS versions, both visible and invisible to Toolkit users, a set of sample production shell scripts; and sample makefiles.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3801	S-TKS-00010	TK5	The interfaces provided by the SCF Toolkit functions to the science software shall either be identical to the interfaces provided by the SDP Toolkit functions to the science software, or they will be transparent emulations.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3802	S-TKS-00020	TK5	Calling sequences of SCF Toolkit functions and SDP Toolkit functions shall be identical.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3803	S-TKS-00040	TK5	Logical file paths referenced by SCF Toolkit functions and SDP Toolkit functions shall be identical, i.e., all file references shall be by logical file names.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3804	S-TKS-00050	TK5	The SCF Toolkit shall provide the capability to run a production process in the SCF test environment.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3805	S-TKS-00060	TK5	The SCF Environment shall provide the capability for science software developers to generate a production script, capable of linking multiple Product Generation Executive (formerly Product Generation Executable) (PGEs) into a single SCF command.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3806	S-TKS-00080	TK5	The SCF Toolkit shall provide the capability to test all I/O transactions among PGEs that originate in the science software, in the same manner as the production environment.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3807	S-TKS-00090	TK5	The SCF Toolkit shall contain error/status handling and reporting capabilities identical to those available in the SDP Toolkit.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3808	S-TKS-00100	TK5	The SCF Toolkit shall contain versions that have been certified for each of the ECS approved computing platforms.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3809	S-TKS-00101	TK5	The SCF Toolkit shall exhibit its portability and adaptability by producing the same results (to an agreed upon tolerance) on each of the approved computing platforms.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3812	S-TKS-00122	TK5	The SDP Toolkit shall be supported under the following UNIX shells: Bourne, csh and the Perl language.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3813	S-TKS-00123	TK5	SCF Toolkit source code shall be delivered to the SCFs.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3814	S-TKS-00140	TK5	The SCF Toolkit shall provide access to Level 0 data provided by science software developers and/or ESDIS.	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3815	S-TKS-00141	TK5	The SCF Toolkit shall provide access to simulated orbit data for at least 1 day and 1 night (15 consecutive orbits).	99-0729	08/25/1999  	No Data	
377	PGS-1030	Complete	The ECS shall provide a toolkit for external processing containing versions of the routines specified in requirements PGS-0970 to PGS-1015.	3816	S-TKS-00170	TK5	A detailed user's guide for the SCF Toolkit shall be delivered, in both hardcopy and electronic versions, and shall include at a minimum detailed descriptions of the SDP Toolkit; all differences between the SCF and PDPS versions, both visible and invisible to Toolkit users, a set of sample production shell scripts; and sample makefiles.	99-0729	08/25/1999  	No Data	
394	PGS-1410	Complete	The ECS shall provide the capability for each DAAC to add to the SDP Toolkit DAAC-developed software required to support discipline specific needs.	1459	S-DPS-20020	B0	The PRONG CI shall have the capability to incorporate DAAC-developed software (PGEs) required to support discipline specific needs.	99-0729	08/25/1999  	No Data	
401	SDPS0091	5A Future	The ECS shall receive a quality report that is generated and transmitted by the PIs or the other science users, and associated with the data products being archived by the  ECS.	450	S-CLS-11100	B1	The WKBCH CI shall accept from the users, user feedback information on product data quality assessment and output it to the DAAC originating the data.	99-0729	08/25/1999  	No Data	
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4082	S-INS-00549	5B	The INGST CI shall be configured to ingest AMSR ADEOS data in accordance with the SIPS ICD.	99-0954	10/04/1999  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4228	S-INS-00541	6A	The INGST CI shall be configured to ingest GLAS data in accordance with the SIPS ICD.	00-0020	01/10/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4364	S-INS-00543	6A	The INGST CI shall be configured to ingest PM-1 MODAPS data in accordance with the SIPS ICD.	00-0343	04/03/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4365	S-INS-00542	5B	The INGST CI shall be configured to ingest EMOS history file data in accordance with the SIPS ICD.	00-0343	04/03/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4366	C-CSS-50478	6A	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. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4367	C-CSS-50130	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4368	C-CSS-50106	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4369	C-CSS-50290	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4370	C-CSS-50015	6A	The MTMGW CI shall base its external interface on remote shell commands submitted by the SIPS via ssh.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4371	C-CSS-50040	6A	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.  	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4372	C-CSS-50514	6A	The MTMGW CI shall reject an integrated search & order request if the search was truncated by the SDSRV.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4373	C-CSS-50150	6A	The MTMGW CI shall translate a search request into a SDSRV inventory search.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4374	C-CSS-50310	6A	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).	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4375	C-CSS-50180	6A	The MTMGW CI shall return the inventory search result formatted in XML in the inventory search response.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4376	C-CSS-50090	6A	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 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4377	C-CSS-50095	6A	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 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4378	C-CSS-50100	6A	The MTMGW CI shall route requests to the MTMGW server that is configured to handle the requests from the respective external client. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4379	C-MSS-75107	6A	The MSS Accountability Service GUI shall allow operators to view orders and requests by external request ID; and external request ID plus user ID. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4380	C-MSS-75106	6A	The MSS Accountability Service shall keep an external request ID and an rpcID as part of the order tracking information. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4381	C-CSS-50070	6A	The MTMGW CI requests and responses shall be ASCII text.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4382	C-CSS-50050	6A	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.  	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4383	C-CSS-50060	6A	The MTMGW CI shall reject requests that cannot be identified as coming from an authorized external client. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4384	C-MSS-75108	6A	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. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4385	C-CSS-50510	6A	The MTMGW CI shall reject a product request and an integrated search & order request if the maximum size permitted for integrated ordering is exceeded.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4386	C-CSS-50360	6A	The MTMGW CI shall verify on start-up that a valid MSS user ID has been configured as the default user ID.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4387	C-CSS-50365	6A	The MTMGW CI shall reject requests that do not provide a user ID if no default user ID has been configured.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4388	C-CSS-50101	6A	The MTMGW CI shall permit an external client to specify a Message Identifier in each request message. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4389	S-DSS-00073	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4390	C-CSS-50392	6A	The MTMGW CI shall initialize the request status to NULL.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4391	C-CSS-50274	6A	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. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4392	C-CSS-50477	6A	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. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4393	C-CSS-50022	6A	The MTMGW CI shall allow operators to execute several MTMGW servers concurrently, each to be used by a different SIPS.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4394	C-CSS-50400	6A	The MTMGW CI shall not process product requests, or searches, or integrated search & orders for Landsat products.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4395	C-CSS-50024	6A	The MTMGW CI shall allow operators to provide a separate set of configuration parameter values for each MTMGW server.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4396	C-CSS-50185	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4397	C-CSS-50140	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4398	C-CSS-50160	6A	The MTMGW CI shall submit inventory searches to the local SDSRV CI.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4399	C-CSS-50155	6A	The MTMGW CI shall use the generic spatial search type when submitting a search request to the SDSRV.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4400	C-CSS-50394	6A	The MTMGW CI shall initialize the order type to MM.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4401	S-DSS-00080	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4403	C-CSS-50010	6A	The MTMGW CI shall provide an external communications interface to receive requests for locally archived data and return responses.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4404	C-CSS-50020	6A	The MTMGW CI shall be able to execute  multiple concurrent requests from a single as well as multiple SIPS.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4405	C-CSS-50030	6A	The MTMGW CI shall permit operators to configure the maximum number of concurrent requests that can be in progress at each MTMGW server.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4406	C-CSS-50080	6A	The MTMGW CI shall validate request syntax and return an error response if the syntax is invalid.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4407	C-CSS-50102	6A	The MTMGW CI shall assume a Message Identifier of NULL if the client does not provide one.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4408	C-CSS-50104	6A	The MTMGW CI shall return the Message Identifier provided by the client in its response message to that request. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4409	C-CSS-50110	6A	The MTMGW CI shall receive inventory search requests from external clients.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4410	C-CSS-50120	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4411	S-DSS-00168	6A	The SDSRV CI shall accept inventory searches from the local MTMGW CI.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4412	S-DSS-00169	6A	The SDSRV CI shall interface with the local MTMGW CI to return inventory search results for the searches the MTMGW CI submitted.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4413	C-CSS-50170	6A	The MTMGW CI shall accept inventory search results from the local SDSRV CI.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4414	C-CSS-50190	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4415	C-CSS-50200	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4416	C-CSS-50202	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4417	C-CSS-50210	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4418	C-CSS-50220	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4419	C-CSS-50230	6A	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. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4420	C-CSS-50250	6A	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. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4421	C-CSS-50252	6A	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 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4422	C-CSS-50255	6A	The MTMGW CI shall include in each inventory search response the total number of granules returned by the SDSRV.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4423	C-CSS-50270	6A	The MTMGW CI shall receive product requests from external client.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4424	C-CSS-50272	6A	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 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4425	C-CSS-50280	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4426	C-CSS-50300	6A	The MTMGW CI product request shall permit an external client to specify contact and shipping information.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4427	C-CSS-50320	6A	The MTMGW CI product request shall permit an external client to order the specified data granules.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4428	C-CSS-50330	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4429	C-CSS-50340	6A	The MTMGW CI requests shall permit an external client to include an MSS User ID in each request.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4430	C-CSS-50342	6A	The MTMGW CI shall obtain the MSS user profile of the external client based on the user ID contained in a request, if present.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4431	C-CSS-50350	6A	The MTMGW CI shall use an operator configurable default user ID if a request does not contain a user ID.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4432	C-CSS-50352	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4433	C-CSS-50370	6A	The MTMGW CI shall obtain the priority of a request from the user profile.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4434	C-CSS-50390	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4435	C-CSS-50410	6A	The MTMGW CI shall translate product requests into SDSRV asynchronous ACQUIRE requests.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4436	C-CSS-50420	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4437	C-CSS-50430	6A	The MTMGW CI shall include the MSS user ID and request priority in all acquire requests it generates.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4438	C-CSS-50432	6A	The MTMGW CI shall include the external request ID in the USERSTRING of any acquire request it submits.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4439	S-DSS-00072	6A	The SDSRV CI shall receive acquire requests from the local MTMGW CI.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4440	S-DSS-00074	6A	The SDSRV CI shall interface with the local MTMGW CI to return acquire responses for the acquire requests the MTMGW CI submitted.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4441	C-CSS-50440	6A	The MTMGW CI shall receive acquire request responses from the local SDSRV CI.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4442	C-CSS-50450	6A	The MTMGW CI shall include the MSS orderID in the product request response if the product request was successfully submitted.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4443	C-CSS-50460	6A	The MTMGW CI shall include the type of error encountered in the product request response if the product request was not accepted.  	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4444	C-CSS-50465	6A	The MTMGW CI shall receive integrated search & order requests from external client.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4445	C-CSS-50470	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4446	C-CSS-50472	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4447	C-CSS-50473	6A	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 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4448	C-CSS-50474	6A	The MTMGW CI integrated search & order request shall permit an external client to order the data granules returned by the SDSRV search.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4449	C-CSS-50475	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4450	C-CSS-50476	6A	The MTMGW CI shall include an rpcID in the ACQUIRE submitted for a product request or integrated search & order request. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4451	C-CSS-50480	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4452	C-CSS-50490	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4453	C-CSS-50500	6A	The MTMGW CI shall translate the search specified in an integrated search & order requests into an SDSRV inventory search.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4454	C-CSS-50512	6A	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) 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4455	C-CSS-50516	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4456	C-CSS-50520	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4457	C-CSS-50522	6A	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.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4458	C-CSS-50530	6A	The MTMGW CI shall include in the integrated search & order response the MSS orderID if the product request was successfully submitted.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4459	C-CSS-50532	6A	The MTMGW CI shall include in the  integrated search & order response the type of error that was encountered if the request failed.  	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4460	C-CSS-50534	6A	The MTMGW CI shall include the number of granules that have been ordered in the response for an integrated search & order request.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4461	C-CSS-50540	6A	The MTMGW CI shall allow operators to monitor its state from a system operator console. 	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4462	C-CSS-50550	6A	The MTMGW CI shall allow operators to start and shut it down from a system operator console.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4463	C-CSS-50560	6A	The MTMGW CI shall be able to operate in multiple modes.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4464	C-CSS-50570	6A	The MTMGW CI shall re-initialize its state upon restart, i.e., it shall always cold start.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4471	C-CSS-50650	6A	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).	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4472	C-CSS-50660	6A	The MTMGW CI shall log all errors.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4474	C-CSS-50680	6A	The MTMGW CI shall obtain from the DDICT CI core and product-specific attribute type information specified in a search request.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4475	C-DMS-20131	6A	The DDICT CI shall accept requests for core and product-specific attribute type information specified in a search request from the local MTMGW CI.	00-0284	04/05/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4478	C-CSS-50665	6A	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.	00-0437	04/26/2000  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4624	S-INS-00600	6B	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   	01-0506A	07/02/2001  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4625	S-INS-00601	6B	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       	01-0506A	07/02/2001  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4626	S-INS-00602	6B	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   	01-0506A	07/02/2001  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	4627	S-INS-00603	6B	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  	01-0506A	07/02/2001  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	5915	C-CSS-51010	SY4	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.	03-0682	10/09/2003  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	5916	C-CSS-51020	SY4	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.	03-0682	10/09/2003  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	5917	C-CSS-51030	SY4	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.	03-0682	10/09/2003  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	5918	C-CSS-51040	SY4	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.	03-0682	10/09/2003  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	5919	C-CSS-51050	SY4	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].	03-0682	10/09/2003  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	5920	C-CSS-51060	SY4	When configured to submit orders to the OMS, the MTMGW CI shall set the order source for the MSS orders it creates to 'MTMGW'.	03-0682	10/09/2003  		
402	SDPS0092	5B 6A	The ECS shall provide an interface as defined in the Science Investigator-led Processing Systems (SIPS) ICD for supporting external production and reprocessing of standard ECS products.	133	S-INS-00540	5B	The INGST CI shall be configured to ingest PM-1 data in accordance with the SIPS ICD.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2038	S-DSS-04020	B0	The SDSRV CI shall provide the capability to process Data Requests for the retrieval and distribution of metadata and data (if any), for the data types specified in the Data Type Services Matrix.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2040	S-DSS-04022	B0	The SDSRV CI shall retrieve metadata, specified by valid Data Requests, from the Metadata Database and provide that metadata to the DDIST CI.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2041	S-DSS-04024	B0	The SDSRV CI shall direct the DDIST CI to retrieve data files, and to distribute data files and associated metadata as specified by valid Data Requests.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2042	S-DSS-04026	B0	The DDIST CI shall direct the retrieval of data files, and direct the distribution of data files and associated metadata as directed by the SDSRV CI.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2043	S-DSS-04028	B0	The DDIST CI shall receive metadata from the SDSRV CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2044	S-DSS-04030	B0	The DDIST CI shall direct the retrieval of data files from the STMGT CI as specified by requests received from the SDSRV CI.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2131	S-DSS-20005	B0	The STMGT CI shall retrieve data files from the archive, as specified by requests received from the DDIST CI.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2331	S-DSS-30711	A	The DDIST CI shall be capable of sending data to a remote DAAC.	99-0729	08/25/1999  	No Data	
404	SDPS0130	5A Future	The ECS shall provide the capability for DAACs to exchange data products, metadata, and data quality information.	2342	S-DSS-30840	B1	The DDIST CI shall support distributing product QA data produced at the collocated Data Processing Subsystem within 1 hour from the time it is ready.	99-0729	08/25/1999  	No Data	
408	SMC-0300	Complete	The ECS shall be designed to accommodate 100 percent growth in System Management processing capacity without requiring modifications or upgrades to existing applications   software.	846	C-CSS-03700	B0	The CSS-DCHW CI Enterprise Communications Server shall be capable of 100 percent growth in the processing speed specified in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2), without modifications or upgrade to software.	99-0729	08/25/1999  	No Data	
408	SMC-0300	Complete	The ECS shall be designed to accommodate 100 percent growth in System Management processing capacity without requiring modifications or upgrades to existing applications   software.	848	C-CSS-03720	B0	The CSS-DCHW CI Local Communications Server shall be capable of 100 percent growth in the processing speed specified in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2) without modifications or upgrade to software.	99-0729	08/25/1999  	No Data	
408	SMC-0300	Complete	The ECS shall be designed to accommodate 100 percent growth in System Management processing capacity without requiring modifications or upgrades to existing applications   software.	2839	C-MSS-03800	B0	The MSS-MHW CI Enterprise Monitoring Server shall be capable of 100 percent growth in the processing speed specified in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2) without modifications or upgrades to software.	99-0729	08/25/1999  	No Data	
409	SMC-0310	Complete	The ECS shall be designed to accommodate 100 percent growth in System Management storage capacity without requiring modifications or upgrades to existing applications software.	847	C-CSS-03710	B0	The CSS-DCHW CI Enterprise Communications Server shall be capable of 100 percent growth in the storage capacity specified in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2) without modifications or upgrade to software.	99-0729	08/25/1999  	No Data	
409	SMC-0310	Complete	The ECS shall be designed to accommodate 100 percent growth in System Management storage capacity without requiring modifications or upgrades to existing applications software.	849	C-CSS-03730	B0	The CSS-DCHW CI Local Communications Server shall be capable of 100 percent growth in the storage capacity specified in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2) without modifications or upgrade to software.	99-0729	08/25/1999  	No Data	
409	SMC-0310	Complete	The ECS shall be designed to accommodate 100 percent growth in System Management storage capacity without requiring modifications or upgrades to existing applications software.	2840	C-MSS-03810	B0	The MSS-MHW CI Enterprise Monitoring Server shall be capable of 100 percent growth in the storage capacity specified in Reference Table:  CSMS Capacity and Performance Characteristics (Table A-2) without modifications or upgrades to software.	99-0729	08/25/1999  	No Data	
411	SMC-0340	Complete	The ECS shall provide notification of system faults within 5 minutes of their detection.	3167	C-MSS-60230	B0	The MSS Fault Management Application Service shall have the capability of generating a notification within a maximum of five minutes of fault detection.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	100	C-MSS-75045	5B	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	2300	S-DSS-30255	B1	The DDIST CI shall interface with the MSS order tracking capability to update order and request information.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	2676	S-IOS-00510	A	The ADSRV CI shall report Accountability Management Data (such as searches, advertisement submissions, etc.) to the MSS.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	2953	C-MSS-36490	B0	The Management Agent Service shall have the capability to send resource availability information to the DPS.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3338	C-MSS-76000	B0	The MSS accountability management service shall be capable of retrieving user activity data (user id, type of user activity, data items used (browsed, searched, or ordered), and date/time of activity) from records generated by the SDPS Data Server, Data Processing, and Client subsystems.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3340	C-MSS-76010	B0	The MSS accountability management service shall be capable of querying user activity data stored in the Management Database.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3341	C-MSS-76020	A	The MSS accountability management service shall be capable of retrieving all activities associated with a particular user or data item from the Management Database.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3344	C-MSS-77040	B0	The MSS accountability management service shall be capable of accepting queries for the status of a particular ordered data item from M&O operators.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3345	C-MSS-77050	B0	The MSS accountability management service shall be capable of interfacing with the SDPS subsystems to determine the status of an ordered data item to be:  a.  Pending  b.  Operator intervention  c.  Staging  d.  Transferring  e.  Not Found  f.  Waiting for Shipment  g.  Shipped	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3579	S-PLS-01410	A	The PLANG CI shall report PLANG error/fault events to MSS.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3580	S-PLS-01430	A	The PLANG CI shall report PLANG performance events to the MSS.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3582	S-PLS-01470	A	The PLANG CI shall report PLANG Accountability events to the MSS.	99-0729	08/25/1999  	No Data	
413	SMC-1330	Complete	The ECS shall support and maintain the following information for end-to-end data ingest, processing, reprocessing, archive, and data distribution for each product:  a. Product information  b. Product generation information  c. Product delivery information	3583	S-PLS-01500	A	The PLANG CI shall report scheduling events to the MSS.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	1147	C-CSS-62070	A	The CSS Bulletin Board Service shall support download of ECS toolkits.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3034	C-MSS-42000	B0	The MSS Software Distribution Service shall  use version-controlled repositories for software packages.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3035	C-MSS-42010	B0	The MSS Software Distribution Service shall have the capability to retrieve the contents for each repository from the MSS Baseline Manager Service.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3037	C-MSS-42030	B0	The MSS Software Distribution Service shall package software, databases, and documentation for delivery to destinations at both ECS and ECS-connected sites.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3038	C-MSS-42035	B0	The MSS Software Distribution Service shall receive version-controlled software packages from the Baseline Manager Service for distribution.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3039	C-MSS-42050	B0	The MSS Software Distribution Service shall make toolkit sofware and documentation available for automated downloading.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3040	C-MSS-42070	B0	The MSS Software Distribution Service shall determine destinations from stored lists as well as via interactive input.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3041	C-MSS-42080	B0	The MSS Software Distribution Service shall have the capability to push software packages from a central distribution point/depot to remote target platforms (servers and workstations).	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3042	C-MSS-42090	B0	The MSS Software Distribution Service at the site shall have the capability to pull  distribution packages from central distribution points/depots onto individual target destinations.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3043	C-MSS-42100	B0	The MSS Software Distribution Service shall initiate electronic transfer of distribution packages either automatically according to schedule or upon direct command.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3044	C-MSS-42110	B0	The MSS  Software Distribution Service  shall maintain a record of successful package transfers as well as of each target that fails to receive a package intended for it.	99-0729	08/25/1999  	No Data	
414	SMC-2120	Complete	The ECS SMC shall make available for automated distribution to users all non-licensed toolkit software, toolkit software upgrades, and toolkit documentation.	3048	C-MSS-42250	B0	The MSS License Management Service shall meter use of software licenses	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3045	C-MSS-42200	XT	The MSS License Management Service shall maintain information on product identification,  licensing provisions, numbers and types of users	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3046	C-MSS-42230	B0	The MSS License Management Service shall distribute software license provisions system-wide.	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3047	C-MSS-42240	B0	The MSS License Management Service shall create, install, modify, and reinstall software licenses on ECS servers.	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3048	C-MSS-42250	B0	The MSS License Management Service shall meter use of software licenses	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3049	C-MSS-42270	B0	The MSS License Management Service shall have the capability to notify the M&O staff when  license metering events occur.	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3050	C-MSS-42280	B0	The MSS License Management Service shall log  license management events	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3051	C-MSS-42290	B0	The MSS License Management Service shall compile license utilization statistics.	99-0729	08/25/1999  	No Data	
415	SMC-2130	Complete	The ECS SMC shall administer the allocation of the number of licenses to each site for deployed commercial-software funded by the ECS contract, including commercial software as authorized for specific users.	3052	C-MSS-42300	B0	The MSS License Management Service shall report license utilization statistics.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3077	C-MSS-50010	XT	The MSS  Maintenance Management Service  shall provide the capability to view specified site's corrective maintenance information.	02-1081	12/13/2002  		
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3079	C-MSS-50030	XT	The MSS Maintenance Management Service at the SMC shall have the capability to receive specified site maintenance data for use in maintenance trends analysis.	02-1081	12/13/2002  		
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3080	C-MSS-50040	B0	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print Preventive Maintenance (PM) information for site equipment.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3081	C-MSS-50050	B0	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print key information concerning PM  performed.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3082	C-MSS-50060	XT	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print corrective maintenance performed (CMP) information.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3083	C-MSS-50070	XT	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.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3084	C-MSS-50090	XT	The MSS Maintenance Management Service shall have the capability to update repaired/replaced equipment component information in the database.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3085	C-MSS-50100	XT	The MSS Maintenance Management Service shall log at least the following information for transactions performed : operation type, userid of initiator, and date time stamp.	99-0729	08/25/1999  	No Data	
416	SMC-2205	Complete	The ECS shall support on-site preventive and corrective hardware and systems software maintenance.	3086	C-MSS-50110	XT	The MSS Maintenance Management Service shall generate chronological reports of logged transactions associated with user selectable: time frames; operation types; and userids.	99-0729	08/25/1999  	No Data	
417	SMC-2210	Complete	The ECS SMC shall coordinate with each site in the management of off-site corrective hardware and systems software maintenance.	3087	C-MSS-50120	B0	The MSS Maintenance Management Service  shall provide the capability to maintain  sites' off-site maintenance information.	99-0729	08/25/1999  	No Data	
417	SMC-2210	Complete	The ECS SMC shall coordinate with each site in the management of off-site corrective hardware and systems software maintenance.	3088	C-MSS-50140	B0	The MSS Maintenance Management Service  shall record off-site maintenance information: identification of component; description of problem; and corrective action taken.	99-0729	08/25/1999  	No Data	
417	SMC-2210	Complete	The ECS SMC shall coordinate with each site in the management of off-site corrective hardware and systems software maintenance.	3089	C-MSS-50160	B0	The MSS Maintenance Management Service shall provide the capabilities to input, store, and update off-site corrective hardware and software information.	99-0729	08/25/1999  	No Data	
417	SMC-2210	Complete	The ECS SMC shall coordinate with each site in the management of off-site corrective hardware and systems software maintenance.	3090	C-MSS-50190	B0	The MSS Maintenance Management Service shall provide the capability to view off-site corrective hardware and software information.	99-0729	08/25/1999  	No Data	
417	SMC-2210	Complete	The ECS SMC shall coordinate with each site in the management of off-site corrective hardware and systems software maintenance.	3091	C-MSS-50200	B0	The MSS Maintenance Management Service shall provide the capability to generate off-site maintenance reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
418	SMC-2220	Complete	The ECS shall support the monitoring of hardware and systems software maintenance status for off-site repair actions.	3092	C-MSS-50210	B0	The MSS Maintenance Management Service  shall provide the capability to access a specified site's off-site maintenance repair information.	99-0729	08/25/1999  	No Data	
418	SMC-2220	Complete	The ECS shall support the monitoring of hardware and systems software maintenance status for off-site repair actions.	3093	C-MSS-50230	XT	The MSS Maintenance Management Service  shall provide the capability to produce maintenance status reports.	99-0729	08/25/1999  	No Data	
419	SMC-2300	Complete	The ECS shall support the monitoring of the spares inventory.	3062	C-MSS-45200	XT	The MSS Logistics Management Service  shall provide the capability to input, store, update and view/print specified site's spare inventory information.	99-0729	08/25/1999  	No Data	
419	SMC-2300	Complete	The ECS shall support the monitoring of the spares inventory.	3063	C-MSS-45210	XT	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.	99-0729	08/25/1999  	No Data	
419	SMC-2300	Complete	The ECS shall support the monitoring of the spares inventory.	3064	C-MSS-45220	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, update, and view/print information concerning site spare parts order information.	99-0729	08/25/1999  	No Data	
419	SMC-2300	Complete	The ECS shall support the monitoring of the spares inventory.	3065	C-MSS-45230	B0	The MSS Inventory/Logistics Management Service shall provide the capability to keep track of spares on-hand quantities, and quantity used.	99-0729	08/25/1999  	No Data	
419	SMC-2300	Complete	The ECS shall support the monitoring of the spares inventory.	3066	C-MSS-45240	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate site spare related reports.	99-0729	08/25/1999  	No Data	
419	SMC-2300	Complete	The ECS shall support the monitoring of the spares inventory.	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3064	C-MSS-45220	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, update, and view/print information concerning site spare parts order information.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3067	C-MSS-45245	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate order information for resupply of spare parts.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3068	C-MSS-45260	B0	The MSS Inventory/Logistics Management Service shall have the capability to identify those items whose on-hand quantity has reached the established reorder point.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3069	C-MSS-45270	XT	The MSS Inventory/Logistics Management Service shall provide the capability to generate site spare parts related reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3070	C-MSS-45280	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3071	C-MSS-45290	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, update, and view/print site consumable item information.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3072	C-MSS-45300	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate site consumable items related reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3073	C-MSS-45310	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, maintain, and view/print sites' consumable items orders information.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3074	C-MSS-45320	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items on-order reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
420	SMC-2310	Complete	The ECS shall support the management of the replenishment of spare parts for all elements.	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3053	C-MSS-45010	XT	The MSS Inventory/Logistics Management Service at the SMC shall maintain an on-line, system-wide catalog of non-expendable and consumable ECS resources.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3057	C-MSS-45050	XT	The MSS Inventory/Logistics Management Service shall maintain inventory records of individual non-expendable ECS resources.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3067	C-MSS-45245	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate order information for resupply of spare parts.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3070	C-MSS-45280	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3071	C-MSS-45290	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, update, and view/print site consumable item information.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3072	C-MSS-45300	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate site consumable items related reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3074	C-MSS-45320	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items on-order reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
421	SMC-2320	Complete	The ECS shall support the monitoring of the consumable inventory for the following items used by the system:    a. Computer  archive  tapes	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
422	SMC-2330	Complete	The ECS shall support the monitoring of the replenishment of consumable items.	3068	C-MSS-45260	B0	The MSS Inventory/Logistics Management Service shall have the capability to identify those items whose on-hand quantity has reached the established reorder point.	99-0729	08/25/1999  	No Data	
422	SMC-2330	Complete	The ECS shall support the monitoring of the replenishment of consumable items.	3073	C-MSS-45310	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, maintain, and view/print sites' consumable items orders information.	99-0729	08/25/1999  	No Data	
422	SMC-2330	Complete	The ECS shall support the monitoring of the replenishment of consumable items.	3074	C-MSS-45320	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items on-order reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
422	SMC-2330	Complete	The ECS shall support the monitoring of the replenishment of consumable items.	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
423	SMC-2400	Complete	The ECS shall support the management of training and certification programs for ECS.	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
423	SMC-2400	Complete	The ECS shall support the management of training and certification programs for ECS.	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
424	SMC-2410	Complete	The ECS SMC shall provide support for the development of schedules for training courses.	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
424	SMC-2410	Complete	The ECS SMC shall provide support for the development of schedules for training courses.	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
425	SMC-2420	Complete	The ECS SMC shall support the development of on-the-job training.	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
426	SMC-2430	Complete	The ECS SMC shall support the development and use of training materials.	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
427	SMC-2450	Complete	The ECS SMC shall support the evaluation of the effectiveness of the training programs.	1113	C-CSS-61050	IR1	The CSS Electronic Mail Service shall be accessible in interactive mode.	99-0729	08/25/1999  	No Data	
427	SMC-2450	Complete	The ECS SMC shall support the evaluation of the effectiveness of the training programs.	3037	C-MSS-42030	B0	The MSS Software Distribution Service shall package software, databases, and documentation for delivery to destinations at both ECS and ECS-connected sites.	99-0729	08/25/1999  	No Data	
427	SMC-2450	Complete	The ECS SMC shall support the evaluation of the effectiveness of the training programs.	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	5257	C-MSS-45350	XT	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.	02-1081	12/13/2002  		
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	5258	C-MSS-45360	XT	The MSS Inventory/Logistics Management Service shall generate chronological reports of logged transactions associated with user selectable: time frames; operation types; and userids.	02-1081	12/13/2002  		
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3053	C-MSS-45010	XT	The MSS Inventory/Logistics Management Service at the SMC shall maintain an on-line, system-wide catalog of non-expendable and consumable ECS resources.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3054	C-MSS-45020	XT	The MSS Inventory/Logistics Management Service at the SMC shall provide consolidated, system-wide views of ECS sites' inventory data.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3055	C-MSS-45030	B0	The MSS Inventory/Logistics Management at the SMC shall track excess resources designated for reutilization or disposal.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3056	C-MSS-45040	XT	The MSS Inventory/Logistics Management Service at the SMC shall generate site and multi-site inventory reports for printout and display.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3057	C-MSS-45050	XT	The MSS Inventory/Logistics Management Service shall maintain inventory records of individual non-expendable ECS resources.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3058	C-MSS-45060	XT	The MSS Inventory/Logistics Management Service shall have the capability to update and track ECS resources status.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3059	C-MSS-45070	XT	The MSS Inventory/Logistics Management Service shall record attributes of inventoried resources.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3060	C-MSS-45080	XT	The MSS Inventory/Logistics Management Service shall distinguish between ECS resources and non-ECS resources in the inventory.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3061	C-MSS-45090	XT	The MSS Inventory/Logistics Management Service shall generate site inventory reports for printout and display.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3351	C-MSS-87500	B0	The Physical Configuration Management Service shall be capable of importing floor plans from existing files .	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3352	C-MSS-87510	B0	The Physical Configuration Management Service shall provide a graphical interface for adding to and editing the existing floor plan.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3353	C-MSS-87520	B0	The Physical Configuration Management Service shall be capable, through interfacing with the ECS Management  framework, of determining and storing information regarding physical components.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3354	C-MSS-87530	B0	The Physical Configuration Management Service shall be capable of determining and storing the following information regarding physical components:  a. physical device identification  b. physical device information    c. physical device location   d. physical device status	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3355	C-MSS-87540	B0	The Physical Configuration Management Service shall have the capability to augment the information obtained from ECS Management framework on each component with additional information.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3356	C-MSS-87550	B0	The Physical Configuration Management Service shall have the capability to allow the entry and storage of information regarding additional physical components that cannot be discerned through the ECS Management framework.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3359	C-MSS-87580	B0	The Physical Configuration Management Service shall be capable of maintaining the following information for all of the physical system components:   a. Inventory data (name, purchase date, purchase price, installation date, manufacturer, serial number, physical location)   b. Network data (network location, protocols)  c. Maintenance data (maintenance date)	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3360	C-MSS-87590	B0	The Physical Configuration Management Service shall be capable of interfacing with the Management Database in order to store and retrieve data.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3361	C-MSS-87600	B0	The Physical Configuration Management Service shall provide a standard set of reports against the physical system components data.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3362	C-MSS-87610	B0	The Physical Configuration Management Service shall provide the ability to produce custom reports against the physical system components data.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3363	C-MSS-87630	B0	The Physical Configuration Management Service shall provide the ability to interface with the ECS Management framework to capture status information on each component.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3367	C-MSS-90060	B0	The DBMS shall provide an SQL interface with query, update, and administrative functions capabilities.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3384	C-MSS-90520	B0	The Report Generator shall have the capability to generate ad hoc reports from management data maintained in the DBMS.	99-0729	08/25/1999  	No Data	
428	SMC-2500	Complete	The ECS SMC shall establish and maintain a system-wide inventory of all hardware and system software  contained within ECS,  including:  a. Hardware or software identification numbers  b. Version numbers and dates  c. Manufacturer  d. Part number  e. Serial number  f. Name and locator information for software maintenance  g. Location where hardware or software is used	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	5257	C-MSS-45350	XT	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.	02-1081	12/13/2002  		
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	5258	C-MSS-45360	XT	The MSS Inventory/Logistics Management Service shall generate chronological reports of logged transactions associated with user selectable: time frames; operation types; and userids.	02-1081	12/13/2002  		
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3057	C-MSS-45050	XT	The MSS Inventory/Logistics Management Service shall maintain inventory records of individual non-expendable ECS resources.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3058	C-MSS-45060	XT	The MSS Inventory/Logistics Management Service shall have the capability to update and track ECS resources status.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3059	C-MSS-45070	XT	The MSS Inventory/Logistics Management Service shall record attributes of inventoried resources.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3060	C-MSS-45080	XT	The MSS Inventory/Logistics Management Service shall distinguish between ECS resources and non-ECS resources in the inventory.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3061	C-MSS-45090	XT	The MSS Inventory/Logistics Management Service shall generate site inventory reports for printout and display.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3064	C-MSS-45220	B0	The MSS Inventory/Logistics Management Service shall provide the capability to input, store, update, and view/print information concerning site spare parts order information.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3367	C-MSS-90060	B0	The DBMS shall provide an SQL interface with query, update, and administrative functions capabilities.	99-0729	08/25/1999  	No Data	
429	SMC-2505	Future	The ECS shall establish and maintain a local inventory data-base consisting of all hardware and system software contained at the site.	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2978	C-MSS-40010	XT	The MSS configuration management application service shall identify versions and variants of configuration controlled resources that comprise the site's operational baseline.	03-0053	01/29/2003  		
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3000	C-MSS-40280	XT	The MSS configuration management application service shall characterize ECS-controlled resources as system-wide or site-specific.	03-0053	01/29/2003  		
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3002	C-MSS-40300	XT	The MSS configuration management application service shall produce formatted data files containing baseline management data records.	03-0053	01/29/2003  		
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	844	C-CSS-02120	B0	The CSS-DCHW CI Enterprise Communications Server processor shall be upgradeable/replaceable within the same product family without major software modification or replacement of any peripheral or attached component.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2983	C-MSS-40080	B0	The MSS configuration management application service at the SMC and the sites shall maintain records describing dependencies among baseline objects.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2984	C-MSS-40100	B0	The MSS configuration management application service at the SMC and the DAACs shall maintain SCF-provided configuration data for individual algorithms, including:   a. algorithm development version numbers, identification codes, and reference numbers;   b. SCF point of contact's name and organization;   c. associated files' names, formats, sizes, and descriptions;    d. number of files by category and type.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2985	C-MSS-40110	XT	The MSS configuration management application service shall maintain lists of configuration-controlled resources that comprise configuration items and their components.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2986	C-MSS-40120	XT	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. 	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2987	C-MSS-40140	XT	The MSS configuration management application service shall maintain, and make available system-wide, information identifying  sites at which each configuration controlled resource is deployed.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2988	C-MSS-40150	XT	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.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2989	C-MSS-40160	B0	The MSS configuration management application service at the SMC shall maintain records that identify the current and previous versions of ECS  documents associated with deployed ECS resources.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2990	C-MSS-40170	B0	The MSS configuration management application service at the SMC shall maintain, and distribute to each site, records that identify the baseline changes included in each release of ECS hardware and software deployed to the site.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2991	C-MSS-40180	B0	The MSS configuration management application service at the SMC shall maintain, and distribute to each site, records that identify the specifications and technical, operations, and maintenance documents associated with versions of ECS hardware and software configuration items deployed to the site.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2992	C-MSS-40190	XT	MSS configuration management application service shall identify the change request that authorize each baseline change.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2993	C-MSS-40200	XT	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  	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2994	C-MSS-40210	B0	The MSS configuration management application service at the SMC shall maintain historical status records about ECS system releases, to include each release's:  a. latest baseline plus approved changes.    b. baseline history.    c. latest release documentation.    d. "level of assembly" representation of the subsystem and configuration item versions that comprise the release configuration  e. history of changes, including changes to subordinate units/components.   f. effectivity and installation status at operational sites.    g. release configuration	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2995	C-MSS-40220	XT	The MSS configuration management application service  shall maintain historical status records about ECS baseline changes to include:  a. sites affected;  b. hosts affected 	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2996	C-MSS-40240	XT	The MSS configuration management application service shall identify critical software items.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2997	C-MSS-40250	B0	The MSS configuration management application  service at the SMC shall produce, and make available system-wide, reports containing the identity and change status of documents associated with deployed ECS resources.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2998	C-MSS-40260	B0	The MSS configuration management application  service at the SMC shall produce, and make available system-wide, reports, containing the identity and change status of individual ECS resources deployed to the sites.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	2999	C-MSS-40270	XT	The MSS configuration management application service  shall produce configuration reports identify the resources  baselined  for deployment to sites.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3004	C-MSS-40410	IR1	The MSS configuration management application service at each DAAC shall maintain user-definable software configuration status information for each algorithm. (IR-1)	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3007	C-MSS-40470	IR1	The MSS configuration management application service shall regulate operations on software library files through use of individual and group permissions.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3008	C-MSS-40480	IR1	The MSS configuration management application service shall use a checkout/edit/checkin paradigm to govern changing of software library files.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3009	C-MSS-40490	IR1	The MSS configuration management application service shall track each software library file that has been changed as a new version of the original file.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3010	C-MSS-40500	IR1	The MSS configuration management application service shall merge versions of software library files and identify version conflicts, if any.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3011	C-MSS-40510	IR1	The MSS configuration management application service shall maintain records of actual changes made to ECS software library files in implementing system enhancement requests.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3014	C-MSS-40540	IR1	The MSS configuration management application service shall perform builds of baseline systems for ECS platforms and audit the builds such that they can be repeated.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3015	C-MSS-40550	IR1	The MSS configuration management application service shall reconstruct previous versions of software library files.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3016	C-MSS-40560	IR1	The MSS configuration management application service shall allow concurrent user access to software library files.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3017	C-MSS-40570	IR1	The MSS configuration management application service shall maintain an audit trail of all changes made to software library files.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3032	C-MSS-40990	IR1	The MSS configuration management application service shall log the following information for configuration management events:  a. operation type;  b. userid of initiator;  c. date-time stamp;  d. host name.  (IR-1, at the sites only)	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3033	C-MSS-40995	IR1	The MSS configuration management application service shall generate chronological reports of logged CM events associated with M&O staff-selectable:    a. time frames;  b. operation types;  c. userids;  d. hosts.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3456	C-MSS-92630	B0	The MSS Report Generation Service shall be capable of generating an SNMP Event Notification report identifying the IP address(es) of the management system(s) to which the selected node is configured to send SNMP events.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3457	C-MSS-92640	B1	The MSS Report Generation Service shall be capable of generating an Indentured Level of Assembly List Report for all managed configuration items (CIs).	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3458	C-MSS-92650	B1	The MSS Report Generation Service shall be capable of generating a Document Configuration Status Report containing the identity and status of documents associated with ECS resources.	99-0729	08/25/1999  	No Data	
430	SMC-2510	Complete	The ECS shall provide  configuration management tools for the operational hardware, scientific and system software contained within ECS.  The configuration management tools shall support the migration of hardware and software upgrades into the operational environment.	3459	C-MSS-92660	B1	The MSS report generation service shall be capable of generating a System Configuration Tracking Report noting the migration of upgrades into the operational environment.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3004	C-MSS-40410	IR1	The MSS configuration management application service at each DAAC shall maintain user-definable software configuration status information for each algorithm. (IR-1)	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3005	C-MSS-40420	IR1	The MSS configuration management application service at each site shall maintain M&O staff-definable software configuration status information for each version of every software library file.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3007	C-MSS-40470	IR1	The MSS configuration management application service shall regulate operations on software library files through use of individual and group permissions.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3008	C-MSS-40480	IR1	The MSS configuration management application service shall use a checkout/edit/checkin paradigm to govern changing of software library files.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3009	C-MSS-40490	IR1	The MSS configuration management application service shall track each software library file that has been changed as a new version of the original file.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3010	C-MSS-40500	IR1	The MSS configuration management application service shall merge versions of software library files and identify version conflicts, if any.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3011	C-MSS-40510	IR1	The MSS configuration management application service shall maintain records of actual changes made to ECS software library files in implementing system enhancement requests.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3012	C-MSS-40520	B0	The MSS configuration management application service shall request, verify, and log a change request number for a software library file before allowing the file to be checked out for modification.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3013	C-MSS-40530	B0	The MSS configuration management application service shall identify implementation status for each version of every software library file, reflecting the lifecycle stage to which it has been promoted.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3014	C-MSS-40540	IR1	The MSS configuration management application service shall perform builds of baseline systems for ECS platforms and audit the builds such that they can be repeated.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3015	C-MSS-40550	IR1	The MSS configuration management application service shall reconstruct previous versions of software library files.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3016	C-MSS-40560	IR1	The MSS configuration management application service shall allow concurrent user access to software library files.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3017	C-MSS-40570	IR1	The MSS configuration management application service shall maintain an audit trail of all changes made to software library files.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3031	C-MSS-40770	B0	The MSS configuration management application service at the SMC shall collect, and make available system-wide, the allocations, schedules and status of tasks for implementing CCB-approved changes to ECS hardware and software and for correcting non-conformance with system requirements.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3034	C-MSS-42000	B0	The MSS Software Distribution Service shall  use version-controlled repositories for software packages.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3037	C-MSS-42030	B0	The MSS Software Distribution Service shall package software, databases, and documentation for delivery to destinations at both ECS and ECS-connected sites.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3038	C-MSS-42035	B0	The MSS Software Distribution Service shall receive version-controlled software packages from the Baseline Manager Service for distribution.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3040	C-MSS-42070	B0	The MSS Software Distribution Service shall determine destinations from stored lists as well as via interactive input.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3041	C-MSS-42080	B0	The MSS Software Distribution Service shall have the capability to push software packages from a central distribution point/depot to remote target platforms (servers and workstations).	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3042	C-MSS-42090	B0	The MSS Software Distribution Service at the site shall have the capability to pull  distribution packages from central distribution points/depots onto individual target destinations.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3043	C-MSS-42100	B0	The MSS Software Distribution Service shall initiate electronic transfer of distribution packages either automatically according to schedule or upon direct command.	99-0729	08/25/1999  	No Data	
431	SMC-2535	Complete	The ECS shall provide tools to facilitate the implementation of changes within its hardware and software.	3044	C-MSS-42110	B0	The MSS  Software Distribution Service  shall maintain a record of successful package transfers as well as of each target that fails to receive a package intended for it.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3094	C-MSS-52010	B1	The MSS Policy and Procedures Management Service at the SMC shall provide the capability to prepare, store, maintain, and make available for distribution ECS policies and procedures.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3095	C-MSS-52020	B1	The MSS Policy and Procedures Management Service shall provide the capability to access, select, and display/print ECS policies and procedures.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3096	C-MSS-52030	B1	The MSS Policy and Procedures Management Service shall provide the capability to input, store, maintain, and view/print site specific policies and procedures.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3389	C-MSS-91012	B0	The MSS Office Automation word processing capability shall be capable of importing from ASCII text and RTF formats.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3390	C-MSS-91015	B0	The MSS Office Automation word processing capability shall be capable of exporting to Postscript,  ASCII text, and RTF formats.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3392	C-MSS-91025	B0	The MSS Office Automation spreadsheet capability shall be capable of importing from and exporting to ASCII text and Excel formats.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3393	C-MSS-91030	B0	The MSS Office Automation shall provide a graphics capability that enables:  a. the development, modification, recording, and printing of graphic images  b. the transfer of graphics images to word processing documents, messages, and reports.	99-0729	08/25/1999  	No Data	
432	SMC-2600	Complete	The ECS shall support, control, and maintain ECS policies and procedures covering the following areas:    a. Site responsibility and authority    b. Resource management    c. Fault identification, priorities, recovery    d. Testing    e.  Maintenance    f. Logistics    g. Performance evaluation    h. Training    i. Quality and product assurance    j. Inventory management    k. System enhancements    l. Administrative actions    m. Security	3394	C-MSS-91035	A	The MSS Office Automation graphics capability shall be capable of importing from and exporting to Postscript and GIF formats.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	858	C-CSS-10530	B0	The CSS DCCI shall accept bulletin board service request from the User.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	862	C-CSS-10570	B0	The CSS  DCCI shall provide bulletin board to the User.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1143	C-CSS-62010	IR1	The CSS Bulletin Board Service shall support multiple (configurable) bulletin boards (newsgroups).	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1148	C-CSS-62080	A	The CSS Bulletin Board Service shall collect and maintain access history and statistical information for the service.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1150	C-CSS-62120	IR1	The CSS Bulletin Board Service shall provide the capability to respond to a posted message on a bulletin board by sending the response message to:  a. the bulletin board (follow up)  b. author of the original message (respond to author)  c. named destinations (forward).	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1151	C-CSS-62130	A	The CSS Bulletin Board Service shall provide a "What's new" feature which informs the user of the new information available on the bulletin boards.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1157	C-CSS-62330	IR1	The CSS Bulletin Board Service shall provide the capability to respond to a message by sending the response to the bulletin board and/or to the author of the original message and/or any other operator specified destination (forward).	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1158	C-CSS-62340	IR1	The CSS Bulletin Board Service shall provide capability:  a. to search for a string in message headers or in message text.  b. to search by author  c. to search by subject.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1159	C-CSS-62350	IR1	The CSS Bulletin Board Service shall provide a catch-up feature which excludes user specified messages from appearing in the bulletin board when it is viewed next time.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1160	C-CSS-62360	IR1	The CSS Bulletin Board Service shall allow the users to post messages to bulletin board(s).	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1161	C-CSS-62380	IR1	The CSS Bulletin Board Service shall allow users to copy/save a message to their local system.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1162	C-CSS-62390	A	The CSS Bulletin Board Service shall allow attaching ASCII or binary files to a message.	99-0729	08/25/1999  	No Data	
433	SMC-2610	Complete	The ECS shall provide and maintain a Web based service with information on ECS status, events, and news.	1163	C-CSS-62800	A	The CSS Bulletin Board Service shall provide an API for an application to post a message to bulletin boards.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	1318	S-DMS-01075	Complete	The LIMGR CI shall receive Shutdown Requests from the MSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2850	C-MSS-12005	IR1	The MSS Management User Interface (MUI) Service shall be compatible with the ECS management framework.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2860	C-MSS-12100	IR1	The MSS MUI Service shall provide a capability for the M&O Staff to load and unload vendor or ECS defined MIB.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2866	C-MSS-12180	IR1	The MSS MUI Service shall provide the capability for an application to display on-line help windows	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2867	C-MSS-14010	IR1	The MSS Maps/Collection Service shall retain the status of managed objects and their relationship to symbols that comprise a graphical representation of the physical network topology.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2875	C-MSS-16040	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to receive ECS management traps/events.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2905	C-MSS-20030	IR1	The MSS Discovery Service shall report missing occurrences of managed objects.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2912	C-MSS-36040	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to send ECS management traps/events to the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2926	C-MSS-36305	B0	The Management Agent Service shall have the capability to receive current mode from the IOS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2930	C-MSS-36330	B0	The Management Agent Service shall have the capability to send life cycle commands to the IOS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2931	C-MSS-36335	B0	The Management Agent Service shall have the capability to send mode requests to the IOS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2933	C-MSS-36355	B0	The Management Agent Service shall have the capability to receive current mode from the DMS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2937	C-MSS-36375	B1	The Management Agent Service shall have the capability to send life cycle commands to the DMS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2938	C-MSS-36380	B1	The Management Agent Service shall have the capability to send mode requests to the DMS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2940	C-MSS-36405	B0	The Management Agent Service shall have the capability to receive current mode from the PLS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2944	C-MSS-36435	B0	The Management Agent Service shall have the capability to send life cycle commands to the PLS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2945	C-MSS-36440	B0	The Management Agent Service shall have the capability to send mode requests to the PLS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2947	C-MSS-36455	B0	The Management Agent Service shall have the capability to receive current mode from the DPS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2951	C-MSS-36480	B0	The Management Agent Service shall have the capability to send life cycle commands to the DPS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2952	C-MSS-36485	B0	The Management Agent Service shall have the capability to send mode requests to the DPS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2955	C-MSS-36505	B0	The Management Agent Service shall have the capability to receive current mode from the INS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2959	C-MSS-36540	B0	The Management Agent Service shall have the capability to send life cycle commands to the INS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2960	C-MSS-36545	B0	The Management Agent Service shall have the capability to send mode requests to the INS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2962	C-MSS-36555	B0	The Management Agent Service shall have the capability to receive current mode from the DSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2967	C-MSS-36600	B0	The Management Agent Service shall have the capability to send life cycle commands to the DSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2968	C-MSS-36605	B0	The Management Agent Service shall have the capability to send mode requests to the DSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2970	C-MSS-36705	B0	The Management Agent Service shall have the capability to receive current mode from the CSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2974	C-MSS-36750	B0	The Management Agent Service shall have the capability to send life cycle commands to the CSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	2975	C-MSS-36755	B0	The Management Agent Service shall have the capability to send mode requests to the CSS.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3097	C-MSS-56010	B0	The MSS Mode Management Service shall support a operational mode capability	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3100	C-MSS-56040	B0	The MSS Mode Management Service shall have the capability to monitor each independently executing mode for performance statistics.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3101	C-MSS-56050	B1	 The MSS Mode Management Service shall provide fault detection and isolation capabilities for each independently executing mode.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3102	C-MSS-56060	B1	The MSS Mode Management Service shall maintain a collection of management statistics for each mode supported.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3109	C-MSS-56090	B0	The MSS Mode Management Service shall have the capability to identify components which have been taken off-line for maintenance	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3143	C-MSS-60012	B0	The MSS Fault Management Service shall provide fault detection and isolation capabilities for each mode.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3144	C-MSS-60014	B0	The MSS Fault Management Service shall provide the capability to distinguish faults between different modes.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3145	C-MSS-60016	B0	The MSS Fault Management Service shall maintain fault statistics for each mode.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3203	C-MSS-66000	IR1	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components  a. network components   1.  routers   2.  links   3.  bridges   4.  gateways  	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3204	C-MSS-66001	B0	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components      a. network components         1.  routers         2.  links         3.  bridges         4.  gateways      b. hosts      c. operating systems      d. peripherals      e. databases     f. ECS applications.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3205	C-MSS-66002	B0	The MSS Performance Management Applications Service shall have the capability to monitor each mode for performance statistics.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3206	C-MSS-66004	B0	The MSS Performance Management Application Service shall provide the capability to distinguish performance metrics between different modes.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3207	C-MSS-66006	B0	The MSS Performance Management Application Service shall maintain performance statistics for a given mode.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3209	C-MSS-66020	IR1	The MSS Performance Management Application Service shall be capable of monitoring ethernet-like device performance parameters as specified in IETF RFC 1623.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3214	C-MSS-66070	B0	The MSS Performance Management Application Service shall be capable of receiving unrequested performance data from ECS managed objects.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3218	C-MSS-66120	IR1	The MSS performance management application service shall be capable of determining the operational state of all network components, hosts, and peripherals to be:  a. on-line  b. off-line  c. in test mode	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3219	C-MSS-66121	B0	The MSS performance management application service shall be capable of determining the operational state of all network components, hosts, and peripherals to be:      a. on-line      b. off-line      c. in test mode      d. In maintenance,      e. in simulation mode.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3220	C-MSS-66130	IR1	The MSS performance management application service shall be capable of receiving operational state change notifications from network components, hosts, applications, and peripherals.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3232	C-MSS-66183	B1	The MSS Performance Management Application Service shall have the capability to monitor the performance of ECS relational and object oriented database servers.	99-0729	08/25/1999  	No Data	
434	SMC-3300	Complete	The ECS shall monitor site hardware status to determine operational states including:  a. On-line  b. Off-line (e.g., failed, off for maintenance)	3258	C-MSS-68000	IR1	The MSS performance management application service shall be capable of graphically displaying the operational state of managed objects through the MUI service.	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	2874	C-MSS-16030	IR1	The MSS Monitor/Control Service shall be able to communicate via ECS management protocol with the MSS Management Agent Service to send ECS management set messages to configure and control the processing performed by the ECS management agent.	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	2877	C-MSS-16060	IR1	The MSS Monitor/Control Service shall allow the capability to set thresholds on managed resources that are monitored	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	2915	C-MSS-36050	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to receive ECS management set message from the Monitor/Control Service.	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	3233	C-MSS-66190	IR1	The MSS performance management application service shall provide a configurable number of thresholds for each performance metric.	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	3234	C-MSS-66200	IR1	The MSS EMC performance management application service shall be capable of creating a list of suggested initial threshold values for each performance metric.	99-0729	08/25/1999  	No Data	
437	SMC-3370	Complete	For each performance parameter, the ECS shall have the capability of establishing and evaluating multiple thresholds to include, as applicable:  a. On/off  b. Pass/fail  c. Various levels of degradation	3237	C-MSS-66230	IR1	The MSS performance management application service shall allow each performance metric threshold to be configurable.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3203	C-MSS-66000	IR1	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components  a. network components   1.  routers   2.  links   3.  bridges   4.  gateways  	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3204	C-MSS-66001	B0	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components      a. network components         1.  routers         2.  links         3.  bridges         4.  gateways      b. hosts      c. operating systems      d. peripherals      e. databases     f. ECS applications.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3211	C-MSS-66040	IR1	The MSS performance management application service shall be capable of specifying which available performance metrics are to be gathered from each individual managed object.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3212	C-MSS-66050	IR1	The MSS performance management application service shall be capable of requesting performance data from each individual managed object:  a. at configurable intervals  b. on demand.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3230	C-MSS-66181	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of system errors and events for system analysis and trending.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3232	C-MSS-66183	B1	The MSS Performance Management Application Service shall have the capability to monitor the performance of ECS relational and object oriented database servers.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3242	C-MSS-66280	B0	The MSS site performance management application service shall be capable of extracting summarized site status information from logged performance data.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3243	C-MSS-66290	B0	The MSS site performance management application service shall be capable of sending summarized status information for that site to the MSS SMC performance management application service.	99-0729	08/25/1999  	No Data	
438	SMC-3380	Complete	The ECS  shall provide tools to monitor overall system performance.	3273	C-MSS-69100	B1	The MSS Performance Trending Service shall have the capability to save and retrieve data from the management database for long and short term trending.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3094	C-MSS-52010	B1	The MSS Policy and Procedures Management Service at the SMC shall provide the capability to prepare, store, maintain, and make available for distribution ECS policies and procedures.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3095	C-MSS-52020	B1	The MSS Policy and Procedures Management Service shall provide the capability to access, select, and display/print ECS policies and procedures.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3096	C-MSS-52030	B1	The MSS Policy and Procedures Management Service shall provide the capability to input, store, maintain, and view/print site specific policies and procedures.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3203	C-MSS-66000	IR1	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components  a. network components   1.  routers   2.  links   3.  bridges   4.  gateways  	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3204	C-MSS-66001	B0	The MSS performance management application service shall be capable of monitoring the performance of the following ECS components      a. network components         1.  routers         2.  links         3.  bridges         4.  gateways      b. hosts      c. operating systems      d. peripherals      e. databases     f. ECS applications.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3212	C-MSS-66050	IR1	The MSS performance management application service shall be capable of requesting performance data from each individual managed object:  a. at configurable intervals  b. on demand.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3213	C-MSS-66060	IR1	The MSS performance management application service shall be capable of receiving requested performance data from ECS components.	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3217	C-MSS-66100	IR1	The MSS performance management application service shall be capable of retrieving the following data for all hosts:  a. total CPU utilization  b. memory utilization  c. physical disk i/o's  d. disk storage size  e. disk storage used  f. number of active processes  g. length of run queue  h. network i/o's (packets)  i. network errors	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3245	C-MSS-66305	B0	The MSS Performance Management Application Service shall be capable of collecting the following performance data for all ECS-managed processes:  a.  start time   b.  stop time   c.  CPU utilization   d.  memory utilization   e.  disk i/o	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3246	C-MSS-66310	IR1	The MSS performance management application service shall be capable of retrieving the following science algorithm performance data via the Management Data Access Service:  a. algorithm name  b. algorithm version  c. start time  d. stop time  e. CPU utilization  f. memory utilization  g. disk reads  h. disk writes	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3247	C-MSS-66320	B0	MSS shall be capable of receiving the following performance data from the Data Server:   a.  total order volume   b.  elapsed time of Data Server events	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3248	C-MSS-66330	B0	MSS shall be capable of receiving the following performance data from Planning:   a.  Notification received  b.  Notification received but not processed  c.  DPRs released	99-0729	08/25/1999  	No Data	
439	SMC-3385	Complete	The ECS shall evaluate system  performance against the ESDIS project established performance criteria.	3249	C-MSS-66340	B0	MSS shall be capable of receiving the following performance data from Ingest:   a.  ingest volumes   b.  processing times   c.  no. of completed requests   d.  no. of unsuccessful requests	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	2858	C-MSS-12080	IR1	The MSS MUI Service shall  provide a capability for applications to alert the M&O Staff	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	2876	C-MSS-16050	IR1	The MSS Monitor/Control Service shall allow customized M&O staff-event notifications and automatic actions.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	2878	C-MSS-16070	IR1	The MSS Monitor/Control Service shall automatically report when a threshold has been exceeded by generating a ECS management event	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	2911	C-MSS-36020	IR1	The MSS Management Agent Service shall communicate via ECS management protocol with the MSS Monitor/Control Service to respond to requests for managed object MIB attributes	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3152	C-MSS-60080	IR1	The MSS Fault Management Application Service shall have the capability to establish, view, modify and delete thresholds on performance metrics it measures.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3153	C-MSS-60100	IR1	The MSS Fault Management Application Service shall have the capability to poll for the detection of fault/performance information.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3154	C-MSS-60110	IR1	The MSS Fault Management Application Service shall be capable of receiving fault notifications.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3155	C-MSS-60120	IR1	The MSS Fault Management Application Service shall have the capability to define the frequency with which polling is done for the detection of fault/performance information.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3157	C-MSS-60140	IR1	The MSS Site Fault Management Application Service shall have the capability to generate a fault notification when a predefined threshold on a performance metric is exceeded.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3160	C-MSS-60162	B0	The MSS SMC Trouble Ticket Application Service shall have the capability to exchange notifications of detected faults and degradation of performance with:  a. EBnet  b. NSI  c. ASTER	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3161	C-MSS-60170	IR1	The MSS EMC Fault Management Application Service shall be capable of requesting fault notification and performance degradation data from :   a. Site Fault Management Applications   b. Other external systems as defined in Section 5.1.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3193	C-MSS-60400	A	The MSS Fault Management Application Service shall support, maintain, and update system fault management policies and procedures, to include:   a. Fault Identification   b. Fault priorities   c. Recovery or corrective actions	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3196	C-MSS-60500	IR1	The MSS EMC Fault Management Application Service shall coordinate the recovery from conditions of performance degradation and faults with the sites and external network service providers.	99-0729	08/25/1999  	No Data	
440	SMC-3390	Complete	The ECS shall generate alert indicators of fault or degraded conditions.	3232	C-MSS-66183	B1	The MSS Performance Management Application Service shall have the capability to monitor the performance of ECS relational and object oriented database servers.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	2873	C-MSS-16020	IR1	The MSS Monitor/Control Service shall communicate via ECS management protocol  with the MSS Management Agent Service to request management data on a managed object.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	2892	C-MSS-18260	B0	The MSS Management Data Access Service shall have the capability to schedule the transfer and loading log files into the management database at the site.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	2894	C-MSS-18280	B0	MSS shall have the capability to schedule the transfer of management data at the sites to the SMC.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3230	C-MSS-66181	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of system errors and events for system analysis and trending.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3231	C-MSS-66182	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of operational status, performance of resources and maintenance activities for system analysis and trending.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3244	C-MSS-66300	B0	The MSS SMC performance management application service shall log received summarized site status.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3256	C-MSS-67000	B0	The MSS performance management application service shall be capable of extracting values of performance metrics gathered for a specified managed objects over a configurable period of time from the Management Database.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3257	C-MSS-67010	B0	The MSS performance management application service shall be capable of generating a graph of the extracted performance metric values.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3273	C-MSS-69100	B1	The MSS Performance Trending Service shall have the capability to save and retrieve data from the management database for long and short term trending.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3274	C-MSS-69105	B1	The MSS Performance Trending Service shall have the capability to generate the following types of trend analysis:  a. time series analysis  b. analysis of variance including multiple analysis of variance  c. correlation analysis  d. regression analysis including non-linear and multiple regression	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3275	C-MSS-69110	B1	The MSS Performance Trending Service shall provide the capability to select parameters for trend analysis.	99-0729	08/25/1999  	No Data	
441	SMC-3410	Complete	The ECS shall provide tools to perform short and long-term trend analysis of system and site performance to include:  a. Operational status  b. Performance of a particular resource  c. Maintenance activities (e.g., number of repairs per item)	3276	C-MSS-69120	B1	The MSS Performance Trending Service shall have the capability to output trend data in textual and graphical formats.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3230	C-MSS-66181	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of system errors and events for system analysis and trending.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3231	C-MSS-66182	B0	The MSS Performance Management Application Service shall have the capability to capture and save histories of operational status, performance of resources and maintenance activities for system analysis and trending.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3256	C-MSS-67000	B0	The MSS performance management application service shall be capable of extracting values of performance metrics gathered for a specified managed objects over a configurable period of time from the Management Database.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3257	C-MSS-67010	B0	The MSS performance management application service shall be capable of generating a graph of the extracted performance metric values.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3273	C-MSS-69100	B1	The MSS Performance Trending Service shall have the capability to save and retrieve data from the management database for long and short term trending.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3274	C-MSS-69105	B1	The MSS Performance Trending Service shall have the capability to generate the following types of trend analysis:  a. time series analysis  b. analysis of variance including multiple analysis of variance  c. correlation analysis  d. regression analysis including non-linear and multiple regression	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3275	C-MSS-69110	B1	The MSS Performance Trending Service shall provide the capability to select parameters for trend analysis.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3276	C-MSS-69120	B1	The MSS Performance Trending Service shall have the capability to output trend data in textual and graphical formats.	99-0729	08/25/1999  	No Data	
442	SMC-3420	Complete	The ECS shall provide tools to perform short and long term trend analysis of system andsite performance to determine the impact on resources of:  a. Modifying system, site, or element activity allocations  b. Potential enhancements to system, site, or element	3277	C-MSS-69150	B1	The MSS Performance Trending Service shall have the capability to perform short and long term trending by system, site and element.	99-0729	08/25/1999  	No Data	
443	SMC-4310	Complete	The ECS shall support fault analysis including:  a. Isolation  b. Location  c. Identification  d. Characterization	3160	C-MSS-60162	B0	The MSS SMC Trouble Ticket Application Service shall have the capability to exchange notifications of detected faults and degradation of performance with:  a. EBnet  b. NSI  c. ASTER	99-0729	08/25/1999  	No Data	
443	SMC-4310	Complete	The ECS shall support fault analysis including:  a. Isolation  b. Location  c. Identification  d. Characterization	3161	C-MSS-60170	IR1	The MSS EMC Fault Management Application Service shall be capable of requesting fault notification and performance degradation data from :   a. Site Fault Management Applications   b. Other external systems as defined in Section 5.1.	99-0729	08/25/1999  	No Data	
443	SMC-4310	Complete	The ECS shall support fault analysis including:  a. Isolation  b. Location  c. Identification  d. Characterization	3188	C-MSS-60370	IR1	The MSS Fault Management Application Service at the SMC shall be capable of sending gathered isolation, location, identification and characterization of reported faults data to the level of subsystem and equipment to the following:   a. the site Fault Management Applications   b. other external systems as defined in Section 5.1 of the current version of 304-CD-003.	99-0729	08/25/1999  	No Data	
443	SMC-4310	Complete	The ECS shall support fault analysis including:  a. Isolation  b. Location  c. Identification  d. Characterization	3189	C-MSS-60372	B0	The MSS Fault Management Application Service at the SMC shall be capable of sending gathered isolation, location, identification and characterization of reported faults data to the level of subsystem and equipment to the Site Fault Management Applications.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2924	C-MSS-36215	B0	The Management Agent Service shall have the capability to receive event notification from the CLS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2928	C-MSS-36320	B0	The Management Agent Service shall have the capability to receive event notification from the IOS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2935	C-MSS-36365	B0	The Management Agent Service shall have the capability to receive event notification from the DMS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2942	C-MSS-36415	B0	The Management Agent Service shall have the capability to receive event notification from the PLS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2957	C-MSS-36515	B0	The Management Agent Service shall have the capability to receive event notification from the INS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2964	C-MSS-36565	B0	The Management Agent Service shall have the capability to receive event notification from the DSS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	2972	C-MSS-36715	B0	The Management Agent Service shall have the capability to receive event notification from the CSS.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	3188	C-MSS-60370	IR1	The MSS Fault Management Application Service at the SMC shall be capable of sending gathered isolation, location, identification and characterization of reported faults data to the level of subsystem and equipment to the following:   a. the site Fault Management Applications   b. other external systems as defined in Section 5.1 of the current version of 304-CD-003.	99-0729	08/25/1999  	No Data	
444	SMC-4311	Complete	The ECS shall support fault analysis to the level of:  a. Software processes  b. Equipment	3189	C-MSS-60372	B0	The MSS Fault Management Application Service at the SMC shall be capable of sending gathered isolation, location, identification and characterization of reported faults data to the level of subsystem and equipment to the Site Fault Management Applications.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3152	C-MSS-60080	IR1	The MSS Fault Management Application Service shall have the capability to establish, view, modify and delete thresholds on performance metrics it measures.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3157	C-MSS-60140	IR1	The MSS Site Fault Management Application Service shall have the capability to generate a fault notification when a predefined threshold on a performance metric is exceeded.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3180	C-MSS-60303	B0	The Fault Management Application Service shall have the capability to send diagnostic test requests to the ISS.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3181	C-MSS-60305	B0	The Fault Management Application Service shall have the capability to receive diagnostic test results from the ISS.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3184	C-MSS-60330	B0	The MSS Fault Management Application Service at each site shall have the capability to perform periodic testing of all ECS communication links at that site to verify that they are operational.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3185	C-MSS-60340	IR1	The MSS Fault Management Application Service shall be capable of verifying the operational status of a host.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3186	C-MSS-60350	A	The MSS Fault Management Application Service shall have the capability to periodically execute diagnostic tests in order to isolate, characterize and identify a fault.	99-0729	08/25/1999  	No Data	
445	SMC-4320	Complete	The ECS shall support the following fault diagnosis testing:  a. Software and hardware testing  b. Resource-to-resource connectivity testing	3187	C-MSS-60360	B0	The MSS Fault Management Application Service shall provide the capability to execute vendor diagnostics in order to diagnose faults traced to hardware equipment.	99-0729	08/25/1999  	No Data	
446	SMC-4330	Complete	The ECS shall have the capability to send fault recovery commands, directives, and instructions to ECS components.	3164	C-MSS-60200	IR1	The MSS Fault Management Application Service shall have the capability to generate the following types of notifications for detected faults :   a. a change in the color of an icon on a display   b. a message in a pop-up notification window   c. logging the following fault information to a disk log file:    1.  fault type    2.  date and time of occurrence of the fault    3.  identification of the source of the notification (e.g. IP address, process name, etc.)    4.  fault data received with the notification    5.  operator-defined descriptive text   d. audible alert	99-0729	08/25/1999  	No Data	
446	SMC-4330	Complete	The ECS shall have the capability to send fault recovery commands, directives, and instructions to ECS components.	3195	C-MSS-60420	A	The MSS Fault Management Application Service shall interface with the MSS Configuration Management Application Service and schedule a change in the configuration of the site when such a change in the configuration of the site is deemed necessary to recover from a fault.	99-0729	08/25/1999  	No Data	
446	SMC-4330	Complete	The ECS shall have the capability to send fault recovery commands, directives, and instructions to ECS components.	3197	C-MSS-60510	A	The MSS EMC Fault Management Application Service at the SMC shall coordinate, as necessary via directives and instructions, the recovery from faults reported from a site.	99-0729	08/25/1999  	No Data	
446	SMC-4330	Complete	The ECS shall have the capability to send fault recovery commands, directives, and instructions to ECS components.	3198	C-MSS-60520	B0	The MSS Fault Management Application Service shall provide the capability to allow the specification and execution of action routines in response to the notification of a fault.	99-0729	08/25/1999  	No Data	
446	SMC-4330	Complete	The ECS shall have the capability to send fault recovery commands, directives, and instructions to ECS components.	3199	C-MSS-60530	B0	The MSS Fault Management Application Service shall provide the capability to pass parameters to action routines.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	83	C-MSS-75021	5B	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')	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	84	C-MSS-75022	5B	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.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	85	C-MSS-75023	5B	The MSS accountability management service shall use a value of Non-NASA User ('N') as the default value for the NASA User attribute.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	911	C-CSS-21000	IR1	The CSS Security service shall provide an API to verify the identity of users.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	914	C-CSS-21020	IR1	The CSS Security service shall provide the capability to create/modify/delete user accounts and privileges in the security registry.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	915	C-CSS-21030	IR1	The CSS Security service shall provide the capability to define/modify/delete group information in the security registry.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	3278	C-MSS-70010	IR1	The MSS Security Management Application Service shall provide the capability to create, modify and delete user accounts with the following attributes:  a.  username  b.  password  c.  group identification code  d.  user identification code  e.  login directory  f.  command line interpreter	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	3279	C-MSS-70020	IR1	The MSS Security Management Application Service shall enable the assignment of user accounts to groups based on the group identification code.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	3283	C-MSS-70130	IR1	The MSS site Security Management Application Service shall provide a command line interface and a GUI for the management of the following security databases:  a. Authentication Database    b.  Authorization Database  c. Network Database	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	3313	C-MSS-75001	B0	The MSS accountability management service shall provide the capability to maintain a user profile database that stores the following information for each registered user:     a.  Name     b.  User ID     c.  Password information      1.  password      2.  password expiration date      d.  Assigned privileges     e.  Mailing address     f.  Telephone number     g.  Product shipping address     h.  E-mail address     i.  Organization (optional)   j.  Project affiliation(s) (optional)      1.  project name      2.  project principal investigator     k.  User group     l.  Account information      1.  creation date      2.  expiration date     m.  Restrictions      1.  time of day      2.  location      3.  type of service   n. Billing address   o. Payment method	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	3328	C-MSS-75120	B0	The Accountability Service shall have the capability to receive user registration status requests from the CLS.	99-0729	08/25/1999  	No Data	
447	SMC-5320	5B Future	The ECS shall establish and maintain user access privileges for ECS scientific users via secure login services or secure web facilities as required.	3329	C-MSS-75125	B1	The Accountability Service shall have the capability to receive user comment survey requests from the CLS.	99-0729	08/25/1999  	No Data	
448	SMC-5340	Complete	The ECS shall provide tools to perform security including secure interactive access and file transfer, auditing and compromise detection.	3290	C-MSS-70400	A	The MSS EMC Security Management Application Service shall have the capability to receive notifications of security events from the site Security Management Application Services.	99-0729	08/25/1999  	No Data	
448	SMC-5340	Complete	The ECS shall provide tools to perform security including secure interactive access and file transfer, auditing and compromise detection.	3291	C-MSS-70410	B0	The MSS SMC Security Management Application Service shall have the capability to receive security audit trails from the site Security Management Application Services.	99-0729	08/25/1999  	No Data	
448	SMC-5340	Complete	The ECS shall provide tools to perform security including secure interactive access and file transfer, auditing and compromise detection.	3292	C-MSS-70420	B0	The MSS SMC Security Management Application Service shall have the capability to analyze security events for the purpose of detecting intrusions.	99-0729	08/25/1999  	No Data	
455	SMC-6300	Complete	The ECS shall support accountability policies and procedures based on ESDIS Project policies and procedures.	3094	C-MSS-52010	B1	The MSS Policy and Procedures Management Service at the SMC shall provide the capability to prepare, store, maintain, and make available for distribution ECS policies and procedures.	99-0729	08/25/1999  	No Data	
455	SMC-6300	Complete	The ECS shall support accountability policies and procedures based on ESDIS Project policies and procedures.	3095	C-MSS-52020	B1	The MSS Policy and Procedures Management Service shall provide the capability to access, select, and display/print ECS policies and procedures.	99-0729	08/25/1999  	No Data	
455	SMC-6300	Complete	The ECS shall support accountability policies and procedures based on ESDIS Project policies and procedures.	3096	C-MSS-52030	B1	The MSS Policy and Procedures Management Service shall provide the capability to input, store, maintain, and view/print site specific policies and procedures.	99-0729	08/25/1999  	No Data	
455	SMC-6300	Complete	The ECS shall support accountability policies and procedures based on ESDIS Project policies and procedures.	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
456	SMC-6310	Complete	The ECS shall generate security audit logs.	3291	C-MSS-70410	B0	The MSS SMC Security Management Application Service shall have the capability to receive security audit trails from the site Security Management Application Services.	99-0729	08/25/1999  	No Data	
456	SMC-6310	Complete	The ECS shall generate security audit logs.	3292	C-MSS-70420	B0	The MSS SMC Security Management Application Service shall have the capability to analyze security events for the purpose of detecting intrusions.	99-0729	08/25/1999  	No Data	
456	SMC-6310	Complete	The ECS shall generate security audit logs.	3341	C-MSS-76020	A	The MSS accountability management service shall be capable of retrieving all activities associated with a particular user or data item from the Management Database.	99-0729	08/25/1999  	No Data	
456	SMC-6310	Complete	The ECS shall generate security audit logs.	3342	C-MSS-76030	B0	The MSS Accountability Management Service shall be capable of browsing, via the Management Data Access service, logged events, for each ECS host, indicating incoming access attempts via:  a.  telnet  b.  FTP  c.  rlogin  d.  finger.	99-0729	08/25/1999  	No Data	
456	SMC-6310	Complete	The ECS shall generate security audit logs.	3343	C-MSS-76040	B0	The MSS Accountability Management Service shall be capable of reporting audit information to M&O staff via the MUI service.	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3338	C-MSS-76000	B0	The MSS accountability management service shall be capable of retrieving user activity data (user id, type of user activity, data items used (browsed, searched, or ordered), and date/time of activity) from records generated by the SDPS Data Server, Data Processing, and Client subsystems.	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3340	C-MSS-76010	B0	The MSS accountability management service shall be capable of querying user activity data stored in the Management Database.	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3341	C-MSS-76020	A	The MSS accountability management service shall be capable of retrieving all activities associated with a particular user or data item from the Management Database.	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3344	C-MSS-77040	B0	The MSS accountability management service shall be capable of accepting queries for the status of a particular ordered data item from M&O operators.	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3345	C-MSS-77050	B0	The MSS accountability management service shall be capable of interfacing with the SDPS subsystems to determine the status of an ordered data item to be:  a.  Pending  b.  Operator intervention  c.  Staging  d.  Transferring  e.  Not Found  f.  Waiting for Shipment  g.  Shipped	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3347	C-MSS-77070	A	The MSS accountability management service shall be capable of searching local history logs to find processing data for an ordered data item.	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3349	C-MSS-77090	B0	The MSS Accountability Management Service shall have the capability to redirect reports to:  a. console  b. disk file  c. printer	99-0729	08/25/1999  	No Data	
457	SMC-6320	Complete	The ECS shall perform, as needed, data and user audit trails.	3381	C-MSS-90290	B0	The DBMS shall provide an audit trail of chronological activities in the database.	99-0729	08/25/1999  	No Data	
458	SMC-6340	Complete	The ECS shall track system configuration that audits:  a. Hardware resources  b. Software resources	2986	C-MSS-40120	XT	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. 	99-0729	08/25/1999  	No Data	
458	SMC-6340	Complete	The ECS shall track system configuration that audits:  a. Hardware resources  b. Software resources	2987	C-MSS-40140	XT	The MSS configuration management application service shall maintain, and make available system-wide, information identifying  sites at which each configuration controlled resource is deployed.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	83	C-MSS-75021	5B	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')	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	84	C-MSS-75022	5B	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.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	85	C-MSS-75023	5B	The MSS accountability management service shall use a value of Non-NASA User ('N') as the default value for the NASA User attribute.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	100	C-MSS-75045	5B	The MSS Accountability Management Service shall be capable of tracking the status of an order and each of its subordinate requests.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	101	C-MSS-75055	5B	The MSS Accountability Management Service shall be capable of displaying the status of a specified data order and its requests to M&O operators.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	893	C-CSS-20000	A	The CSS Directory service shall provide the basic functionality to save and retrieve information into the local namespace:  a. Create/Delete/Get context (key)  b. List context.  c. Set/Get attributes.  d. Create/Delete attributes.  e. List attributes.  f. Set/Get attribute information.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	904	C-CSS-20090	A	The CSS Directory service shall define a minimum of 20 user defined attribute types for application users to store/retrieve attribute information.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3313	C-MSS-75001	B0	The MSS accountability management service shall provide the capability to maintain a user profile database that stores the following information for each registered user:     a.  Name     b.  User ID     c.  Password information      1.  password      2.  password expiration date      d.  Assigned privileges     e.  Mailing address     f.  Telephone number     g.  Product shipping address     h.  E-mail address     i.  Organization (optional)   j.  Project affiliation(s) (optional)      1.  project name      2.  project principal investigator     k.  User group     l.  Account information      1.  creation date      2.  expiration date     m.  Restrictions      1.  time of day      2.  location      3.  type of service   n. Billing address   o. Payment method	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3314	C-MSS-75010	B0	The MSS accountability management service shall be capable of receiving user profile records entered by M&O personnel.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3315	C-MSS-75015	B0	The MSS accountability management service shall provide the capability for M&O Staff to modifying and delete user profile records.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3316	C-MSS-75020	B0	The MSS Accountability Management Service shall create a new user account whenever a new record is added to the user profile database.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3317	C-MSS-75025	B0	The MSS Accountability Management Service shall be capable of receiving requests for user profile data from ECS applications.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3318	C-MSS-75030	B0	The MSS Accountability Management Service shall be capable of receiving requests for user profile data from M&O operators.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3319	C-MSS-75035	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to ECS applications	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3320	C-MSS-75040	B0	The MSS Accountability Management Service shall be capable of sending requested user profile data to M&O operators.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3321	C-MSS-75050	B0	The MSS Accountability Management Service shall be capable of receiving requests for user account history data from M&O operators.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3323	C-MSS-75057	B0	The MSS Accountability Management Service shall be capable of sending requested user account history data to M&O operators.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3325	C-MSS-75105	B0	The  Accountability Service shall have the capability to receive user registration requests from the CLS.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3327	C-MSS-75115	B0	The Accountability Service shall have the capability to receive requests for user profile updates from the CLS.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3331	C-MSS-75135	B0	The Accountability Service shall have the capability to send user registration status to the CLS.	99-0729	08/25/1999  	No Data	
459	SMC-7300	5B Partial	The ECS shall establish, maintain, and update the authorized users inventory to include:  a. Users identifications  b. Addresses  c. Allowed privileges	3339	C-MSS-76005	B0	The MSS Accountability Management Service shall be capable of retrieving user history data for a specified managed resource.	99-0729	08/25/1999  	No Data	
461	SMC-8730	Complete	The ECS shall have the capability to generate reports showing the following detailed and summary information about the maintenance schedule for system hardware and system software:  a. Routine maintenance schedules  b. Non-routine maintenance schedules  c. Upgrade maintenance schedule	3078	C-MSS-50020	XT	The MSS Maintenance Management Service shall provide the M&O staff the capability to produce corrective maintenance reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
461	SMC-8730	Complete	The ECS shall have the capability to generate reports showing the following detailed and summary information about the maintenance schedule for system hardware and system software:  a. Routine maintenance schedules  b. Non-routine maintenance schedules  c. Upgrade maintenance schedule	3080	C-MSS-50040	B0	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print Preventive Maintenance (PM) information for site equipment.	99-0729	08/25/1999  	No Data	
461	SMC-8730	Complete	The ECS shall have the capability to generate reports showing the following detailed and summary information about the maintenance schedule for system hardware and system software:  a. Routine maintenance schedules  b. Non-routine maintenance schedules  c. Upgrade maintenance schedule	3081	C-MSS-50050	B0	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print key information concerning PM  performed.	99-0729	08/25/1999  	No Data	
461	SMC-8730	Complete	The ECS shall have the capability to generate reports showing the following detailed and summary information about the maintenance schedule for system hardware and system software:  a. Routine maintenance schedules  b. Non-routine maintenance schedules  c. Upgrade maintenance schedule	3082	C-MSS-50060	XT	The MSS Maintenance Management Service shall provide the capability to input, store, maintain, and view/print corrective maintenance performed (CMP) information.	99-0729	08/25/1999  	No Data	
461	SMC-8730	Complete	The ECS shall have the capability to generate reports showing the following detailed and summary information about the maintenance schedule for system hardware and system software:  a. Routine maintenance schedules  b. Non-routine maintenance schedules  c. Upgrade maintenance schedule	3460	C-MSS-92670	B1	The MSS Report Generation Service shall be capable of generating a Maintenance Schedule Report on H/W, system S/W and science S/W indicating the type of maintenance (i.e,  routine, non-routine and upgrade)	99-0729	08/25/1999  	No Data	
462	SMC-8750	Complete	The ECS shall have the capability to generate the following detailed and summary training reports:  a. Training programs  b. Training course schedules   c. Training course contents  d. Training course locations   e. Training attendees	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
462	SMC-8750	Complete	The ECS shall have the capability to generate the following detailed and summary training reports:  a. Training programs  b. Training course schedules   c. Training course contents  d. Training course locations   e. Training attendees	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3056	C-MSS-45040	XT	The MSS Inventory/Logistics Management Service at the SMC shall generate site and multi-site inventory reports for printout and display.	02-1081	12/13/2002  		
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3061	C-MSS-45090	XT	The MSS Inventory/Logistics Management Service shall generate site inventory reports for printout and display.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3062	C-MSS-45200	XT	The MSS Logistics Management Service  shall provide the capability to input, store, update and view/print specified site's spare inventory information.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3063	C-MSS-45210	XT	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.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3066	C-MSS-45240	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate site spare related reports.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3069	C-MSS-45270	XT	The MSS Inventory/Logistics Management Service shall provide the capability to generate site spare parts related reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3070	C-MSS-45280	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3072	C-MSS-45300	B0	The MSS Inventory/Logistics Management Service shall provide the capability to generate site consumable items related reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3074	C-MSS-45320	B0	The MSS Inventory/Logistics Management Service at the SMC shall provide the capability to generate individual site or consolidated sites consumable items on-order reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3091	C-MSS-50200	B0	The MSS Maintenance Management Service shall provide the capability to generate off-site maintenance reports based on operator entered criteria.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3367	C-MSS-90060	B0	The DBMS shall provide an SQL interface with query, update, and administrative functions capabilities.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3383	C-MSS-90510	A	The Report Generator shall provide a Motif based Graphical User Interface (GUI) for creating ad hoc reports.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3384	C-MSS-90520	B0	The Report Generator shall have the capability to generate ad hoc reports from management data maintained in the DBMS.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3385	C-MSS-90530	B0	The Report Generator shall provide the capability to format reports to include the report:  a. title  b. header  c. footer  d. page number  e. date/time of report	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3387	C-MSS-90600	A	The Report Generator shall provide the capability to redirect generated reports to:  a. console  b. disk file  c. printer	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
463	SMC-8770	Complete	The ECS shall have the capability to generate detailed and summary reports showing the inventory of:  a. Hardware  system, and scientific software  b. Spares and consumables  c. COTS Software	3461	C-MSS-92690	B1	The MSS Report Generation Service shall be capable of generating an Inventory Status Report containing summary and detailed status information on H/W, system S/W and science S/W and listing spares and consumables status at sites.	99-0729	08/25/1999  	No Data	
464	SMC-8790	Complete	The ECS shall have the capability to generate, as necessary, a list of proposed enhancements with these elements:  a. Proposal name  b. Description of enhancement  c. Rationale  d. Impacts  e. Costs  f. Milestone schedule	3388	C-MSS-91010	B0	The MSS Office Automation word processing capability shall facilitate the:  a. preparation, revision, and recording of documents, messages, reports, and data  b. import, transformation, and editing of documents produced by other word processing packages  c. insertion of worksheet and graphic images into documents, messages, and reports  d. transfer of document, message, and report information to spreadsheet and graphics applications  e. printing of documents, messages, reports, and data	99-0729	08/25/1999  	No Data	
464	SMC-8790	Complete	The ECS shall have the capability to generate, as necessary, a list of proposed enhancements with these elements:  a. Proposal name  b. Description of enhancement  c. Rationale  d. Impacts  e. Costs  f. Milestone schedule	3391	C-MSS-91020	IR1	The MSS Office Automation shall provide a spreadsheet capability that:  a. simulates and displays an accountant's worksheet  b. enables revisions and calculations on the displayed worksheet's data  c. enables transfer of the worksheet data to database, word processing and graphics applications  d. enables printing of worksheet information.	99-0729	08/25/1999  	No Data	
464	SMC-8790	Complete	The ECS shall have the capability to generate, as necessary, a list of proposed enhancements with these elements:  a. Proposal name  b. Description of enhancement  c. Rationale  d. Impacts  e. Costs  f. Milestone schedule	3402	C-MSS-92070	B1	The MSS Report Generation Service shall be capable of generating an Enhancement Proposal Status Report containing the status of proposed enhancements including:     a.  name     b. description     c. rationale     d. impacts     e. cost to implement       f. implementation milestone schedule	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3116	C-MSS-57500	B0	The Trouble Ticketing Service shall have a graphical user interface to support the entry and editing of trouble tickets.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3117	C-MSS-57510	B0	The Trouble Ticketing Service shall provide the ability to automatically notify the originator of the trouble ticket of changes in status.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3118	C-MSS-57520	B0	The Trouble Ticketing Service shall provide an Application Program Interface which supports integration of entry of trouble tickets by other packages.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3119	C-MSS-57530	B0	The Trouble Ticketing Service shall provide the ability to search historical and current trouble tickets by various criteria including keyword, user id, and trouble ticket ID.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3120	C-MSS-57540	B0	The Trouble Ticketing Service shall provide the ability to forward trouble tickets from one organization to another to facilitate the escalation of trouble tickets (e.g. from DAAC to SMC).	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3121	C-MSS-57550	B0	The Trouble Ticketing Service shall be capable of indicating whether a trouble ticket is open, in progress, closed, or archived.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3122	C-MSS-57560	B0	The Trouble Ticketing Service shall provide the ability to search for trouble tickets relating to the same resource (equipment).	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3123	C-MSS-57580	B0	The Trouble Ticketing Service shall provide the ability to store the following minimum set of information : unique trouble ticket ID, status, description, associated resources, problem solution, originator, keywords.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3124	C-MSS-57590	B0	The Trouble Ticketing Service shall integrate with the MSS framework to allow management and monitoring of its services.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3125	C-MSS-57600	B0	The Trouble Ticketing Service shall allow entry of a trouble ticket by any registered user of the system.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3126	C-MSS-57610	B0	The Trouble Ticketing Service shall provide the capability to generate reports from the its data.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3127	C-MSS-57620	B0	The Trouble Ticketing Service shall allow output of reports to either the screen or printer.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3128	C-MSS-57630	B0	The Trouble Ticketing Service shall provide customization features to allow sites to specify notification and escalation rules.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3201	C-MSS-60600	IR1	The MSS Fault Management Application Service shall have the capability to generate, on an interactive and on a scheduled basis, reports on performance/error data that it has been configured to collect.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3426	C-MSS-92310	B1	The MSS Report Generation Service shall be capable of generating a Fault Management Report containing summary and detailed information on fault management of ground resources including:       a. Fault type and description     b. Time of fault occurrence     c. Effect of fault on system     d. Status of fault resolution     e. Fault statistics	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3427	C-MSS-92320	B0	The MSS Report Generation Service shall be capable of generating a Trouble Status Report containing statistics on the number of trouble tickets opened, closed, and in work at a site.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3428	C-MSS-92330	B0	The MSS Report Generation Service shall be capable of generating an Ethernet Errors Report graphically depicting Ethernet error statistics for a selected node in real-time.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3429	C-MSS-92340	B0	The MSS Report Generation Service shall be capable of generating an SNMP Errors report graphically depicting SNMP error statistics in real-time for the selected network nodes.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3430	C-MSS-92350	B0	The MSS Report Generation Service shall be capable of generating an SNMP Authentication Failures Report listing the management systems that caused an authentication failure on the operator selected node(s).	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3431	C-MSS-92360	B0	The MSS Report Generation Service shall be capable of generating an SNMP Event Log Report containing a chronological list of SNMP events which occurred over the report interval for the selected node(s).	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3432	C-MSS-92370	B0	The MSS Report Generation Service shall be capable of generating a Site Host Errors Report containing a statistical summary of the types of errors logged at each host at a site over the reporting period.	99-0729	08/25/1999  	No Data	
465	SMC-8860	Complete	The ECS shall have the capability to generate the following fault management reports describing the fault management of ground resources:  a. Fault type and description  b. Time of occurrence of fault  c. Effect on system  d. Status of fault resolution  e. Fault statistics	3433	C-MSS-92380	B0	The MSS Report Generation Service shall be capable of generating an SMC Host Errors Report containing a statistical summary of the types of errors logged at each site over the reporting period.	99-0729	08/25/1999  	No Data