Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “custom”

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,207 records · Page 67
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Best Buy: Planning for Disaster

When a 1981 tornado in Minnesota revolutionized the retail approach of Sound of Music, which later changed its name to the now very familiar Best Buy, those who founded the company never imagined that a series of hurricanes twenty years later would also help give it a cutting-edge lead in customer service and disaster planning. That original "Tornado Sale'' introduced low prices in a "no-frills" environment that gave the company higher sales than the industry average and paved the way to a new business model. But before Best Buy could find the silver lining of these new storm clouds., it needed to survive them by planning for the destructive weather that plagued Florida during the summer of 2004. Having seen the power of listening to its employees and customers, Best Buy now seeks to capture their thoughts and feedback about other elements of the business.

Sachs, Adam↗
NASA NTRS2006

Initial On-Orbit Spatial Resolution Characterization of OrbView-3 Panchromatic Images

Characterization was conducted under the Memorandum of Understanding among Orbital Sciences Corp., ORBIMAGE, Inc., and NASA Applied Sciences Directorate. Acquired five OrbView-3 panchromatic images of the permanent Stennis Space Center edge targets painted on a concrete surface. Each image is available at two processing levels: Georaw and Basic. Georaw is an intermediate image in which individual pixels are aligned by a nominal shift in the along-scan direction to adjust for the staggered layout of the panchromatic detectors along the focal plane array. Georaw images are engineering data and are not delivered to customers. The Basic product includes a cubic interpolation to align the pixels better along the focal plane and to correct for sensor artifacts, such as smile and attitude smoothing. This product retains satellite geometry - no rectification is performed. Processing of the characterized images did not include image sharpening, which is applied by default to OrbView-3 image products delivered by ORBIMAGE to customers. Edge responses were extracted from images of tilted edges in two directions: along-scan and cross-scan. Each edge response was approximated with a superposition of three sigmoidal functions through a nonlinear least-squares curve-fitting. Line Spread Functions (LSF) were derived by differentiation of the analytical approximation. Modulation Transfer Functions (MTF) were obtained after applying the discrete Fourier transform to the LSF.

Blonski, Slawomir↗
NASA NTRS2008

National Aeronautics and Space Administration's (NASA) Third-Generation Tracking and Data Relay Satellites (TDRS)

NASA has contracted with Boeing to provide two third-generation Tracking and Data Relay Satellites (TDRS) designated TDRS K and L, with an option to provide two additional satellites designated TDRS M and N. These TDRS will be used to continue and enhance the user support services of the existing first- and second-generation TDRS spacecraft. The existing TDRS, in conjunction with the TDRS Ground Terminals at the White Sands NM Complex (WSC) and Guam, constitute the Tracking and Data Relay Satellite System (TDRSS). The TDRSS, with other supporting elements, is referred to as the Space Network (SN). The launch of the TDRS K is projected for 2012 with TDRS L planned to follow in 2013. The contract also provides for the modifications to the TDRS Ground Terminals at the WSC required for operation of the new TDRS. This paper provides an overview of the customer services provided by the existing and new TDRS. In addition, planned future customer services such as Bandwidth Efficient Modulation (BEM) and new coding schemes are briefly discussed.

Berndt, Allen K.↗
NASA NTRS2008

Proposed Facility Modifications to Support Propulsion Systems Testing Under Simulated Space Conditions at Plum Brook Station's Spacecraft Propulsion Research Facility (B-2)

