Page 22«..10..21222324..3040..»

First Due and Fire Engineering Training Partner to Bridge the Gap Between LMS Training Content and Reporting RMS … – Fire Engineering

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

Read the original post:

First Due and Fire Engineering Training Partner to Bridge the Gap Between LMS Training Content and Reporting RMS ... - Fire Engineering

Read More..

Data science and business minors to move to School of Engineering, Owen in Fall 2024 – The Vanderbilt Hustler

As of Fall 2024, the undergraduate business and data science minors will be housed in the Owen Graduate School of Management and the School of Engineering, respectively, instead of Vice Provost for Undergraduate Education Tiffiny Tungs portfolio. Tung emphasized that these programs will retain their interdisciplinary qualities, which she said is a core aspect of a Vanderbilt education.

This shift comes amid Vanderbilt Law School offering a new introduction to legal studies minor starting in Fall 2024. The business and legal studies minors will be governed by students home schools academic policies due to Owen and VLS not having undergraduate academic policies.

Were hoping that well get more classes added [for these minors] because now those programs will be in an academic school or department that can focus on curricular development, which will be nice for enhancing student options, Tung said. I respect the autonomy of academic departments and schools and the professors within them. Because theyre on the ground teaching in the classroom, they know really well what to develop for the students.

Director of the Business Minor Program Gary Kimball said the structure of the business minor will largely remain the same despite moving to a professional school.

One change that students will see in the future is that Owen faculty will begin offering [undergraduate] elective courses as well, giving students even more choices, Kimball said in a message to The Hustler.

Dr. Charreau Bell, director of the data science minor, said its move to the School of Engineering was a collaborative effort among Vanderbilt leaders. She was unsure whether the minor will eventually move to the College of Connected Computing.

The move to Engineering is fortuitous, Bell said. We have this new capacity to leverage the resources for academic programs within a school. I think were going to be able to grow more and offer more electives, which is something Im very happy about.

Here is the original post:

Data science and business minors to move to School of Engineering, Owen in Fall 2024 - The Vanderbilt Hustler

Read More..

Richest 0.1% in UK emit 22x more transport emissions than low earners – Interesting Engineering

A groundbreaking report by the Institute for Public Policy Research (IPPR) has unveiled a stark reality in the UKs transport emissions landscape, highlighting a significant disparity in contributions to the climate crisis.

Emissions from travel are not fairly shared across people living in Great Britain, says the report.

The research reveals that the nations wealthiest individuals are disproportionately responsible for these emissions.

As per the study, the richest 0.1% of the population have been found to emit a staggering 22 times more emissions from transport compared to low earners, and 12 times more than the national average.

This revelation comes amidst increasing concerns about climate change and its devastating impacts, including soaring temperatures and catastrophic weather events.

Globally, we are not on track to keep warming below 1.5C and have not made the required commitments to keep warming below 2C, expressed the report titled Moving Together: A People-focussed Pathway to Fairer and Greener Transport.

The report highlights that half of all transport emissions in Britain originate from just one-fifth of the population. Besides, the top 10% of polluters are responsible for a staggering 42% of all transport emissions.

This startling statistic paints a clear picture of the unequal distribution of environmental burden within the country. This finding further emphasizes the concentration of environmental impact within a small segment of society.

Moreover, a closer examination of travel patterns reveals a direct correlation between wealth and distance traveled.

People with an income over 100k travel at least double as far each year as those under 30k, and almost three times further than those under 10k, the researchers mentioned.

These numbers suggest that higher income levels facilitate increased mobility and, consequently, higher emissions.

There is huge disparity between the emissions from transport of the wealthiest and those on lowest incomes, commented the report.

It also sheds light on demographic disparities in transport emissions.

Men, individuals aged 35-64, and residents of less deprived areas tend to have higher emissions levels, while those with disabilities, non-white British ethnicities, and individuals from more deprived backgrounds tend to emit less.

This finding underscores the complex interplay between socioeconomic factors and environmental impact.

Our transport system both reflects and contributes to social inequalities. Reducing emissions can actually tackle some of that injustice, if done fairly, said Dr Maya Singer Hobbs, senior research fellow at IPPR.

Alarmingly, the UKs progress in reducing transport emissions over the past three decades has been minimal, with the transport sector now standing as the countrys largest emitter.

The report urges the government to take decisive action to address this inequality and accelerate efforts towards decarbonization.

Among the suggestions offered by the report are the implementation of new taxes on private jets, a mode of transport favored by the wealthy, and improvements to public transportation to provide more sustainable options for all.

Additionally, it calls for a faster transition to electric vehicles to reduce reliance on fossil fuels in the transport sector. This comprehensive study aims to mitigate the environmental impact of the transport sector while addressing the underlying socioeconomic disparities that contribute to it.

