NACRC_TMSA_Template_2015_11_30.docx

DOCX document 283 KB Posted

Attached to
NIMITZ-class Aircraft Carrier Recovery Capability
Solicitation number
N68335-16-RFI-0084
Issued by

About this file

Technology Maturity Self-Assessment

View the file

Other files

File Type Posted
NACRC_RFI_2016_1_13_1.docx DOCX document
NACRC_RFI_Clarifications_2016_1_13.docx DOCX document
NACRC_System_Metrics_template_2016_1_5.xlsx XLSX spreadsheet
NACRC_RFI_2015_12_1.docx DOCX document
NACRC_System_Metrics_template_2015_11_10.xlsx XLSX spreadsheet
NCRC_MIL-STD-881C-based_Electronic_Systems_WBS_Template_2015_10_1.docx DOCX document
NACRC_RFI_NDA_2015_11_24.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

TMA RFI Language

Concept Maturity - In support of this AoA, the Offeror is to provide a fully-populated, self-contained Technology Maturity Self-Assessment (TMSA) of the design concept provided in response to this RFI.

The Government provided Excel-based template (see attached) is a tool which the NAVAIR Independent Technical Review Office (ITRO) will use in support of a Technology Maturity Assessment (TMA) on the submitted design concept. Instructions for populating the TMSA are provided in the spreadsheet at the top, along with Guidance in a separate tab at the bottom.

The TMSA tool is based on a methodical approach to decompose the design concept into various lower levels of indenture to identify those systems/subsystems, components, and devices that may contain immature technologies (i.e. Critical Technology Elements (CTEs)). The Government will subsequently assess each identified candidate CTE a Maturity Category range consisting of green, yellow, and red which is used in lieu of Technology Readiness Level (TRL) assignments based on the risk of achieving TRL 6 by a targeted MS B as depicted in the Table below.

For MDAPs, the regulatory and statutory requirement is for all identified candidate CTEs to have been demonstrated in a relevant environment (TRL 6) by the Milestone B decision. Historically, non-MDAPs have been held to this standard as well.

TMA Maturity Categories Table

GREEN

Strong Chance:

TRL 6 or higher by Targeted MS-B

- Maturation activity can be identified (on-going & funded).

- Maturation roadmap fully supports TRL 6 by MS-B.

- Technology likely TRL 5 or 6 today.

- “System/subsystem demo … in a relevant environment”.

YELLOW

Moderate Chance:

TRL 6 by Targeted MS-B

- Maturation activity planned (funding identified); or with attention, maturation can be accommodated; or maturation exists but some question whether timeline allows sufficient maturation progress.

- Possible risk (level of data available to qualify) whether “System/sub-system demo … in a relevant environment” can be achieved in time (“Component” Vs “System/subsystem”; and/or fidelity of “relevant environment”).

- Technology likely TRL 4 or 5 today.

- Maturation is possible.

RED

Low Chance:

TRL 6 by Targeted MS-B

- No maturation activity currently planned and/or funding identified.

- Maturation activity ongoing or planned but will not allow for a “System/subsystem demo … in a relevant environment”.

- No chance of meeting TRL 6 by MS-B without significant intervention (if possible).

- Technology likely TRL 4 or lower today.

- Maturation is unlikely as it stands today.

image1.emf

Nimitz class recovery AoA TMSA.xlsx TMSA Guidance

TMA GENERAL GUIDANCE

TMA ► A Technology Maturity Assessment (TMA) is a systematic, metrics-based process that assesses the maturity of, & the risk associated with, Critical Technology Elements (CTEs) to be used in systems. It follows the same rigor & discipline of a TRA, but it is conducted on a non-finalized design, i.e. system concepts or concept designs during the MS-A TMRR Phase or Pre-MS-A on the results of an Analysis of Alternatives (AoA).

CTE
Definition► CTE DEFINITION: A technology element (TE) is defined as “critical” if the system being acquired depends on that TE to meet its capability development document (CDD) and capability production document (CPD) requirements and if its application is either new or novel in an area that poses major technological risk during detailed design or demonstration.

► NOT A CTE: This TE is NOT “critical” because the system being acquired does depend on this TE to meet operational rqmts with acceptable development cost and schedule, and with acceptable production and operation costs BUT this TE or its application IS NOT considered either new, novel, or in an area that poses a major risk in completing technology maturation development.