Preparing NASA's Plum Brook Station's Spacecraft Propulsion Research Facility (B-2) to support NASA's new generation of launch vehicles has raised many challenges for B-2's support staff. The facility provides a unique capability to test chemical propulsion systems/vehicles while simulating space thermal and vacuum environments. Designed and constructed in the early 1960s to support upper stage cryogenic engine/vehicle system development, the Plum Brook Station B-2 facility will require modifications to support the larger, more powerful, and more advanced engine systems for the next generation of vehicles leaving earth's orbit. Engine design improvements over the years have included large area expansion ratio nozzles, greater combustion chamber pressures, and advanced materials. Consequently, it has become necessary to determine what facility changes are required and how the facility can be adapted to support varying customers and their specific test needs. Exhaust system performance, including understanding the present facility capabilities, is the primary focus of this work. A variety of approaches and analytical tools are being employed to gain this understanding. This presentation discusses some of the challenges in applying these tools to this project and expected facility configuration to support the varying customer needs.

Edwards, Daryl A.↗
NASA NTRS2008

Learning About Ares I from Monte Carlo Simulation

This paper addresses Monte Carlo simulation analyses that are being conducted to understand the behavior of the Ares I launch vehicle, and to assist with its design. After describing the simulation and modeling of Ares I, the paper addresses the process used to determine what simulations are necessary, and the parameters that are varied in order to understand how the Ares I vehicle will behave in flight. Outputs of these simulations furnish a significant group of design customers with data needed for the development of Ares I and of the Orion spacecraft that will ride atop Ares I. After listing the customers, examples of many of the outputs are described. Products discussed in this paper include those that support structural loads analysis, aerothermal analysis, flight control design, failure/abort analysis, determination of flight performance reserve, examination of orbit insertion accuracy, determination of the Upper Stage impact footprint, analysis of stage separation, analysis of launch probability, analysis of first stage recovery, thrust vector control and reaction control system design, liftoff drift analysis, communications analysis, umbilical release, acoustics, and design of jettison systems.

Hanson, John M.↗
NASA NTRS2008

Precision Cleaning - Path to Premier

ITT Space Systems Division s new Precision Cleaning facility provides critical cleaning and packaging of aerospace flight hardware and optical payloads to meet customer performance requirements. The Precision Cleaning Path to Premier Project was a 2007 capital project and is a key element in the approved Premier Resource Management - Integrated Supply Chain Footprint Optimization Project. Formerly precision cleaning was located offsite in a leased building. A new facility equipped with modern precision cleaning equipment including advanced process analytical technology and improved capabilities was designed and built after outsourcing solutions were investigated and found lacking in ability to meet quality specifications and schedule needs. SSD cleans parts that can range in size from a single threaded fastener all the way up to large composite structures. Materials that can be processed include optics, composites, metals and various high performance coatings. We are required to provide verification to our customers that we have met their particulate and molecular cleanliness requirements and we have that analytical capability in this new facility. The new facility footprint is approximately half the size of the former leased operation and provides double the amount of throughput. Process improvements and new cleaning equipment are projected to increase 1st pass yield from 78% to 98% avoiding $300K+/yr in rework costs. Cost avoidance of $350K/yr will result from elimination of rent, IT services, transportation, and decreased utility costs. Savings due to reduced staff expected to net $4-500K/yr.

Mackler, Scott E.↗
NASA NTRS2009

DSN Beowulf Cluster-Based VLBI Correlator

