Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Systems Engineering and Program Integration”

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.

At least 1,747 records · Page 97

Challenges of Maintaining Institutional Controls: Maintenance of an Alternate Water Supply- A Case Study - 19583

The US Department of Energy (DOE) cofunded an alternate water-supply system (AWSS) with the Indian Health Service that was installed in the vicinity of the former uranium mill site near Riverton, Wyoming, as one of the institutional controls (ICs) at the site. The AWSS was constructed in 1998 to supply drinking water to residents within the IC boundary in lieu of drinking untreated groundwater that could potentially be impacted by the contaminated shallow aquifer. The AWSS derives water from three source wells that pump groundwater from the sandstones of the Wind River Formation to a 3.8 x 106 liter (1,000,000 gallon) storage tank. Water from the storage tank is distributed throughout the AWSS service area by approximately 18 kilometers (11 miles) of PVC pipeline. The AWSS currently serves 103 residential customers and 1 commercial customer. DOE and the Northern Arapaho tribe (owner of the AWSS) have partnered over the years to address numerous challenges with the AWSS that included engineering assessments, scientific investigations, sampling support, a hydrant flushing program, and funding. Challenges with the AWSS have included the following: (1) Transmission pipe installed during initial construction did not have a pressure rating high enough to account for system pressure surges. (2) AWSS appurtenances were initially installed without accounting for the effects of corrosive soils on metal components. (3) Natural radium from the Wind River Formation groundwater builds up in the AWSS transmission pipes to levels above the primary drinking water standard because of the lack of a flushing program, dead-end lines, and low system demand. A 2-year study showed that a unidirectional hydrant-flushing program will control the radium buildup. (4) Aging system components including hydrants, valves, and pumps are nearing their effective lifespan and are in need of replacement. (5) With the addition of large commercial customers, demand on the system has increased since the initial installation of the system, and future growth in the area will continue to increase demand. (6) Additional connections and integration of the AWSS with an areawide water system in the near future will require changes to the current flushing plan and add additional complexity regarding areas of responsibility. (7) A well-organized financial and administrative infrastructure is not in place, and additional revenue is needed to operate, maintain, and improve the AWSS. To be a viable IC, the AWSS will require management, maintenance, and upgrades to provide safe drinking water until groundwater meets drinking water standards. Responsibilities and funding for maintaining the AWSS as a viable IC are the focus of current discussions, and decisions regarding responsibilities and funding will be formalized in future cooperative agreements and memoranda of understanding with the owners. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Integrated Laser Characterization, Data Acquisition, and Command and Control Test System

Satellite-based laser technology has been developed for topographical measurements of the Earth and of other planets. Lasers for such missions must be highly efficient and stable over long periods in the temperature variations of orbit. In this innovation, LabVIEW is used on an Apple Macintosh to acquire and analyze images of the laser beam as it exits the laser cavity to evaluate the laser s performance over time, and to monitor and control the environmental conditions under which the laser is tested. One computer attached to multiple cameras and instruments running LabVIEW-based software replaces a conglomeration of computers and software packages, saving hours in maintenance and data analysis, and making very longterm tests possible. This all-in-one system was written primarily using LabVIEW for Mac OS X, which allows the combining of data from multiple RS-232, USB, and Ethernet instruments for comprehensive laser analysis and control. The system acquires data from CCDs (charge coupled devices), power meters, thermistors, and oscilloscopes over a controllable period of time. This data is saved to an html file that can be accessed later from a variety of data analysis programs. Also, through the LabVIEW interface, engineers can easily control laser input parameters such as current, pulse width, chiller temperature, and repetition rates. All of these parameters can be adapted and cycled over a period of time.

Stysley, Paul↗

Predictive Modeling to Assess and Address Challenges and Limitations Associated with Clinical Care and Decision Support in Deep Space

Probabilistic risk assessment (PRA) is a method for assessing and integrating the risk of failure in a multivariate system. While it is often applied by engineers designing complex machines, it could also be applied to humans to assess the probability of a health “failure” treating diseases as the multiple “variables” and the human as the “complex machine.” The Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) was developed to apply PRA to assess medical risk for exploration spaceflight and inform the design of medical systems for space flight. The NASA engineering community utilizes event-driven and fault tree probabilistic techniques to classify risk in the space flight environment by leveraging the inherent knowledge of complex space flight system design and testing to quantify risk. However, in harmonizing the risk of human space flight, answering the question of “How do we balance astronaut health, performance and resource risks with other engineering risks on exploration space missions?” remains a profoundly challenging and largely qualitative practice. The Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) is one aspect of the Human Research Program’s efforts to represent space fight human health and performance risks quantitatively.