► CTE lists of varying origin exist during the TMA. “Candidate” CTEs can be self-assessed by the program manager (PM), by the Integrated Product Team (IPT), or from the pre-Materiel Solution Analysis (MSA) early evaluations of technology maturity. A final “candidate” CTE list is identified by the TMA Independent Review Panel (IRP) and represents the IRP product for Chief of Naval Research (CNR) concurrence. The term “CTE” is reserved for the final list concurred with by the CNR. The final list is coordinated with the Director, Research & Development (DRD).

Basis of Technology Maturity Assessments Throughout Acquisition ► The TMA process highlights immature technologies usually associated with enabling technologies that may contribute to program level risk areas that require the PM’s attention.

► The disciplined identification of CTEs is important to a program’s success. If a CTE is overlooked & not brought to the requisite maturity level for exploitation at the start of Engineering & Manufacturing Development (EMD), the system performance, program schedule, and overall cost could be jeopardized. On the other hand, if an overly conservative approach is taken and a plethora of technology elements (TEs) are categorized as CTEs, then energy and resources are likely to be diverted from the few technologies that deserve an intense maturation effort. If a disciplined process with due diligence does lead to an inordinate number of CTEs, this process should indicate that the proposed development is reaching too far for its goals.

Pre-Milestone A (MS-A) Milestone A (MS-A) Milestone B (MS-B) Milestone C (MS-C)

Basis of CTE ID Very early assessment of enabling technologies. Early assessment of prototype Concept Designs. Current level of form, fit, function design & CDD rqmts. Planned LRIP article, prior TRAs, & final Post-CDR design.

CTE ID Status Candidate CTEs or CTE Areas. Candidate CTEs. CTEs - actual technologies in a Post-PDR design. CTEs of planned LRIP articles.

Assessment Method Pre-MS-A TMA via TMSA in RFI response. Post-MS-A TD Phase TMA via TMSA in source selection. MS-B TRA via TMSA in source selection. MS-C TRA via TMSA in source selection.

Documentation ADM, AoA Report, Pre-MS-A TMA, & AS. ADM, TD Phase TMA & AS. ADM, MS-B TRA & AS. ADM, MS-C TRA & AS.

Technical Work Breakdown Structure (TWBS) ► The TWBS should decompose the design to the lowest level of indenture necessary to conclusively show that the system/subsystem is or is not a CTE by itself (as an integrated product) and that there is or is not a lower level technology component of the system /subsystem that dictates the system is a candidate CTE .

► The length of the TWBS should be as long as necessary and represent an exhaustive listing of the decomposed existing or conceptual threshold compliant baseline HW and SW design configuration elements (i.e., systems, subsystems, components and devices).

► Do not separate the TWBS into separate HW & SW sections. Instead, embed the SW in its associated system/subsystem items.

ENABLING TECHNOLOGY

NOVEL ► A technology element could be "novel" if it is unfamiliar, an original concept or approach, a nonexisting technology, or an emerging technology in early development that has never been done before, it is not in production or production representative, and it has never been operated in a relevant (lab) environment or flown in an operational (field) environment. The environment where the technology has been used must be relevant to the application of the technology in the system under consideration. For example, a radio known to work in a pristine electromagnetic environment would be new or novel in a more challenging or complex electromagnetic environment.

NEW ► A technology may be considered "new" if it has only existed for a short time, or if it is different from one in the same category that has existed previously. A technology may truely be "new", or it may simply be considered or labeled as "new" because it is an upgrade to, modernization of, or the next evolution of an existing technology. For example, a 20-slice toaster may be identified as "new", but it certainly is not novel, & the technology is just an extension of what is well understood. However, if the 20-slice toaster is now expected to work in an environment it was not designed for, then it may be considered new based on the intended operational environment.

► The environment in which the technology will be utilized is key to determining "new" or "novel". How you define the "relevant (lab) or operational (field) environment" is important.