The NASA Deep Space Network (DSN) requires a broadband VLBI (very long baseline interferometry) correlator to process data routinely taken as part of the VLBI source Catalogue Maintenance and Enhancement task (CAT M&E) and the Time and Earth Motion Precision Observations task (TEMPO). The data provided by these measurements are a crucial ingredient in the formation of precision deep-space navigation models. In addition, a VLBI correlator is needed to provide support for other VLBI related activities for both internal and external customers. The JPL VLBI Correlator (JVC) was designed, developed, and delivered to the DSN as a successor to the legacy Block II Correlator. The JVC is a full-capability VLBI correlator that uses software processes running on multiple computers to cross-correlate two-antenna broadband noise data. Components of this new system (see Figure 1) consist of Linux PCs integrated into a Beowulf Cluster, an existing Mark5 data storage system, a RAID array, an existing software correlator package (SoftC) originally developed for Delta DOR Navigation processing, and various custom- developed software processes and scripts. Parallel processing on the JVC is achieved by assigning slave nodes of the Beowulf cluster to process separate scans in parallel until all scans have been processed. Due to the single stream sequential playback of the Mark5 data, some ramp-up time is required before all nodes can have access to required scan data. Core functions of each processing step are accomplished using optimized C programs. The coordination and execution of these programs across the cluster is accomplished using Pearl scripts, PostgreSQL commands, and a handful of miscellaneous system utilities. Mark5 data modules are loaded on Mark5 Data systems playback units, one per station. Data processing is started when the operator scans the Mark5 systems and runs a script that reads various configuration files and then creates an experiment-dependent status database used to delegate parallel tasks between nodes and storage areas (see Figure 2). This script forks into three processes: extract, translate, and correlate. Each of these processes iterates on available scan data and updates the status database as the work for each scan is completed. The extract process coordinates and monitors the transfer of data from each of the Mark5s to the Beowulf RAID storage systems. The translate process monitors and executes the data conversion processes on available scan files, and writes the translated files to the slave nodes. The correlate process monitors the execution of SoftC correlation processes on the slave nodes for scans that have completed translation. A comparison of the JVC and the legacy Block II correlator outputs reveals they are well within a formal error, and that the data are comparable with respect to their use in flight navigation. The processing speed of the JVC is improved over the Block II correlator by a factor of 4, largely due to the elimination of the reel-to-reel tape drives used in the Block II correlator.

Rogstad, Stephen P.↗
NASA NTRS2009

Southern Impact Testing Alliance (SITA)

Efforts to form this Alliance began in 2008 to showcase the impact testing capabilities within the southern United States. Impact testing customers can utilize SITA partner capabilities to provide supporting data during all program phases-materials/component/ flight hardware design, development, and qualification. This approach would allow programs to reduce risk by providing low cost testing during early development to flush out possible problems before moving on to larger scale1 higher cost testing. Various SITA partners would participate in impact testing depending on program phase-materials characterization, component/subsystem characterization, full-scale system testing for qualification. SITA partners would collaborate with the customer to develop an integrated test approach during early program phases. Modeling and analysis validation can start with small-scale testing to ensure a level of confidence for the next step large or full-scale conclusive test shots. Impact Testing Facility (ITF) was established and began its research in spacecraft debris shielding in the early 1960's and played a malor role in the International Space Station debris shield development. As a result of return to flight testing after the loss of STS-107 (Columbia) MSFC ITF realized the need to expand their capabilities beyond meteoroid and space debris impact testing. MSFC partnered with the Department of Defense and academic institutions as collaborative efforts to gain and share knowledge that would benefit the Space Agency as well as the DoD. MSFC ITF current capabilities include: Hypervelocity impact testing, ballistic impact testing, and environmental impact testing.

Hubbs, Whitney↗
NASA NTRS2009

CCSDS Spacecraft Monitor and Control Mission Operations Interoperability Prototype

We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the capabilities of existing legacy systems. Various custom applications and middleware solutions will be combined into one system providing the illusion of a set of homogenous services. This paper will document our journey as we implement the interoperability prototype. The team consists of software engineers with experience on the current command, telemetry and messaging systems that support the International Space Station (ISS) and Space Shuttle programs. Emphasis will be on the objectives, results and potential cost saving benefits.

Lucord, Steve↗
NASA NTRS2008

Increasing the Cost-efficiency of the DSN

JPL has operated the Deep Space Network (DSN) on behalf of NASA since the 1960's. Over the last two decades, the DSN budget has generally declined in real-year dollars while the aging assets required more attention, and the missions became more complex. As a result, the budget has been increasingly consumed by Operations and Maintenance (O and M), significantly reducing the funding wedge available for technology investment and for enhancing the DSN capability and capacity. Responding to this budget squeeze, the DSN launched an effort to improve the cost-efficiency of the O and M. In this paper we: Analyze the components of O&M. We note for example that, for the DSN, less than 20% of the staff engage in the traditional human-in-front-a-console role, so any effort to increase the cost efficiency must go beyond reducing the number of "Real-time operators." Explain the underlying organizational and cultural structures. Any cost-efficiency activities changes either accept, or carefully modify these structures. For example, the DSN O&M is based on the concept that there are three nearly identical antenna complexes separated by approximately 1200 in latitude and that each antenna complex is operated by a different contractor (driven by international agreements). Explore planned changes in the customer interface, e.g. web-based automated scheduling, and the processes required for a transition. Changes have to be evaluated in the larger end-to-end context, e.g. do the changes provide a net cost-efficiency for the DSN and the missions, or do they merely shift cost from the DSN to the missions. Consider possible significant changes in real-time pass management, e.g. full-remoting of operations, and lights-dim operations, while maintaining (or improving) the performance metrics of the DSN. Investigate how procedural and administrative changes could increase cost-efficiency, in conjunction with changes in the customer interfaces and real-time pass management. Examples would be handling of inter-governmental agreements, improved sharing of resources with other agencies, and better use of commercial (rather than government) resources

Deep Space Network (DSN)↗
NASA NTRS2010

AutoGen Version 5.0

Version 5.0 of the AutoGen software has been released. Previous versions, variously denoted Autogen and autogen, were reported in two articles: Automated Sequence Generation Process and Software (NPO-30746), Software Tech Briefs (Special Supplement to NASA Tech Briefs), September 2007, page 30, and Autogen Version 2.0 (NPO- 41501), NASA Tech Briefs, Vol. 31, No. 10 (October 2007), page 58. To recapitulate: AutoGen (now signifying automatic sequence generation ) automates the generation of sequences of commands in a standard format for uplink to spacecraft. AutoGen requires fewer workers than are needed for older manual sequence-generation processes, and greatly reduces sequence-generation times. The sequences are embodied in spacecraft activity sequence files (SASFs). AutoGen automates generation of SASFs by use of another previously reported program called APGEN. AutoGen encodes knowledge of different mission phases and of how the resultant commands must differ among the phases. AutoGen also provides means for customizing sequences through use of configuration files. The approach followed in developing AutoGen has involved encoding the behaviors of a system into a model and encoding algorithms for context-sensitive customizations of the modeled behaviors. This version of AutoGen addressed the MRO (Mars Reconnaissance Orbiter) primary science phase (PSP) mission phase. On previous Mars missions this phase has more commonly been referred to as mapping phase. This version addressed the unique aspects of sequencing orbital operations and specifically the mission specific adaptation of orbital operations for MRO. This version also includes capabilities for MRO s role in Mars relay support for UHF relay communications with the MER rovers and the Phoenix lander.

Gladden, Roy E.↗
NASA NTRS2007

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗
NASA NTRS2007

Recombinant Collagenlike Proteins

A group of collagenlike recombinant proteins containing high densities of biologically active sites has been invented. The method used to express these proteins is similar to a method of expressing recombinant procollagens and collagens described in U. S. Patent 5,593,859, "Synthesis of human procollagens and collagens in recombinant DNA systems." Customized collagenous proteins are needed for biomedical applications. In particular, fibrillar collagens are attractive for production of matrices needed for tissue engineering and drug delivery. Prior to this invention, there was no way of producing customized collagenous proteins for these and other applications. Heretofore, collagenous proteins have been produced by use of such biological systems as yeasts, bacteria, and transgenic animals and plants. These products are normal collagens that can also be extracted from such sources as tendons, bones, and hides. These products cannot be made to consist only of biologically active, specific amino acid sequences that may be needed for specific applications. Prior to this invention, it had been established that fibrillar collagens consist of domains that are responsible for such processes as interaction with cells, binding of growth factors, and interaction with a number of structural proteins present in the extracellular matrix. A normal collagen consists of a sequence of domains that can be represented by a corresponding sequence of labels, e.g., D1D2D3D4. A collagenlike protein of the present invention contains regions of collagen II that contain multiples of a single domain (e.g., D1D1D1D1 or D4D4D4D4) chosen for its specific biological activity. By virtue of the multiplicity of the chosen domain, the density of sites having that specific biological activity is greater than it is in a normal collagen. A collagenlike protein according to this invention can thus be made to have properties that are necessary for tissue engineering.

Fertala, Andzej↗
NASA NTRS2006

Correction for Thermal EMFs in Thermocouple Feedthroughs

A straightforward measurement technique provides for correction of thermal-electromotive-force (thermal-EMF) errors introduced by temperature gradients along the pins of non-thermocouple-alloy hermetic feedthrough connectors for thermocouple extension wires that must pass through bulkheads. This technique is an alternative to the traditional technique in which the thermal-EMF errors are eliminated by use of custom-made multipin hermetic feedthrough connectors that contain pins made of the same alloys as those of the thermocouple extension wires. One disadvantage of the traditional technique is that it is expensive and time-consuming to fabricate multipin custom thermocouple connectors. In addition, the thermocouple-alloy pins in these connectors tend to corrode easily and/or tend to be less rugged compared to the non-thermocouple-alloy pins of ordinary connectors. As the number of thermocouples (and thus pins) is increased in a given setup, the magnitude of these disadvantages increases accordingly. The present technique is implemented by means of a little additional hardware and software, the cost of which is more than offset by the savings incurred through the use of ordinary instead of thermocouple connectors. The figure schematically depicts a typical measurement setup to which the technique is applied. The additional hardware includes an isothermal block (made of copper) instrumented with a reference thermocouple and a compensation thermocouple. The reference thermocouple is connected to an external data-acquisition system (DAS) through a two-pin thermocouple-alloy hermetic feedthrough connector, but this is the only such connector in the apparatus. The compensation thermocouple is connected to the DAS through two pins of the same ordinary multipin connector that connects the measurement thermocouples to the DAS.

Ziemke, Robert A.↗
NASA NTRS2010

Real-Time Visualization of Spacecraft Telemetry for the GLAST and LRO Missions

GlastCam and LROCam are closely-related tools developed at NASA Goddard Space Flight Center for real-time visualization of spacecraft telemetry, developed for the Gamma-Ray Large Area Space Telescope (GLAST) and Lunar Reconnaissance Orbiter (LRO) missions, respectively. Derived from a common simulation tool, they use related but different architectures to ingest real-time spacecraft telemetry and ground predicted ephemerides, and to compute and display features of special interest to each mission in its operational environment. We describe the architectures of GlastCam and LROCam, the customizations required to fit into the mission operations environment, and the features that were found to be especially useful in early operations for their respective missions. Both tools have a primary window depicting a three-dimensional Cam view of the spacecraft that may be freely manipulated by the user. The scene is augmented with fields of view, pointing constraints, and other features which enhance situational awareness. Each tool also has another "Map" window showing the spacecraft's groundtrack projected onto a map of the Earth or Moon, along with useful features such as the Sun, eclipse regions, and TDRS satellite locations. Additional windows support specialized checkout tasks. One such window shows the star tracker fields of view, with tracking window locations and the mission star catalog. This view was instrumental for GLAST in quickly resolving a star tracker mounting polarity issue; visualization made the 180-deg mismatch immediately obvious. Full access to GlastCam's source code also made possible a rapid coarse star tracker mounting calibration with some on the fly code adjustments; adding a fine grid to measure alignment offsets, and introducing a calibration quaternion which could be adjusted within GlastCam without perturbing the flight parameters. This calibration, from concept to completion, took less than half an hour. Both GlastCam and LROCam were developed in the C language, with non-proprietary support libraries, for ease of customization and portability. This no-blackboxes aspect enables engineers to adapt quickly to unforeseen circumstances in the intense operations environment. GlastCam and LROCam were installed on multiple workstations in the operations support rooms, allowing independent use by multiple subsystems, systems engineers and managers, with negligible draw on telemetry system resources.

Stoneking, Eric T.↗
NASA NTRS2010

Design and Demonstration of a Miniature Lidar System for Rover Applications

A basic small and portable lidar system for rover applications has been designed. It uses a 20 Hz Nd:YAG pulsed laser, a 4-inch diameter telescope receiver, a custom-built power distribution unit (PDU), and a custom-built 532 nm photomultiplier tube (PMT) to measure the lidar signal. The receiving optics have been designed, but not constructed yet. LabVIEW and MATLAB programs have also been written to control the system, acquire data, and analyze data. The proposed system design, along with some measurements, is described. Future work to be completed is also discussed.

Robinson, Benjamin↗
NASA NTRS2010

Facilitating NASA's Use of GEIA-STD-0005-1, Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-Free Solder

GEIA-STD-0005-1 defines the objectives of, and requirements for, documenting processes that assure customers and regulatory agencies that AHP electronic systems containing lead-free solder, piece parts, and boards will satisfy the applicable requirements for performance, reliability, airworthiness, safety, and certify-ability throughout the specified life of performance. It communicates requirements for a Lead-Free Control Plan (LFCP) to assist suppliers in the development of their own Plans. The Plan documents the Plan Owner's (supplier's) processes, that assure their customer, and all other stakeholders that the Plan owner's products will continue to meet their requirements. The presentation reviews quality assurance requirements traceability and LFCP template instructions.

Plante, Jeannete↗
NASA NTRS2009

Modeling Guidelines for Code Generation in the Railway Signaling Context

Modeling guidelines constitute one of the fundamental cornerstones for Model Based Development. Their relevance is essential when dealing with code generation in the safety-critical domain. This article presents the experience of a railway signaling systems manufacturer on this issue. Introduction of Model-Based Development (MBD) and code generation in the industrial safety-critical sector created a crucial paradigm shift in the development process of dependable systems. While traditional software development focuses on the code, with MBD practices the focus shifts to model abstractions. The change has fundamental implications for safety-critical systems, which still need to guarantee a high degree of confidence also at code level. Usage of the Simulink/Stateflow platform for modeling, which is a de facto standard in control software development, does not ensure by itself production of high-quality dependable code. This issue has been addressed by companies through the definition of modeling rules imposing restrictions on the usage of design tools components, in order to enable production of qualified code. The MAAB Control Algorithm Modeling Guidelines (MathWorks Automotive Advisory Board)[3] is a well established set of publicly available rules for modeling with Simulink/Stateflow. This set of recommendations has been developed by a group of OEMs and suppliers of the automotive sector with the objective of enforcing and easing the usage of the MathWorks tools within the automotive industry. The guidelines have been published in 2001 and afterwords revisited in 2007 in order to integrate some additional rules developed by the Japanese division of MAAB [5]. The scope of the current edition of the guidelines ranges from model maintainability and readability to code generation issues. The rules are conceived as a reference baseline and therefore they need to be tailored to comply with the characteristics of each industrial context. Customization of these recommendations has been performed for the automotive control systems domain in order to enforce code generation [7]. The MAAB guidelines have been found profitable also in the aerospace/avionics sector [1] and they have been adopted by the MathWorks Aerospace Leadership Council (MALC). General Electric Transportation Systems (GETS) is a well known railway signaling systems manufacturer leading in Automatic Train Protection (ATP) systems technology. Inside an effort of adopting formal methods within its own development process, GETS decided to introduce system modeling by means of the MathWorks tools [2], and in 2008 chose to move to code generation. This article reports the experience performed by GETS in developing its own modeling standard through customizing the MAAB rules for the railway signaling domain and shows the result of this experience with a successful product development story.

Ferrari, Alessio↗