Now is not the time to slow down our efforts to reach net zero; doing so just fuels existing transport inequalities, concluded Stephen Frost, a principal research fellow at IPPR.


Stay up-to-date on engineering, tech, space, and science news with The Blueprint.

Aman Tripathi An active and versatile journalist and news editor. He has covered regular and breaking news for several leading publications and news media, including The Hindu, Economic Times, Tomorrow Makers, and many more. Aman holds expertise in politics, travel, and tech news, especially in AI, advanced algorithms, and blockchain, with a strong curiosity about all things that fall under science and tech.

Follow this link:

Richest 0.1% in UK emit 22x more transport emissions than low earners - Interesting Engineering

Read More..

The Evolution of Use Cases in Modern Software Engineering –

Subscribe on:ApplePodcasts Google Podcasts Soundcloud Spotify Overcast Podcast Feed Transcript

Shane Hastie: Good day, folks. This is Shane Hastie for the InfoQ Engineering Culture Podcast. Today, I have the privilege of sitting down again with Ivar Jacobson.

Ivar has been a guest on the podcast before, and is one of the stalwarts of software engineering. Ivar, welcome. Thanks for taking the time to talk to us today.

Ivar Jacobson: Oh, thank you. I really appreciate the invitation. Thank you.

Shane Hastie: I mentioned that you're a stalwart, but perhaps for some of our audience, they might not have come across your work before, so do you want to give us a brief overview of, who is Ivar Jacobson?

Ivar Jacobson: Well, yes, I will be happy to do that. I didn't know I was interested in methodology when I was 28 years old and worked at Ericsson, and became project manager for our most mission-critical project at that time. It was a computer-based telecom switch. The methodology people used, even if it didn't talk about the methodology, was very close to what the many methods were at that time, separating functions from data.

We had a big data program store, where you put in the functions, and you had a big data store where you put your data, and you developed a program separate from the data. My job was to make sure we built the product that could be marketed around the world, easily adapted to new requirements. And thanks to having a hardware background, I understood what they were doing was really not working, and would never work. I said they, I mean the development team; it was 70 people, or something like that.

As a project manager, I shouldn't put my fingers in that. I should run the project, and the method was already set in stone. It was the intention. But as a bad project manager, I couldn't keep my fingers away from how to do it. So I came up with a way that we now classify as component-based and that resulted in success.

Ericsson was the only telecom vendor that we used that approach and they won everything, but it took 10 years before people at Ericsson knew it. But then I was awarded to get the PhD during work hours. I spent five years doing nothing for Ericsson, only get the PhD. That was very educational because now I started to understand how a computer worked too. Well, a little bit exaggerated. And that was late of my part of my life.

I always was involved in methodology work and I had great interest in it. So they sent me to standardization and we created a modeling language in this standard group that is the predecessor to UML and that was the biggest competitor to UML when UML came out in 1997. So in 1980 say, this telecom standard was adopted and almost 20 years later UML came. And it is very similar languages in some aspect, in other aspects, not.

After my PhD, I set up a company and we developed what later became Rational Unified Process because Rational acquired us and because of what we had and Rational Software grew dramatically. I was there with two other gentlemen, Grady Booch and Jim Rumbaugh. We were nicknamed the Three Amigos and traveled around the world talking about what we had done together, namely Unified Modeling Language and later also Rational Unified Process, which came from my company in Sweden.

That went well until Agile came. Agile just killed first Rational Unified Process; it took only a couple of years, also UML, no one would do modeling anymore. By the way, all that is coming back. It's all coming back and this is what has happened in the history of software engineering. It all comes back. The good ideas come back. And at some point, in time I also came up, it was called use cases and use cases became really the thing that was adopted all around the world.

But that also because it belonged to the old generation so to speak, it was also thrown out and replaced by a simpler approach, user stories, and that's it. Now we are about around 2005 or 2000 something. I have always been interested in artificial intelligence. So in 2000 I founded a company, actually with my eldest daughter, and we developed a product to support software development. So we had copilots, we call them developer assistants.

We used AI technique called intelligent agents and we got a Jolt Award in 2003, if I remember correctly, for one of the most interesting products at that time. At that time, I also was fed up with methodologies to be very honest with you. Methods was just a number of problems. We have methods war, so good people were fighting with one another which had the best method.

We created sects around every method, there were people that loved that method and talked about that method and talked bad about other methods. And you couldn't use... For instance, many people want to use use cases with their method. So they tried to take cases from my method and put into their method, but since they were totally differently described it became not really successful.

So I said that methods put good ideas into prison, namely their own prison. So you couldn't take them or use it at other place, but many problems like that.

