CAD Forum - Database of tips, tricks and utilities for AutoCAD, Inventor and other Autodesk products [www.cadforum.cz]
CZ | EN | DE
Login or
registration
  Visitors: 9111
RSS channel - CAD tips RSS tips
RSS discussions

Discussion Discussion forum

 

HelpCAD discussion

 
CAD Forum - Homepage CAD discussion forum - ask any CAD-related questions here, share your CAD knowledge on AutoCAD, Inventor, Revit and other Autodesk software with your peers from all over the world. To start a new topic, choose an appropriate forum.

Please abide by the rules of this forum.

How to post questions: register or login, go to the specific forum and click the NEW TOPIC button.
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Topic ClosedAutodesk Labs and NASA Technology Readiness Levels

 Post Reply Post Reply
Author
AliveInTheLab View Drop Down
RSS robots
RSS robots


Joined: 20.Nov.2009
Status: Offline
Points: 425
Direct Link To This Post Topic: Autodesk Labs and NASA Technology Readiness Levels
    Posted: 18.Aug.2016 at 04:00
Have you ever noticed that projects on Autodesk Labs are called technology previews instead of alphas or betas? There's a reason for that. When someone is evaluating an alpha, their assumption is that the next step is beta. When someone is evaluating a beta, their expectation is that the next step is a production release. With Autodesk Labs, that is not the case. The technologies being evaluated are so early in their development that the real possibility exists that the technology will not take the next step. In fact, this happens 38% of the time. Whether a technology graduates to the next steps or takes an early retirement depends heavily on the feedback we get during the preview. Your informed opinion counts! The National Aeronautics and Space Administration (NASA) works with a lot of external vendors to obtain technology. As such, NASA has defined some technical readiness levels that I have reproduced below. TRL 1 Basic principles observed and reported: Transition from scientific research to applied research. Essential characteristics and behaviors of systems and architectures. Descriptive tools are mathematical formulations or algorithms. TRL 2 Technology concept and/or application formulated: Applied research. Theory and scientific principles are focused on specific application area to define the concept. Characteristics of the application are described. Analytical tools are developed for simulation or analysis of the application. TRL 3 Analytical and experimental critical function and/or characteristic proof-of-concept: Proof of concept validation. Active Research and Development (R&D) is initiated with analytical and laboratory studies. Demonstration of technical feasibility using breadboard or brass board implementations that are exercised with representative data. TRL 4 Component/subsystem validation in the laboratory environment: Standalone prototyping implementation and test. Integration of technology elements. Experiments with full-scale problems or data sets. TRL 5 System/subsystem/component validation in the relevant environment: Thorough testing of prototyping in a representative environment. Basic technology elements integrated with reasonably realistic supporting elements. Prototyping implementations conform to target environment and interfaces. TRL 6 System/subsystem model or prototyping demonstration in a relevant end-to-end environment (ground or space): Prototyping implementations on full-scale realistic problems. Partially integrated with existing systems. Limited documentation available. Engineering feasibility fully demonstrated in the actual system application. TRL 7 System prototyping demonstration in an operational environment (ground or space): System prototyping demonstration in an operational environment. The system is at or near the scale of the operational system, with most functions available for demonstration and test. Well integrated with collateral and ancillary systems. Limited documentation available. TRL 8 Actual system completed and "mission qualified" through test and demonstration in an operational environment (ground or space): End of system development. Fully integrated with operational hardware and software systems. Most user documentation, training documentation, and maintenance documentation completed. All functionality tested in simulated and operational scenarios. Verification and Validation (V&V) completed. TRL 9 Actual system "mission proven" through successful mission operations (ground or space): Fully integrated with operational hardware/software systems. Actual system has been thoroughly demonstrated and tested in its operational environment. All documentation completed. Successful operational experience. Sustaining engineering support in place. This list struck me because I wondered where technology previews fit in. How should they be classified? IMHO it's either readiness level 5, 6, or 7 and depends on the technology preview itself. Here is how I see it: TRL 5 Export LMC for AutoCAD Project Play Project PRAXIS These technologies really are in their infancy and feedback can help round them out. TRL 6 2D to 3D Tool for Inventor Dynamo Plug-in for Robot Structural Analysis Project Calrissian for CFD Project Kameleon These technologies have advanced past their initial infancy stage. TRL 7 Project Arro Project Draco Project Monolith Project Scandium for Moldflow Insight React Structures These technologies are on a solid foundation for their continued development. The notion of readiness determination is alive in the lab.

Go to the original post...

It's Alive in ihe Lab - Autodesk Labs blog by Scott Sheppard
Back to Top

Related CAD tips:


 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0,367 seconds.