► Sometimes CTEs are comprised of several tightly coupled elements. Closer examination may reveal that each element is a CTE whose maturity needs to be evaluated independently. For example, a thorough analysis was conducted on a SW intensive system in order to identify CTEs. These included: .Net Framework – Microsoft programming model & integral Windows runtime component for building XLM Web services & applications consisting of the Common Language Runtime (CLR) & a unified set of class libraries; COM Callable Wrappers – A wrapper around a .NET object that is automatically generated by the .NET Framework CLR; & Runtime Callable Wrappers – A wrapper around (proxy for) a COM object that is generated automatically by the .NET Framework Common Language Runtime. The team could have integrated these 3 tightly coupled elements into a single CTE, however, since each is new or novel & critical to the functionality, it would not have been appropriate to combine the 3 elements into one CTE. Instead, they maintained segregation.

NEW APPLICATION
of a Technology► Is this technology being applied to solve a problem or meet an operational performance threshold beyond it's original design intention or demonstrated capability? The application can be mission based or local to the design architecture.

► Is this technology going to be operating at or outside of what would be considered to be the normal performance envelope? If so, do the specs address the anticipated / predicted behavior of the technology under these conditions? Consider what is unique or different about the proposed operations environment? Is the physics understood?

► The performance being demanded from the technology exceeds previous requirements.

► If more dollars, human resources, or schedule could be applied all within the Program of Record constraints to solve a technology limitation it is most likely not a CTE.

ENABLING TECHNOLOGY
Critical TE (CTE)Describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on that TE to meet its capability development document (CDD) and capability production document (CPD) requirements, AND (2) this TE or its application is either new or novel in an area that poses major technological risk during detailed design or demonstration.

CHANGE DESCRIPTION

COTS