So I decided enough is enough for me. We had a new method coming out that was agile and would very well compete with the methods we see today or popular methods like SAFe for instance. Nothing bad said about SAFe, it's probably one of the better if you talk about these full scale methods. But we selected another path. We decided we want to find what is the common ground of all these methods, what do we share? They must share something. They all use the software; all for product development engineering. So we created such a common ground, Essence, and it became an international standard.

And since then we have worked on popularizing it. We have come a very long way, but that's a very different story.

Shane Hastie: There's a lot there. The classic tool of requirements representation coming out of your work is the use case. So a sequence of interactions, a flow of interaction between a person and a system, a tool to represent and communicate the requirements. But one that seemed to, and you alluded to it there, they seemed to go out of favor.

What happened there?

Ivar Jacobson: Yes. When Agile came starting with extreme programming around, let's say, at the beginning of 2000. The Agile movement basically killed any old approach and they were more focused on how people work together, basically social engineering. Agile didn't really introduce any new technical practices. You can say that iterative development using sprints and working in small periods to deliver concrete results was already there. It was used since the early 1980s. There were scientific work around the spiral model of development by Barry Beam.

So it had been around and my own work and the work that we did at Rational Software at that time was definitely iterative. What has probably happened, has happened, is that iterations are short, sprints are shorter than it were at that time. At that time they may a month, now they're down to days, but the idea is basically the same. And then the technical practices you can mention user stories as one of these technical practices.

It was focused on small things that a team could do in such an iteration or sprint. So Agile flirted with the developers, the people really did something of useful value. Whereas in the old days, I must confess, we flirted, if I use that word, the more system engineers as higher level people, not the programmers directly.

We felt that a lot of code is done in modeling. You identify the components, you identify the interfaces without writing a line of code, but of course, you need to understand how it is going to be implemented. So there was a switch that made the majority of developers feel they got support from the methodology, they got support from the Agile way of thinking, and we were the old dinosaurs and everything that we had done was just rubbish, get it out. And that was, of course, something I understood very early.

So I didn't want to continue create a new dinosaur or something that people would call a dinosaur, whatever it was, so we did this common ground instead. But when it comes to use cases, use stores was a really great contribution. I remember when I met Kent Beck who was one maybe the key originator of the user stories at the conference and I went over to him, he was signing books and I said to him, "Congratulations, Kent." I'd known him for many years at that time, 10, 15 years, and actually I'd invited him to come to Sweden and teach and so on, small talk action to my people.

So we were congratulated him and he said something, a compliment back, "Well inspired by use cases," or something like that. So these two things should never have been seen as in conflict. They were extremely good compliments to one another because use cases deal with a bigger picture.

You can, in a couple of hours, present a model of the system in the form of say 20 use cases and everyone will understand what the system is going to do. Of course, to go deeper, you require more thinking, but to get the big picture very quickly. And use case also is language where people talk about from a business perspective. For instance, I don't know any modern product that doesn't talk about which use cases does this product have. And you see it also in normal English. So it has become a normal English word, use case. And if you Google it, you will find maybe a hundred times more hits than you find on user stores. I don't know really, but it's dramatic difference.

So there is a value in use case thinking that help you to understand the big picture of a product. You may have 800 user stories but only a couple of use cases, maybe 10 use cases. And so you get a really good picture of what the system is doing. And people do use cases, they have done it all the time, particular business analysts, but then they have a problem to communicate with the developer team because we don't want to hear about use cases, we want to hear about user stories. And this is what has gone on for now many years, 20 years or so. But we are going to change it.

Shane Hastie: Use cases definitely are... We are seeing a reassurgence, but I'm also seeing that there's something different about the way you and people like Alistair Coburn are talking about use cases today compared to what were. I will confess to having seen some pretty appalling use cases in my time.

One that springs to mind was an author who tried to write all of the functionality for a complete ERP system in a single use case. It ended up 127 pages and a week later even the author couldn't tell us what it was. Now that in my experience, is the extreme example of a really badly done use case.

Ivar Jacobson: Yes, absolutely. When I started with use cases, I developed one way of using use cases; we call it use case driven development. So it's not only for requirements. A use case was also something you realized. So for every use case we identified, we describe how to realize it as a collaboration among components with messages and so on. We use diagrams, very popular diagrams, they still popular, sequence diagrams. They are actually popular, but you describe how components interact to do something.

And then use cases with test cases. So once you understood the use case, you could direct it from a use case, identify a huge number of test cases, a big number of test cases. So use cases, we had a very big picture for them. Of course, we used them also only for requirements, but that was then simpler use cases. So we learned was that it can be used in so many different ways.

If you develop life critical systems, you have requirements on more details, level of detail. If you write for instance a business application or website or something like that. So it's not one use case that is needed for people about many different variants. Alistair, you mentioned Alistair, he came to Sweden and learned about use cases. He felt it can be done better as natural and of course it can be done better, so he started to work on a different way of doing use cases.

