Publications

Abstract not provided.

Abstract not provided.

Abstract not provided.

Abstract not provided.

Abstract not provided.

Abstract not provided.

SNL’s IDC Reengineering Phase 2 team developed 31 Use Cases (UCs) during the E3 Elaboration Iteration. This document describes the changes made to these UCs after their initial delivery to the IDC in October 2016.

Sandia National Laboratories has prepared a budgetary cost estimate for planning for the IDC Re-engineering Phase 3 effort, based on leveraging a fully funded, Sandia executed NDC Modernization project. This report provides the budgetary cost estimate and describes the methodology, assumptions, and cost model details used to create the budgetary cost estimate.

This document contains 4 use case realizations generated from the model contained in Rational Software Architect. These use case realizations are the current versions of the realizations originally delivered in Elaboration Iteration 3.

Sandia National Laboratories has prepared a project development plan that proposes how the parties interested in the IDC Re-Engineering system will coordinate its development, testing and transition to operations.

This document contains a description of the system architecture for the IDC Re-Engineering Phase 2 project.

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Re-Engineering Phase 2 project. This System Specification Document (SSD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The routine processing includes characterization of events with the objective of screening out events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena. This document does not address requirements concerning acquisition, processing and analysis of radionuclide data but does include requirements for the dissemination of radionuclide data and products.

This System Requirements Document (SRD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The IDC applies, on a routine basis, automatic processing methods and interactive analysis to raw International Monitoring System (IMS) data in order to produce, archive, and distribute standard IDC products on behalf of all States Parties. The routine processing includes characterization of events with the objective of screening out events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena. This document does not address requirements concerning acquisition, processing and analysis of radionuclide data, but includes requirements for the dissemination of radionuclide data and products.

This document contains 4 use case realizations generated from the model contained in Rational Software Architect. These use case realizations are the current versions of the realizations originally delivered in Elaboration Iteration 1.

This document contains 4 use case realizations generated from the model contained in Rational Software Architect. These use case realizations are the current versions of the realizations originally delivered in Elaboration Iteration 2.

Abstract not provided.

This document contains 4 use case realizations generated from the model contained in Rational Software Architect.

This architecturally significant use case describes how the System acquires meteorological data to build atmospheric models used in automatic and interactive processing of infrasound data. The System requests the latest available high-resolution global meteorological data from external data centers and puts it into the correct formats for generation of infrasound propagation models. The system moves the meteorological data from Data Acquisition Partition to the Data Processing Partition and stores the meteorological data. The System builds a new atmospheric model based on the meteorological data. This use case is architecturally significant because it describes acquiring meteorological data from various sources and creating dynamic atmospheric transmission model to support the prediction of infrasonic signal detections.

Abstract not provided.

This architecturally significant use case describes how the System acquires meteorological data to build atmospheric models used in automatic and interactive processing of infrasound data. The System requests the latest available high-resolution global meteorological data from external data centers and puts it into the correct formats for generation of infrasound propagation models. The system moves the meteorological data from Data Acquisition Partition to the Data Processing Partition and stores the meteorological data. The System builds a new atmospheric model based on the meteorological data. This use case is architecturally significant because it describes acquiring meteorological data from various sources and creating dynamic atmospheric transmission model to support the prediction of infrasonic signal detection

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Re- Engineering Phase 2 project.

This report contains a draft Component Interface Specification (CIS) for an application controlling signal detection calculations. It is an example of the contents and level of detail of information in a CIS. The classes, interfaces, and data types in this report reflect current understanding of system concepts and potential implementation patterns but should not be interpreted as containing the finalized interface specifications, classes, etc. The primary purpose of this report is to discuss the potential OSD APIs represented in class diagrams for the Waveform, QC Mask, and Signal Detection Repository interfaces.

This report contains a draft Component Interface Specification (CIS) for a signal detector. It is an example of the contents and level of detail of information in a CIS. The classes, interfaces, and data types in this report reflect current understanding of system concepts and potential implementation patterns but should not be interpreted as containing the finalized interface specifications, etc.

This initial draft document contains formative data model content for select areas of Re-Engineering Phase 2 IDC System. The purpose of this document is to facilitate discussion among the stakeholders. It is not intended as a definitive proposal.

Abstract not provided.