L Mcintyre↗

The Inspectability Metric: A Formalized System Of Measurement Enabling The Design For Inspection Framework

Nondestructive evaluation (NDE) engineers are often confronted with structural design choices that present challenges to meeting inspection requirements. These challenges, at best, increase the resources needed to design an inspection solution and, at worst, require resource intensive redesign of the structure. If the inspectability of the structure can be determined early in the design cycle, these challenging inspection scenarios can be avoided. The emergence of additive manufacturing has further compounded this problem by enabling the creation of highly optimized structures with no regard to inspection constraints. Design for inspection (DFI) offers a framework to integrate nondestructive evaluation (NDE) into the design process to alleviate the mechanisms that produce uninspectable designs. DFI is the concept of including inspectability in a multi-objective optimization framework so that it can be considered in parallel to other metrics such as mass and manufacturability. This allows rapid evaluation of the trade-off between design metrics to find solutions that meet the inspection needs of a particular material system, structural concept, or vehicle program. To enable DFI, there must be a system by which the inspectability of a structure can be measured. This system must be agile to produce results quickly, it must be versatile to work with the type of incomplete information one would encounter early in the design process (such as lack of inspection requirements), and it must be delivered in a form that is easily understood by designers. To meet this need, this presentation introduces the novel inspectability metric as a system to measure inspectability. The inspectability metric is a standardized, automation friendly procedure that uses simulations to determine inspectability. Along with guidelines to properly process designs and integrate with existing workflows, the inspectability metric provides a suite of simulation tests to interrogate the ability to find defects and the sensitivity to variability. The testing rubric is designed to maximize the coverage of the parameter space while minimizing the number of simulations needed. The inspectability metric has been in development in collaboration with industry partners to ensure compatibility with modern simulation tools and aerospace design workflows. In this study, we will demonstrate how the inspectability metric is able to determine the inspectability of multiple types of structures, including aerospace composites and additively manufactured parts. We will then show how the inspectability score can be plugged into existing design optimization tasks, such as structural sizing algorithms or design for manufacturing (DFM) frameworks.

Design for inspection↗

Performance Assessment of a Photonic Radiative Cooling System for Office Buildings

Spectrally selective materials show high technical potential for use as radiative cooling heat exchangers for buildings. Recent work by Stanford University has applied a photonic approach to tailor the optical properties of a coating material. In a prototype test, a radiative cooler based on that photonic material has demonstrated the ability to maintain radiator surfaces at below-ambient temperatures in the presence of intense, direct sunlight. This paper presents the simulation and parametric analysis of photonic radiative cooling system that integrates the use of the photonic radiative cooler and radiant floor cooling via the whole energy simulation program EnergyPlus. The simulation was made for a medium office building with three floors and a total floor area of 5,000 m2. Three key design parameters including the storage tank size, the radiator area, and the number of floors are expected to have a large impact on system performance were investigated in this paper. The results show that the percentage of cooling electricity savings from the photonic radiative cooling system relative to a reference variable-air-volume system has a linear relationship with the radiator area, and a quadratic correlation with both tank size and the number of floors. The findings from this parametric analysis are valuable to understand how component sizing affects system performance.

Wang, Weimin↗

Titan/Centaur T/C-1 post flight evaluation report