The value of that is that more people talked about it. He has definitely contributed a lot when it comes to popularizing use cases. He introduced a goal structure, so a goal has sub goals and sub goals have sub goals and so on, all the way down to very small things and many people like that and it's fine.

So you mentioned bad use of use cases and I've seen similar application of use cases that I've immediately said this is trying to do too much. People have loved the concept and tried to use it more than is proper.

So what we have done now recently, I have been thinking personally for a couple of years and worked with some people on what we called use cases need to come back. We had a plan for a campaign but I said no, this is not enough. We need to get the more people to stand behind it. So I saw an article of Alistair, it probably was a LinkedIn article where he said basically that use cases are needed and I contacted him and we decided to write the paper together.

So that's how we started now probably eight months ago or something like that. We wrote the paper together and writing papers together when you sit far away and don't have an immediate contact is not an easy thing, but it went very well. I had a colleague in my company who started off with a proposal, Alistair took it and said, "No, no, no, this is not how I want to write it." So he wrote a completely new, we decided that it's close enough. With some modifications, we had a paper and it was published in ACM Queue in September, October of last year.

So that was our first step towards doing something together.

Shane Hastie: What does a good use case look like today?

Ivar Jacobson: It depends. I'll tell you one thing it does, it follows, we could call it the foundation. So Alistair and I, we have written a paper together, together with actually Ian Spence who has been working with me for, I think. Almost 20 years and is really a use case expert. And we have written a paper together which is called Use Case Foundation. It includes a definition of use cases. I mean, just having a clear definition that we all can agree on what is a use case was a good thing.

Now, if you ask me to tell you what is use case, I have to think a little, but it is basically all the ways to use a system. It's very important. It's a system that owns the use case. So it's all the way to use the system to achieve a particular goal for a user.

Maybe very some word here that I have got wrong, but it's basically what it is. It's super critical. But there is an entity for which the use case belong. Use case is all the ways of using it. All the ways meaning if you do a particular use case, there are many different paths you can follow, success paths and alternative paths and failure paths. So all these ways to use the system to achieve the goal for a particular use or something like that. And that's a very good start. And then there is other things in this use case foundation document like principles that we think are important to obey and also some patterns.

It's not a thick document, I think it's four pages, but it gives a really good foundation. The idea is that people, not only Alistair and myself or my people, will use this foundation and then describe our different ways we can create use case practices, how we can practice use cases.

And Alistair is working on a book now and we also working on a kind of book, but it's not a thick book. It's a very thin book, maybe 50 pages, maybe something similar to the SCRUM guide when it comes to use cases. It'll describe a family of use case practice, not only one. So for instance, one practice we call use case storytelling, which is a very simple practice that works very well. For instance, web development, just to take an example. And then there is another called use case visualization or something like that. I don't know the names in detail. Well I don't know exact wording, but it's about visualization. This is where you can use diagrams. For instance, many typical products require much more detail about the use case that you need for developing a website. So they use, for instance, activity diagrams, they use swim lanes to describe what is done by the user and what's done by the system and sequence diagrams.

So a whole bunch of diagrams you can use. So these are the basic stuff. On top of that, you can have use case offering, which is more advanced than use case storytelling. And when it comes to the modeling side, you can have use case modeling and that means you make, for instance, a model of all your use cases and give basically a design of the use cases. Use cases are not design, it is a specification, it's requirements. But you can get very good complete picture of what the system is supposed to do by just looking at such a use case model.

And there are more and more advanced and we have six such practices we are just now working on and they should be presentable in a couple of weeks I will say.

Shane Hastie: So at a fundamental level, I suppose I want to explore what is different today about these use cases and the range that you're talking about to what we were working with when you first came up with these.

Ivar Jacobson: Yes. So in the first version, let's call it use case 1.0, we identified iterations and we started to work with the most critical paths in every use case. So we didn't take one use case specifying it completely at once, and then we went to design it and code it and test it. No, that is what the people who wanted to kill us said we did, but it's never true. We can go back to the original book from 1992 and it's very clear we develop in iterations and we don't develop complete use cases. So what we did is we took a path through use case. These paths could very well be described as a user story today or many user stories, such a path. We didn't have that term, but that is how we were thinking. Now people didn't feel like that. So in that sense, the Agile movement were right, people did waterfall, people did sitting and doing all the use case models.

And when we did a lot of modeling, we did too much modeling of the system. I mean I remember I worked with one bank, big bank in the US, they had 800 people sitting and doing models and then they threw these models over to the developers and the developers were then supposed to code them, but the developers said this is rubbish. So we did it their way anyway, so there was a complete total disconnect between these two big groups of people.

We tried to change it, but I think the whole organization dissolved and it was recreated without our chance to have an impact. So I mean they were using them wrong. Now, I cannot only blame them. We could have done more to describe it better. So in 2005 we wrote the paper called Use Case 2.0 where we integrated into use cases, something very similar to user stories.

We call them stories, but they were not identical. We had slices. So use case were sliced into a number of slices and you prioritize the slices and every such slice had a number of stories. So we are getting close, but the mistake, I must admit, I think today was a mistake we did like that. We should have kept use the stories outside use cases and we should have integrated it. Whatever way, people like to do user stories. Let them do user stories exactly as we are doing today.

We keep us to simpler use cases and then we have an integration mechanism. We show how to integrate use cases with user stories. And that could be a very simple pattern. So what we are doing now is we are actually doing just that. Our use cases are easily integrated with user stories but user stories all what people have come up with, other people like Mike Cohn has come up with and that is now concrete. So we will have this use case family separate from the user stories and they will be what they are in particularly Mike Cohn's world. So having said all this, maybe I leave it a little.

Shane Hastie: There's a lot there. We'll make sure that we have a link to the ACM article, but if people are looking for some more guidance, where do they go?

Ivar Jacobson: So that is the new thing here in each city. So Alistair and I, we wrote not only this use case foundation, we also wrote a call to action where we said basically use cases fill a hole that none of the other existing practices fill and that hole is an important hole to fill. Then we said, so we are going to do these things. We want to support doing these things.

Number one is to create the use case foundation, which I talked about. Number two was to create a number of initiatives where we integrate use cases with other elements such as user stories, story mapping, and many other practices that are out there and we identify how they can be integrated. I think we are talking about BDD and ATDD as well. So we are working with these people that are founders or have played a significant role in development of these practices.

For instance, BDD and ATDD is Ken Pugh and when it comes to user stories we work with Mike Cohn and also with Gunnar Overgaard who wrote a book Use Cases, patterns and Blueprints. So together this initiative, we develop how to integrate use cases with these other practices and that's going on now. We have identified two such initiatives, user stories and BDD and ATDD, and I expect a couple of others coming quite soon. And that work will be done without Alistair and I trying to play any kind of management role. It's not our style. So we'd see what come out of it, but apart from that we will see people developing their use cases, ideas on top of a foundation. So Alistair is doing that. We are doing that. As I said, we have six practices that we think we will publish in a short while, weeks.

Of course, Alistair is already out training in his new use cases. I don't know if I should call them new, but I believe it's at least refreshing of them and we will do the same thing. Hope to create an interest for them so people can learn about it. And I think we will serve different markets, different part of a market. Alistair has a populistic and still very useful style for doing it. His goal orientation attracts a lot of people. We do it our style, which is probably a little bit more scientific, but let's just guess. Who knows? Anyway, and there are others. I know there are many other people that want to do training and use cases and we will develop our own courses based on use case foundation. So it's all fun.

Shane Hastie: A lot's happening with use cases. What was old is new again.

Ivar Jacobson: New.

Shane Hastie: Yes. So Ivar, again, thank you very much. If people want to continue the conversation, where do they find you?

Ivar Jacobson: LinkedIn. Well I am not shy, so we can get my email address too.

Shane Hastie: All right, I'll make sure we have both of those links in the show notes. Thank you so much.

Ivar Jacobson: Thank you. I appreciate it.


. From this page you also have access to our recorded show notes. They all have clickable links that will take you directly to that part of the audio.

Continue reading here:

The Evolution of Use Cases in Modern Software Engineering -

Read More..

Polyextremophile Engineering: A Review Of Organisms That Push The Limits Of Life – Astrobiology – Astrobiology News

Root causes of stress under extreme conditions. There are several essential cellular functions that are frequently the proximal cause of disruption in extreme conditions (A). When an essential function is disrupted, it can lead to disruption of other essential functions, resulting in a cascade of failure (B). Resistance mechanisms can protect against multiple extremes with the same root cause (C), and stressors with opposite root causes can be easier to tolerate together than separately (D). Frontiers In Microbiology

Nature exhibits an enormous diversity of organisms that thrive in extreme environments. From snow algae that reproduce at sub-zero temperatures to radiotrophic fungi that thrive in nuclear radiation at Chernobyl, extreme organisms raise many questions about the limits of life.

Is there any environment where life could not find a way? Although many individual extremophilic organisms have been identified and studied, there remain outstanding questions about the limits of life and the extent to which extreme properties can be enhanced, combined or transferred to new organisms. In this review, we compile the current knowledge on the bioengineering of extremophile microbes.

We summarize what is known about the basic mechanisms of extreme adaptations, compile synthetic biologys efforts to engineer extremophile organisms beyond what is found in nature, and highlight which adaptations can be combined. The basic science of extremophiles can be applied to engineered organisms tailored to specific biomanufacturing needs, such as growth in high temperatures or in the presence of unusual solvents.


