|
||||
![]() |
||||
PTB >>Designing Electro-Optical Sensors Using Collaborative Systems Engineering Technology
About 25% of space-borne electro-optical (EO) sensor programs in both the civil and National Security Space (NSS) communities have experienced re duced on-orbit reliability, as well as cost and schedule overruns of 100% or more1-3. Many of these EO sensor program overruns can be largely attributed to delays, errors, and inadequate communication that occur at the many handoff points between team members and contractors in the current design process. This leads to the late discovery of technical problems, making them more expensive and time-consuming to fix. The design of EO sensors requires careful attention to the thermal and structural effects that adversely affect optical performance in terms of instrument pointing accuracy and image quality. Teams of domain experts, each focusing on a separate aspect of the sensor, work towards understanding and managing its complex behavior. The current engineering process is typically fragmented into silos of experts, tools and data. Separate models are constructed, one for each of the disciplines (mechanical CAD, thermal, structures, and optics). Analysis proceeds within each discipline silo with relatively infrequent interaction between groups. There is no organized way for individual domains, or the team as a whole, to manage their design and analysis models over the entire project.
Project design reviews are typically conducted using time-consuming "static" reports and PowerPoint summaries. There is no unified view of the engineering models that represent the product's behavior, nor is there easy access to key system performance data. An engineering project team at The Aerospace Corporation comprised of a lead structural, thermal, optical, and mechanical design engineer, directed by Senior Project Engineer Dr. David Thomas, has successfully implemented a new collaborative systems engineering approach on an actual flight hardware program, reducing each design evaluation cycle by over 50%, while providing better insight into the multi-disciplinary behavior of a space-borne sensor4. Using expertise captured in bi-directionally associative design/simulation process templates, integrated structural, thermal, optical analyses were performed in a matter of days vs. weeks/months in the traditional "silo" approach. The Aerospace Corp. has also recently participated in the contractor's final thermal vacuum (TVAC) testing of the flight hardware to correlate and validate the STOP (structural- thermal-optical performance) pro - cess models and results. A significant reduction in the cycle time of the EO sensor design evaluation and validation was achieved while meeting overall sensor design reliability and optical system performance target levels.
The analysis details were captured in a system-level design/simulation template as well as in the individual discipline templates, allowing the team to easily run a large number of STOP analysis design studies while modifying both geometric and non-geometric model parameters, and the thermal environment conditions. After each STOP analysis iteration, key performance metrics were available for immediate visualization in the Project Dashboard and compared against the system analysis performance requirements. The team performed STOP analyses using Comet's Performance Engineering Workspace, combined with their current commercial CAD and CAE tools - Pro/ENGINEER®, Thermal Desktop®, Nastran, Abaqus®, SigFit, CODE V®, Excel® and Matlab®. The workspace provided a single, consistent view of all the data - models, environments, processes and results - allowing the team to create, share and access data easily. The workspace allowed domain experts to work within their own "domain sandboxes" to understand their aspect of the sensor, but also to work together with other domain experts to gain overall system performance in sights. By automatically reusing the expertise captured by the experts in simulation templates, manual data handoff errors were eliminated and the confidence in the accuracy of each analysis iteration was significantly increased. Throughout this project, the team worked independently in their offices, as well as in concurrent sessions held in a common location, always sharing and managing design and simulation data within a single project tree data model located on a secure, shared disk. The keys to success were easy and constant access to system performance metrics, regardless of the tool that generated the data, and team collaboration throughout the entire multi-physics design process. By working within the integrated workspace, each team member quickly and easily saw how their changes affected other aspects by running the template and reviewing the results in the project dashboard. This increased the systems knowledge of the entire team, contributing to a better general understanding of the sensor's physical behavior. STOP Process Template Execution Typical CAD or CAE software templates that capture analysis processes are specified using a particular version of the geometry. These can be reused with only small changes to the geometry. The key technology of the Comet workspace is the Abstract Engineering Model (AEM™), a single integrated data model that captures all the CAD and CAE data at all levels of model fidelity, in a manner that is independent of the underlying tools. The AEM™ allows the STOP template to be reused across widely varying geometry changes, with little or no data re-entry, significantly reducing the rework that is usually required. As the geometry changes, the new CAD models are re-imported and the abstract model automatically reattaches all the engineering data to the new version of the model. As the AEM™ is component-centric and not geometry-centric, analysts can also create analysis processes that perform calculations on models at any desired mixed level of fidelity. The AEM™ spans the traditional chasm between low fidelity modeling (without CAD geometry) and high fidelity modeling; results from low fidelity calculations can be fed to downstream high fidelity calculations and vice versa. The AEM™ also allows users to create and manage multiple representations of each component in the product structure; these representations are required for various types of downstream analyses, different physics calculations at different levels of fidelity. For example, the optics representation of a lens element and the 3-D CAD representation of the same component are managed simultaneously; the former is used to perform optics calculations while the latter is used for creating both the thermal and structural meshes. From the STOP analysis results, it was discovered that, despite high axial thermal gradients and smaller radial thermal gradients across the lenses, the focus shifts due to deformations at each end of the assembly cancelled each other out for the thermal soak cases that were analyzed. This was a highly non-intuitive and unexpected finding that provided insight into the behavior of the sensor. The finding was that the unconventional, active thermal controls in the EO sensor design, using two heaters that had the same power settings applied over significantly different lens mounting surface areas, were actually adequate to ensure good optical performance in the field4. For the TVAC test correlation activity, the STOP process template automatically extracted the thermal results from Thermal Desktop® at test configuration thermocouple locations and plotted these against the actual TVAC test data. The team directly used such test data, stored within an Excel spreadsheet, to validate the high fidelity simulation models. It is important to note that the workspace does not generate the underlying calculations within each physics domain or at the overall system level. That is all still performed by individual solver codes so the accuracy of any simulation iteration is still very much dependent on the underlying modeling and analysis assumptions made by the individual domain experts, just as it is done manually today. The STOP Project Results Our baseline optical design model will be updated to include fabrication, alignment, and gravity induced effects, and more of the visible channel components will be added to the model to allow higher fidelity comparisons of predicted and measured visible channel image quality. We also plan to add an adapter to the Comet environment so that the controls algorithm software may be included in the integrated analysis. This will allow the entire focus control system to be modeled from ground command through final image quality." This article was written by Malcolm Panthaki, Founder and CTO, Comet Solutions, Inc. (Cincinnati, OH). For more information, contact Mr. Panthaki at Malcolm.panthaki@cometsolutions.com, or visit http://info.hotims.com/22928-200. References |
||||