The first Titan/Centaur launch vehicle, TC-1, was launched from the Eastern Test Range Complex 41 at 09:48:01.46 hours Eastern Daylight Time on February 11, 1974. The vehicle carried a dynamic mass model of the Viking spacecraft and a SPHINX spacecraft, intended to study high voltage interactions in space. This launch was a Proof Flight of a vehicle con- figuration integrating the Air Force Titan booster and the NASA Centaur upper stage. It also was the first flight of the Centaur Standard Shroud developed for the Titan/Centaur. The countdown for the launch proceeded normally except for an additional 45 minute hold which was required to resolve a question concerning interpretation of booster hydraulic system data. The launch window opened at 09:03:00 hours Eastern Daylight Time. The vehicle was launched o on a flight azimuth of 105°. The Titan boost phase of flight was satisfactory. Solid Motor operation, Stage I and Stage II operation were normal. Venting of the Centaur Standard Shroud during ascent was successful and shroud separation and jettison was accomplished without incident. At the completion of the Titan Stage II burn, the Centaur successfully separated from the Titan. At this time, the Centaur main engines were sequenced through the first planned starting cycle but failed to achieve steady state operation. The vehicle flight control system, not sensing vehicle acceleration, commanded engine shutdown, and recycled, as programmed, through a back-up engine start attempt. The second engine start attempt was also unsuccessful. The flight control system then placed the vehicle in a coast-phase mode and the vehicle continued downrange in free fall. The vehicle was destroyed by Range Safety when the impact point was approximately 2200 nautical miles downrange, 12 minutes, 28.5 seconds after liftoff.

S. V. Szabo, Jr.↗

NASA Space Flight Vehicle Fault Isolation Challenges

The Space Launch System (SLS) is the new NASA heavy lift launch vehicle and is scheduled for its first mission in 2017. The goal of the first mission, which will be uncrewed, is to demonstrate the integrated system performance of the SLS rocket and spacecraft before a crewed flight in 2021. SLS has many of the same logistics challenges as any other large scale program. Common logistics concerns for SLS include integration of discrete programs geographically separated, multiple prime contractors with distinct and different goals, schedule pressures and funding constraints. However, SLS also faces unique challenges. The new program is a confluence of new hardware and heritage, with heritage hardware constituting seventy-five percent of the program. This unique approach to design makes logistics concerns such as testability of the integrated flight vehicle especially problematic. The cost of fully automated diagnostics can be completely justified for a large fleet, but not so for a single flight vehicle. Fault detection is mandatory to assure the vehicle is capable of a safe launch, but fault isolation is another issue. SLS has considered various methods for fault isolation which can provide a reasonable balance between adequacy, timeliness and cost. This paper will address the analyses and decisions the NASA Logistics engineers are making to mitigate risk while providing a reasonable testability solution for fault isolation.

Bramon, Christopher↗

Cyber Informed Engineering (CIE) Curriculum Guide

The Cyber-Informed Engineering (CIE) Curriculum Guide provides a framework, guidance, and resources for incorporating CIE into university-level engineering programs and related educational activities. A key goal of this guide is to help institutions deliver CIE focused education to produce future engineers and technicians who meet the nation’s infrastructure needs. To accommodate a broad range of educational goals and approaches, this guide outlines several practical integration strategies, links to resources that can accelerate CIE adoption, and offers perspectives from partner academic institutions on the various implementation strategies.

42 ENGINEERING↗

Dedicated Laboratory Setup for CO{sub 2} TEA Laser Propulsion Experiments at Rensselaer Polytechnic Institute

Laser propulsion research progress has traditionally been hindered by the scarcity of photon sources with desirable characteristics, as well as integrated specialized flow facilities in a dedicated laboratory environment. For TEA CO{sub 2} lasers, the minimal requirements are time-average powers of >100 W), and pulse energies of >10 J pulses with short duration (e.g., 0.1 to 1 {mu}s); furthermore, for the advanced pulsejet engines of interest here, the laser system must simulate pulse repetition frequencies of 1-10 kilohertz or more, at least for two (carefully sequenced) pulses. A well-equipped laser propulsion laboratory should have an arsenal of sensor and diagnostics tools (such as load cells, thrust stands, moment balances, pressure and heat transfer gages), Tesla-level electromagnet and permanent magnets, flow simulation facilities, and high-speed visualization systems, in addition to other related equipment, such as optics and gas supply systems. In this paper we introduce a cutting-edge Laser Propulsion Laboratory created at Rensselaer Polytechnic Institute, one of the very few in the world to be uniquely set up for beamed energy propulsion (BEP) experiments. The present BEP research program is described, along with the envisioned research strategy that will exploit current and expanded facilities in the near future.

47 OTHER INSTRUMENTATION↗

Rocketdyne - Lunar Ascent Engine

The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I).

Harmon, Tim↗