Extremophilic microbes have long been studied in hopes of better understanding the origin and limits of life. Extremophile biology is also relevant to biomanufacturing (Ye et al., 2023), where large-scale growth occurs in non-natural, extreme chemical conditions ranging from the use of toxic waste streams as feedstocks to the intentional production of toxic chemicals like butane.

The space science community hopes to push the capabilities of biomanufacturing even further for in situ resource utilization (ISRU) (Cockell, 2022), especially on human missions to the moon, Mars, and beyond. This will require microbes that are well adapted to chemically unusual feedstocks derived in part from highly oxidized Moon regolith or perchlorate-containing Mars regolith.

A microbe that can thrive, growing and metabolizing at high rates, in extreme bioprocessing conditions can enable robust, high-yield, and low-cost synthesis of biological products. We aim to not just understand the basic science of extremophile biology, but also how that basic science supports current and future extremophilic bioengineering.

Polyextremophile engineering: a review of organisms that push the limits of life, Frontiers In Microbiology (open access)


Originally posted here:

Polyextremophile Engineering: A Review Of Organisms That Push The Limits Of Life - Astrobiology - Astrobiology News

Read More..

BioLargo Engineering Secures Multi-Year Air Force Base Air Compliance Project – AccessWire

WESTMINSTER, CA / ACCESSWIRE / June 7, 2024 / BioLargo, Inc. (OTCQX:BLGO), a company that creates and commercializes sustainable technologies to solve tough environmental and cleantech challenges, announced that its engineering subsidiary has been awarded a contract to provide air quality services to three New Mexico U.S. Air Force (USAF) bases for up to five years, with a potential annual average revenue of $650,000.

The new contract is in addition to ongoing environmental support work at six Air Force bases and is the company's largest dollar-value Air Force contract to date. These contracts provide regularly monthly flat fee revenue to the company over the life of the contract, which the Air Force may renew each year. BioLargo's work at the New Mexico bases includes air quality regulatory compliance. Bhate Environmental Associates is the prime contractor with the Air Force under the Fence-to-Fence (F2F) support contract.

BioLargo Engineering, Science & Technologies President Randall Moore commented, "Our team has served Air Force bases with fence-to-fence air quality compliance services for years, but this is the largest such contract we've secured to-date. Larger, long-term contracts such as this one are crucial to our strategy of securing steady, reliable income from external clients. This empowers us to focus on commercializing BioLargo's innovative cleantech technologies, including advancements in water treatment, energy storage, and air quality solutions."

About BioLargo, Inc.

BioLargo, Inc. (OTCQB:BLGO) is a cleantech and life sciences innovator and engineering services solution provider. Our core products address PFAS contamination, achieve advanced water and wastewater treatment, control odor and VOCs, improve air quality, enable energy-efficiency and safe on-site energy storage, and control infections and infectious disease. Our approach is to invent or acquire novel technologies, develop them into product offerings, and extend their commercial reach through licensing and channel partnerships to maximize their impact. See our website at

About Bhate Environmental Associates, Inc.

Bhate Environmental Associates, Inc. (Bhate) provides a diverse range of technical services in the environmental and infrastructure markets to the federal government and private industry. Headquartered in Birmingham, Alabama, Bhate's reach is both national and global. At Bhate, we value high standards of safety, professionalism, ethics, and service to our clients. We foster a collaborative environment that encourages innovative ideas while providing challenges and rewards for our dedicated staff. Through our team's Responsiveness, Integrity, and Teamwork, Bhate delivers professional, quality, cost-effective, and on-time results to our clients. See their website at

Contact Information

Dennis P. Calvert President and CEO, BioLargo, Inc. 888-400-2863

Safe Harbor Act

This press release contains forward-looking statements within the meaning of the Private Securities Litigation Reform Act of 1995. These forward-looking statements include without limitation those about BioLargo's (the "Company") expectations regarding anticipated revenue; and plans for future operations. These statements involve risks and uncertainties, and actual results may differ materially from any future results expressed or implied by the forward-looking statements. Risks and uncertainties include without limitation: the effect of regional economic conditions on the Company's business, including effects on purchasing decisions by consumers and businesses; the ability of the Company to compete in markets that are highly competitive and subject to rapid technological change; the ability of the Company to manage frequent introductions and transitions of products and services, including delivering to the marketplace, and stimulating customer demand for, new products, services, and technological innovations on a timely basis; the dependency of the Company on the performance of distributors of the Company's products. More information on these risks and other potential factors that could affect the Company's business and financial results is included in the Company's filings with the SEC, including in the "Risk Factors" and "Management's Discussion and Analysis of Financial Condition and Results of Operations" sections of the Company's most recently filed periodic reports on Form 10-K and Form 10-Q and subsequent filings. The Company assumes no obligation to update any forward-looking statements or information, which speak as of their respective dates.

