Building Fuel Cycle Options Collaboratively With Microsoft SharePoint SQL Server and SQL Server Reporting Services.
Abstract not provided.
Barela, Amanda Crystal↗
SEARCH · Search NASA
Results for “Microsoft SQL”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
FJET Database Project: Extract, Transform, and Load
The Data Mining & Knowledge Management team at Kennedy Space Center is providing data management services to the Frangible Joint Empirical Test (FJET) project at Langley Research Center (LARC). FJET is a project under the NASA Engineering and Safety Center (NESC). The purpose of FJET is to conduct an assessment of mild detonating fuse (MDF) frangible joints (FJs) for human spacecraft separation tasks in support of the NASA Commercial Crew Program. The Data Mining & Knowledge Management team has been tasked with creating and managing a database for the efficient storage and retrieval of FJET test data. This paper details the Extract, Transform, and Load (ETL) process as it is related to gathering FJET test data into a Microsoft SQL relational database, and making that data available to the data users. Lessons learned, procedures implemented, and programming code samples are discussed to help detail the learning experienced as the Data Mining & Knowledge Management team adapted to changing requirements and new technology while maintaining flexibility of design in various aspects of the data management project.
excel vba↗
Technical Evaluation Report for the NDMAS AGR-5/6/7 TRISO Irradiation Monitoring System
The Nuclear Data Management and Analysis System (NDMAS) manages irradiation experiment data collected under the Advanced Gas Reactor (AGR) Fuel Development and Qualification program within the Advanced Reactor Technologies Technology Development Office. The AGR-5/6/7 irradiation experiment combines the fifth, sixth, and seventh planned irradiation campaigns of the U.S. Department of Energy AGR Fuel Development and Qualification Program. These combined irradiation tests will consist of fuel qualification tests (AGR-5/6) and a margin test (AGR-7) for the industrially produced uranium oxycarbide (UCO) tristructural isotropic (TRISO) coated particle fuel developed by the AGR program. The objective of the AGR-5/6/7 irradiation experiment is to establish the performance of UCO TRISO fuel fabricated using engineering-scale equipment in a production environment under and beyond normal operating conditions (PNL-5245). Experimental irradiation measurements for this experiment (i.e., thermocouple temperature, gas flow rate, fission product release rate, gross gamma count, and Advanced Test Reactor (ATR) operational parameters) are captured automatically to the NDMAS database. Data derived from numerical simulation or other mathematical analyses (i.e., fast fluence, burnup, temperature, and fission product release to birth ratio) are captured to the database when provided by the researchers. The NDMAS database is a relational database accessed via structured query language and managed with Microsoft SQL Server. While select users can directly access the database, that is not the most convenient way to interact with the data. The NDMAS team constructs numerous tables that combine related datasets, and delivers those data to researchers via graphs and spreadsheets on a Microsoft SharePoint-based website. For the AGR-5/6/7 experimental data, a new subsite has been developed, along with a set of web pages. These pages will be used by members of fuel irradiation team for monitoring irradiation conditions according to specification (SPC-1749), by the physics modelers to access necessary model inputs, and by the nuclear engineering community to view and access data such as fuel temperatures, fission product release from capsules, and ATR operational parameters. The deliverable represented in this document is a SharePoint website containing tables of the AGR-5/6/7 measured and calculated data, graphs displaying the data, and links to source documents and references.
11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
AGR-5/6/7 Irradiation Monitoring Web Site Design
The Nuclear Data Management and Analysis System (NDMAS) manages irradiation experiment data collected under the Advanced Gas Reactor (AGR) Fuel Development and Qualification program within the Advanced Reactor Technologies Technology Development Office. The AGR-5/6/7 irradiation experiment combines the fifth, sixth, and seventh planned irradiation campaigns of the U.S. Department of Energy AGR Fuel Development and Qualification Program. These combined irradiation tests will consist of fuel qualification tests (AGR-5/6) and a margin test (AGR-7) for the industrially produced uranium oxycarbide (UCO) tristructural isotropic (TRISO) coated particle fuel developed by the AGR program. The objective of the AGR-5/6/7 irradiation experiment is to establish the performance of UCO TRISO fuel fabricated using engineering-scale equipment in a production environment under and beyond normal operating conditions (PNL-5245). Experimental irradiation measurements for this experiment (i.e., thermocouple temperature, gas flow rate, fission product release rate, gross gamma count, and Advanced Test Reactor (ATR) operational parameters) are captured automatically to the NDMAS database. Data derived from numerical simulation or other mathematical analyses (i.e., fast fluence, burnup, temperature, and fission product release to birth ratio) are captured to the database when provided by the researchers. The NDMAS database is a relational database accessed via structured query language and managed with Microsoft SQL Server. While select users can directly access the database, that is not the most convenient way to interact with the data. The NDMAS team constructs numerous tables that combine related datasets, and delivers those data to researchers via graphs and spreadsheets on a Microsoft SharePoint-based website. For the AGR-5/6/7 experimental data, a new subsite has been developed, along with a set of web pages. These pages will be used by members of fuel irradiation team for monitoring irradiation conditions according to specification (SPC-1749), by the physics modelers to access necessary model inputs, and by the nuclear engineering community to view and access data such as fuel temperatures, fission product release from capsules, and ATR operational parameters. The deliverable represented in this document is a SharePoint website containing tables of the AGR-5/6/7 measured and calculated data, graphs displaying the data, and links to source documents and references.
11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
SU-E-T-235: Data Mining for Evaluating Treatment Performances Over a Large Quantity of Data to Monitor and Improve SBRT Workflow
Purpose: To quality assure a large quantity of retrospective treatment cases for treatment performances by randomly sampling is inefficient. Here we provide a method to efficiently monitor and investigate the QA of SBRT workflow over Mosaiq. Methods: The code developed with Microsoft SQL Server Management Studio 2008R2 and VBA was used for retrieving and sorting data from Mosaiq (version 2.3–2.6 during 2012–2015). SBRT patients were filtered by fractional dose over 350cGy and total fraction number less than 6, which SBRT prescriptions were defined. The quality assurance on the SBRT workflow was focused on the treatment deliveries such as patient positioning setup, CBCT indicated offsets and couch shifted corrections. The treatment delivery were done by Varian Truebeam systems and the record/verify by Mosaiq. Results: Total 82 SBRT patients corresponding to 103 courses and 854 CBCT images were found by the retrieval query. Most centers record daily pre-treatment (Pre-Tx: before treatment shift) image-guided shifts along treatment course for inter-fraction motion record, and it is useful to also verify it with post-treatment imaging (Post-Tx: after treatment CBCT verification) to verify intra-fraction motion. Analyzing the details of daily recorded shifts can reveals the information of patient-setup and staff’s record/verify behaviors. 3 examples were provided as solid evidences and on-going rectification for preventing future mistakes. Conclusions: The report gave feasible examples for inspector to verify a large amount of data during site investigation. This program can also be extended to a scheduled data mining with software to periodical analyze the timely records in Mosaiq, for example, a various control charts for different QA purposes. As the current trend of automation in radiation therapy field, the data mining would be a necessary tool in the future, just as the automatic plan quality evaluation has been under development in Eclipse.
60 APPLIED LIFE SCIENCES↗
Integrated Budget Office Toolbox
The Integrated Budget Office Toolbox (IBOT) combines budgeting, resource allocation, organizational funding, and reporting features in an automated, integrated tool that provides data from a single source for Johnson Space Center (JSC) personnel. Using a common interface, concurrent users can utilize the data without compromising its integrity. IBOT tracks planning changes and updates throughout the year using both phasing and POP-related (program-operating-plan-related) budget information for the current year, and up to six years out. Separating lump-sum funds received from HQ (Headquarters) into separate labor, travel, procurement, Center G&A (general & administrative), and servicepool categories, IBOT creates a script that significantly reduces manual input time. IBOT also manages the movement of travel and procurement funds down to the organizational level and, using its integrated funds management feature, helps better track funding at lower levels. Third-party software is used to create integrated reports in IBOT that can be generated for plans, actuals, funds received, and other combinations of data that are currently maintained in the centralized format. Based on Microsoft SQL, IBOT incorporates generic budget processes, is transportable, and is economical to deploy and support.
Rushing, Douglas A.↗
Medical Optimization Network for Space Telemedicine Resources
INTRODUCTION: Long-duration missions beyond low Earth orbit introduce new constraints to the space medical system. Beyond the traditional limitations in mass, power, and volume, consideration must be given to other factors such as the inability to evacuate to Earth, communication delays, and limitations in clinical skillsets. As NASA develops the medical system for an exploration mission, it must have an ability to evaluate the trade space of what resources will be most important. The Medical Optimization Network for Space Telemedicine Resources (MONSTR) was developed over the past year for this reason, and is now a system for managing data pertaining to medical resources and their relative importance when addressing medical conditions. METHODS: The MONSTR web application with a Microsoft SQL database backend was developed and made accessible to Tableau v9.3 for analysis and visualization. The database was initially populated with a list of medical conditions of concern for an exploration mission taken from the Integrated Medical Model (IMM), a probabilistic model designed to quantify in-flight medical risk. A team of physicians working within the Exploration Medical Capability Element of NASA's Human Research Program compiled a list diagnostic and treatment medical resources required to address best- and worst-case scenarios of each medical condition using a terrestrial standard of care and entered this data into the system. This list included both tangible resources (e.g. medical equipment, medications) and intangible resources (e.g. clinical skills required to perform a procedure). The physician team then assigned criticality values to each instance of a resource, representing the importance of that resource to diagnosing or treating its associated condition(s). Medical condition probabilities of occurrence during a Mars mission were pulled from the IMM and imported into the MONSTR database for use within a resource criticality-weighting algorithm. DISCUSSION: The MONSTR tool is a novel approach to assess the relative value of individual resources needed for the diagnosis and treatment of medical conditions. Future work will add resources for prevention and long term care of these conditions. Once data collection is complete, MONSTR will provide the operational and research communities at NASA with information to support informed decisions regarding areas of research investment, future crew training, and medical supplies manifested as part of any exploration medical system.
Rubin, D.↗
What is EA?
An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives. A single slide PowerPoint, size 36" x 48" has been produced for printing onto a poster board for display in the Pathways Internship showcase November 2018. This poster board presentation is a display of my internship from 2014 to present, to include my NIFS (NASA Interns, Fellowships, Scholarships) internship, ITSS (Information Technology Support Services) contract, and current Pathways internship. The presentation discusses my years producing deliverables for: the ISS (International Space Station) Anomaly Project in 2014, the FJET (Frangible Joint Empirical Test) database project in 2015, the CUI (Compact Unique Identifier) project in early 2016, and various Enterprise Architecture deliverables and contributions such as the Roadmap SQL (Structured Query Language) stored procedure and architectural views of Program data elements.
MySQL↗
SU-F-R-12: Prediction of TrueBeam Hardware Issues Using Trajectory Log Analysis
Purpose: To predict potential failures of hardware within the Varian TrueBeam linear accelerator in order to proactively replace parts and decrease machine downtime. Methods: Machine downtime is a problem for all radiation oncology departments and vendors. Most often it is the result of unexpected equipment failure, and increased due to lack of in-house clinical engineering support. Preventative maintenance attempts to assuage downtime, but often is ineffective at preemptively preventing many failure modes such as MLC motor failures, the need to tighten a gantry chain, or the replacement of a jaw motor, among other things. To attempt to alleviate downtime, software was developed in house that determines the maximum value of each axis enumerated in the Truebeam trajectory log files. After patient treatments, this data is stored in a SQL database. Microsoft Power BI is used to plot the average maximum error of each day of each machine as a function of time. The results are then correlated with actual faults that occurred at the machine with the help of Varian service engineers. Results: Over the course of six months, 76,312 trajectory logs have been written into the database and plotted in Power BI. Throughout the course of analysis MLC motors have been replaced on three machines due to the early warning of the trajectory log analysis. The service engineers have also been alerted to possible gantry issues on one occasion due to the aforementioned analysis. Conclusion: Analyzing the trajectory log data is a viable and effective early warning system for potential failures of the TrueBeam linear accelerator. With further analysis and tightening of the tolerance values used to determine a possible imminent failure, it should be possible to pinpoint future issues more thoroughly and for more axes of motion.
46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗
Precursor Analysis Report: SQL Slammer Worm Infection of Davis-Besse Nuclear Power Plant 2003
The SQL Slammer Worm Infection of Davis-Besse Nuclear Power Plant 2003 Precursor Analysis Report leverages publicly available information about Davis-Besse’s 2003 cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. On 25 January 2003, the SQL Slammer worm infected more than 90% of vulnerable hosts and crashed the internet in 10 to 15 minutes, making it one of the fastest spreading worms in history. SQL Slammer is a fileless, memory-resident worm that remotely exploits a stack-based buffer overflow vulnerability on local hosts to intensively scan and rapidly self-propagate across the internet. The worm infected approximately 300,000 unpatched hosts running Microsoft Structured Query Language (SQL) Server 2000 or Microsoft Desktop Engine (MSDE) 2000 with SQL Server Resolution Service. The SQL Slammer worm indirectly infected FirstEnergy’s Davis-Besse nuclear power plant by first infecting a consultant’s company network server and then propagating through an external misconfigured connection into Davis-Besse’s site network. The infection caused major network congestion, slow performance, data overloads, and the inability of local hosts to communicate with each other, which eventually caused a loss of availability and a loss of view when the Safety Parameter Display System (SPDS) and Plant Process Computer (PPC) crashed. At the time of the infection, the plant was already offline, the digital monitoring systems had redundant analog backups, and the plant control and safety functions were not affected, so there were no concerns of a safety breach. However, this incident resulted in many lessons learned and spawned important discussions about cybersecurity’s role in nuclear safety and electric power reliability regulation, policy, and guidance. Researchers and analysts identified 10 unique techniques utilized during the attack with a total of 640 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Eight of the identified techniques used during Davis-Besse cyber attack were precursors to the triggering event. Analysis identified 596 observables associated with these precursor techniques, 428 of which were assessed to have an increased likelihood of being perceived in the 331 days preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.
45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
SU-F-T-100: Development and Implementation of a Treatment Planning Tracking System Into the Radiation Oncology Clinic
Purpose: With increasing numbers of cancer patients being diagnosed and the complexity of radiotherapy treatments rising it’s paramount that patient plan development continues to stay fluid within the clinic. In order to maintain a high standard of care and clinical efficiency the establishment of a tracking system for patient plan development allows healthcare providers to view real time plan progression and drive clinical workflow. In addition, it provides statistical datasets which can further identify inefficiencies within the clinic. Methods: An application was developed utilizing Microsoft’s ODBC SQL database engine to track patient plan status throughout the treatment planning process while also managing key factors pertaining to the patient’s treatment. Pertinent information is accessible to staff in many locations, including tracking monitors within dosimetry, the clinic network for both computers and handheld devices, and through email notifications. Plans are initiated with a CT and continually tracked through planning stages until final approval by staff. Patient’s status is dynamically updated by the physicians, dosimetrists, and medical physicists based on the stage of the patient’s plan. Results: Our application has been running over a six month period with all patients being processed through the system. Modifications have been made to allow for new features to be implemented along with additional tracking parameters. Based on in-house feedback, the application has been supportive in streamlining patient plans through the treatment planning process and data has been accumulating to further improve procedures within the clinic. Conclusion: Over time the clinic will continue to track data with this application. As data accumulates the clinic will be able to highlight inefficiencies within the workflow and adapt accordingly. We will add in new features to help support the treatment planning process in the future.
60 APPLIED LIFE SCIENCES↗
Database Reports Over the Internet
Most of the summer was spent developing software that would permit existing test report forms to be printed over the web on a printer that is supported by Adobe Acrobat Reader. The data is stored in a DBMS (Data Base Management System). The client asks for the information from the database using an HTML (Hyper Text Markup Language) form in a web browser. JavaScript is used with the forms to assist the user and verify the integrity of the entered data. Queries to a database are made in SQL (Sequential Query Language), a widely supported standard for making queries to databases. Java servlets, programs written in the Java programming language running under the control of network server software, interrogate the database and complete a PDF form template kept in a file. The completed report is sent to the browser requesting the report. Some errors are sent to the browser in an HTML web page, others are reported to the server. Access to the databases was restricted since the data are being transported to new DBMS software that will run on new hardware. However, the SQL queries were made to Microsoft Access, a DBMS that is available on most PCs (Personal Computers). Access does support the SQL commands that were used, and a database was created with Access that contained typical data for the report forms.
Dean Lance Smith↗
Accessing Microsoft Access Databases Using ODBC and RODBC
ODBC (Open Database Connectivity) is an industry-standard API (Application Program Interface) that provides a standard interface, based on SQL (Structured Query Language) between applications and databases. This insulates applications from specific details of different database management systems (DBMS). Microsoft Windows TM provides an implementation of ODBC, which, along with drivers for various databases, supports the API. Windows also provides a driver for Access databases.
97 MATHEMATICS AND COMPUTING↗
BESTEST-GSR (Building Energy Simulation Test - Generation Simulation and Reporting) [SWR 18-23]
Building Energy Simulation Test (BESTEST) is an NREL-developed method to validate the qualitative performance of different whole building simulations engines relative to each other. https://www.nrel.gov/docs/legosti/old/6231.pdf For EnergyPlus® and OpenStudio®, generation of test cases, simulation, and reporting has been a manual or partially automated process that typically took a number of months after a new version of EnergyPlus came out. Building Energy Simulation Test - Generation Simulation and Reporting (BESTEST-GSR) was developed to fully automate this process so it is less error-prone, less time-consuming, and can be quickly run on request for any development branch of EnergyPlus and OpenStudio. The initial use case is to directly support OpenStudio and EnergyPlus development, but the software is configured to support use by external software developers that build tools on top of EnergyPlus and/or OpenStudio. Tools built on top of OpenStudio can leverage the test generation, simulation, and reporting, while tools built on EnergyPlus can leverage the test simulation and reporting. The model generation is accomplished by running OpenStudio measures for envelope, heating, or cooling test cases. At this stage the specified weather file required for a specific test case is assigned to the model. Simulation is enabled using the OpenStudio Command Line Interface (CLI) to run a series of OpenStudio and Reporting measures to a specified seed model. The specified workflow is defined with an OpenStudio OSW file. The first measure generates the test case model, while the second measure is a reporting measure that runs after the simulation to collect necessary simulation results from the EnergyPlus SQL file. The Reporting stage gathers data from individual OpenStudio OSW files and populates a series of BESTEST Microsoft Excel spreadsheets. BESTEST-GSR also gathers zip files from individual simulations for diagnostic purposes.
Goldwasser, David↗
Using CLIPS in a distributed system: The Network Control Center (NCC) expert system
This paper describes an intelligent troubleshooting system for the Help Desk domain. It was developed on an IBM-compatible 80286 PC using Microsoft C and CLIPS and an AT&T 3B2 minicomputer using the UNIFY database and a combination of shell script, C programs and SQL queries. The two computers are linked by a lan. The functions of this system are to help non-technical NCC personnel handle trouble calls, to keep a log of problem calls with complete, concise information, and to keep a historical database of problems. The database helps identify hardware and software problem areas and provides a source of new rules for the troubleshooting knowledge base.
Wannemacher, Tom↗
Multi–LDAP Dynamic User Management Tool Utilizing Oracle Application Express and PL/SQL
A Center for Infrastructure Security Analysis (CISA) client system required support of multiple Lightweight Directory Access Protocol (LDAP) directories for multiple, varied user communities. The LDAP directories were all based upon different technologies, i.e., Microsoft Active Directory (AD), Microsoft Active Directory Lightweight Directory Services (ADLDS), and Oracle Internet Directory (OID), depending on system setup, security requirements, and legacy software. Research revealed that PL/SQL provided the capability to execute dynamic PL/SQL and SQL blocks. The dynamic capabilities were utilized along with several configuration tables to provide an object-oriented, polymorphic-like behavior. This architecture was chosen so that a top-level application programming interface (API) could be defined for all calls, no matter what type of LDAP was being manipulated, as each LDAP type has slightly different attributes and requirements. The dynamic nature of the user management system allowed for easy setup and utilization of any new LDAP directories, minimizing the time and effort expended on system changes.
97 MATHEMATICS AND COMPUTING↗
SU-E-T-255: Development of a Michigan Quality Assurance (MQA) Database for Clinical Machine Operations
Purpose: A unified database system was developed to allow accumulation, review and analysis of quality assurance (QA) data for measurement, treatment, imaging and simulation equipment in our department. Recording these data in a database allows a unified and structured approach to review and analysis of data gathered using commercial database tools. Methods: A clinical database was developed to track records of quality assurance operations on linear accelerators, a computed tomography (CT) scanner, high dose rate (HDR) afterloader and imaging systems such as on-board imaging (OBI) and Calypso in our department. The database was developed using Microsoft Access database and visual basic for applications (VBA) programming interface. Separate modules were written for accumulation, review and analysis of daily, monthly and annual QA data. All modules were designed to use structured query language (SQL) as the basis of data accumulation and review. The SQL strings are dynamically re-written at run time. The database also features embedded documentation, storage of documents produced during QA activities and the ability to annotate all data within the database. Tests are defined in a set of tables that define test type, specific value, and schedule. Results: Daily, Monthly and Annual QA data has been taken in parallel with established procedures to test MQA. The database has been used to aggregate data across machines to examine the consistency of machine parameters and operations within the clinic for several months. Conclusion: The MQA application has been developed as an interface to a commercially available SQL engine (JET 5.0) and a standard database back-end. The MQA system has been used for several months for routine data collection.. The system is robust, relatively simple to extend and can be migrated to a commercial SQL server.
60 APPLIED LIFE SCIENCES↗