- Joined
- Feb 15, 2012
- Messages
- 9,567
- Reaction score
- 4,408
For anyone following the Avidyne 540 development/release. This is from their public forums ( http://forums.avidyne.com ), Jacobson is the VP, Product Development.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Definitely not August for IFD540 Cert. Instead of providing a date, I'll say that we have a few major milestones to get through before we can spike the ball. You should consider measuring us against these remaining milestones to get a sense of the higher and higher confidence date. Those remaining big milestones are:
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;
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;
3. Officially declare DO-160 Hardware Qual testing to be complete;
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;
5. Complete official company "for-credit" flight testing of the final submittable system;
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.
7. Make our final submissions to the FAA of 100% of the certification artifacts.
We do consider this to be end-game of the program. Some of those activities typically last only a matter of a few days (e.g. 5, 6, 7) and some take several weeks to get through (e.g. 2, 4).
S. Jacobson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I will report on the FAA MPSUE findings and the Code Complete milestones noted above (#1, 2) and at that point, will focus on the pilot program selection and date estimates since at that point, we have a much more deterministic schedule.
We're working weekends and holidays to get this done.
S. Jacobson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I continue to be amazed at how open and consultative they have been in this process.
* Orest
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Definitely not August for IFD540 Cert. Instead of providing a date, I'll say that we have a few major milestones to get through before we can spike the ball. You should consider measuring us against these remaining milestones to get a sense of the higher and higher confidence date. Those remaining big milestones are:
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;
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;
3. Officially declare DO-160 Hardware Qual testing to be complete;
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;
5. Complete official company "for-credit" flight testing of the final submittable system;
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.
7. Make our final submissions to the FAA of 100% of the certification artifacts.
We do consider this to be end-game of the program. Some of those activities typically last only a matter of a few days (e.g. 5, 6, 7) and some take several weeks to get through (e.g. 2, 4).
S. Jacobson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I will report on the FAA MPSUE findings and the Code Complete milestones noted above (#1, 2) and at that point, will focus on the pilot program selection and date estimates since at that point, we have a much more deterministic schedule.
We're working weekends and holidays to get this done.
S. Jacobson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I continue to be amazed at how open and consultative they have been in this process.
* Orest
Last edited:
