New posts

Reply to thread

Message

My comment turned out to be, well, alarmingly timed.....

At 11:35am on Wednesday (eastern states time) AEMO implemented a change to NEMDE (National Electricity Market Dispatch Engine) which in simple terms is the software controlling the physical dispatch of power generation into grid.

Anyone like to guess what happened?

Well it resulted in about 16% of all generation running at 11:35 promptly shutting down with impacts across all 5 NEM states. It being the wind and solar farms which were affected.

[ATTACH=full]145203[/ATTACH]

Emphasis in orange is mine.

Noting that it's pure coincidence that the example I've used here is an electrical one. It would be equally relevant if it were anything else.

I've nothing against those who code software for a living, it's nothing personal, and nor is my example intended as criticism of AEMO. It's just an example, it could've been any industry anywhere.

It's just a reality that I've personally seen a few too many real world near misses caused by software flaws to be comfortable with the idea that someone's remotely tinkering with a car that I'm driving, potentially whilst I'm driving it.

<blockquote data-quote="Smurf1976" data-source="post: 1188031" data-attributes="member: 676">My comment turned out to be, well, alarmingly timed.....At 11:35am on Wednesday (eastern states time) AEMO implemented a change to NEMDE (National Electricity Market Dispatch Engine) which in simple terms is the software controlling the physical dispatch of power generation into grid.Anyone like to guess what happened?Well it resulted in about 16% of all generation running at 11:35 promptly shutting down with impacts across all 5 NEM states. It being the wind and solar farms which were affected.[ATTACH=full]145203[/ATTACH]Emphasis in orange is mine.Noting that it&#039;s pure coincidence that the example I&#039;ve used here is an electrical one. It would be equally relevant if it were anything else.I&#039;ve nothing against those who code software for a living, it&#039;s nothing personal, and nor is my example intended as criticism of AEMO. It&#039;s just an example, it could&#039;ve been any industry anywhere.It&#039;s just a reality that I&#039;ve personally seen a few too many real world near misses caused by software flaws to be comfortable with the idea that someone&#039;s remotely tinkering with a car that I&#039;m driving, potentially whilst I&#039;m driving it. <img src="https://www.aussiestockforums.com/styles/default/xenforo/smilies/twocents.gif"&nbsp; class="smilie" loading="lazy" alt=":2twocents" title="Two Cents&nbsp; &nbsp; :2twocents" data-shortname=":2twocents" /></blockquote>

[QUOTE="Smurf1976, post: 1188031, member: 676"] My comment turned out to be, well, alarmingly timed..... At 11:35am on Wednesday (eastern states time) AEMO implemented a change to NEMDE (National Electricity Market Dispatch Engine) which in simple terms is the software controlling the physical dispatch of power generation into grid. Anyone like to guess what happened? Well it resulted in about 16% of all generation running at 11:35 promptly shutting down with impacts across all 5 NEM states. It being the wind and solar farms which were affected. [ATTACH type="full"]145203[/ATTACH] Emphasis in [COLOR=rgb(243, 121, 52)]orange[/COLOR] is mine. Noting that it's pure coincidence that the example I've used here is an electrical one. It would be equally relevant if it were anything else. I've nothing against those who code software for a living, it's nothing personal, and nor is my example intended as criticism of AEMO. It's just an example, it could've been any industry anywhere. It's just a reality that I've personally seen a few too many real world near misses caused by software flaws to be comfortable with the idea that someone's remotely tinkering with a car that I'm driving, potentially whilst I'm driving it. :2twocents [/QUOTE]

Verification