From a pilot’s perspective I would like to say thank you to all the engineers and maintenance personnel around the world and for keeping the systems in top notch service for our safety and well being.
nice video... however i would like to know how that avionics automation manages the safety integrity levels? or do they have such kind of fail safe action in terms of system malfunctions?. dual redundancies on the sensors in aircraft are critical, i guess so, TCAS can be bypassed in case of discrepancies indicator occurs from the pilot and first officer ones, for example..this is kind of fail safe,probably... i been working on dual fired power stations as control system engineer and managing "auto pilot" of the plant to automated functions for coal consumption, megawatts management, turbine controls and so on with SIL level and logic solver based on IEC61511. In case of system discrpancies, plant auto pilot can be overridden, and Operator takes fully control.
Avionics programs adhere to DO-178x and ARP-4754x in commercial aerospace in the US. The certification collaboration with the FAA will determine the assurance level and appropriate redundancies are implemented. The systems engineers are responsible for making sure the requirements are sufficient to meet these standards and that the systems has enough testing to prove that the systems actually meet the requirements.
You don't need the deepest background in math, as you almost always work with a specialist who can explain/figure stuff out for you. But it's really beneficial if you have a very broad knowledge of math, as that's the common language of engineering experts. So the more math you can read the fewer text and diagrams you need from your specialists, and it will be much easier for you to communicate the right text and diagrams to other stakeholders like business owners or officials. That said you should be rock solid in logic and the basics of algebra like identity, inverse, and linearity. Those describe the solution space of the system you want to build, and where you can place subsystems. This also cuts graph theory a little bit. The second is a deep dive into algebra. You should have simulated an electrical circuit, bend a beam in a FEM tool, placed a cow in a fluid simulation, and build something like the famous inverse pendulum in control theory. It doesn't need to be perfect you just need to get a view of things done and be able to talk with an expert in that field on his level. The third is statistics. Anything that can be measured is not a fixed value. Even if you approximate so later. You need to understand the mean and the variance as a concept. This will be used to communicate in terms like accuracy, and precision with the stakeholders, and physical units with the engineers. Also with the umbrella terms AI and ML a lot of statistics became relevant over the years, and with cryptography aspects of safety and security knowing some graph theory will be helpful. So there's a lot you need to know about math, but you don't need to dig too deep. Binging videos from 3Blue1Brown, Michael Douglas, and Steven Brunton should give you about the right level. Do a lot of the simpler stuff in each discipline yourself and focus on how you would communicate this math to someone who doesn't have the time to learn it, or how you might need to talk to somebody that's fluid in those terms. And be prepared that you will need to learn new areas of math all the time. Also if your team can't afford an expert in one field, be prepared to replace that role within the team with external help.
There is no such thing as a systems engineer. It's like calling people a general contractor. But in practice if you hire an electrical engineer to design a hybrid vehicle you end up with a tesla. Like in construction if a bricklayer is design the house the house ends up all brick because they're trying to make themselves the most money by doing something they can make money off of more than others, and it's what they understand the most so they're trying to make it easier. That's why there is no such thing as a systems engineer. You're just trying to hide what you know. In hospitals they started putting computers on the beds with flat screens and all kinds of stuff then they'll say a systmes engineer designed. Someone trying to make an extra buck selling more computer junk designed it. It's like the cranberry salesman who comes along and suddenly have cranberry in all of the other juices.
It's an extremely technical field, you need to know how the components are connected, how they deliver the result, the requirements needed to supply and so on. I'll give an example of a vehicle company, and at least you need to know about vehicle electronics, cybersecurity, communication protocols, etc. So that in the end you can develop how the entire system will work and from then on there will be the departments of each area mentioned, going even deeper, creating in fact what was previously planned After everything is completed, you are still responsible for applying the product, if what was created actually meets the requirements made above, failure analysis and the testing process of the product created, validating or not the project and finally the final application
Project Management is definitely part of it but project manager does not equal a project engineer. And it is quite technical. Usually it takes years of experience to get to that level.
You need a very broad knowledge of math, and be fluid in the technical terms of all engineering departments in your projects. But you obviously can't get as deep as a specialist as you simply don't have the time for that. While the project manager is responsible for managing the people and budget, a systems engineer is responsible for the requirements and exploring the possible solution space. So the engineer reasons about if and how you could build something, while the project manager distributes money(salary) to the right people to make it work.
![Basic Introduction of Systems Engineering (V-method) [Part 1 of 2]](http://i.ytimg.com/vi/9b4GYQfUuGE/mqdefault.jpg)
![Basic Introduction of Systems Engineering (V-method) [Part 1 of 2]](/img/tr.png)
From a pilot’s perspective I would like to say thank you to all the engineers and maintenance personnel around the world and for keeping the systems in top notch service for our safety and well being.
This guy is a true gem! We need more people like him
Just accepted a role as a systems engineer with Boeing. I’m a prior pilot as well. Looking forward to this new role!
Congrats!!!
Thats awesome... Best of luck.
Im starting at bae next monday, how have you found it
That's awesome congrats. How are you liking it? Trying to get into this myself.
Man that looks like a real true hardcore solid team there.
The paintjob on that 650 is awesome
This sounds absolutely breathtaking 😍
Very well detailed video. Thanks for the insight! Will definitely share with my engineering student audience
sir i love your work..thank you for this video
"Uuh, yeah, Steve, I might need you to hurry up implementing that popsicle holder on my yoke"
What is his “avionics for everyone” certification and how can I get that?
i was just wondering the same thing. did u find out?
@@firesoldier3051 did you find out?
@@OmSaiSwarupSetty did you find out?
@@johantang8417 No😥
Electrical engineering degree for this title I’m a systems engineer at Honeywell
Inspiring. The guy is my dream to be. Wow.
Helpful video! Thanks!
nice video... however i would like to know how that avionics automation manages the safety integrity levels? or do they have such kind of fail safe action in terms of system malfunctions?. dual redundancies on the sensors in aircraft are critical, i guess so, TCAS can be bypassed in case of discrepancies indicator occurs from the pilot and first officer ones, for example..this is kind of fail safe,probably... i been working on dual fired power stations as control system engineer and managing "auto pilot" of the plant to automated functions for coal consumption, megawatts management, turbine controls and so on with SIL level and logic solver based on IEC61511. In case of system discrpancies, plant auto pilot can be overridden, and Operator takes fully control.
Avionics programs adhere to DO-178x and ARP-4754x in commercial aerospace in the US. The certification collaboration with the FAA will determine the assurance level and appropriate redundancies are implemented. The systems engineers are responsible for making sure the requirements are sufficient to meet these standards and that the systems has enough testing to prove that the systems actually meet the requirements.
I do know that the fault handling code far surpasses the regular code in terms of amounts.
Thank you
So what's the difference between an aerospace engineering and aerospace systems engineer?
both have knowledge in aerospace field, but one project the component and other project the system (this is a overview)
In reality? The systems one will be concerned with electronic subsystems as well.
Does this require alot of math what kind of math is involved is the math challenging i struggle with math
You don't need the deepest background in math, as you almost always work with a specialist who can explain/figure stuff out for you. But it's really beneficial if you have a very broad knowledge of math, as that's the common language of engineering experts. So the more math you can read the fewer text and diagrams you need from your specialists, and it will be much easier for you to communicate the right text and diagrams to other stakeholders like business owners or officials.
That said you should be rock solid in logic and the basics of algebra like identity, inverse, and linearity. Those describe the solution space of the system you want to build, and where you can place subsystems. This also cuts graph theory a little bit. The second is a deep dive into algebra. You should have simulated an electrical circuit, bend a beam in a FEM tool, placed a cow in a fluid simulation, and build something like the famous inverse pendulum in control theory. It doesn't need to be perfect you just need to get a view of things done and be able to talk with an expert in that field on his level. The third is statistics. Anything that can be measured is not a fixed value. Even if you approximate so later. You need to understand the mean and the variance as a concept. This will be used to communicate in terms like accuracy, and precision with the stakeholders, and physical units with the engineers. Also with the umbrella terms AI and ML a lot of statistics became relevant over the years, and with cryptography aspects of safety and security knowing some graph theory will be helpful.
So there's a lot you need to know about math, but you don't need to dig too deep. Binging videos from 3Blue1Brown, Michael Douglas, and Steven Brunton should give you about the right level. Do a lot of the simpler stuff in each discipline yourself and focus on how you would communicate this math to someone who doesn't have the time to learn it, or how you might need to talk to somebody that's fluid in those terms. And be prepared that you will need to learn new areas of math all the time. Also if your team can't afford an expert in one field, be prepared to replace that role within the team with external help.
Systems Engineering = Group of Engineers with an Euphemism
idiot
he is in another lvl, too far away from a regular brazilian like me
There is no such thing as a systems engineer. It's like calling people a general contractor. But in practice if you hire an electrical engineer to design a hybrid vehicle you end up with a tesla. Like in construction if a bricklayer is design the house the house ends up all brick because they're trying to make themselves the most money by doing something they can make money off of more than others, and it's what they understand the most so they're trying to make it easier. That's why there is no such thing as a systems engineer. You're just trying to hide what you know. In hospitals they started putting computers on the beds with flat screens and all kinds of stuff then they'll say a systmes engineer designed. Someone trying to make an extra buck selling more computer junk designed it. It's like the cranberry salesman who comes along and suddenly have cranberry in all of the other juices.
Sounds like system engineer role isn't very technical or need math. More like a project manager?
It's an extremely technical field, you need to know how the components are connected, how they deliver the result, the requirements needed to supply and so on.
I'll give an example of a vehicle company, and at least you need to know about vehicle electronics, cybersecurity, communication protocols, etc.
So that in the end you can develop how the entire system will work and from then on there will be the departments of each area mentioned, going even deeper, creating in fact what was previously planned
After everything is completed, you are still responsible for applying the product, if what was created actually meets the requirements made above, failure analysis and the testing process of the product created, validating or not the project and finally the final application
Project Management is definitely part of it but project manager does not equal a project engineer. And it is quite technical. Usually it takes years of experience to get to that level.
Very technical and heavy math
You need a very broad knowledge of math, and be fluid in the technical terms of all engineering departments in your projects. But you obviously can't get as deep as a specialist as you simply don't have the time for that. While the project manager is responsible for managing the people and budget, a systems engineer is responsible for the requirements and exploring the possible solution space. So the engineer reasons about if and how you could build something, while the project manager distributes money(salary) to the right people to make it work.