or GOTS ► If a technology is COTS (commercial off-the-shelf) or GOTS (gov't off-the-shelf) it may or may not be a CTE.

► A COTS product is one that is used unmodified "as-is" off-the-shelf & if so, then it should have a production part # that is required to substantiate maturity. COTS products are designed to be easily installed and to interoperate with existing system components. For example, almost all SW bought by the average computer user fits into the COTS category (operating systems, office product suites, word processing, and e-mail programs).

► A GOTS product is typically developed by the technical staff of the gov't agency for which it is created. It is sometimes developed by an external entity, but with funding and specs from the agency. Because agencies can directly control all aspects of GOTS products, these are generally preferred for gov't purposes.

► The "environment" in which the technology will be used is important and key to determining if the "COTS or GOTS" is a CTE.

► Provide evidence that this COTS item has been previously installed on the intended platform or a similar platform and demo'd in the intended relevant and/or operational environment or a different, but similar environment.

► Is it known if sufficient quantities exist?

► Are there any known short-comings with this COTS item?

REPACKAGED
COTS or GOTS► A repackaged COTS or GOTS product may or may not be a CTE.

► Identify whether the technology has been repackaged from it's original packaging footprint / form factor or design elements into a more dense, more stressful relevant and operational environment. Explain in detail the extent of the repackaging effort.

► A high-fidelity Relevant (lab) environment relates to form, fit, & function representative packaging environment as well as representative environmental conditions, such as dynamic flight environment, CV deck extremes (salt spray, electromagnetic CV environment, etc.).

Repackaged COTS or GOTS may = a New Relevant/Operational Environment ► Is the physical / logical / data environment in which this technology has been or will be demonstrated in identical or even similar to the intended environment?

► If it is different is the difference important or significant?

► Does any evidence exist such as test data, reports, or analyses comparing this technology demonstrated in an environment relevant to the intended environment?

► If modeling and simulation is an important aspect of that comparison, are the analysis techniques utilized common and generally accepted within the respective technological industry?

MODIFIED
COTS or GOTS► A modified COTS or GOTS product may or may not be a CTE.

► The extent of the COTS or GOTS mod is a detemining factor as well as whether or not the modified COTS or GOTS product can perform in the intended relevant (lab) environment. The extent of the mod needs to be explained in detail in the "Change Description" column.

► Is there any quantitative evidence to substantiate that the modified COTS or GOTS can perform in the intended relevant (lab) and operational (field) environment?

► A MOTS (either modified or modifiable off-the-shelf, or military off-the-shelf, depending on the context) product is typically a COTS product whose source code can be modified. The product may be customized by the purchaser, by the vendor, or by another party to meet the requirements of the customer. In the military context, MOTS refers to an off-the-shelf product that is developed or customized by a commercial vendor to respond to specific military requirements. Because a MOTS product is adapted for a specific purpose, it can be purchased & used immediately. However, since MOTS SW specs are written by external sources, gov't agencies are sometimes leery of these products, because they fear that future changes to the product will not be under their control.

► Consequently, a "modified COTS" product is no longer considered a COTS product, because similar products from competitive sources will not easily replace it.

Modified COTS or GOTS may = a New Relevant/Operational Environment ► Is the physical / logical / data environment in which this technology has been or will be demonstrated in identical or even similar to the intended environment?

► If it is different is the difference important or significant?

► Does any evidence exist such as test data, reports, or analyses comparing this technology demonstrated in an environment relevant to the intended environment?

► If modeling and simulation is an important aspect of that comparison, are the analysis techniques utilized common and generally accepted within the respective technological industry?

DEVELOPMENTAL
ITEM► An item is neither COTS nor GOTS, but an extension of or next generation of an internal developmental item.

Development - The process of working out and extending the theoretical, practical, and useful applications of a basic design, idea, or scientific discovery. Design, building, modification, or improvement of the prototype of a vehicle, engine, instrument, or the like as determined by the basic idea or concept. Includes all efforts directed toward programs being engineered for Service use but which have not yet been approved for procurement or operation, and all efforts directed toward development engineering and test of systems, support programs, vehicles, and weapons that have been approved for production and Service deployment.

► If in development, what is the status and roadmap? Is it a Breadboard, Advanced Development Model, Prototype, Engineering Development Model, Pre-Production, Laboratory Unit or Flyable Unit?

► The question to consider is was the identified COTS or GOTS designed to perform in the extreme conditions associated with a Naval aviation environment and this program's intended relevant (lab) & operational (field) environment?

► Identify whether or not the intended relevant and operational environment the COTS or GOTS product will be required to perform in is within the scope of the COTS or GOTS original design.

&"Arial,Bold"&11TMA TMSA GUIDANCE

&11V1, Jan 2013, Pre-MS-A TMA TMSA &"Arial,Bold"&11TMA TMSA GUIDANCE &11Page &P

Nimitz Class Recovery AoA TMSA

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and U.S. DoD contractors only. Information includes Proprietary Information / Critical Technology. Other requests for this document shall be referred to the Naval Air Systems Command (AIR-4.0M) or the ITRO.

INSTRUCTIONS (see the TMSA TWBS Guidance tab below for add'l guidance).

(1) Fill in the program name.

(2) Fill in the program background info, provide a picture of your top level system/subsystem, & provide your program level risk cube.

(3) Provide a description of what constitutes a relevant environment (lab) & operational environment (field) for your system /subsystem, a picture/chart of your overall system /subsystem architecture, & associated technology-related risk cube.

(4) Refer to the sample aircraft system decomposition, & complete the 1st 4 columns for each Technology Element (TE) of your system /subsystem based on your system /subsystem architecture.

(5) Provide a description of each TE by filling in the 5 white boxes identifying the Technology, its Function in the system /subsystem, its Location in the platform, system, or subsystem, the Requirement Reference for this TE, & if this TE can be traced to a KPP. (6) Decide, utilizing the CTE definition provided, if this TE is or is not a CTE. If a CTE, then complete the green section & place a "Y" in the cell for a novel, new, or new application of a technology & also the recommended to be a CTE cell. In the white box, explain why it is novel, new, or a new application. Explain if it's being repackaged such that a new relevant or operational environmental is applicable, & describe the differences between the original & new environments. If it has been modified from prior successful use, explain the extent of the mods & the technological challenges resulting from the mods. If it is expected to operate in an environment and/or achieve a performance beyond its original design intention or demo'd capability, explain & describe the new technological challenges. (7) If not a CTE, then identify if its COTS, modified COTS, repackaged technology, or an extension of, or next generation of an internal developmental effort. Under change description, provide the production part # for unmodified COTS in the pink box, or describe the extent of the mods or repackaging effort in the white box.

(8) Under the CTE/Non-CTE Justification Narrative, regardless of the category chosen for a TE, substantiate the developmental maturity of the TE by providing its heritage/pedigree, quantitative TE demonstration evidence from the prototype or end-item integrated system/subsystem testing in a low or high fidelity lab relevant environment, or simulated or real operational environment, as appropriate (include dates, quantities, lab hrs., platforms, & flight hrs.), & a concluding statement in the adjacent white boxes.

NAVAIR Pre-MS-A Technology Maturity Self-Assessment (TMSA) Technical Work Breakdown Structure (TWBS) for Nimitz Class Recovery AoA

Program Background Information The PMA, the MDA, & program master schedule including the Milestone A event, items on the critical path, & current status/progress. Picture 1 - Top Level System Program Level Risks PREDICTED TRL CTE DEFINITION: A technology element (TE) is “critical” if the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND

(2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.

Note to Offeror - By definition, if you assign a TRL to a Technology Element (TWBS Item) you are identifying it as a CTE, i.e. an immature technology. If a Technology Element is not a CTE, then it does not get assigned a TRL.

Relevant Environment Operational Environment Description Describe here what constitutes the intended relevant environment for your system, & the intended operational environmental boundaries for your system. Generally, the requirement statement for your system will provide some description of the environment in which the system is expected/required to operate.

A relevant environment is a testing environment that simulates both the most important & most stressing aspects of the operational environment.

An operational environment is a set of operational conditions, representative of the full spectrum of operational employments. Picture 2 - Overall System / Subsystem Architecture highlighting the System / Subsystem elements that will be assessed. Associated Technology-Related Risks

Note that the system breakdown below is a generic example that should be changed to reflect your system design.

TWBS #LEVELTECHNOLOGY ELEMENT
(TE)TECHNOLOGY ELEMENT (TE) MAPPINGTECHNOLOGY ELEMENT (TE)
DESCRIPTIONENABLING TECHNOLOGY
(Note: complete this column only if a CTE has been identified for the row.)CHANGE
DESCRIPTIONTECHNOLOGY ELEMENT (TE) CTE / Non-CTE
JUSTIFICATION NARRATIVETECHNOLOGY ELEMENT (TE) TRL JUSTIFICATION

1.0 1 Nimitz Class Arresting Gear This is a Level 1 roll-up. The program of record & threshold compliant design for this Nimitz Class Arresting Gear includes the Arresting Engine, Arresting Control System, Drive Fairlead System, Ancillary Support Systems, and Platform Integration.

The Nimitz Class Arresting Gear

1.1 2 Arresting Engine Nimitz Class Arresting Gear This is a Level 2 roll-up. The Arresting Engine includes the Hardware and Software. The Arresting Engine….(does what?). Picture

1.1.13HardwareArresting EngineTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.1.23SoftwareArresting EngineTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.2 2 Arresting Control System Nimitz Class Arresting Gear This is a Level 2 roll-up. The Arresting Control System includes Hardware and Software. The Arresting Control System…(does what?). Picture Picture

1.2.13HardwareArresting Control SystemTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.2.23SoftwareArresting Control SystemTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.3 2 Drive Fairlead System Nimitz Class Arresting Gear This is a Level 2 roll-up. Drive Fairlead System includes Hardware and Software. The Drive Fairlead System…(does what?). Picture Picture

1.3.13HardwareDrive Fairlead SystemTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.3.23SoftwareDrive Fairlead SystemTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.4 2 Ancillary Support Systems Nimitz Class Arresting Gear This is a Level 2 roll-up. The Ancillary Support Systems include …Subsystem 1, Subsytem 2….etc Subsystem 1…(does what?).

Subsystem 2…(does what?). Picture Picture

1.4.13Subsystem 1Ancillary Support SystemsTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.4.23Subsystem 2Ancillary Support SystemsTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.5 2 Platform Integration Nimitz Class Arresting Gear This is a Level 2 roll-up. Platform Integration includes Shipboard and Land-Based Integration. Picture Picture

1.5.13Shipboard IntegrationPlatform IntegrationTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

1.5.23Land-Based IntegrationPlatform IntegrationTechnology: describe the composition of this TE.NOVEL TECHNOLOGYNEW TECHNOLOGYNEW APPLICATION of TECHRECOMMENDED TO BE A CTEENABLING TECHNOLOGY
Critical TE (CTE): describe the component that may drive technology maturity. [An enabling TE is "critical" if: (1) the system being acquired depends on this TE to meet its capability development document (CDD) & capability production document(CPD) requirements, AND (2) this TE or its application is new or novel in an area that poses major technological risk during detailed design or demostration.]COTS or GOTSMODIFIED COTSREPACKAGED TECHNOLOGYCHANGE DESCRIPTION
If the answer to the "MODIFIED COTS or GOTS" or "REPACKAGED TECHNOLOGY" columns is "Yes", then provide a detailed description here of the mod incurred, and/or the new or novel environment, or of the extent of the repackaging.DEVELOPMENTAL ITEMHeritage/Pedigree: of this TE design /development approach. Is it a derivative of a previous design with minor mods, a complete redesign, or a brand new design?

Function: describe the action for which this TE is specially fitted or used in its operational environment.

Picture Platform Location: describe where this TE resides in the host platform. N N N Quantitative Evidence: this TE has been integrated at the system/subsystem level & demo'ed in the intended relevant (lab) or operational (field) environment (include quantities, platforms, flight hrs, dates).

Requirement Ref: for this TE from CDD, specs, etc. Unmodified COTS Supplier / Production Part #: of this TE.

KPP: traced to this TE. N N N N N Conclusion: This TE is not a CTE because ... OR This TE is a CTE because ...

TWBS #LEVELTECHNOLOGY
ELEMENT (TE)TECHNOLOGY

ELEMENT (TE)

MAPPING SPACE for ADDITIONAL NARRATIVE if REQUIRED

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and U.S. DoD contractors only. Information includes Proprietary Information / Critical Technology. Other requests for this document shall be referred to the Naval Air Systems Command (AIR-4.0M) or the ITRO.

This document is a work of the United States Government authored as part of the official duties of employee(s) of the United States Navy. No copyright is claimed in the United States under Title 17, U.S. Code. All other rights are reserved by the United States Government. Any publisher accepting this document for publication acknowledges that the United States Government retains a nonexclusive, irrevocable, worldwide license to prepare derivative works, publish or reproduce the published form of this document, or allow others to do so, for United States Government purposes. This legend must be retained on all copies of this document.

DO NOT REFORMAT &"Arial,Bold Italic"&11For Official Use Only DO NOT REFORMAT

&G NAVAIR Pre-MS-A TMA TMSA V1, Jan 2013 (Configuration controlled by the TRA Chairman - DO NOT REFORMAT)&12
&"Arial,Bold Italic"&11For Official Use OnlyPage &P

TRL Definitions

HARDWARE Technology Readiness Level (TRL) Definition Description Supporting Information

1. Basic principles observed & reported.Lowest level of technology readiness. Scientific research begins to be translated into applied research and development (R&D).
Examples might include paper studies of a technology's basic properties.Published research that identifies the principles that underlie this technology. References to who, where, when.
2. Technology concept and/or application formulated.Invention begins. Once basic principles are observed, practical applications can be invented. Applications are speculative and there may be no proof or detailed analysis to support the assumptions.
Examples are limited to analytic studies.Publications or other references that outline the application being considered and that provide analysis to support the concept.
3. Analytical & experimental critical function and/or characteristic proof of concept.Active R&D is initiated. This includes analytical studies & laboratory studies to physically validate the analytical predictions of separate elements of the technology.
Examples include components that are not yet integrated or representative.Results of laboratory tests performed to measure parameters of interest and comparison to analytical predictions for critical subsystems. References to who, where, and when these tests and comparisons were performed.
4. Component and/or breadboard validation in laboratory environment.Basic technological components are integrated to establish that they will work together. This is relatively "low fidelity" compared with the eventual system.
Examples include integration of "ad hoc" hardware in the laboratory.System concepts that have been considered and results from testing laboratoryscale breadboard(s). References to who did this work and when. Provide an estimate of how breadboard hardware and test results differ from the expected system goals.
5. Component and/or breadboard validation in relevant environment.Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so they can be tested in a simulated environment.
Examples include "high fidelity" laboratory integration of components.Results from testing a laboratory breadboard system are integrated with other supporting elements in a simulated operational environment. How does the “relevant environment” differ from the expected operational environment? How do the test results compare with expectations? What problems, if any, were encountered? Was the breadboard system refined to more nearly match the expected system goals?
6. System/subsystem model or prototype demonstration in a relevant environment.Representative model or prototype system, which is well beyond that of TRL 5, is tested in a relevant environment. Represents a major step up in a technology's demonstrated readiness.
Examples include testing a prototype in a high-fidelity laboratory environment or in a simulated operational environment.Results from laboratory testing of a prototype system that is near the desired configuration in terms of performance, weight, and volume. How did the test environment differ from the operational environment? Who performed the tests? How did the test compare with expectations? What problems, if any, were encountered? What are/were the plans, options, or actions to resolve problems before moving to the next level?
7. System prototype demonstration in an operational environment.Prototype near or at planned operational system. Represents a major step up from TRL 6 by requiring demonstration of an actual system prototype in an operational environment (e.g., in an aircraft, in a vehicle, or in space).
Examples include testing the prototype in a test bed aircraft.Results from testing a prototype system in an operational environment. Who performed the tests? How did the test compare with expectations? What problems, if any, were encountered? What are/were the plans, options, or actions to resolve problems before moving to the next level?
8. Actual system completed & qualified through test & demonstration.Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development.
Examples include developmental test & evaluation (DT&E) of the system in its intended weapon system to determine if it meets design specifications.Results of testing the system in its final configuration under the expected range of environmental conditions in which it will be expected to operate. Assessment of whether it will meet its operational requirements. What problems, if any, were encountered? What are/were the plans, options, or actions to resolve problems before finalizing the design?
9. Actual system proven through successful mission operations.Actual application of the technology in its final form & under mission conditions, such as those encountered in operational test & evaluation (OT&E).
Examples include using the system under operational mission conditions.OT&E reports.

Term Additional Definitions of TRL Descriptive Terms (Source: Defense Acquisition Guidebook)

TRLs indicate what has been accomplished in the development of a technology from several perspectives; theory to laboratory to field, relevant environment to operational environment, subscale to full scale, breadboard to brassboard to prototype, & partial performance to full performance. TRLs do not indicate that the technology is right for the job or that the application of the technology will result in successful development of the system, & TRLs do not address risk or system integration.

Breadboard Integrated components that provide a representation of a system/subsystem & that can be used to determine concept feasibility & to develop technical data. Typically configured for lab use to demo the technical principles of immediate interest. May resemble final system/subsystem in function only.

High Fidelity Addresses form, fit & function. A high-fidelity lab environment would involve testing with equipment that can simulate & validate all system specs within a lab setting.

Low Fidelity A representative of the component or system that has limited ability to provide anything but first-order information about the end item product. Low-fidelity assessments are used to provide trend analysis.

Model A functional form of a system generally reduced in scale, near or at operational specification. Models will be sufficiently hardened to allow demonstration of the technical & operational capabilities required of the final system.

Operational Environment Environment that addresses all the operational requirements & specs required of the final system to include platform/packaging.

Prototype A physical or virtual model used to evaluate the technical or manufacturing feasibility or military utility of a particular technology or process, concept, end item, or system.

Relevant Environment Testing environment that simulates the key aspects of the operational environment.

Simulated Operational Environment Either (1) a real environment that can simulate all the operational requirements & specs required of the final system or (2) a simulated environment that allows for testing of a virtual prototype. Used in either case to determine whether a developmental system meets the operational requirements & specs of the final system.

&"Arial,Bold"&11Maturity Categories

&11V1, Jan 2013, Pre-MS-A TMA TMSA &"Arial,Bold"&11Maturity Categories &11Page &P image1.png image2.jpeg image10.emf

Microsoft_Excel_Worksheet2.xlsx TMSA Guidance

TMA GENERAL GUIDANCE

TMA ► A Technology Maturity Assessment (TMA) is a systematic, metrics-based process that assesses the maturity of, & the risk associated with, Critical Technology Elements (CTEs) to be used in systems. It follows the same rigor & discipline of a TRA, but it is conducted on a non-finalized design, i.e. system concepts or concept designs during the MS-A TMRR Phase or Pre-MS-A on the results of an Analysis of Alternatives (AoA).

CTE
Definition► CTE DEFINITION: A technology element (TE) is defined as “critical” if the system being acquired depends on that TE to meet its capability development document (CDD) and capability production document (CPD) requirements and if its application is either new or novel in an area that poses major technological risk during detailed design or demonstration.

► NOT A CTE: This TE is NOT “critical”…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .