Author: AviJake
Subject: IFD540 Certification Status
Posted: 19 Mar 2014 at 8:48pm
(19 Mar 2014 Status Update):
Subject: IFD540 Certification Status
Posted: 19 Mar 2014 at 8:48pm
(19 Mar 2014 Status Update):
We had an unexpected but very welcome meeting today with the FAA who came into our lab with an objective of closing out some open cert issues for the IFD540.
Updates in bold red below. I stick by the externally consumable milestones earlier in this thread, namely:
6. Complete FAA TIA (Type Inspection Authorization) testing. This is the FAA's final exam of the complete system before they sign off on cert. One of the most interesting things that happened today is that the FAA is talking (I emphasize talking and has not made a decision) about delegating all TIA back to us. That became a lot easier for them after they closed out the open TIA issues. We'll keep doing whatever we can to influence their decision on that one.
7. Make our final submissions to the FAA of 100% of the certification artifacts. No change on this item since Jan.
1. Receive, and react accordingly to, the FAA-generated MPSUE assessment of the unit. This will likely drive some code changes but we won't know the magnitude until we get the official list from the FAA; Officially Done. There had been roughly a dozen, albeit not risky, items open from the MPSUE that the FAA intended to keep open until TIA. They were all closed today and none require any further FAA flight or evaluation.
2. Achieve 100% DO-178B Code Complete status. This is well beyond "feature complete". DO-178B "Code Complete" means we've finished all the code review and requirement tracing of the code per the FAA-recognized software standard. We can't finish this until we know the code is done changing. Note that we're done with all the changes on our end, we're just reacting now to any mandated changes; This was completed a few months ago so nothing new to report here.
3. Officially declare DO-160 Hardware Qual testing to be complete; Already reported to be done.
4. Achieve "Red Label" status on the combined hardware/software system. This means that all formal for-credit software and hardware testing have been completed. In other words, this is a submittable-for-cert system; Refer back to the Jan post for more details on what this one means. We've made great progress on this one. Approximately 97% of all requirements have tests written for them now. We're still plugging away on Code Coverage which will take the bulk of the remaining time. We also been able to start official Test-For-Credit on some of the system (math libraries, OS, lower design assurance level code, etc)
5. Complete official company "for-credit" flight testing of the final submittable system; No change here since Jan.
2. Achieve 100% DO-178B Code Complete status. This is well beyond "feature complete". DO-178B "Code Complete" means we've finished all the code review and requirement tracing of the code per the FAA-recognized software standard. We can't finish this until we know the code is done changing. Note that we're done with all the changes on our end, we're just reacting now to any mandated changes; This was completed a few months ago so nothing new to report here.
3. Officially declare DO-160 Hardware Qual testing to be complete; Already reported to be done.
4. Achieve "Red Label" status on the combined hardware/software system. This means that all formal for-credit software and hardware testing have been completed. In other words, this is a submittable-for-cert system; Refer back to the Jan post for more details on what this one means. We've made great progress on this one. Approximately 97% of all requirements have tests written for them now. We're still plugging away on Code Coverage which will take the bulk of the remaining time. We also been able to start official Test-For-Credit on some of the system (math libraries, OS, lower design assurance level code, etc)
5. Complete official company "for-credit" flight testing of the final submittable system; No change here since Jan.
6. Complete FAA TIA (Type Inspection Authorization) testing. This is the FAA's final exam of the complete system before they sign off on cert. One of the most interesting things that happened today is that the FAA is talking (I emphasize talking and has not made a decision) about delegating all TIA back to us. That became a lot easier for them after they closed out the open TIA issues. We'll keep doing whatever we can to influence their decision on that one.
7. Make our final submissions to the FAA of 100% of the certification artifacts. No change on this item since Jan.