SOURCE: BioLargo, Inc.

Go here to see the original:

BioLargo Engineering Secures Multi-Year Air Force Base Air Compliance Project - AccessWire

Read More..

ST Engineering Breaks Ground For Third Hangar In Pensacola – Aviation Week

Credit: ST Engineering

SINGAPOREST Engineering has broken ground for its third maintenance hangar at Pensacola International Airport in northwest Florida, which will see the MRO facility handle up to six widebody aircraft by the second half of 2026.

The 167,000 ft.2 building is the third of four hangars planned for Pensacola and will add 500,000 manhours to the facility. There is no timeline set for construction of the fourth and final hangar.

Once completed, the entire site will generate at least 1,700 jobs.

The company has also partnered with Florida Power & Light (FPL) to provide renewable energy from FPLs offsite solar farm, and features light harvesting skylights as well as integrated vertical lift machines to improve operational efficiency.

Pensacola is one of three ST Engineering airframe MRO facilities in the U.S., alongside nearby Mobile, Alabama, and San Antonio, Texas. ST Engineering also runs a nacelle manufacturing and MRO facility in Middle River, Maryland.

As we deepen our partnership with the City of Pensacola and play a major role in its growth, we look forward to facilitating job creation in the community and strengthening Northwest Floridas status as a national hub for the aviation industry, ST Engineering North America president Timothy McBride said.

Chen Chuanren is the Southeast Asia and China Editor for the Aviation Week Networks (AWN) Air Transport World (ATW) and the Asia-Pacific Defense Correspondent for AWN, joining the team in 2017.

Apple app store ID


Apple app name


App argument URL

Read the original:

ST Engineering Breaks Ground For Third Hangar In Pensacola - Aviation Week

Read More..

Seniors present engineering tech inventions – The Triangle – Drexel University The Triangle Online

Photo by Lucas Tusinean | The Triangle

On May 29, Engineering Technology seniors presented their Senior Design projects. Over the course of their senior year, students worked in teams to engineer a solution to a specific problem. Projects covered multiple industries, including manufacturing, health, education and combating carbon emissions.

The Engineering Technology program began with presenting Haas-sponsored scholarships to five students, selected based on essays submitted about their interest in pursuing a career in manufacturing.

Seniors then stood next to their projects and poster boards. Attendees and faculty walked around to learn about each project and hear how they designed their solution. Seniors then gave presentations detailing their design process and answered questions.

Senior design mimics a product development process and incorporates experiential aspects of our program, which is more applied and hands on, shared Dr. Ertekin, the associate director of engineering technology. Students at the end produce a working prototype while applying theoretical knowledge and learn from their mistakes what not to do in actual industrial settings. They also develop soft skills like project management, communication and teamwork skills.

One group partnered with IFM Electronic to build a machine-vision system to minimize errors in assembly processes. IFM is a global company that specializes in manufacturing and sensors, aiming to improve efficiency and reliability. Through the partnership, IFM sponsored the student project, covering the $30,000 cost.

Their project incorporates two 3D-sensing cameras along with RFID detection for managing the assembly process. Attendees tried out the system and were intuitively able to follow the instructions on screen to assemble a pen. The cameras and RFID detection work together to ensure the operator follows the correct assembly steps to complete the assembly process without mistakes.

I feel accomplished to a degree because I was working with professionals and I got first hand experience Yahya Abdulrasool, one of the team members, shared. Communication is key, especially when working with people youve never worked with before. In total he estimates that it took two and a half months of work on the prototype after nine months of research.

Another group shared that they didnt know what they should do for their project at first. We asked people in other industries what issues they had that we could solve. Since many of my friends are nurses, we looked towards the health industry, shared Pitchapa Inroon. They found that many hospitals are short staffed, especially in the wake of the Covid-19 pandemic, and some tasks are suffering because of it. According to their executive summary, their project is designed to address a labor-intensive aspect of frequent repositioning of bed-bound patients to prevent complications like bed sores our project focuses on developing a bed system utilizing individually inflatable air cells with pressure-sensing capabilities.

Currently, repositioning requires two nurses to use a trendelenburg bed to tilt the bed downward, then slide the patient down. The team shared that this process is both time consuming and dangerous as patients may hit their head on the headboard. Their design automates the patient repositioning process and allows for pressure management.

Another senior project focused on making robotic education more accessible to schools. Modern manufacturing and iteration tools are large and expensive, so they can be cost prohibitive for schools, shared Aaron Kane. We wanted to build an open source project that can teach the same manufacturing and coding concepts at an affordable price.

