|SA Service||Common Data & Metadata Model||Data Exchange||Data Catalog||Persistent Archive||Elastic Computing||Execution Engine||Resource Management||Federated Facility||Messaging||State Management||Identity Management||Policy||Resource Catalog|
|Data Acquisition|| The data that is acquired by this service must be described (translated) into the common data and metadata forms.
|| All data acquired will be put into the data exchange.
|| The description of the data that is acquired must be stored in the data catalog.
|| The historical data that was acquired will be available through the persistent archival service.
|| The data acquisition process will need to be managed as a resource.
||All interactions for Data Acquisition service (including data acquired) will be through the messaging service.|| The acquired data will have to be tagged with an identity.
|| The data acquisition process as well as the end data products will have to be registered in the catalog
|Comment|| Should include standardized State information (latest configuration, calibration, etc.)
|| Will any data be restricted? Will data access log allow "data recall" or "notice to user" if data is later deemed flawed?
Skip to end of metadata Go to start of metadata