#Systems engineering

[engineering]

alias please=sudo

Keeping a site like Tumblr alive and snappy for you to post at a moment’s notice, all day and night, is no small feat. Pesky crabs sneak into our data centers and cut cables all the time…

If you want to help our small but excellent systems team, want to work from anywhere, and are deep into nginx, mysql, kubernetes, and caching, join us in this adventure. Or, if you have a friend or a colleague who’s good with servers, send them our way.

[curvymommy70]

Welcome to Reliability Engineering as a part of Systems Engineering.

[mxy-makes]

I'm so excited for next year!

So I'm a first year teacher and I was given Systems Engineering for year 8s and 9s with no experience (yay).

What is Systems Engineering? It's essentially engineering and it can be an awesome class if done right.

So I got assigned these classes and the year 8s have a curriculum which is 3D designing and printing and that is awesome but the year 9s have nothing.

Like nothing at all.

So I go to the internet on search of something fun and I find an escape room project.

"Escape room project? That sounds fun" I thought.

It was but it was also a disaster.

Despite the disaster, let me tell you what my kids made (out of cardboard):

Working safes

Full on puzzles that took me a while to solve (and I'm pretty good at puzzles too)

A giant sword (its pretty solid and has been swung around and isnt close to breaking)

These kids took what I gave them and ran with it.

With the year 8s who are using Fusion360, it's a shame that the 3D printer at my school isn't working because some stuff they have designed is amazing. I told them to push themselves and boy did they.

Anyway the Victorian curriculum in Australia has been updated so someone needs to write new assignments and stuff and guess who's AuADHD thought it would be a good idea to hyperfocus on it?

Me. My brain did.

So now I've written the years 8-10 Systems Engineering curriculum and let me tell you what my students will be doing next year:

Year 8 is going to be doing 3D modelling and printing (why mess with something that's working so well?) and designing systems to help communities (global citizenship for the win).

Year 9s are going to be doing the escape room (its going to be so much better now I know what I'm doing) and it's going to be D&D themed and they'll also be doing a research task (because the curriculum asks for it).

And the year 10s are going to be making robot cars that they will race which is going to be so much fun. (And some mechanical stuff because curriculum).

I just can't wait.

[agilesyseng]

“A complex system that works is invariably found to have evolved from a simple system that works. The inverse proposition also appears to be true: A complex system designed from scratch never works and cannot be made to work.” ― John Gall, The Systems Bible: The Beginner's Guide to Systems Large and Small

[juh-wasnt-deactivated19691231]

i'll never find that post again where we were talking about how tumblr might store duplicate data, but it turns out they tell us a lot about their infrastructure: https://automattic.com/work-with-us/job/systems-engineering/

[burnwater13]

Grogu knew how starships worked. They had engines or motors that created thrust. The thrust was aimed in a direction and the ship moved away from that direction. Simple, right? Wrong.

Starships were way more complicated than that. First, those engines/motors had to work hard. Really hard. They didn’t just carry themselves up into the atmosphere, but they carried the weight of the ship’s hull and all of its contents. And in Grogu’s experience the contents were always the problem. 

First there was the equipment and control systems that were needed just so the engines worked. They didn’t just control themselves. Then they needed fuel. Starships used all sorts of energy conversion systems depending on what they did or were meant to do. Some of them were pretty straightforward. 

A liquid fuel went through a controlled combustion chamber and the flame, fire, plasma, whatever, that was generated moved away from its point of origin because it was hot. Those molecules and atoms and sub-atomic particles did not want to stay where they were. So they moved one way and the thing attached to it went the other. Same for solid fuels, more or less. But importantly you had to store that fuel. It had to be somewhere. Unless you used ion sails or hydrogen scoops or stuff like that (the Force anyone?) you had to have your fuel on board. 

That sounded pretty awful to Grogu. No wonder so many of the ships that tried to target the Razor Crest ended up looking like a tiny sun when they blew up. That fuel needed to be treated carefully. Almost delicately. But that is not what happened when laser cannons whomped on your ship. Nope. 

Once you moved on from the fuel system (and who could blame you if you found it hard to move on), then you had navigational systems, gravity compensating systems, weapons systems, defense systems, communication systems, hyperdrive systems (a whole different problem with energy and fuel), and life support systems, just to name a few.  That was a lot of systems so there was an OOS or Overall Operations System. 

Grogu had almost forgotten about all the acronyms in use, like OOS. Those existed at the system level, the sub-system level, the object or assembly level (depending on the ship builder), the sub-assembly level, and the component level. He had once heard Din Djarin tell Peli that the NFCIR for the NFCISA, that fit into the NFICULA, and supported the NFCI in the Razor Crest was missing. Grogu had eaten his whole lunch and a snack while Din repeated all that when Peli looked up at him and said ‘I didn’t catch that’. 

After that he just pretended that he didn’t understand what the Mandalorian was asking for until he said something like, ‘Hand me that 5 ohm resistor’. Grogu was happy to help when he actually understood what was going on. He had also made it clear to his friend and protector that when it was called  ‘the RED one’ (resistor, electrical di-optic) he wasn’t going to touch it. Nope. Not making that mistake again (the resistor was in the end of that cable, ouch).

Grogu was baffled that once you crammed all that stuff on a ship it all had to survive contact with the enemy. People. All sorts of people ended up on starships. In his personal experience they could fall into two categories. Good people and bad people. The good people were great. They knew what they needed to do, they did it, and no one else was hurt, threatened or even mildly inconvenienced by them. Grogu mostly tried to be a good person when he was on a ship. 

On the other hand the bad people required extra systems to manage their behaviors. Some of them ended up secured in a room of their own. That added a security system to the list of all the systems. Others had to be made cold. Very cold. That meant you had to have a carbonite system. Grogu had asked the Mandalorian if the carbonite system was a sub-system to the security system or if it was its own system, but his dad told him to drink his broth and Grogu did that instead, because someone seemed pretty cranky. 

That might have been due to all the questions Grogu had about the food preserving and preparation systems. Grogu had asked Din Djarin why the Razor Crest didn’t have a food generator on board that could make good food, like frogs and shrimp and gorgs on a stick, but it did have a caf system. Considering that the caf system was offline at the time, the Mandalorian had been pretty annoyed. That may have been due to Grogu trying to program it to make him frog stew, but only ending up with broth. Oops. 

A short time later they also had a long discussion about the waste management system on the ship. Or, to put it differently, Din Djarin had lectured him ad nauseam about the proper use of the privy and how to return it to a functional configuration. 

Grogu had tried to explain that the privies on Coruscant, at the Jedi Temple, had a very different configuration and included a user interface that made it clear how to use the system in a step by step manner most appropriate for the species of the user and where they were in their life cycle. The Mandalorian must have turned off his auditory sensors because he just gave Grogu a look and ordered him to go to his hammock, pretty loudly. 

While Grogu was laying back in the hammock he wondered about the other life support systems, like the air recycler and filters that kept in them in cool, comfortable, clean air. Well, mostly clean. The privy configuration issue had raised more than one kind of stink and Grogu was pretty sure that was the root of Din Djarin’s problems. 

No matter how good a system was it couldn’t address every possible failure mode. This one certainly hadn’t been designed with Grogu in mind. Or maybe it needed a different systems manager. Grogu was happy to hand that job off to someone else.  Anyone interested?

[ziggy-scardust]

I DID SPACE SYSTEMS INTEGRATION & TEST FOR FIVE FUCKING YEARS AND WHAT THE ACTUAL FUCK

And I did half that time AT. SPACEX. (Not on Starship, but still surrounded by tech bros.) Because it’s NECESSARY (of which I was convinced by…the guys at NASA who were buying off on our contract!) (FYI, in those five years, two NEW spacecraft I worked on, one carrying humans, launched and they worked the first goddamn time.)

I’m reading this and I just straight up CANNOT believe this shit wasn’t tested. It is late and I have like twelve other tasks and zero energy for the rant that this deserves but what the hell kind of engineers do you call yourselves?? Shut up and sit down Matt Gialich. My shit’s alive and well on Mars, so I get to say that.

the number of spacecraft failures recently has been absolutely insane and it all comes down to tech bros barging into the industry going "it's not that hard wtf is nasa so bad" and then completely skipping out on any testing

[systems-engineering-and-ai]

The world’s moving faster than ever! AI is everywhere these days, from smartphones to factory robots. But for engineers who design complex systems like power grids and satellites, AI offers to be their secret weapon!

Systems Engineering: The Mastermind Behind the Scenes

Let us jump into the AI game, but first, let us meet the behind-the-scenes hero – system engineers. They function as the architect and conductor of complex projects. It is a meticulous process that ensures all the intricate parts of a system work together flawlessly; they make sure all the components of a complex system, like a spacecraft or a medical device, function in perfect harmony. Here is a glimpse into their toolbox:

At its core, DDDM involves utilizing data and analytics to inform decision-making processes. Gone are the days of relying solely on intuition or past experiences. Instead, DDDM emphasizes evidence-based decision-making, where insights derived from data analysis drive the course of action. By leveraging various analytical techniques, such as statistical analysis, machine learning, and simulation, engineers can gain deeper insights into system behavior, identify patterns, and predict outcomes with greater accuracy.

● Methodical and Structured Approach: They break the work into clear steps or phases, such as planning, design, development, and testing. It is like a well-planned show – each part knows its role for a smooth performance.

● Break Complex Systems: Systems engineers break down complex problems into manageable chunks. Think of them as puzzle ninjas!

● Collaboration is Key: Systems engineering projects require a symphony of talented engineers working together. They need folks from all engineering fields – mechanical, software, electrical, etc.

To read the full blog post you can visit here

https://blue-kei.com/exploring-the-intersection-of-systems-engineering-and-artificial-intelligence-opportunities-and-challenges/

[lifecycle-of-systems-engineering]

Systems Engineering provides a comprehensive framework for managing complex projects by aligning all components to achieve the desired results. The process of developing, deploying, and overseeing these intricate systems necessitates a well-defined roadmap, referred to as the Systems Engineering lifecycle, which guides teams through each phase—from initial concept and requirements gathering to design, implementation, verification, and maintenance—ensuring that all aspects of the system work together seamlessly to meet stakeholder needs.

Systems Engineering is more than just a methodology – it is a mindset that drives project success. At its core lies the Systems Engineering lifecycle, a framework that guides projects from conception to deployment.

The Systems Engineering lifecycle is a series of phases, each serving a distinct purpose in the project’s development. These phases offer a roadmap for success, ensuring that projects are completed efficiently and effectively.

To excel in Systems Engineering, it is essential to prioritize effective risk management, integrate project management techniques, and plan for seamless transition and support.

In this comprehensive guide, we delve into the main seven phases of the Systems Engineering lifecycle, providing insights and tips to navigate your journey from concept to deployment.

The Systems Engineering lifecycle can be effectively aligned with the stages outlined in the ISO/IEC/IEEE 15288 standard, which provides a comprehensive framework for managing system development from conception to retirement. Below is a rephrased overview of the phases, emphasizing the distinction between verification and validation.

To read the full blog post you can visit here

https://blue-kei.com/from-concept-to-deployment-the-lifecycle-of-a-systems-engineering-project/

[aipuconnects]

Innovative Computing and Engineers Association

The Innovative Computing and Engineers Association (ICEA) brings together professionals from the fields of computing and engineering to drive groundbreaking innovations, foster collaboration, and advance technological progress.

[agilesyseng]

And this is why you need to be explicit about the things that need to be done on any project... there are many things happening at any one time, specially when the number of contributors to your project keeps increasing. And personal life is just one of them, although of course the most important!

[engineersretreat]

Simulating a Quadcopter’s Flight

Gain the skills to model the mechanical subsystems, analyze flight dynamics, and refine a quadcopter simulation.

✅ 1 Week (5-7 hours per week)

✅ Self-Paced

✅ Optional upgrade

What You Will Learn

✅ How to model the mechanical component

✅ How to simulate and test the mechanical subsystem

✅ How to analyze flight dynamics

✅ How to refine a quadcopter simulation

[800db-cloud]

i’m literally shaking buy them brown contacts pls

[merchantservices444]

“POS Systems in Garland, TX: Enhancing Business Efficiency and Customer Experience”

[confusednconfusing]

studying the systems engineering module like

“yeah sure whatever u say bro”

* furiously takes notes *

[ziggy-scardust]

oh man. As an aerospace engineer whose career has wound up falling WAY more on the space end of things but also loves the SR-71 (I mean, who doesn’t?) I kinda hate reductionist explanations of “selfish men” and unnecessary hate towards satellites. I mean, there’s so much cool tech that could be invented that just won’t be, because there’s no need or no use for it. The SR-71 was BONKERS. I love it. It’s an amazing piece of machinery. And also, satellites are still way, way better - and continuing to get better! - for reconnaissance. That’s just a fact.

This is the kind of thing you hear from people at, say, Relativity Space - who’re making additively manufactured rockets (that aren’t even good and haven’t reached orbit yet) for…no good reason that anyone’s been able to articulate to me. Getting good at streamlining operations for ordinary rockets is a way cheaper way to bring new small launch vehicles to market. I’ve had a conversation with Ursa Major folks who told me they designed a few different thrust classes of rocket engines, for one of which they straight-up had no customers. Like. A very cool exercise, yes - but why?

I love the XB-70. I LOVE it. Was just thinking about it again bc someone sent a video. It’s wildly cool (and unlike the SR-71, was LESS bonkers because they figured out smart ways to build it so it didn’t have to be ENTIRELY TITANIUM and leak fuel all over the ground and shit!) Harrison Storms and Dutch Kindelberger are among my personal heroes, and I mean that seriously. But only 2 prototypes were built because by the time they got there, ICBMs had arrived on the scene - and it no longer made sense to build a bomber that could do Mach 3 (tbf, the Air Force wanted Mach 0.9 lol) or carry that kind of payload. Bombers now needed to be different because nuclear warheads weren’t going to be dropped by aircraft anymore. It’s shortsighted and mean-spirited to be bitter about very cool things being canceled when, genuinely, they outlived their purpose. Now, I’ll concede that a lot of stuff gets abandoned when it shouldn’t because of petty squabbles and such, but the B-2 was a lot cheaper than the SR-71! The case to be made for keeping the Blackbird just wasn’t that strong by the time it was canceled.

(This is also why in the Top Gun fandom I’m always the Admiral Cain apologist - he was right, sooner or later there won’t be as much of a need for human pilots anymore. He’s a dick to Maverick. He’s also not wrong. And even Maverick can’t argue with sending fewer people in harm’s way.)

In its heyday, the SR 71 only need it one hour to fly coast to coast in the United States of America. It was faster than a speeding bullet. Unfortunately, it was canceled because of jealous men who preferred to keep the U2 and invest in satellites …you can read all about it later this year when my book is published ‘SR 71 to the Skunk Works “the Colonel Richard Butch Sheffield story 🔥🇺🇸🔥

@Habubrats71 via X