Downloaded from https://www.everyspec.com ADS-79D-HDBK Validation is the final phase of development and confirms the ability of the developed system to perform in real-world conditions. K.6.2.1 Ground Station System Validation. System Validation represents the final V&V phase for developed products. The purpose of system validation is to determine whether the system is indeed performing the functions for which it was created, in the real-world production environment. The system should be installed, calibrated, and operated in the production environment using established training and maintenance procedures, run by the end-user operators for which it was designed.
Consideration should be given to introducing this stage of validation in a controlled manner (for example, a designated unit or units) and ensuring that all personnel involved with the system receive adequate training and preparation for its use. The time period for system validation should be long enough to establish the system in routine use, and to evaluate the operations and maintenance recommendations it will generate during that period. Supplier input and assistance during this phase should be limited to that which would normally be provided to any production environment.
If Contractor Logistic Support (CLS) is envisioned for the system, CLS personnel should be allowed to participate to the same extent they would in the production environment. If the system is designed for organic support, then the necessary personnel should be available to supply that support. There should be no difference between the supplier and customer support provided to the unit(s) in validation and those used in any other production system.
In order to benefit from the system validation phase, a report should be generated at its conclusion highlighting the degree to which the system performed as intended, and identifying any issues or problems with the system, as well as any unanticipated benefits or other unplanned impacts. By providing an objective evaluation of the overall system, the validation report can serve as a basis for planned updates, future modifications, or enhanced attention to the product. It can also serve as a baseline scorecard for the development effort to assess its overall degree of success in meeting the customer‘s intent.
A successful system validation would normally be followed by introducing the system into the full production environment. The airworthiness authority should evaluate the system validation report and provide its guidance on fleet-wide implementation and the need for any subsequent modifications or alterations to the system. Experimental or developmental approaches and methods, though certainly useful for the continued development of HUMS technology, should be either isolated within the data collection and reporting system (i.e.
‗background‘ data collection or analysis performed which is transparent to the end user and which does not interfere with the normal operation of the system), or should be assigned to test aircraft on an as-available basis. Similarly, on the Ground Station, acceptable approaches and methods related to software development, verification, configuration management, and application maintenance should be employed as a means of developing, fielding, and maintaining certifiable verified and validated software. Guidance in the form of RTCA DO-178B and similar publications can provide a 223