I'm currently studying CS, and used to think it's kind of weak compared to some real engineering disciplines, but really being an expert at one fieid is also important if you want to do something more complex.
That’s what industrial engineers do, but then whether this is engineering or managment is a real question. I have read papers in systems of systems engineering and met researchers in that field. They speak a pure nonsense to me because they have no proper field. Systems engineering needs to be coupled with something to be valuable.
I am a Systems Engineer. I studied Mechanical Engineering in College with a minor in Chemistry. Studied Astrophysics, Chemical Engineering, Computer Engineering, Network Engineering, Software Engineering, Telecommunications Engineering, and Cloud Engineering on my own. As well as working as a Fiber Optic Technician, Network Technician, then Telecommunications Engineer and Cloud Architect/Engineer, building my experience over the last 15 years. I now own and run a tech company that specializes in business technology solutions, and I oversee Engineers of all disciplines. It took a long time and a lot of effort to become what I am today. But I truly enjoy it, and I wouldn't trade it for the world.
May I ask when you self-studied all these subjects? Did you do that concurrently with your college education? If at least partially, what topics did you self-study while in undergrad? I’m about to start a bachelors in mechanical engineering program and am infatuated and deeply interested by all those other disciplines you mention. I’d really appreciate your input.🙏
@@Parsimoniouspenguin1 Yes. Exactly. I have been reading extensively since I was in my mid twenties. I graduated with an associate degree in landscape development when I was 25. I switched from a business major to mechanical engineering at 30yo for my second degree. I admit I am a bit of a high performer. I was running a landscape company and working on fiber optic transmission line installation while studying mechanical engineering and chemistry, and still read a lot outside of school. That mixed with the many videos available on RUclips. And the hands on experience I gained in the field of IT and telecommunications. Then got certified in cloud architecture. I have a unique experience as someone who has worked in almost every phase of IT, from long range data transmission, to structure cabling of large building projects, to networking, to all sorts of equipment installation and programming to Cloud Computing. One can learn anything if they are willing to dedicate their time to it. The hands on experience is key, but the experience can be drastically improved by always studying as well. As an engineer, I am continually learning. It’s easy if you are passionate and have a thirst for knowledge. If not you may get burned out. It’s definitely not for everyone, but if you love it, you look forward to it. I love solving problems. And everyday I am faced with new ones. lol. Good luck with your studies. And go at your own pace, if you’re dedicated you’ll get there. And if you fail, do it agin until you succeed. Never give up.
I will likely be studying Cyber Physical Systems Engineering for my bachelor's, which used to be called Embedded Systems and IoT Engineering. They go over all the required maths and mostly it's technical. Programming and Circuits are huge. Essentially it's all learned to build an innovative product, which is essentially a system. I do hope though, to be able to do a Master's in Data Science, specifically ML + AI tool development... That'll hopefully allow me to build lots of systems that I can only dream of right now :(
Many Systems Engineering roles require the knowledge of virtualization/containerization, active directory, group policy, IaC, clustering & loadbalancing, cloud computing platforms (AWS/Azure/etc), CI/CD, CDN, backups, bigdata, web servers, database servers, DNS servers, DHCP servers, email servers, VOIP servers, file servers, etc, etc (most of which probably aren't included in Mechatronics Engineering programs). Some roles require a heavier emphasis on software engineering or network engineering or data engineering or even mechatronics engineering. Some leans more towards DevOps, while others towards SRE. It all depends on what company you work in and what system they need to get working. I've been working as a systems engineer for a decade now without knowing a single thing about mechatronics engineering. And that's why I think Mechatronics Engineering programs are called Mechatronics Engineering programs (and not a Systems Engineering program).
@@senantiasa Those topics are included in MTE programs around my area. Systems Engineering as an academic program is also frankly quite vague so that could amount to practically anything depending on what the curriculum actually entails. And above that, one can teach themselves any Engineering concept they were not taught in class if they cared to do so for their own benefit.
My Dad was a systems engineer and learned everything on the job over the last 40yrs before retiring recently. No university or "formal education". He started in the Navy, eventually managed maintenance crews at Disneyland for a few years and then ended up doing more contract work for the Navy before retiring. He has always been handy, built or fixed anything he could get his hands on and just has an awesome mind for seeing the big picture aka systems. You and other Engineers are the kind of problem solvers this world truly needs. Thanks for the cool content. 🤙
There are lots of jobs titled "Systems Engineer" that are not the kind of SE discussed in this video. Look at the description given by INCOSE to really compare apples to apples with the ideas in this video.
@@davidh4374 lot of defense contracting and DoD jobs willing to hire non-engineers as systems engineers. There’s intimate knowledge of the INCOSE handbook by these companies and agencies. Usually, however, they’re not getting hired to do something like design work. CONOPs, testing to requirement validation, sustainment of a deployed system, and obsolescence planning is usually the purview of these non-engineer systems engineers.
My grandfather became an EE through his tenure in the navy. Radio operator. He always claimed his navy service was the best thing that ever happened to him. Respect to your dad
I am a mechanical engineer that works in electronics development (RF inverters and amplifiers). This kind of discipline is critically needed to come up with good design approaches for tightly integrated systems. For example, it’s almost impossible to have a truly small or lightweight system without a system architect that is looking at how to design the system electrically, but also consider it mechanically, identifying newer, smaller parts. We don’t have this role at my job (we have systems engineers but they do not do this architecting role sadly), so it turns into a haphazard back and forth during detailed design. Or, Even worse, it becomes a straight out adversarial “that’s not my job” relationship between disciplines which results in bloated, disjointed design. So yes this degree would be very useful.
systems in systems engineering by convention refers to i.t based or any application that takes in data and CRUD type actions and the engineer is an administrator, creator of such an app or deployment of an app or tech stack. What you are asking of your 'systems engineers' is a LOT. src: im a principal systems engineer)
"System engineering is basically the engineering of systems" - this could be the most engineering way of defining a term I heard in a long time. I used to do this trick in my uni vivas when I didn’t fully knew the answer of a question 😂😂
Most real systems out there are multidisciplinary and extremely complex, that is why experts are needed for each system. Randomness is inherent to these systems. Modelling uncertainties is part of experts jobs
Isn't systems engineer a jack of all trades but master of none? Not specialised experts in any engineering field nor better than business school grads in big project management. Neither here nor there.
@@grapefruitsyrup8185 problem with both of those niche fields are that they really never understand the big picture. Specialized experts in the engineering field are only sought for that specific field of expertise. and with business school grads in project management, they often mess up the project plan and requirments because they only know how to talk business but no idea how to actually implement business solutions if its more complex than an excel sheet (which is usually the case). Which is why computer science, data engineers, software engineers, technical (buzzword) roles, alll poppped up. because they need expert generalists to be the glue
Hey Ali, you’re quite literally living the dream of what I want to be, albeit starting from a later age of 30 (!). Thanks for forging a path for those of us coming in the next generation of engineers. We need more communicator-engineers like you, who are able to inspire others by example and showing them the real brilliance of engineering- the mindset and the disposition to solve any problem that comes their way.
Really enjoyed your take on systems engineering. I agree 100% that you need a solid core and experience in the field. The “stack” you mention is exactly that. I was chief systems engineer for a navy sonar system years ago. You absolutely need the fundamentals and a broad view of many disciplines. I too have a BSEE/MSEE background but had to cross over into many other engineering and science topics. Great job explaining this.
One of the universities in Norway has a masters in systems engineering. Looking at the courses and talking to friends who have finished it, it seems like a REALLY nice addition to their bachelors. The added benefit of the master's is that it works with the industry. Instead of 2 years in uni, you spend 3, but work 50% in industry, and your workplace works with you and the uni to implement the Systems courses into your workday. I'm not sure how common this is globally, but it seems to be a fantastic solution. The 50% work is obviously paid like any engineer. The master's degree in Systems Engineering at this university has been around for quite a while, so I think (again, based on what friends say and the industry which works with the students) that it has both good teachers and facilities, and that it kept relevant without big gaps in what you'd expect from a proper Systems Engineer when they finish.
@@nate7243 Typically English if there are any non-norwegians present, especially at graduate level. That said, some greedy dipshit of an """"""education minister""""""(without a degree even, go figure) recently made it so non-schengens now have to pay absurd tuitions(like $15k or even more), not like we liked attracting smart people anyway....
Thanks for this insight. I have always wondered what systems engineers do, and now I have a clearer understanding. I have an ME degree and am about to pursue a master's in systems engineering, focusing on industrial engineering and sustainable technologies. This will really help with my future pursuits.
This reminds me of how operations research is super underrated. Hidden within industrial engineering or mechanical engineering departments and is essentially a major in optimization which as we all know is critical today with AI systems.
I once showed my transcript with all my OR coursework during an interview for an entry-level AI position. The recruiter responded "I don't see anything here that's relevant to this job description." I understood this was the wrong company to apply to and moved on.
I clicked on this video wondering when I would hear the word “zoom” and that happened around the 3:30 min mark. Great video - from my point of view as a power electronics engineer with experience in SW & mechanical too, what makes a great system engineer is the capacity to “effortlessly” and confidently zoom in and zoom out of systems & subsystems. Many engineering disciplines are fundamentally defined by differential equations in matrix form, which are not conceptually that different, regardless of the engineering area. Always having an engineering mindset, zooming in and breaking problems down in simple forms, then putting the pieces together and progressively zooming out more and more is how an intimate understanding of a working system is achieved - at the end of the day, everything from a class A amplifier to a car is a system. Great points!
Hi Ali, I’m an undergraduate Aerospace Systems Engineering student in my 3rd year, and your video has been so helpful. I would appreciate it, as would many others, if you made more videos like this. Also, if you could include real life projects and career related content in the future, that would be awesome. Books and materials would also be appreciated. Thanks Ali.
Im a junior in mche . I like systems engineering. Im more of an innovator type person. I always have new ideas. It could be a bed to utensel or electronics. I came up with my first electronic device converting mechanical motion to signal and current. I know some matlab. Still trying to get great at it. It takes time to learn a language like that. Love matlab and love your content. You have a firm grasp of this electronics. Keep making stuff like this or should i say electronic physics was awesome. Im finished physics i wish you had explained it to me like that my first time. Materials science is awesome stuff too.
My high school has an engineering program where one of the upper level classes is a year studying systems engineering and manufacturing systems in collaboration with some companies in real world industries. glad to see it will most likely be useful in the future.
I would love this Master. I finished an apprenticeship as a design engineer and now I start my Bsc in EE. That would be a perfect combination of the two I think.
Hey, I'm an electrical engineer with experience in FPGAs, Hardware Development and a little bit of circuit design. I've always been fascinated by space and especially big picture engineering and I plan to go back for a masters in space systems engineering. Thank you for such a valuable video!!
When I studied mechanical engineering as an undergrad, in our final year we had an Introductory Systems Engineering subject. It was as joint subject with other mechatronic engineering students. This forced us to work together and merge our expertise to identify, specify and design a system in a project. Just helped with the methods and strategies one would use to execute a project from start to end.
Nice video showcasing practical experience of building a system. Only thing I would like to add is to highlight is that systems engineering is more of a structured process which enables problem definition, requirement gathering (functional, non functional, performance, reliability, availability, maintainability, safety, HMI, operational ), collaboration between stakeholders, ensures traceability throughout system lifecycle and lastly , making choice of technology as per the problem and NOT the solution!
Great content! As an Electrical engineer and a practicing control systems engineer in the Oil & Gas industry for almost 30 years, what's Ali's covering is great! 2 thumbs up and hats off to this young man! 👍👍👍👍
Even working on my super simple year 2 project, i noticed its quite a puzzle figuring out how to arrange components so that everything works smoothly. I didnt know that was its own branch of engineering til i found your video. I wish it gets more popular
I work with lean principles and process improvement and your video was recommended to me by YT. One of the best presentations I've ever seen, with a very detailed explanation of the idea in plain English. Congratulations and thanks for sharing this.
Hey , Ali your channel was like a gateway for me to get into engineering , love learning about all the topics you explain , today started my journey in BE Information Technology, your channel has already guided me on what and how should I spend time in my 1st year, keep uploading man great content
This is a massively important thing and I commend you for addressing this topic, can you please expand further or teach more on it. This era needs this desperately, please fill this void.
@ I have my own domain of skills but have been trying to learn programming and engineering to help realize those goals, I have quickly realized the whole begets the means. So having a cohesive systems engineering framework became an obvious rabbit hole to help guild all domains I was trying to integrate cohesively
this is too verbose for no reason. I have a background in visual design, however instead of just making concepts or designs for fictional things I would like to build something complete. It has brought me down the rabbit hole of programming and engineering. However, when deciding what to build and how - I quickly started to realize I cant build parts without understanding how they will all come together. So I was looking into system engineering. To expand further I enjoy looking at whole systems and cross disciplinary solution - so understanding how to build cohesive systems across different domains intruiges me. There is very little content on it though.
This is a great video! I work at an aerospace company but I work in IT/SWE. I saw we were hiring for a Sys Engineer and was confused that none of the requirements mentioned cloud engineering, proficiency in multiple languages, networking skills, skills in multiple operating systems, etc. It then dawned on me - a systems engineer in my profession is completely different from an “Aerospace Systems Engineer”. Many different systems at play, but my idea of engineering a system has to do more with building a system like an application, or a program, or a scalable way to deploy an upgrade or software or keep track of computer inventory, etc. I have a deep understanding of programming (particularly Windows, but am skilled in Linux). To your credit, I became very good at one thing before I started touching systems at a larger scale. It also dawned on me that I’m essentially the full stack dev/systems engineer to my tech team… and that I might want to update my resume and start looking for a different job. lol.
Two years into a hypersonic flow fluid dynamics PhD and I’m starting to feel like a SE with all the disciplines involved: aerothermochemistry, materials science, aerodynamics, radiation and now global sensitivity analysis and uncertainty quantification for all these disciplines.
I’ve never had a RUclips video feel so relevant to me lol. I just started a new job as a THz radar systems engineer a week ago. Good to see mmWave/THz representation on RUclips!
My electrical engineering program has a specialization in systems engineering in undergrad, I'm excited to get into more advanced courses in it soon. We're learning about integrated control systems and control engineering as well as signal processing, VLSI, and quite a few other topics. Very happy to be in this program.
My aerospace undergrad program had a systems engineering discipline and I took umbrage with it for the exact reason you specify. I would offer my view that what you described isn’t necessarily a “systems engineer” in the classical definition but an “engineer with systems thinking.” The average systems engineering profession in my experience is full of requirements, verification and validation, and other things that are very “2D.” This video is great advice for anyone who wants to have a framework to be an effective engineer no matter what they do, because being able to interface with a system effectively will reduce project development time and cost and will allow you to expand your skillset as an engineer in general.
Very inspiring video! If systems engineering got popular, engineers who each specialize in different domains would be able to work with each other on any aspect of any technology… think about how much innovation would happen there!
This is actually an issue I noticed in the construction design management (CDM) industry I work in as a project engineer having studied mechanical engineering I struggle with keeping tabs with other disciplines despite the need. Noticed our company and similar companies in our space struggle in the engineering control roles liasoning between M&E and structural disciplines as the senior project engineers and managers sorta just expect the mechanical, electrical and structural engineers to sit down and have meetings with contractors related to producing and delivering these packages on guiding them according to our expectations. The issue being a lot of the things discussed by one major are either not picked up by other majors in prior with accuracy so we struggle with managing design expectations with contractors which takes longer than expected or struggling to deliver changes from one contractor to the other with the correct level of detail, possibly shaving off months of delay with simply a CDM systems engineer holding/running the meeting with the subbies instead delivering explaining the entire systems layout updates. As there are standards and regulations to abide by minor changes cause delays in fixing to account for otherwise. It is weird but the way the current system has adapted is that the sub contracts who are supposed to just be delivering the package are essentially doing that part for us taking on that extra duty's burden.
I’m actually a second year engineer and want to go into electrical engineering and specialize in mechatronics but I think what I have been doing is just the same thing you described by getting really good in one area and then branching out which sort of a being a polymath like Da Vinci. Thanks Ali
Systems Engineer for NOAA here. I started as a meteorologist and gained satellite expertise as I used the products derived from their observations. That allows me to delve deep into requirements for satellite programs from a top-down view. I'm currently pursuing my Masters of Space Systems from Embry Riddle university. I agree with your assessment of Systems Engineering, I don't think there should be a Bachelors course for it. You need a foundation to build upon for a systems mindset. I do find my Masters course work to be beneficial though.
I love engineering, and I am really interested in systems where mechanics, electronics, and software meet and work in a symphony. I am a Mechatronics Engineering student. I chose this engineering because I thought this would be the best way for me to learn every bit of these components. If there were an option called systems engineering, I would jump to this option. And based on what little I know, my humble opinion is that if this idea becomes real, it should be based on electronics. Software is easy to grasp. Mechanics is a field in which humans relate very easily. But the electronics is a completely different world.
Worked as a Linux Systems Admin and currently a Cloud Engineer and man do I love systems engineering. Just to understand how components are connected together and having a system finally work is so satisfying. You can literally apply Systems Engineering to so many different engineering paradigms which is what makes it so fascinating to me. Curious on everyone else's perspective.
Formalized abstraction of devices and the interactions between Super important topic here Truly good systems engineers have depth in all disciplines. Only they, by definition, can truly derive the optimal solution and guard against instabilities and real-world non-idealities Cool video
This video taught me what my job has been for the last few years. Well articulated, thank you. P.S. Fun fact: one can do system engineering without ever knowing UML.
recently, I had a friend who is doing Physics, wanting to take some courses in mechanical engineering. He wanted some sort of general overview of engineering, which is very hard to get, cause what you really have is a lot of courses, in different areas (materials, design, mechanisms, stress, thermo, fluids, machines, electrical...) that complete that general view. Maybe something like "intro to systems engineering" could be what he was looking for. Yet, I recomend him a course in applied mechanics that I had just completed, where we studied a lot of different components and mechanical systems.
Thanks to algorithm of youtube which reccomended this amazing video by you, i myself wanted to do MEng in Systems and control but i found MPEng with mechatronic engineering to be more interesting. Ali you explained concepts of systems with complete architecture wonderful video.
One of the early pioneers in System Safety Engineering, after WWII, was my Godfather Lt.Col. Roger A. Lockwood. He was an a Founder of the Systems Safety Engineering Society. He was recognized by the Society a few years ago before his death.
I am a 42-year-old electronic engineer working as a NAVAIDS specialist. My role, particularly in maintaining and optimizing Instrument Landing Systems (ILS), demands knowledge in diverse fields such as telecommunications, phased array antennas, simulations (using Python, MATLAB, and JavaScript), power systems, embedded systems, MS-DOS, Linux, cybersecurity, networking, surveying, topography, map analysis, navigation, optimization, and IoT. I have mastered all these skills independently, without formal mentorship, while carrying out my responsibilities. Although my official job title is "Electronic Engineer," the scope of my work reflects that of a Systems Engineer in practice.
There are industrial engineering programs offered in many universities at undergraduate levels which I believe lay the fundamentals of systems engineering. People who want to pursue this path could start from industrial engineering programs and continue with systems on master and phd levels.
I’m in my last semester of ME undergrad at TAMUCC. Dr. Jose Baca is an awesome professor we have here that is trying to do this currently at an undergrad level in some way. I took mechatronics as an elective and he aims to use that class as a gateway to get young engineers acquainted with interdisciplinary fields and not just think of themselves as an EE or ME. He is big on modular designs and gets you thinking about the systems Engineer view of things early on while you’re building that foundation. I’d love to see a systems engineering approach for grad programs here in the future. Hopefully it will happen, dean Ma looks to be doing promising work to benefit future engineers here.
I have a bachelor in electrical electronics engineering and I am currently a software engineer in practice. I'd love to be a systems engineer and I think a masters in systems engineering is good. Reason is there needs to be a path for those that already have the relevant backgrounds so that they can consolidate their skills
Systems Engineering is probably one of the hardest engineering. Its when you have expertise in multiple disciplines of engineering and mathematics to such a point where you can tie it together into a full design. I am a chemical and electrical engineer and still working on being a systems engineer. Its kind of the A in steam (adding A to STEM), the art part of it, the design. Like hey I want to detect some poisen gas, how do I do this what kind of parts pieces, first principles. Its like a PFD level engineering but for ALL the disaplines, maybe you have electro mechanical, electronic chips, a chemical process, etc.
I have a bachelor's in Mechatronics Engineering. The one thing I regret is not building a strong foundation in Physics. I loved the idea of becoming a software engineer who programs robots/machines. I'm an app developer at present. IMO, the one crucial skill which helps you across diverse fields is the ability to mathematically model a concept thereby defining the problem and solve it. This is what is taught in System Dynamics and acts a transferable skill for fields like Machine Learning, Data Science, Operations Reseach, Management Science, Econometrics, Financial Engineering, Risk Management, Marketing Reasearch, Product Management, etc. Most fields are nowadays becoming algorithmic in nature. Systems Engineering = Mathematical Modeling + Domain Knowledge
Love the idea of making a masters for systems engineering (naturally pre-requiring a deep foundation in a given engineering discipline). I think it would be valuable because it could help students build the "connective tissue" to "move" and between disciplines and "drill down" into them as needed to solve an overarching goal. All while giving them the skill to "zoom out" and see the system as a whole and ask "what is it really doing? what is it for? where is it inefficient or becoming unstable?". With such a skillset, systems are able to be not only engineered, but imbued with cohesive intention - designed with a greater harmony (less loss) to achieve a specific purpose and reduce unintended side-effects. It's easy to see the value in that with a tad of effort in imagination. All created systems have designers and architects, some have engineers too.
I am watching your video for the first time Ali. Thanks for uploading this amazing video. I think a systems engineering masters program is really necessary because multi dimentional knowledge can really be proven better in real life problem solving because in real life if you try to solve one problem you need to check many boxes. Having proper knowledge of multiple fields will help an engineer to think and solve in a better and efficient way.
I am a mechanical engr. Got masters in mech engr designs. I think a well-thought systems engr masters program would be good for engineers willing to learn more about another discipline to theirs. Like a mech engr may like to understand more on electromagnets and circuits, using Maxwell's Equation.
I started out my career as a Land Surveyor who also developed skills in GIS and AutoCAD. Then I became a GIS Manager of a large city and was exposed to networking, systems administration, software development, and Web GIS. And now I am an IT Systems Engineer. Your career has been top-down and mine bottom-up. At some point I would like to complete my EE degree.. and get a similar PhD to yours.. around GPS and Signals Processing. But because I came from the field work (measurement path) my BA is in Geography and MS is in MCIS.
Yeah, this is what I like. I've been developing software for a long time, for many companies, a variety of experiences. It's been a great ride so far, but one of the main points of friction is that companies like to pigeon hole everyone, and for me that kills me. I enjoy going wide and deep on a lot of topics because the learning part is really fun. I have the most fun in tying everything together to make something new, and understanding the complete flow that makes it all work. But not everybody is used to that. Rather management often works by gathering all of individual component experts together and having them make the major decisions. This rarely works because many people have trouble going beyond their sphere. And similarly, there are situations where people expect you to swim in your own lane, so they get defensive or protective when they perceive some sort of encroachment. So a lot of my work involves giving some time for the problem to fully marinate, putting my ideas on paper and slowly garnering support for the full vision, and negotiating personalities so that everyone feels like this is their idea. And when we're done and succeeded, the process starts all over again. But because my experience crosses a lot of disciplines and I'm not pigeon holed into one particular silo, it takes more effort getting management to give my approach the same weight as those who stick to one discipline. It usually does work out eventually, but could be easier if more companies treated this as a skill on its own.
I think it is important because during undergraduate studies, you can deeply understand one of the fields you’ve been talking about . In a master's program, which is often more practical and experimental, you can gain a broader understanding of the systems.
I think that a systems engineering masters would be so useful, not just for engineers but for so many people. This is literally the skill that distinguishes the most successful and creative entrepreneurs / leaders / generals / you name it from the average. Can you please do an online course?
Ali habibi, I love your content, you talk about things in details. Like i never have the time urge to ask more questions because you answer everything. No clickbaity washed engineering content.
As one who began his career with a BSCS, obtained a BSEE while working and then later an MSCE/SSE and working as a software engineer, controls and measurements engineer, then moving into project management, functional management and then systems engineering and program management over a 32 year career, I hesitate to call software or systems engineering engineering in the most fundamental definition of the word. I believe the essence of modern engineering (not talking about train engineers or such), is the “application of science and mathematics” in the creation of something useful for humankind. My experience is that very, very few people with the title of software engineer or systems engineering really apply science and math in any meaningful way. There are a few exceptions, but the percentage is small as compared to electrical or structural engineers that use math and science on an almost daily basis. Software development is hard to categorize as it is part logic, part writing, part art, etc., but very little of it involves math or science. Systems engineering is really more management than engineering. It is more focused on requirements definition and communication and, again, involves very little math or science. I’m not knocking either field as I enjoyed working in both, but I still hesitate to call them engineering as I think that is really distorting the essence of engineering.
An Aerospace Engineering major is a good basis for space system engineering, as it provides exposure to orbital mechanics, upon which all space system engineering rests, along with all the fundamentals of structures, electronics, computer science etc . A Masters in Systems Engineering does not make up for deficiencies in undergraduate education in physics, applied math, and electronics, in my experience, which was also at JPL. In the end the degrees do not make the person, they just help.
Thank you for this explanation, as an automation engineer I found this interesting for me, since always I have to think about it as a system (input, output and decision)
I took a systems thinking course in college and it was awesome! It applies to so much. It’s essentially and language or tool you can use to look at the world from a different perspective
Have a bachelors in electronic systems engineering technology with a major in mechatronics and I work with every bit of solar technology you can think of except the panels themselves. I can confidently say that systems engineering is extremely helpful in everything I’ve encountered.
I think I finally understand my role. For context, I am completely self-taught software engineer. Although I did learn 3D production in college, I learned how to create games on my own. I more recently started to notice my skills set aligns well with systems engineering. I think if the college had a degree like this, I hope it might encourage other STEM related schools or programs to follow and show up earlier education because if someone explained systems engineering as you did here I would have resonated more with that degree or definition of engineering when I was younger. I might consider taking this degree if it becomes available! 🎉
In 1982 & even some years earlier I think IIT Bombay India had a Systems & Control Engineering 2yr Masters program, the objective was to get to the Mathematical basis of essentially disparate systems & treat them uniformly at that level in order to map the results back to those disparate systems.
As someone with trade school I do all in the house (Industrial Automation also my current Job) Electrical, mechanical, pneumatic, hydraulic,3d printing , PLC logic mostly Rockwell, HMI,Scada,Communication and started on Cisco CCNA,my passion is Natural Electrical Science or Electro-Magnetic world based on minimal resistance frequencies or so called resonance flux fields or waves that are everywhere and everything,I whould also look into the Nature to get complex systems work perfectly...Knowledge is the power.
Did undergrad mechanical engineering, class of 2018, so it's been awhile. Been considering grad school and this video came up. I think something like your master's in systems engineering might be perfect for what I'm looking to do. I enjoy ME, but I don't want to do just ME. I actually wanted to do physics originally but wasn't sure if I was up for grad school and all that back in community college. Oh the irony LOL.
I would say that a Master's program in systems engineering would be very awesome. After building some foundation in undergrad, this masters degree gives you the ability to think very broadly and also dive deep and approach each problem with a proper attitude. In my opinion, it's the ultimate sense of what an engineer should be and would definitely enroll in this program!
Wow, it's so interesting to hear systems engineering being described together with electrical engineering and mechanical engineering. In my world, it's usually mentioned together with software engineering, network engineering and data engineering. (mind you, I work in offices) In my world, the system is a layer that sits on top of the hardware layer but below the application (software) layer and so to become a good systems engineer you need to have a good understanding of those layers too... And the one who handles the system for day-to-day operations is called a systems administrator. Everything you've said are very different, yet very are relatable. Probably the one thing that I can't relate is "a systems engineer needs a good foundation in physics". From my perspective, for my work, everything boils down to logic, not physics. Even though these two fields of systems engineering both similarly try to make various components work together in a system, would it better to distinguish them? Physical systems engineering vs virtual systems engineering? Or factory/industrial systems engineering vs office/operations systems engineering?
I think this would be an awesome masters I would definitely take. I'm studying engineering physics for many of the reasons you described systems engineering to be important. I think expertise of the fundamental basics is the key to developing anything complicated, which like you said is just a combination of components with basic principles working towards a common goal.
I was looking for a systems engineering bachelors degree when I started college in 2020. I've just graduated with a degree in data science and would love to approach the field from a systems engineering perspective. I'd love to study these deep neural network architectures from a higher level now that I've driven so deeply into the math and programming of it all. Things change so fast in the field, it's important to know what model to use when, and how each new model architecture is distinct. I like to think of NNs as control systems in themselves. Lots of advancements in AI come from simply shifting the around the architecture. I think a Masters program in systems engineering could be very helpful for students like myself.
I’m currently doing a double degree in Electrical Engineering (Honours) and Physics. I’d say a masters program in systems engineering would be so valuable for students who have a passion for problem solving and want to go into industry where research is pioneered at the individual level. Without PhD students like yourself going full gas at a massive project like the high speed space Comms we don’t typically get to see the need for multidisciplinary engineers but in most cases it is their individual work which becomes the most valuable as they can conceptualise all aspects of a project at there own heightened level of understanding, and then feed it down the ladder.
In Europe Systems engineering is often called Automation, Automatic control or something similar. At my university it actually falls under Electrical engineering :P
It just means there's no system engineer in Europe. And it's not hard to see why. Systems engineer is basically a jack of all trades but master of none. They are not specialised experts in any engineering field nor better than business school grads in big project management. Its neither here nor there.
An area you didn’t touch on much is chemical systems (ex: oil and gas, pharma, etc.). Within this space, chemical engineering with a graduate degree in control theory will be most valuable
Hey, I think a Master’s program in systems Engineering is a valuable resource for many companies out there. I am a Graduate student getting my Master’s in Mechanical Engineering But the research area I am working in required me to not only have expertise in Thermodynamics but also in Electomagnitism because Transistors produce heat when you apply bias accross the channel. So I do understand why we need a program that can provide variety.
as the way i see it, i'm studying embedded systems on my own but as you said it is vital to get good at one thing and branch off from there so it would be wise to structure the learning material so that it follows The Three-Y's principle: Hierarchy involves dividing a system into modules, then further subdividing each of these modules until the pieces are easy to understand. Modularity states that the modules have well-defined functions and interfaces, so that they connect together easily without unanticipated side effects. Regularity seeks uniformity among the modules. Common modules are reused many times, reducing the number of distinct modules that must be designed. So that everything is foundational in nature yet should be followed in a certain order so that it's coherent to the student
for me as a CS sophomore undergrad, i feel system engg is a multidisciplinary thing - super vast and complex with dependence on a variety of fields like math electronics electrical and mechanical engg and software. theres often money involved as well. my goal in the future is to become a system engineer atleast if not in career as a hobbyist where i build complete machines from scratch from prototype to product. i think having a masters degree is cool cuz you get to work in this direction with a specialized focus. probably no place for me to comment on your idea of the master program but i feel skills where many field come to together is where most ppl are lacking. they cant put together a electronic circuit with super optimized software running on it that works on core mathematics and physics concepts. they rather form teams of large numbers and do the work. if your master program can fix this, i promise ill attend it when i am done with uni. As always thank you for sharing a valuable piece of information with us. great stuff 🔥🔥
Starting out as an engineer instead of picking one, schools should create a crash course that includes trifecta of engineering fields ex. mechanical electrical physics engineering and botany, medical, and physics and from there specialize in one for a while
For more chalkboard videos including the next one: ruclips.net/p/PLZZOG63zmCLE1eWvazftEMl8kMpXvSzst
"System engineering is not a jack of all trades, you need an expertise in one field and other things are built upon that." Nice saying!
I'm currently studying CS, and used to think it's kind of weak compared to some real engineering disciplines, but really being an expert at one fieid is also important if you want to do something more complex.
I have a Masters in Systems Engineering at Boston University College of Engineering.
tbh, system engineering is almost the only 'jack of all trades' in real sense
That’s what industrial engineers do, but then whether this is engineering or managment is a real question.
I have read papers in systems of systems engineering and met researchers in that field. They speak a pure nonsense to me because they have no proper field.
Systems engineering needs to be coupled with something to be valuable.
Can I become a systems engineer with a degree in electronics and computer science, and then a masters in electrical engineering?
I am a Systems Engineer. I studied Mechanical Engineering in College with a minor in Chemistry. Studied Astrophysics, Chemical Engineering, Computer Engineering, Network Engineering, Software Engineering, Telecommunications Engineering, and Cloud Engineering on my own. As well as working as a Fiber Optic Technician, Network Technician, then Telecommunications Engineer and Cloud Architect/Engineer, building my experience over the last 15 years. I now own and run a tech company that specializes in business technology solutions, and I oversee Engineers of all disciplines. It took a long time and a lot of effort to become what I am today. But I truly enjoy it, and I wouldn't trade it for the world.
Civil engineer here working as a systems engineer in IT 😁
May I ask when you self-studied all these subjects? Did you do that concurrently with your college education? If at least partially, what topics did you self-study while in undergrad?
I’m about to start a bachelors in mechanical engineering program and am infatuated and deeply interested by all those other disciplines you mention. I’d really appreciate your input.🙏
@@Parsimoniouspenguin1 Yes. Exactly. I have been reading extensively since I was in my mid twenties. I graduated with an associate degree in landscape development when I was 25. I switched from a business major to mechanical engineering at 30yo for my second degree. I admit I am a bit of a high performer. I was running a landscape company and working on fiber optic transmission line installation while studying mechanical engineering and chemistry, and still read a lot outside of school. That mixed with the many videos available on RUclips. And the hands on experience I gained in the field of IT and telecommunications. Then got certified in cloud architecture. I have a unique experience as someone who has worked in almost every phase of IT, from long range data transmission, to structure cabling of large building projects, to networking, to all sorts of equipment installation and programming to Cloud Computing. One can learn anything if they are willing to dedicate their time to it. The hands on experience is key, but the experience can be drastically improved by always studying as well. As an engineer, I am continually learning. It’s easy if you are passionate and have a thirst for knowledge. If not you may get burned out. It’s definitely not for everyone, but if you love it, you look forward to it. I love solving problems. And everyday I am faced with new ones. lol. Good luck with your studies. And go at your own pace, if you’re dedicated you’ll get there. And if you fail, do it agin until you succeed. Never give up.
do you take interns want to learn from you !!
@@C-1-FRYAwesome story man! You’re incredibly talented. What made you want to switch from landscaping into engineering??
FYI, most Mechatronics Engineering programs, at least the good ones, are effectively Systems Engineering programs.
Likewise a lot of Aero and BME programs follow a systems Engineering framework
I will likely be studying Cyber Physical Systems Engineering for my bachelor's, which used to be called Embedded Systems and IoT Engineering. They go over all the required maths and mostly it's technical. Programming and Circuits are huge. Essentially it's all learned to build an innovative product, which is essentially a system. I do hope though, to be able to do a Master's in Data Science, specifically ML + AI tool development... That'll hopefully allow me to build lots of systems that I can only dream of right now :(
Same as Electrical Engineering
Many Systems Engineering roles require the knowledge of virtualization/containerization, active directory, group policy, IaC, clustering & loadbalancing, cloud computing platforms (AWS/Azure/etc), CI/CD, CDN, backups, bigdata, web servers, database servers, DNS servers, DHCP servers, email servers, VOIP servers, file servers, etc, etc (most of which probably aren't included in Mechatronics Engineering programs). Some roles require a heavier emphasis on software engineering or network engineering or data engineering or even mechatronics engineering. Some leans more towards DevOps, while others towards SRE. It all depends on what company you work in and what system they need to get working.
I've been working as a systems engineer for a decade now without knowing a single thing about mechatronics engineering. And that's why I think Mechatronics Engineering programs are called Mechatronics Engineering programs (and not a Systems Engineering program).
@@senantiasa Those topics are included in MTE programs around my area. Systems Engineering as an academic program is also frankly quite vague so that could amount to practically anything depending on what the curriculum actually entails.
And above that, one can teach themselves any Engineering concept they were not taught in class if they cared to do so for their own benefit.
My Dad was a systems engineer and learned everything on the job over the last 40yrs before retiring recently. No university or "formal education". He started in the Navy, eventually managed maintenance crews at Disneyland for a few years and then ended up doing more contract work for the Navy before retiring. He has always been handy, built or fixed anything he could get his hands on and just has an awesome mind for seeing the big picture aka systems. You and other Engineers are the kind of problem solvers this world truly needs. Thanks for the cool content. 🤙
There are lots of jobs titled "Systems Engineer" that are not the kind of SE discussed in this video.
Look at the description given by INCOSE to really compare apples to apples with the ideas in this video.
@@davidh4374but there are in fact systems engineering jobs that don’t require formal degrees and do actually engage in SE processes
He wasn't an engineer. Sounds like a technician handyman to me. You can't become an engineer with an engineering degree.
@@davidh4374 lot of defense contracting and DoD jobs willing to hire non-engineers as systems engineers. There’s intimate knowledge of the INCOSE handbook by these companies and agencies. Usually, however, they’re not getting hired to do something like design work. CONOPs, testing to requirement validation, sustainment of a deployed system, and obsolescence planning is usually the purview of these non-engineer systems engineers.
My grandfather became an EE through his tenure in the navy. Radio operator. He always claimed his navy service was the best thing that ever happened to him. Respect to your dad
Vision without action is a daydream. Action without vision is a nightmare.
I am a mechanical engineer that works in electronics development (RF inverters and amplifiers). This kind of discipline is critically needed to come up with good design approaches for tightly integrated systems. For example, it’s almost impossible to have a truly small or lightweight system without a system architect that is looking at how to design the system electrically, but also consider it mechanically, identifying newer, smaller parts. We don’t have this role at my job (we have systems engineers but they do not do this architecting role sadly), so it turns into a haphazard back and forth during detailed design. Or, Even worse, it becomes a straight out adversarial “that’s not my job” relationship between disciplines which results in bloated, disjointed design. So yes this degree would be very useful.
systems in systems engineering by convention refers to i.t based or any application that takes in data and CRUD type actions and the engineer is an administrator, creator of such an app or deployment of an app or tech stack. What you are asking of your 'systems engineers' is a LOT. src: im a principal systems engineer)
"System engineering is basically the engineering of systems" - this could be the most engineering way of defining a term I heard in a long time.
I used to do this trick in my uni vivas when I didn’t fully knew the answer of a question 😂😂
Most real systems out there are multidisciplinary and extremely complex, that is why experts are needed for each system. Randomness is inherent to these systems. Modelling uncertainties is part of experts jobs
Nothing is random, everything follows strict cause and effect
Isn't systems engineer a jack of all trades but master of none? Not specialised experts in any engineering field nor better than business school grads in big project management. Neither here nor there.
@@grapefruitsyrup8185 problem with both of those niche fields are that they really never understand the big picture. Specialized experts in the engineering field are only sought for that specific field of expertise. and with business school grads in project management, they often mess up the project plan and requirments because they only know how to talk business but no idea how to actually implement business solutions if its more complex than an excel sheet (which is usually the case). Which is why computer science, data engineers, software engineers, technical (buzzword) roles, alll poppped up. because they need expert generalists to be the glue
It's unbelievable how valuable it is to get a peek into your thought process and the way you approach these things.
Hey Ali, you’re quite literally living the dream of what I want to be, albeit starting from a later age of 30 (!). Thanks for forging a path for those of us coming in the next generation of engineers. We need more communicator-engineers like you, who are able to inspire others by example and showing them the real brilliance of engineering- the mindset and the disposition to solve any problem that comes their way.
absolutely :)
Really enjoyed your take on systems engineering. I agree 100% that you need a solid core and experience in the field. The “stack” you mention is exactly that. I was chief systems engineer for a navy sonar system years ago. You absolutely need the fundamentals and a broad view of many disciplines. I too have a BSEE/MSEE background but had to cross over into many other engineering and science topics. Great job explaining this.
Great input, thank you!!
One of the universities in Norway has a masters in systems engineering. Looking at the courses and talking to friends who have finished it, it seems like a REALLY nice addition to their bachelors. The added benefit of the master's is that it works with the industry. Instead of 2 years in uni, you spend 3, but work 50% in industry, and your workplace works with you and the uni to implement the Systems courses into your workday. I'm not sure how common this is globally, but it seems to be a fantastic solution. The 50% work is obviously paid like any engineer. The master's degree in Systems Engineering at this university has been around for quite a while, so I think (again, based on what friends say and the industry which works with the students) that it has both good teachers and facilities, and that it kept relevant without big gaps in what you'd expect from a proper Systems Engineer when they finish.
i know norway is a very english friendly country, is the curriculum taught in the universities in norwegian or english?
👍
@@nate7243 Typically English if there are any non-norwegians present, especially at graduate level. That said, some greedy dipshit of an """"""education minister""""""(without a degree even, go figure) recently made it so non-schengens now have to pay absurd tuitions(like $15k or even more), not like we liked attracting smart people anyway....
And then your sys eng job will be offshored to India 😂
@@bl-nb8fo skill issue
Thanks for this insight. I have always wondered what systems engineers do, and now I have a clearer understanding. I have an ME degree and am about to pursue a master's in systems engineering, focusing on industrial engineering and sustainable technologies. This will really help with my future pursuits.
This reminds me of how operations research is super underrated. Hidden within industrial engineering or mechanical engineering departments and is essentially a major in optimization which as we all know is critical today with AI systems.
I once showed my transcript with all my OR coursework during an interview for an entry-level AI position.
The recruiter responded "I don't see anything here that's relevant to this job description."
I understood this was the wrong company to apply to and moved on.
Correct. Ga Tech has ISYE - Industrial and Systems Engineering
I clicked on this video wondering when I would hear the word “zoom” and that happened around the 3:30 min mark. Great video - from my point of view as a power electronics engineer with experience in SW & mechanical too, what makes a great system engineer is the capacity to “effortlessly” and confidently zoom in and zoom out of systems & subsystems. Many engineering disciplines are fundamentally defined by differential equations in matrix form, which are not conceptually that different, regardless of the engineering area. Always having an engineering mindset, zooming in and breaking problems down in simple forms, then putting the pieces together and progressively zooming out more and more is how an intimate understanding of a working system is achieved - at the end of the day, everything from a class A amplifier to a car is a system. Great points!
spot on! thank you for sharing, I can see you are already quite good yourself!
Hi Ali, I’m an undergraduate Aerospace Systems Engineering student in my 3rd year, and your video has been so helpful. I would appreciate it, as would many others, if you made more videos like this. Also, if you could include real life projects and career related content in the future, that would be awesome. Books and materials would also be appreciated. Thanks Ali.
Im a junior in mche . I like systems engineering. Im more of an innovator type person. I always have new ideas. It could be a bed to utensel or electronics. I came up with my first electronic device converting mechanical motion to signal and current. I know some matlab. Still trying to get great at it. It takes time to learn a language like that. Love matlab and love your content. You have a firm grasp of this electronics. Keep making stuff like this or should i say electronic physics was awesome. Im finished physics i wish you had explained it to me like that my first time.
Materials science is awesome stuff too.
I love seeing other engineers that are as passionate about their problem domain as you are.
My high school has an engineering program where one of the upper level classes is a year studying systems engineering and manufacturing systems in collaboration with some companies in real world industries. glad to see it will most likely be useful in the future.
I would love this Master. I finished an apprenticeship as a design engineer and now I start my Bsc in EE. That would be a perfect combination of the two I think.
Hey, I'm an electrical engineer with experience in FPGAs, Hardware Development and a little bit of circuit design. I've always been fascinated by space and especially big picture engineering and I plan to go back for a masters in space systems engineering. Thank you for such a valuable video!!
When I studied mechanical engineering as an undergrad, in our final year we had an Introductory Systems Engineering subject.
It was as joint subject with other mechatronic engineering students. This forced us to work together and merge our expertise to identify, specify and design a system in a project.
Just helped with the methods and strategies one would use to execute a project from start to end.
Nice video showcasing practical experience of building a system. Only thing I would like to add is to highlight is that systems engineering is more of a structured process which enables problem definition, requirement gathering (functional, non functional, performance, reliability, availability, maintainability, safety, HMI, operational ), collaboration between stakeholders, ensures traceability throughout system lifecycle and lastly , making choice of technology as per the problem and NOT the solution!
Great content! As an Electrical engineer and a practicing control systems engineer in the Oil & Gas industry for almost 30 years, what's Ali's covering is great! 2 thumbs up and hats off to this young man! 👍👍👍👍
Even working on my super simple year 2 project, i noticed its quite a puzzle figuring out how to arrange components so that everything works smoothly. I didnt know that was its own branch of engineering til i found your video. I wish it gets more popular
Big support from mech engineer from italy!
I work with lean principles and process improvement and your video was recommended to me by YT. One of the best presentations I've ever seen, with a very detailed explanation of the idea in plain English. Congratulations and thanks for sharing this.
Glad it was helpful!
This new video style is fantastic!
I have got a lot of things in this video , thank you amazing ALI.
Happy to hear that!
Agreed @@alithedazzling
Excellent description. Never mind the mastery of linear differentials and the second order nature of, well, everything.
Hey , Ali your channel was like a gateway for me to get into engineering , love learning about all the topics you explain , today started my journey in BE Information Technology, your channel has already guided me on what and how should I spend time in my 1st year, keep uploading man great content
This is a massively important thing and I commend you for addressing this topic, can you please expand further or teach more on it. This era needs this desperately, please fill this void.
can you tell me more?
@ I have my own domain of skills but have been trying to learn programming and engineering to help realize those goals, I have quickly realized the whole begets the means. So having a cohesive systems engineering framework became an obvious rabbit hole to help guild all domains I was trying to integrate cohesively
this is too verbose for no reason. I have a background in visual design, however instead of just making concepts or designs for fictional things I would like to build something complete. It has brought me down the rabbit hole of programming and engineering. However, when deciding what to build and how - I quickly started to realize I cant build parts without understanding how they will all come together. So I was looking into system engineering. To expand further I enjoy looking at whole systems and cross disciplinary solution - so understanding how to build cohesive systems across different domains intruiges me. There is very little content on it though.
This is a great video! I work at an aerospace company but I work in IT/SWE. I saw we were hiring for a Sys Engineer and was confused that none of the requirements mentioned cloud engineering, proficiency in multiple languages, networking skills, skills in multiple operating systems, etc. It then dawned on me - a systems engineer in my profession is completely different from an “Aerospace Systems Engineer”. Many different systems at play, but my idea of engineering a system has to do more with building a system like an application, or a program, or a scalable way to deploy an upgrade or software or keep track of computer inventory, etc. I have a deep understanding of programming (particularly Windows, but am skilled in Linux). To your credit, I became very good at one thing before I started touching systems at a larger scale.
It also dawned on me that I’m essentially the full stack dev/systems engineer to my tech team… and that I might want to update my resume and start looking for a different job. lol.
Two years into a hypersonic flow fluid dynamics PhD and I’m starting to feel like a SE with all the disciplines involved: aerothermochemistry, materials science, aerodynamics, radiation and now global sensitivity analysis and uncertainty quantification for all these disciplines.
I’ve never had a RUclips video feel so relevant to me lol. I just started a new job as a THz radar systems engineer a week ago. Good to see mmWave/THz representation on RUclips!
nice! where?
I am control and instrumentation engineering student and I was delighted to see someone talking about my major
My electrical engineering program has a specialization in systems engineering in undergrad, I'm excited to get into more advanced courses in it soon. We're learning about integrated control systems and control engineering as well as signal processing, VLSI, and quite a few other topics. Very happy to be in this program.
My aerospace undergrad program had a systems engineering discipline and I took umbrage with it for the exact reason you specify. I would offer my view that what you described isn’t necessarily a “systems engineer” in the classical definition but an “engineer with systems thinking.” The average systems engineering profession in my experience is full of requirements, verification and validation, and other things that are very “2D.” This video is great advice for anyone who wants to have a framework to be an effective engineer no matter what they do, because being able to interface with a system effectively will reduce project development time and cost and will allow you to expand your skillset as an engineer in general.
Very inspiring video! If systems engineering got popular, engineers who each specialize in different domains would be able to work with each other on any aspect of any technology… think about how much innovation would happen there!
Thank you Dr.Ali keep more videos coming I am inspired by your videos.
Glad to hear that!
This is actually an issue I noticed in the construction design management (CDM) industry I work in as a project engineer having studied mechanical engineering I struggle with keeping tabs with other disciplines despite the need. Noticed our company and similar companies in our space struggle in the engineering control roles liasoning between M&E and structural disciplines as the senior project engineers and managers sorta just expect the mechanical, electrical and structural engineers to sit down and have meetings with contractors related to producing and delivering these packages on guiding them according to our expectations. The issue being a lot of the things discussed by one major are either not picked up by other majors in prior with accuracy so we struggle with managing design expectations with contractors which takes longer than expected or struggling to deliver changes from one contractor to the other with the correct level of detail, possibly shaving off months of delay with simply a CDM systems engineer holding/running the meeting with the subbies instead delivering explaining the entire systems layout updates. As there are standards and regulations to abide by minor changes cause delays in fixing to account for otherwise.
It is weird but the way the current system has adapted is that the sub contracts who are supposed to just be delivering the package are essentially doing that part for us taking on that extra duty's burden.
I’m actually a second year engineer and want to go into electrical engineering and specialize in mechatronics but I think what I have been doing is just the same thing you described by getting really good in one area and then branching out which sort of a being a polymath like Da Vinci. Thanks Ali
Systems Engineer for NOAA here. I started as a meteorologist and gained satellite expertise as I used the products derived from their observations. That allows me to delve deep into requirements for satellite programs from a top-down view. I'm currently pursuing my Masters of Space Systems from Embry Riddle university. I agree with your assessment of Systems Engineering, I don't think there should be a Bachelors course for it. You need a foundation to build upon for a systems mindset. I do find my Masters course work to be beneficial though.
I love engineering, and I am really interested in systems where mechanics, electronics, and software meet and work in a symphony. I am a Mechatronics Engineering student. I chose this engineering because I thought this would be the best way for me to learn every bit of these components. If there were an option called systems engineering, I would jump to this option. And based on what little I know, my humble opinion is that if this idea becomes real, it should be based on electronics. Software is easy to grasp. Mechanics is a field in which humans relate very easily. But the electronics is a completely different world.
Worked as a Linux Systems Admin and currently a Cloud Engineer and man do I love systems engineering. Just to understand how components are connected together and having a system finally work is so satisfying. You can literally apply Systems Engineering to so many different engineering paradigms which is what makes it so fascinating to me. Curious on everyone else's perspective.
Formalized abstraction of devices and the interactions between
Super important topic here
Truly good systems engineers have depth in all disciplines. Only they, by definition, can truly derive the optimal solution and guard against instabilities and real-world non-idealities
Cool video
This video taught me what my job has been for the last few years. Well articulated, thank you.
P.S. Fun fact: one can do system engineering without ever knowing UML.
recently, I had a friend who is doing Physics, wanting to take some courses in mechanical engineering. He wanted some sort of general overview of engineering, which is very hard to get, cause what you really have is a lot of courses, in different areas (materials, design, mechanisms, stress, thermo, fluids, machines, electrical...) that complete that general view. Maybe something like "intro to systems engineering" could be what he was looking for. Yet, I recomend him a course in applied mechanics that I had just completed, where we studied a lot of different components and mechanical systems.
Thanks to algorithm of youtube which reccomended this amazing video by you, i myself wanted to do MEng in Systems and control but i found MPEng with mechatronic engineering to be more interesting. Ali you explained concepts of systems with complete architecture wonderful video.
One of the early pioneers in System Safety Engineering, after WWII, was my Godfather Lt.Col. Roger A. Lockwood. He was an a Founder of the Systems Safety Engineering Society. He was recognized by the Society a few years ago before his death.
I am a 42-year-old electronic engineer working as a NAVAIDS specialist. My role, particularly in maintaining and optimizing Instrument Landing Systems (ILS), demands knowledge in diverse fields such as telecommunications, phased array antennas, simulations (using Python, MATLAB, and JavaScript), power systems, embedded systems, MS-DOS, Linux, cybersecurity, networking, surveying, topography, map analysis, navigation, optimization, and IoT.
I have mastered all these skills independently, without formal mentorship, while carrying out my responsibilities. Although my official job title is "Electronic Engineer," the scope of my work reflects that of a Systems Engineer in practice.
There are industrial engineering programs offered in many universities at undergraduate levels which I believe lay the fundamentals of systems engineering. People who want to pursue this path could start from industrial engineering programs and continue with systems on master and phd levels.
I’m in my last semester of ME undergrad at TAMUCC. Dr. Jose Baca is an awesome professor we have here that is trying to do this currently at an undergrad level in some way. I took mechatronics as an elective and he aims to use that class as a gateway to get young engineers acquainted with interdisciplinary fields and not just think of themselves as an EE or ME. He is big on modular designs and gets you thinking about the systems Engineer view of things early on while you’re building that foundation. I’d love to see a systems engineering approach for grad programs here in the future. Hopefully it will happen, dean Ma looks to be doing promising work to benefit future engineers here.
Great video! There’s no videos out there that explains systems this well!
I have a bachelor in electrical electronics engineering and I am currently a software engineer in practice.
I'd love to be a systems engineer and I think a masters in systems engineering is good. Reason is there needs to be a path for those that already have the relevant backgrounds so that they can consolidate their skills
Just started working at a new space company, never fully understood how the system engineers operated, but now I do! :)
Systems Engineering is probably one of the hardest engineering. Its when you have expertise in multiple disciplines of engineering and mathematics to such a point where you can tie it together into a full design. I am a chemical and electrical engineer and still working on being a systems engineer.
Its kind of the A in steam (adding A to STEM), the art part of it, the design. Like hey I want to detect some poisen gas, how do I do this what kind of parts pieces, first principles. Its like a PFD level engineering but for ALL the disaplines, maybe you have electro mechanical, electronic chips, a chemical process, etc.
I have a bachelor's in Mechatronics Engineering. The one thing I regret is not building a strong foundation in Physics. I loved the idea of becoming a software engineer who programs robots/machines. I'm an app developer at present.
IMO, the one crucial skill which helps you across diverse fields is the ability to mathematically model a concept thereby defining the problem and solve it. This is what is taught in System Dynamics and acts a transferable skill for fields like Machine Learning, Data Science, Operations Reseach, Management Science, Econometrics, Financial Engineering, Risk Management, Marketing Reasearch, Product Management, etc. Most fields are nowadays becoming algorithmic in nature.
Systems Engineering = Mathematical Modeling + Domain Knowledge
Love the idea of making a masters for systems engineering (naturally pre-requiring a deep foundation in a given engineering discipline). I think it would be valuable because it could help students build the "connective tissue" to "move" and between disciplines and "drill down" into them as needed to solve an overarching goal. All while giving them the skill to "zoom out" and see the system as a whole and ask "what is it really doing? what is it for? where is it inefficient or becoming unstable?". With such a skillset, systems are able to be not only engineered, but imbued with cohesive intention - designed with a greater harmony (less loss) to achieve a specific purpose and reduce unintended side-effects. It's easy to see the value in that with a tad of effort in imagination.
All created systems have designers and architects, some have engineers too.
I am watching your video for the first time Ali. Thanks for uploading this amazing video. I think a systems engineering masters program is really necessary because multi dimentional knowledge can really be proven better in real life problem solving because in real life if you try to solve one problem you need to check many boxes. Having proper knowledge of multiple fields will help an engineer to think and solve in a better and efficient way.
I am a mechanical engr. Got masters in mech engr designs. I think a well-thought systems engr masters program would be good for engineers willing to learn more about another discipline to theirs. Like a mech engr may like to understand more on electromagnets and circuits, using Maxwell's Equation.
I started out my career as a Land Surveyor who also developed skills in GIS and AutoCAD. Then I became a GIS Manager of a large city and was exposed to networking, systems administration, software development, and Web GIS.
And now I am an IT Systems Engineer.
Your career has been top-down and mine bottom-up. At some point I would like to complete my EE degree.. and get a similar PhD to yours.. around GPS and Signals Processing.
But because I came from the field work (measurement path) my BA is in Geography and MS is in MCIS.
Great content btw!
That's a very interesting path!
Can I become a systems engineer with a degree in electronics and computer science, and then a masters in electrical engineering?
please keep on making these videos. These videos light my dream path! thank you so much Ali
Glad you like them!
Yeah, this is what I like. I've been developing software for a long time, for many companies, a variety of experiences. It's been a great ride so far, but one of the main points of friction is that companies like to pigeon hole everyone, and for me that kills me. I enjoy going wide and deep on a lot of topics because the learning part is really fun. I have the most fun in tying everything together to make something new, and understanding the complete flow that makes it all work. But not everybody is used to that. Rather management often works by gathering all of individual component experts together and having them make the major decisions. This rarely works because many people have trouble going beyond their sphere. And similarly, there are situations where people expect you to swim in your own lane, so they get defensive or protective when they perceive some sort of encroachment. So a lot of my work involves giving some time for the problem to fully marinate, putting my ideas on paper and slowly garnering support for the full vision, and negotiating personalities so that everyone feels like this is their idea. And when we're done and succeeded, the process starts all over again. But because my experience crosses a lot of disciplines and I'm not pigeon holed into one particular silo, it takes more effort getting management to give my approach the same weight as those who stick to one discipline. It usually does work out eventually, but could be easier if more companies treated this as a skill on its own.
Nice explanation about system engineering! Oriented completely in control systems. I'm also learning this for automotive applications. Thank you bro!
Love your MSc in systems engineering! Good idea!
I think it is important because during undergraduate studies, you can deeply understand one of the fields you’ve been talking about . In a master's program, which is often more practical and experimental, you can gain a broader understanding of the systems.
Deep understanding of Basics is the Key to advancement!
I think that a systems engineering masters would be so useful, not just for engineers but for so many people. This is literally the skill that distinguishes the most successful and creative entrepreneurs / leaders / generals / you name it from the average. Can you please do an online course?
This is so good work, and easy to understand!!
now I'm going to watch everything in your channel lol! thank you!
Ali habibi, I love your content, you talk about things in details. Like i never have the time urge to ask more questions because you answer everything. No clickbaity washed engineering content.
As one who began his career with a BSCS, obtained a BSEE while working and then later an MSCE/SSE and working as a software engineer, controls and measurements engineer, then moving into project management, functional management and then systems engineering and program management over a 32 year career, I hesitate to call software or systems engineering engineering in the most fundamental definition of the word. I believe the essence of modern engineering (not talking about train engineers or such), is the “application of science and mathematics” in the creation of something useful for humankind. My experience is that very, very few people with the title of software engineer or systems engineering really apply science and math in any meaningful way. There are a few exceptions, but the percentage is small as compared to electrical or structural engineers that use math and science on an almost daily basis. Software development is hard to categorize as it is part logic, part writing, part art, etc., but very little of it involves math or science. Systems engineering is really more management than engineering. It is more focused on requirements definition and communication and, again, involves very little math or science. I’m not knocking either field as I enjoyed working in both, but I still hesitate to call them engineering as I think that is really distorting the essence of engineering.
An Aerospace Engineering major is a good basis for space system engineering, as it provides exposure to orbital mechanics, upon which all space system engineering rests, along with all the fundamentals of structures, electronics, computer science etc . A Masters in Systems Engineering does not make up for deficiencies in undergraduate education in physics, applied math, and electronics, in my experience, which was also at JPL.
In the end the degrees do not make the person, they just help.
i'm a computer systems engineering student!! loved the video
Thank you for this explanation, as an automation engineer I found this interesting for me, since always I have to think about it as a system (input, output and decision)
I took a systems thinking course in college and it was awesome! It applies to so much. It’s essentially and language or tool you can use to look at the world from a different perspective
Have a bachelors in electronic systems engineering technology with a major in mechatronics and I work with every bit of solar technology you can think of except the panels themselves. I can confidently say that systems engineering is extremely helpful in everything I’ve encountered.
I think I finally understand my role. For context, I am completely self-taught software engineer. Although I did learn 3D production in college, I learned how to create games on my own. I more recently started to notice my skills set aligns well with systems engineering. I think if the college had a degree like this, I hope it might encourage other STEM related schools or programs to follow and show up earlier education because if someone explained systems engineering as you did here I would have resonated more with that degree or definition of engineering when I was younger. I might consider taking this degree if it becomes available! 🎉
that's a very good video for juniors who are trying to do something but don't know what to do. thanks for sharing your story!!
Really helpful stuff.! Gave a clear idea about what I was searching for. thanks :)
I actually started as a mechanical systems engineer. Now i work as a software developer. I hope to return to systems engineering some day :)
In 1982 & even some years earlier I think IIT Bombay India had a Systems & Control Engineering 2yr Masters program, the objective was to get to the Mathematical basis of essentially disparate systems & treat them uniformly at that level in order to map the results back to those disparate systems.
As someone with trade school I do all in the house (Industrial Automation also my current Job) Electrical, mechanical, pneumatic, hydraulic,3d printing , PLC logic mostly Rockwell, HMI,Scada,Communication and started on Cisco CCNA,my passion is Natural Electrical Science or Electro-Magnetic world based on minimal resistance frequencies or so called resonance flux fields or waves that are everywhere and everything,I whould also look into the Nature to get complex systems work perfectly...Knowledge is the power.
Did undergrad mechanical engineering, class of 2018, so it's been awhile. Been considering grad school and this video came up. I think something like your master's in systems engineering might be perfect for what I'm looking to do. I enjoy ME, but I don't want to do just ME. I actually wanted to do physics originally but wasn't sure if I was up for grad school and all that back in community college. Oh the irony LOL.
Congrats Ali adn thank you for spreading knowledge !
I would say that a Master's program in systems engineering would be very awesome. After building some foundation in undergrad, this masters degree gives you the ability to think very broadly and also dive deep and approach each problem with a proper attitude. In my opinion, it's the ultimate sense of what an engineer should be and would definitely enroll in this program!
Wow, it's so interesting to hear systems engineering being described together with electrical engineering and mechanical engineering. In my world, it's usually mentioned together with software engineering, network engineering and data engineering. (mind you, I work in offices) In my world, the system is a layer that sits on top of the hardware layer but below the application (software) layer and so to become a good systems engineer you need to have a good understanding of those layers too... And the one who handles the system for day-to-day operations is called a systems administrator.
Everything you've said are very different, yet very are relatable. Probably the one thing that I can't relate is "a systems engineer needs a good foundation in physics". From my perspective, for my work, everything boils down to logic, not physics.
Even though these two fields of systems engineering both similarly try to make various components work together in a system, would it better to distinguish them?
Physical systems engineering vs virtual systems engineering?
Or factory/industrial systems engineering vs office/operations systems engineering?
The foundation example is spot On. The thingbabout string foundation is its the most gruelling part of anything to get through
I think this would be an awesome masters I would definitely take. I'm studying engineering physics for many of the reasons you described systems engineering to be important. I think expertise of the fundamental basics is the key to developing anything complicated, which like you said is just a combination of components with basic principles working towards a common goal.
I was looking for a systems engineering bachelors degree when I started college in 2020. I've just graduated with a degree in data science and would love to approach the field from a systems engineering perspective. I'd love to study these deep neural network architectures from a higher level now that I've driven so deeply into the math and programming of it all. Things change so fast in the field, it's important to know what model to use when, and how each new model architecture is distinct. I like to think of NNs as control systems in themselves. Lots of advancements in AI come from simply shifting the around the architecture. I think a Masters program in systems engineering could be very helpful for students like myself.
I’m currently doing a double degree in Electrical Engineering (Honours) and Physics. I’d say a masters program in systems engineering would be so valuable for students who have a passion for problem solving and want to go into industry where research is pioneered at the individual level. Without PhD students like yourself going full gas at a massive project like the high speed space Comms we don’t typically get to see the need for multidisciplinary engineers but in most cases it is their individual work which becomes the most valuable as they can conceptualise all aspects of a project at there own heightened level of understanding, and then feed it down the ladder.
In Europe Systems engineering is often called Automation, Automatic control or something similar. At my university it actually falls under Electrical engineering :P
Indeed
It just means there's no system engineer in Europe. And it's not hard to see why.
Systems engineer is basically a jack of all trades but master of none. They are not specialised experts in any engineering field nor better than business school grads in big project management. Its neither here nor there.
Great video! I learned a lot honestly and there was no fluff. Good stuff.
You knew this guy was legit when he whipped out the “such that” in his systems explanation 1:25
Oh man! I was looking copper and I found gold. Thank you for your explain, I've suscribed at your channel. Saludos desde México
thanks a lot, glad you like the video! un abrazo fuerte
An area you didn’t touch on much is chemical systems (ex: oil and gas, pharma, etc.). Within this space, chemical engineering with a graduate degree in control theory will be most valuable
Hey, I think a Master’s program in systems Engineering is a valuable resource for many companies out there.
I am a Graduate student getting my Master’s in Mechanical Engineering But the research area I am working in required me to not only have expertise in Thermodynamics but also in Electomagnitism because Transistors produce heat when you apply bias accross the channel. So I do understand why we need a program that can provide variety.
fun energetic video. rollercoaster of new developments certain to follow
as the way i see it, i'm studying embedded systems on my own but as you said it is vital to get good at one thing and branch off from there so it would be wise to structure the learning material so that it follows The Three-Y's principle:
Hierarchy involves dividing a system into modules, then further subdividing each of these modules until the pieces are easy to understand.
Modularity states that the modules have well-defined functions and interfaces, so that they connect together easily without unanticipated side effects.
Regularity seeks uniformity among the modules. Common modules are reused many times, reducing the number of distinct modules that must be designed.
So that everything is foundational in nature yet should be followed in a certain order so that it's coherent to the student
for me as a CS sophomore undergrad, i feel system engg is a multidisciplinary thing - super vast and complex with dependence on a variety of fields like math electronics electrical and mechanical engg and software. theres often money involved as well. my goal in the future is to become a system engineer atleast if not in career as a hobbyist where i build complete machines from scratch from prototype to product. i think having a masters degree is cool cuz you get to work in this direction with a specialized focus. probably no place for me to comment on your idea of the master program but i feel skills where many field come to together is where most ppl are lacking. they cant put together a electronic circuit with super optimized software running on it that works on core mathematics and physics concepts. they rather form teams of large numbers and do the work. if your master program can fix this, i promise ill attend it when i am done with uni. As always thank you for sharing a valuable piece of information with us. great stuff 🔥🔥
Starting out as an engineer instead of picking one, schools should create a crash course that includes trifecta of engineering fields ex. mechanical electrical physics engineering and botany, medical, and physics and from there specialize in one for a while