Kane and his team built an Educational Automated Manufacturing Workcell for students to experiment with robotics programming, and use the hands-on work cell to learn key concepts. Im glad to have been part of a team taking the initiative to help make automation training more accessible to Engineering Students around the world, said Kane.

The students start with a dream, and we [advisors and I] help them scope the dream to become reality without clipping their wings. They dream big and they should do so every day, shared Dr. Irina Ciobanescu Husanu, associate clinical professor, engineering technology program director and senior design coordinator. It is not an easy task, I wouldnt trade it for another course. I cant wait to see whats in store for next year.


Seniors present engineering tech inventions - The Triangle - Drexel University The Triangle Online

Read More..

S. Shailja: Lancaster Dissertation Award | Electrical and Computer Engineering | UC Santa Barbara – UCSB ECE

Excerpt from theThe UCSB Current article"Dissertations in geography and electrical & computer engineering receive Lancaster awards for excellence"

It is always so exciting to see the amazing research our students are doing in different fields, said Interim Graduate Dean Leila J. Rupp. The Lancaster Award recognizes the best of the best, showcasing the diversity of talent across campus.

Shailja received the mathematics, physical sciences and engineering award for her dissertation, Reeb graphs for topological connectomics of the human brain. Advised by B. S. Manjunath, chair of UCSBs Electrical and Computer Engineering Department, Shailja builds mathematical tools for modeling neuronal fibers in human brains as geometrical objects in three-dimensional space. Modeling connectivity of the human brain is critical to understanding and treating neurological disorders such as Alzheimers disease and strokes.

What an honor, said Shailja,an incoming postdoctoral fellow at Stanford University.It added to the feeling of accomplishment, marking a spectacular finish to this long journey.

For Shailja, the award has additional significance because her mother will make her first trip to the U.S. to attend the commencement ceremony. I feel so proud that I will be named a Lancaster Dissertation Award winner in front of her. This has made the commencement day very special for us. I feel incredibly fortunate to have been selected from a pool of such talented peers and I felt grateful to the award committee for deeming my thesis worthy of this award.

The award includes a $1,000 prize to be presented at theGraduate Division commencement ceremonyon June 14. The awardees will also serve as UCSBs entrants in the national competition sponsored by the Council of Graduate Schools and ProQuest.

TwoLancasterawards are given annually to doctoral degree recipients or candidates from two broad academic areas. The four fields of competition alternate each year, as specified by the National Council of Graduate Schools.

Reeb Graph For Brain Connectome

Our brain is a complicated anatomical network responsible for cognition and behavior. Neurodegenerative diseases impede the associated network architecture in millions of affected people. My research aims to mathematically model the neuronal activities in the human brain using tools from computational geometry and artificial intelligence to characterize the evolution of neuronal fibers. We model the high-level topological structures of the fibers from diffusion MRI imaging data to construct graph-based mathematical objects. My research will pave the way for advanced AI methods to compare brain regions and provide pathological insights that are currently infeasible due to the complexity of the neuronal fibers.

Visit link:

S. Shailja: Lancaster Dissertation Award | Electrical and Computer Engineering | UC Santa Barbara - UCSB ECE

Read More..

How scammers used ‘social engineering’ to steal over $1 million from an Idaho town of less than 4000 people – Business Insider Africa

Officials in Gooding said this week that an employee sent a payment of $1,092,519 meant for contractors working on a wastewater project, but it went to scammers instead.

According to a city press release, the scammers impersonated representatives ofa contractor hired by city officials, using a tactic called social engineering to gain the employee's trust.

In the Idaho case, after the scammers gained the trust of the employee, they told the employee the bank information needed updating before sending payment.

"In this case, the request to change payment information was done with legitimate appearing documentation," city officials said. "The conspirators then waited for the city to transfer the vendor payment. After the funds were unknowingly deposited in the scammers' account, they were diverted to a different account."

The city's bank says it hasn't recovered the funds yet.

It's notoriously difficult for banks and law enforcement to recover money lost to scammers. Police in Florida said they were only able to recover about $40,000 after an older woman lost over $400,000 in a fake sweepstakes scam in April.

"You go obtain subpoenas and then the bank takes their time about getting data back, the money is gone, long gone," the local sheriff said during a press conference at the time.

If you lose money to a scammer, the Federal Trade Commission recommends asking whatever payment service credit card, bank, or transaction app you sent the money through to help recover the funds.

The Gooding Sheriff's Office and the FBI are investigating the incident, the city said.

The FBI Salt Lake City office which oversees investigations in Idaho did not immediately return a request for comment from Business Insider.

See more here:

How scammers used 'social engineering' to steal over $1 million from an Idaho town of less than 4000 people - Business Insider Africa

Read More..