Constraints and Opportunities in GCM Model Development

Over the past 30 years climate models have evolved from relatively simple representations of a few atmospheric processes to complex multi-disciplinary system models which incorporate physics from bottom of the ocean to the mesopause and are used for seasonal to multi-million year timescales. Computer infrastructure over that period has gone from punchcard mainframes to modern parallel clusters. Constraints of working within an ever evolving research code mean that most software changes must be incremental so as not to disrupt scientific throughput. Unfortunately, programming methodologies have generally not kept pace with these challenges, and existing implementations now present a heavy and growing burden on further model development as well as limiting flexibility and reliability. Opportunely, advances in software engineering from other disciplines (e.g. the commercial software industry) as well as new generations of powerful development tools can be incorporated by the model developers to incrementally and systematically improve underlying implementations and reverse the long term trend of increasing development overhead. However, these methodologies cannot be applied blindly, but rather must be carefully tailored to the unique characteristics of scientific software development. We will discuss the need for close integration of software engineers and climate scientists to find the optimal processes for climate modeling.

Schmidt, Gavin↗

NASA’s Space Launch System: Progress Toward Launch

The Space Launch System (SLS), NASA’s cornerstone launch capability for a new generation of deep space exploration, has begun assembly at Kennedy Space Center (KSC) in preparation for launch in 2021. SLS will provide an unparalleled launch capability for human and robotic deep space exploration missions. Its proven propulsion system, upgrade path to more powerful vehicles, and high-volume payload fairings make it the foundation for ambitious and demanding as part of the Artemis program. Artemis is NASA’s 21st-century plan to put boots on the Moon and to perform sustainable, long-term science in deep space, with eyes toward sending explorers to Mars. The initial SLS vehicle to fly, Block 1 in the crew configuration – with the new Orion spacecraft – is scheduled to lift off from revitalized launch facilities at KSC in 2021 for an uncrewed test flight known as Artemis I. Manufacturing is complete on the vehicle and all elements have been delivered to the Exploration Ground Systems (EGS) Program, except the core stage. The program’s all-new development, the core stage is currently in the midst of a “Green Run” test campaign at Stennis Space Center (SSC). Eight progressively more challenging tests in the Green Run series will culminate in a hot-fire of four flight-proven liquid hydrogen/liquid oxygen (LH2/LOX) RS25 engines. Following the Green Run hotfiring, the core stage will ship to KSC. Already at KSC, aft sections of the fivesegment solid rocket boosters are being assembled. Previously delivered elements, including the upper stage, are undergoing final checkouts in preparation for stacking. An exciting 2021 will include such milestones as stacking SLS and Orion in KSC’s Vehicle Assembly Building (VAB), modal testing, roll out to Launch Pad 39B, Wet Dress Rehearsal (WDR), and launch. Teams across the country are preparing for launch by finalizing procedures, defining launch constraints and flight rules, training console operators, performing simulations, and more. With the SLS Block 1 vehicle for Artemis I nearing integration and launch, the second Block 1 vehicle in the crew configuration, which will carry astronauts on an Artemis II hybrid lunar flyby mission, has several elements manufactured. In fact, the solid rocket motor segments and RS-25 engines are complete. Those program elements are processing hardware for the third flight and working toward manufacturing the second SLS variant to fly, Block 1B, which will onramp a powerful new upper stage, the Exploration Upper Stage (EUS).

John Honeycutt↗

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

M Kaetzer↗

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

Mary Susan Kaetzer↗

Launch Pad Coatings for Smart Corrosion Control

Corrosion is the degradation of a material as a result of its interaction with the environment. The environment at the KSC launch pads has been documented by ASM International (formerly American Society for Metals) as the most corrosive in the US. The 70 tons of highly corrosive hydrochloric acid that are generated by the solid rocket boosters during a launch exacerbate the corrosiveness of the environment at the pads. Numerous failures at the pads are caused by the pitting of stainless steels, rebar corrosion, and the degradation of concrete. Corrosion control of launch pad structures relies on the use of coatings selected from the qualified products list (QPL) of the NASA Standard 5008A for Protective Coating of Carbon Steel, Stainless Steel, and Aluminum on Launch Structures, Facilities, and Ground Support Equipment. This standard was developed to establish uniform engineering practices and methods and to ensure the inclusion of essential criteria in the coating of ground support equipment (GSE) and facilities used by or for NASA. This standard is applicable to GSE and facilities that support space vehicle or payload programs or projects and to critical facilities at all NASA locations worldwide. Environmental regulation changes have dramatically reduced the production, handling, use, and availability of conventional protective coatings for application to KSC launch structures and ground support equipment. Current attrition rate of qualified KSC coatings will drastically limit the number of commercial off the shelf (COTS) products available for the Constellation Program (CxP) ground operations (GO). CxP GO identified corrosion detection and control technologies as a critical, initial capability technology need for ground processing of Ares I and Ares V to meet Constellation Architecture Requirements Document (CARD) CxP 70000 operability requirements for reduced ground processing complexity, streamlined integrated testing, and operations phase affordability. Researchers at NASA's Corrosion Technology Laboratory at KSC are developing a smart, environmentally friendly coating system for early corrosion detection, inhibition, and self healing of mechanical damage without external intervention. This smart coating will detect and respond actively to corrosion and mechanical damage such as abrasion and scratches, in a functional and predictable manner, and will be capable of adapting its properties dynamically. This coating is being developed using corrosion sensitive microcapsules that deliver the contents of their core (corrosion inhibiting compounds, corrosion indicators, and self healing agents) on demand when corrosion or mechanical damage to the coating occurs.

Calle, Luz M.↗

NASA Space Rocket Logistics Challenges

The Space Launch System (SLS) is the new NASA heavy lift launch vehicle and is scheduled for its first mission in 2017. The goal of the first mission, which will be uncrewed, is to demonstrate the integrated system performance of the SLS rocket and spacecraft before a crewed flight in 2021. SLS has many of the same logistics challenges as any other large scale program. Common logistics concerns for SLS include integration of discreet programs geographically separated, multiple prime contractors with distinct and different goals, schedule pressures and funding constraints. However, SLS also faces unique challenges. The new program is a confluence of new hardware and heritage, with heritage hardware constituting seventy-five percent of the program. This unique approach to design makes logistics concerns such as commonality especially problematic. Additionally, a very low manifest rate of one flight every four years makes logistics comparatively expensive. That, along with the SLS architecture being developed using a block upgrade evolutionary approach, exacerbates long-range planning for supportability considerations. These common and unique logistics challenges must be clearly identified and tackled to allow SLS to have a successful program. This paper will address the common and unique challenges facing the SLS programs, along with the analysis and decisions the NASA Logistics engineers are making to mitigate the threats posed by each.

Neeley, James R.↗

Automated Reconstruction of Control Logic for Programmable Logic Controller Forensics

This paper presents Similo, an automated scalable framework for control logic forensics in industrial control systems. Similo is designed to investigate denial of engineering operations (DEO) attacks, recently demonstrated to hide malicious control logic in a programmable logic controller (PLC) at field sites from an engineering software (at control center). The network traffic (if captured) contains substantial evidence to investigate DEO attacks including manipulation of control logic. Laddis, a state-of-the-art forensic approach for DEO attacks, is a binary-logic decompiler for the Allen-Bradley’s RSLogix engineering software and MicroLogix 1400 PLC. It is developed with extensive manual reverse engineering effort of the underlying proprietary network protocol and the binary control logic. Unfortunately, Laddis is not scalable and requires similar efforts to extend on other engineering software/PLCs. The proposed solution, Similo, is based on the observation that engineering software of different vendors are equipped with decompilers. Similo is a virtual-PLC framework that integrates the decompilers with their respective (previously-captured) ICS network traffic of control logic. It recovers the binary logic into a high-level source code (of the programming languages defined by IEC 61131-3 standard) automatically. Similo can work with both proprietary/open protocols without requiring protocol specifications and the binary formats of control logic. Thus, it is scalable to different ICS vendors. We evaluate Similo on three PLCs of two ICS vendors, i.e. MicroLogix 1400, MicroLogix 1100, and Modicon M221. These PLCs support proprietary protocols and the control logics written in two programming languages: Ladder Logic and Instruction List. The evaluation results show that Similo can accurately reconstruct a control logic from an ICS network traffic and can be used to investigate the DEO attacks effectively.

Ali qasim, Syed↗