#Application Decommissioning
Explore tagged Tumblr posts
Text
The Importance of Application Decommissioning in Reducing IT Complexity
In the rapidly evolving world of technology, managing IT infrastructure efficiently is a constant challenge. As organizations grow and adapt to new technological advancements, the need to streamline operations and reduce IT complexity becomes increasingly critical. One effective strategy for achieving this is through application decommissioning. By retiring outdated or redundant applications, organizations can simplify their IT landscape, reduce costs, and enhance operational efficiency. This article explores the importance of application decommissioning and its role in reducing IT complexity.
Understanding Application Decommissioning
Application decommissioning involves the systematic retirement of obsolete, redundant, or underutilized applications. This process includes migrating essential data to newer systems, ensuring data integrity, and securely disposing of the decommissioned applications. Effective application decommissioning requires careful planning, risk assessment, and execution to minimize disruptions and maximize benefits.
Reducing IT Complexity
Streamlined Operations
One of the primary benefits of application decommissioning is the streamlining of IT operations. Over time, organizations accumulate numerous applications, many of which become redundant or obsolete. Maintaining these applications can be resource-intensive, leading to inefficiencies. By decommissioning unnecessary applications, organizations can reduce the complexity of their IT environment, making it easier to manage and maintain.
Cost Savings
Maintaining legacy applications often comes with high costs, including licensing fees, maintenance expenses, and the need for specialized support. Application decommissioning can lead to significant cost savings by eliminating these expenses. Additionally, reducing the number of applications in use can lower infrastructure costs, as fewer resources are needed to support the IT environment.
Improved Security
Outdated applications can pose significant security risks, as they may no longer receive regular updates or patches. This makes them vulnerable to cyber threats and data breaches. By decommissioning these applications, organizations can enhance their security posture. Ensuring that only up-to-date, secure applications are in use reduces the attack surface and minimizes the risk of security incidents.
Enhanced Compliance
Compliance with regulatory requirements is a critical concern for many organizations. Legacy applications may not meet current compliance standards, putting the organization at risk of legal and financial penalties. Application decommissioning helps ensure that all active applications comply with relevant regulations. Properly archiving or migrating data from decommissioned applications also helps maintain compliance with data retention and privacy requirements.
Key Steps in Application Decommissioning
Assessment and Inventory
The first step in application decommissioning is to conduct a thorough assessment of the existing applications. This includes creating an inventory of all applications, identifying their functions, dependencies, and usage patterns. Understanding which applications are redundant or obsolete is crucial for developing an effective decommissioning plan.
Stakeholder Engagement
Engaging stakeholders throughout the decommissioning process is essential. Stakeholders include IT staff, business unit leaders, and end-users who rely on the applications. Their input helps identify critical applications, potential risks, and the impact on business operations. Clear communication ensures that all parties are informed and supportive of the decommissioning efforts.
Data Migration and Archiving
Migrating and archiving data from decommissioned applications is a critical component of the process. Ensuring data integrity and compliance with regulatory requirements is paramount. Data migration should be carefully planned and executed to avoid data loss and ensure that all necessary data is available in the new system or archive.
Risk Assessment and Mitigation
A comprehensive risk assessment identifies potential challenges and issues that may arise during the decommissioning process. Developing a mitigation strategy for each identified risk ensures the organization is prepared to handle any issues that arise, minimizing their impact on operations.
Implementation and Testing
Before fully decommissioning an application, thorough testing is essential. This involves verifying that data migration has been successful, ensuring that new systems are functioning correctly, and addressing any issues. Testing provides an opportunity to identify and resolve problems before the final shutdown.
Conclusion
Application decommissioning plays a vital role in reducing IT complexity and enhancing operational efficiency. By systematically retiring outdated or redundant applications, organizations can streamline their IT environment, reduce costs, improve security, and ensure compliance with regulatory requirements. A well-executed decommissioning plan, supported by thorough assessment, stakeholder engagement, risk mitigation, and careful implementation, is essential for maximizing the benefits of application decommissioning. Embracing this strategic approach allows organizations to optimize their IT infrastructure and stay competitive in an ever-evolving technological landscape.
0 notes
Text
Legacy to Cloud: Unleashing the Potential of SAP System Migration
In the ever-evolving landscape of enterprise technology, the migration from legacy SAP systems to cloud environments has emerged as a pivotal strategy, promising organizations unparalleled benefits in efficiency, agility, and innovation. This transformative journey, often referred to as SAP system migration, opens new horizons for businesses seeking to harness the full potential of modern cloud infrastructures.
Introduction: Unlocking the Cloud's Potential for SAP Systems
In the initial stages of the blog, it's imperative to set the stage by emphasizing the dynamic nature of the business environment and the pressing need for organizations to adapt. Introduce the concept of SAP system migration as a proactive response to stay ahead in a competitive digital era.
The Legacy Challenge: Overcoming Constraints in Traditional SAP Systems
Detail the limitations inherent in traditional on-premise SAP systems that hinder scalability, flexibility, and rapid adaptation to changing business requirements. Discuss issues such as infrastructure maintenance, high costs, and the difficulty of accommodating emerging technologies in legacy environments.
Cloud Migration as a Strategic Imperative: Key Drivers
Explore the driving forces compelling organizations to embark on the migration journey. Highlight factors such as scalability, cost-efficiency, real-time collaboration, and the ability to leverage advanced technologies seamlessly. Use real-world examples or case studies to illustrate successful transitions.
Seamless Transition: Navigating the Migration Process
Delve into the technicalities of the SAP system migration process. Discuss step-by-step procedures, potential challenges, and best practices to ensure a smooth transition. Address concerns related to data integrity, system downtime, and the importance of a well-thought-out migration plan.
Advantages of Cloud-Ready SAP Systems: A Comprehensive Overview
Provide an in-depth examination of the advantages organizations stand to gain by migrating their SAP systems to the cloud. This could include improved accessibility, enhanced collaboration, instant scalability, and the ability to leverage advanced analytics and artificial intelligence.
Realizing Innovation: Integration with Emerging Technologies
Highlight how the migration to the cloud opens up opportunities for organizations to integrate emerging technologies seamlessly. Discuss how cloud environments serve as fertile ground for adopting and experimenting with technologies such as AI, machine learning, and IoT.
Case Studies: Success Stories of SAP System Migration
Support your narrative with real-world examples of organizations that have successfully migrated their SAP systems to the cloud. Showcase the positive impact on their operations, cost savings, and ability to innovate in a rapidly changing market.
Security Considerations: Safeguarding Data in the Cloud
Address concerns related to data security and compliance. Discuss the robust security measures in place in leading cloud platforms and how organizations can ensure the confidentiality and integrity of their critical data during and after migration.
Challenges and Mitigations: A Pragmatic Approach
Acknowledge potential challenges and pitfalls associated with SAP system migration, offering practical solutions and strategies for mitigation. Discuss the importance of collaboration between IT and business stakeholders throughout the migration journey.
Conclusion: A New Horizon for SAP Systems
Conclude the blog by summarizing the transformative journey from legacy SAP systems to the cloud. Emphasize that SAP system migration is not just a technological shift but a strategic move that positions organizations to thrive in the digital age.
Call to Action: Embracing the Future Today
Encourage readers to evaluate their current SAP landscapes, consider the benefits of migration, and embark on their own journey to unlock the full potential of SAP systems in the cloud. Provide resources, links, or contacts for further guidance.
By weaving together technical insights, real-world examples, and strategic considerations, this blog aims to be a comprehensive guide for organizations contemplating or undergoing the migration of SAP systems to the cloud.
#carve-out#it application decommissioning#mergers and acquisitions#sap system#system decommissioning#insolvency#legacy system#liquidation#application decommissioning
1 note
·
View note
Text
Decommissioning legacy applications is a complex process that requires careful planning and execution. Some of the common challenges faced by organizations include..
Please click Below link to read more: https://avendata.com/blog/simplifying-it-application-decommissioning
0 notes
Text
The Sergeant's Senator | Chapter 7
Summary: The day of the vote has finally arrived. As the senator prepares her departure to the senate, the assassin makes one final attempt which ends up causing more destruction than anticipated.
Warning: language, suggestive sexual content, assassination attempt, weapons used (guns and bombs), sniper/shooter/assassin mentioned, characters getting shot at, blood lose and major bodily injuries, slight language, somebody dying
Pairing: Hunter x Fem!Reader Senator
Type: Short Series
Word Count: 4.4k words
Series Masterlist
An agreement had been reached the following morning. Despite their growing feelings for one another, the sergeant and senator came to realize that they could never truly be together. Should it come out that they were a thing, they'd both be demoted from their positions and the sergeant would be decommissioned. Therefore, they decided the sever the connection altogether. And it was the most painful thing either of them had to do.
For whatever time they had left working together, they created boundaries with one another to prevent feelings from developing any further. The distance between the two was bound to cause a deeper longing to reunite. But they knew this couldn't happen and their time was running out.
In the morning, Senator Rayna made the decision to fill out the application form for a new escort. Signing her name had never been so difficult in her life and sending the form off to the guard only caused tears to well in the corners of her eyes.
There was no point in putting it off, especially since Echo knew about it and it would have only been a matter of time before the others found out. As the leader of the group, Hunter ended up breaking the news to them when they arrived that day. He explained that the senator sent in the paperwork and that they should be receiving new orders any day now.
The Bad Batch took the news with mixed emotions. While they missed being in action on the field, there was something simple about protecting a senator in a busy city. It seemed like Crosshair was the only one who was the most pleased with the news, muttering a "finally" under his breath.
The Senator of Coruscant had been standing near the back of the room, listening to the entire conversation with her head hanging low. Her heart never ached so badly then it did in that moment. She tried keeping the tears back.
The memories of their night spend together weighed heavy on her mind, wishing more than ever that she'd be able to have that again with him. Though it was highly unlikely.
After breaking the news, Hunter's eyes drifted up to gaze at the senator from across the room. Only Y/n was quick to look away in order to avoid any more unnecessary pain. He wanted nothing more than to reach out to her, to touch her arm and reassure her that everything was going to be alright even if they weren't there. But he just couldn't do it.
What drew Hunter out of his thoughts was when Echo went up to approach him. He saw the conflict behind his eyes and in his demeanor. He brought a reassuring hand to his shoulder.
"That couldn't have been an easy conversation for you two," Echo noted with a sense of concern in his voice.
"No," Hunter hung his head low. He pushed the pain in his heart away. "It wasn't."
"You really did care about her, didn't you?" Echo wondered. He tilted his head to the side slightly.
"Still do," Hunter acknowledged painfully with a shrug of the shoulders. "Just...can't do anything about it now."
With some hesitation, Echo nodded his head as if to say he understood where he was coming from. He gave his shoulder a couple pats, reassuring him that he'd get over this eventually. But Hunter wondered if he truly could.
Near the back of the room, Crosshair managed to sneak his way over to stand right beside the senator. He leaned back against the wall and cross his arms over his chest. His eyes briefly glanced up at Hunter from across the room, curious to what Echo was talking to him about. He struck up his own conversation.
"He looks miserable," Crosshair grunted. He pulled a single toothpick out of his box, popping it into his mouth to naw on. "Makes you wonder what kinds of things were said between you two yesterday."
"It was a private conversation," Y/n said sourly. She wore an evident frown on her face. "What was said is meant to stay private."
"It doesn't matter anyways," Crosshair shrugged off. "Because we'll be shipped off soon. And everything will go back to normal like how it always should have been."
His words sounded like they were laced with fire. The senator turned her body to face him, staring up at him with a slight look of shock on her face.
"You've never liked me," Senator Rayna pointed out. "From the moment you got here, I could only see the contempt behind your eyes."
"I don't just dislike you," Crosshair pushed off the wall to face her. He leaned down to be eye level and pushed himself forward slightly. With narrowed eyes, Crosshair spat out how he truly felt: "I despise you."
Upon hearing those words, Senator Rayna's face only dropped. A massive wave of newfound hurt sought to drown her and consumed her entire body. She felt the tears gathering in her eyes, which she tried to hide because she knew it would only bring him satisfaction.
"W-What have I ever d-done to you?" Y/n said through her tears.
"It's not what you did to me. It's what you did to him," Crosshair acknowledged. He tipped his head to gesture to his oldest brother from across the room. She turned her head to look towards the sergeant. "You made him weak and soft," Crosshair scowled.
The sniper took a step towards her, which only caused her to stumble over her own feet as she put distance between them. He towered over her to intimidate her. She hated to admit that it was working.
"If anything happens to you, I wouldn't give a damn because that would mean we'd finally be rid of you. Leaving this place will be the best thing to happen for this squad," Crosshair spat down at her.
"Crosshair," Hunter's voice called from across the room.
Neither of them turned their heads to address him, but they knew he was looking directly at them.
"That's enough," Hunter scolded.
For a brief moment, Crosshair and Y/n had forgotten about Hunter's enhanced senses, particularly his hearing. Their entire exchange hadn't gone unheard. He heard every word of hatred that came from his brother and he resented him for it.
Because the senator didn't deserve to be treated that way and if his brother had a problem with how he was acting, then he should have confronted him instead.
"We should get going. I don't want the senator to miss the vote," Hunter announced.
The senator didn't care about the speech she had given a week prior, the vote that was about to happen, or even the results that she worked so hard for. Her mind had been completely captivated by her sergeant that she couldn't have.
Without wanting to cause any further arguments, the Bad Batch proceeded to follow the senator out of her office. They followed directly behind her and would escort her to the vote. However, Crosshair and Hunter lingered behind for a brief moment until the room was completely empty.
In that moment, Hunter sent his brother a glaring look of disapproval and complete anger. His hands had subconsciously clenched into tight fists at his sides. He looked away and started heading towards the door of the office, but right as he met the threshold, Crosshair finally broke the silence.
"You fucked her, didn't you?" Crosshair's tone didn't seem to waver.
Upon hearing those words, Hunter stopped short in his steps. His shoulders began to tense up and his hands remained clenched. It was getting harder to him to not blow up. He didn't say anything at first.
His silence was enough of an answer.
"That's why this has been so hard for you. You got attached," Crosshair pointed out.
Slowly, Crosshair went to approach his the doorway in which his brother stood. He let out a small scoff, quickly glancing him up and down.
"Didn't think you had it in you. Hope you left her feeling satisfied," Crosshair spoke with venom in his tone. He threw another toothpick into his mouth before wordlessly making his exit. The sergeant was left alone in the room, but the weight of his guilt was ever present.
The hired hitman felt a single bead of sweat sliding down the side of his face as he hid behind one of the pillars in the sniper's nest. He clutched a small device in his hands, hanging his thumb over a solid red button. He waited for the perfect moment.
Unbeknownst to the Bad Batch, there were three hidden bombs scattered around the landing platform that they just walked out on. One of the bombs was hidden right underneath the airspeeder and had been activated a couple minutes ago. Any electronic frequencies from the bomb would remain hidden since it was attached to a vehicle that also emitted frequencies. The other two bombs were yet to be activated.
The sniper was careful to peer around the pillar; his gaze fell on the small group walking across the platform and heading directly towards the airspeeder. He pressed the single red button which activated the countdown from one of the other bombs.
In that exact moment, Hunter froze in his place. He held up his hand to stop the rest of the group. His eyes seemed to narrow in slight confusion as his hearing focused on the little faint beeping sound coming from the opposite side of the platform. He looked over his shoulder, settling his sights on the entrance of the building they just came from. He felt the frequencies radiating heavily from one specific area.
"What is it, Hunter?" Echo inquired.
"There is a bomb nearby," Hunter whispered under his breath.
"A bomb?" Wrecker repeated just a little too loud. He quickly looked around as if he magically spot it. He raised his own blaster a little higher. "Where is it? I'll take it out."
"Not your brightest plan," Crosshair said while rolling his eyes.
"We must calculate our steps," Tech pointed out. "Any certain movement could trigger it."
"Wait for my signal," Hunter order. He began to make his way through the group, heading back towards the center of the platform.
"Hunter," Y/n called after him. "I don't like this."
"Don't worry," Hunter reassured her with a small smile. "If anything happens, Tech will stay to protect you."
"Alright," Y/n agreed. "Just be careful."
With some hesitation, Hunter started walking back towards the entrance of the building. He had retrieved his own blaster from his holster and now held it up. He peered through the scope in hopes of spotting something. He waved his hand to signal the other members to follow him.
Now Wrecker, Echo, and Crosshair began moving towards the center of the platform with their own weapons raised. They scouted the peaks in the tower, searching for any sign of the sniper. Back near the airspeeder, Tech made sure to stand relatively close to the senator in case anything happened. He held his blaster in front of him.
Kneeling down, Hunter spotted the small beeping device that was tucked behind one of the pillars. He felt a tight knot forming in his stomach at the mere sight of an active bomb in front of him. He quickly called for Wrecker to disarm it.
Slowly, Hunter forced himself to rise to his feet so that Wrecker was able to get into position. He spun around on the heels of his feet in order to face the senator. He gave a single wave of the hand as if to say they had the situation handled.
Suddenly, Hunter could feel his heart dropping so fast in the pit of his stomach as his eyes landed on the same beeping device hidden underneath the speeder. He broke into a run, urging them to get down. But it was much too late for that.
The device had detonated, which sparked an explosion of destructive fire that consumed everything. There was a loud and echoing boom that caused ears to start ringing in pain. The shockwave that came from the explosion only pushed the others back to the ground. The bright red, yellow, and orange flames only grew as more fuel was added from the airspeeder. Cracks had begun to form on the platform and black smoke surrounded them.
Just as the device had detonated, Hunter had lost sight of the two people standing in front of the speeder. Their bodies disappearing in the midst of flame and smoke. Before he knew it, Hunter was lying on the ground having been thrown back from the blast. He rolled onto his side.
The sergeant groaned in slight pain. He held his arm up to shield his visor from the blinding flames. He did manage to find his footing as he stood on two shaky feet. He quickly turned around to find his other brothers behind him which brought a wave of relief over him. But that also didn't last long because the other two bombs detonated a second later.
The Bad Batch was knocked down from the force of the blast and debris falling around them. The pillars from the building caved from the destructive explosion, crumbling down and striking the platform with such force that it made deeper cracks. More clouds of black smoke swept around their bodies and the ash began fluttering through the air. The world disappeared underneath the veil of darkness, claiming the conscious mind of the sergeant.
The dust had failed to settle anytime soon. With the fire still burning steadily, a thick aroma of black smoke consumed the area. The platform could be heard groaning in pain because the supports holding it up had been compromised. It was only a matter of time before parts of the platform began to give way.
On the sidelines, Tech had to take a moment to gather himself. He had only just come to a second ago. Squeezing his eyes shut tightly, Tech tried to ignore the painful ache that consumed his entire body. His armor had done its job of protecting him from the explosion, but it had still grown hot to the touch from the flames.
Rolling onto his back, Tech's eyes drifted to the bright blue sky above him. He pushed himself into a sitting position, finally turning to address some of his surroundings. There was a small explosion on his left, which caused him to wince roughly and cower behind his arm.
"D-Does anyone copy?" Tech spoke into his communication system, silently praying that someone would hear his message. "I-I r-repeat: does anyone copy?"
The line remained silent much to his dismay.
Forcing himself to stand, Tech tried to use his helmet to scan the area in search for any remaining lifeforms. His visor illuminated the form of a red body underneath some heavy debris not too far away from him. He quickly made his way over to the body, mindfully avoiding the cracks below him.
Upon closer inspection, Tech had recognized the figure belonging to that of the senator. He knelt down beside her unconscious form, desperately searching for a way to lift the heavy debris off her body. Though Tech didn't ignore the fact that the side of her head was dripping with blood, having sustained a traumatic head injury. Right now, Tech just needed to get her out of there.
"If anyone can hear me, the senator is down. I repeat: the senator is down." Tech announced through the communication line though it came through super spotty to the others. As the other squad members came to their senses, the words 'senator' and 'down' were coming through their helmets.
Despite his efforts, Tech was unable to lift the cement debris by himself. He tried a couple times; He pulled and pushed with all of his might to move the huge chuck of pillar, but he wasn't the muscle of the group.
All of the sudden, Tech was able to hear a familiar groaning coming from the cloud of smoke beside him. The familiar figure of the biggest group member appeared to pierce through the smoke. He slowly trudged towards his brother while holding his arm and limping slightly.
"Wrecker!" Tech exclaimed. "I've never been more happy to see you."
"Yeah," Wrecker groaned in slight pain as he approached his brother. "Good to see you too, Tech."
The platform shook slightly under the added weight to that specific area. In response, Tech's eyes fell onto a large crack developing on the ground near them. He realized that the platform was beginning to fall away. He looked up at his brother with wide eyes.
"Watch your step," Tech ordered strategically. "This place could give away at any second."
With a firm nod, Wrecker made sure to watch his steps carefully and maneuvered his way over to them both. He quickly found a sturdy place to stand. He bent his knees and took hold of the debris.
"I'll lift. You pull her out," Wrecker explained. He counted down from three before lifting the heavy piece of cement upwards a couple inches. It was just enough space for his brother to pull the senator out.
Once the senator was secure, Wrecker slowly lowered the pillar back down onto the platform while being careful not to destroy the ground. He knelt down beside them just as Tech began scanning the senator with his data pad.
"How bad is she?" Wrecker inquired with a sad look in his eyes.
"Bad," Tech said blatantly. He typed something into his data pad. "She is suffering from severe internal bleeding and will likely succumb to her injuries if she does not receive immediate medical attention soon."
"We need to get to the Marauder," Wrecker realized.
In another part of the platform, Echo felt like he was reliving what he gone through years ago. The familiar aches and pains were almost too much for his body since he had been close to the explosion. He struggled to compose himself, standing to his feet slowly and shakily. He let out a low groan.
In a brief moment of panic, Echo turned his head to the left and to the right in a desperate attempt of locating the others. He called their names a few times, but failed to receive a response from them. He brought his hand up the the ventilator of his helmet, coughing slightly as he ingested smoke that failed to filter.
"I-If anyone..." Tech's voice cracked through the comms. Echo quickly pressed his finger against the side of his helmet to hear the message more clearly. "Sen-n--nator--d-do-own. M-M-Mauad--now," Tech called.
The only thing going through Echo's mind was how he needed to get to the Marauder. He quickly broke off into a sprint back towards the building with every intention of retrieving the ship from one of the other platforms. He shielded himself from the burning flames and rising smoke, risking it all for the mission.
"I'm o-on...my...way," Echo's voice spoke through the weak communication line.
Upon hearing the broken message, Tech and Wrecker breathed a small sigh of relief. They could rest easy for a moment knowing that help was on it's way and that another one of their brothers was alive. They glanced at each other before redirecting their attention back to helping the senator.
"Senator?" Tech spoke softly while gazing down at her. "Can you hear me? We need you to wake up."
But she hadn't moved.
All the while, Wrecker watched his brother's hands work quickly and skillfully. He had a handful of gauzes and serums from his pack. Pulling out his data pad again, Tech pressed a button which imitated a blue scan over her entire body. He didn't like the look of what showed up on the screen.
"Brain activity is dangerously low," Tech commented more to himself than anyone.
"W-What does that mean?" Wrecker worried.
"She's dying, Wrecker." Tech replied.
Without hesitation, Tech removed his helmet and tossed it to the side. He proceeded to take off his gloves next. His gaze shuffled down to the large gaping wound on the side of the senator's abdomen. The blood was seeping out of her body at a rapid pace. And Tech didn't know if he could slow it down.
"Wrecker," Tech called. He pointed to the leaking wound on her side. "I need you to apply pressure right here. Don't let up. It will slow the bleeding."
Carefully, Wrecker's large hands hovered over the spot. It took him a second before he finally gave into the internal conflict. He pressed his hands into the fresh wound in hopes of stopping the blood from flowing so quickly. He tried to ignore the way the blood seeped over his fingers. And he had to look away in fear of losing his stomach to the sight of gore.
In the midst of chaos, Hunter was slow to come back to his senses. His body was screaming in pain from the mere force of the blast. He shifted his hands underneath himself, pushing his upper body upwards slightly. His muscles shook as he did so; a small groan escaping past his filtered helmet.
With some difficulty, Hunter was able to get to his feet. He desperately searched for the others, but he couldn't see anything beyond the smoke and debris surrounding him. His senses failed him as well because he couldn't seem to pick up their all-too familiar smell. He called for them over the comms, but it seemed like his helmet was busted.
All of the sudden, a blaster shot came out of nowhere and lodged itself in the back of his right shoulder. The proximity of the shot caused him to stumble forward onto his knees. He grabbed his shoulder in pain, hissing at the sharp pain. He just barely managed to glance over his shoulder to spot the assailant walking through the black clouds of smoke with a blaster raised in his hand.
"I must admit: it hasn't been easy trying to take my target down. You're one hell of a soldier," the mysterious assassin spoke with a deep cynical voice behind his mask. He took a couple more steps forward until he was standing right above the clone.
"What do you want...a medal?" Hunter groaned in slight agony. He gripped his shoulder a little tighter in hopes that it would relieve some of the pain.
"Oh, I don't care about you." He knelt down in front of him, pointing the blaster directly at his face. "I only care about killing the senator and getting paid. I'm looking forward to cashing those credits in."
The assailant was taunting him. The anger and rage began to boil within the sergeant's veins, threatening to break loose at any moment. He held a stoic face, but was biting his tongue until he tasted his own blood. He wanted nothing more than to punch that stupid helmet off the guy's face.
All of the sudden, another random blaster bolt had whizzed through the air. The blaster shot smacked into the center of the assassins chest, sending him flying backwards until he was laying flat against the platform. The sergeant scrambled into a sitting position, shifting to glance over his shoulder. His eyes landed on the familiar sharpshoot pointing his rifle at the body.
For a brief moment, Hunter had never been more relieved to see his brother despite the risk he had taken in shooting the assassin down. He tried to rise to his feet while still holding onto his shoulder. However, Crosshair had joined his side and grabbed his arm. He helped him rise to his feet, double checking to make sure his oldest brother was alright.
"T-Thanks," Hunter said. He looked at his youngest brother with a small hint of pride in his eyes.
"Don't mention it," Crosshair scolded him with a serious look behind his eyes. "I mean it."
Together, Hunter and Crosshair made their way over to the suffering body of the assailant that was still laying on the ground. As they drew closer, Hunter was the first to step forward and kneel down in front of him. He pressed the bottom on the side of mysterious man's helmet, activating the trigger to retract the facemark.
What they both saw was shocking. It was a clone.
However, he wasn't wearing the typical clone armor; this style was coated in black and the mask had dark green eyes. They weren't even sure what generation of clone he would have been. His tactics were far from a regular clone. But he wore the face that millions of clones shared. This was something else, something new.
"This...complicates things," Hunter noted. He furrowed his eyebrows in slight confusion. They stood tall above him. "You're just a reg. Why are you trying to kill the senator?"
The clone assassin only let out a crazed laugh, which caused a few steams of blood to escape the corners of his mouth. His body was starting to succumb to his injuries, growing weaker with each passing moment. He looked up at the two enhanced clones, shaking his head slightly.
"L-Like I said, I was just doing a job to get paid."
"Who hired you?" Hunter demanded an answer.
"I'll never tell you," the assassin hissed. "You'll have to shoot me de--"
But the man was never able to finish that sentence because the sharpshooter had shot him once more to silence him forever. He silently strapped his rifle onto his back, turning to walk away and ignoring the look his brother was sending him.
At the given moment, Hunter was overwhelmed with a million different emotions. He wore a shocked expression on his face, not believing what his brother just pulled off. Not only that, but he was also incredibly taken back by the fact that he shot a clone without hesitation. He watched his figure retreat, but he called after him.
"What the hell were you thinking? Shooting a brother like that," Hunter gestured to the motionless body behind him.
"He's not a brother," Crosshair shrugged his shoulders. "He's just another reg. They're disposable."
"We didn't know anything about this clone. What his motives were, where he came from, or why he was trying to kill the senator," Hunter listed off. "He deserved to stand a fair trial," Hunter argued.
Upon hearing this, Crosshair stopped in the middle of his tracks. He threw a brief glance over his shoulder with a taunting smirk gracing his lips. He huffed.
"Starting to sound like your little girlfriend," Crosshair mocked.
"That's enough, Crosshair. You shouldn't have done what you did. You crossed a line," Hunter said through gritted teeth. His hands began to clench at his sides.
"You know...you should be thanking me," Crosshair replied. He was now turned to face his brother head on. "The threat is gone. Your girlfriend is safe. And we can finally leave this place. We completed the mission."
"You killed a clone," Hunter ignored him.
"I completed the mission," Crosshair corrected. The two brothers stared at each other with dangerously narrowed eyes, waiting for the other one to break first. But a familiar voice pulled them out of their internal war.
"H-Hunter...H--Hunter," Echo's voice broke through the communication system. "Come in. D-Do you read me?"
"I hear you, Echo." Hunter spoke while pressing the side of his helmet.
"I-I'm bringing the Marauder around now," Echo explained. The line was starting to get a little clearer and crispy as he spoke. "Tech says we need to get the senator out of here as soon as possible. She doesn't have a lot of time."
"Copy that," Hunter nodded. "We are on our way."
The ship was able to round the side of the building. The wind blasting from the engines was enough to push the clouds of black smoke away from the platform momentarily, providing a clear direction for where the others were on the opposite side. The ship was descending until it hovered right by the edge of the platform.
With great precision, Crosshair and Hunter began to make their way towards the group of others. They avoided the cracks in the ground, coming up beside their fellow brothers. The sergeant took a moment to stare down at the senator's motionless body, surveying her injuries carefully.
Though Tech was still working on bandaging up some of her wounds, Wrecker was still keeping his hands pressed against the gaping hole on her side. He made sure to avoid his sergeant's gaze, feeling a bit helpless in their failed attempt to protect her from harm. The sharpshooter was the only one brave enough to look directly at the sergeant with an all-knowing look in his eyes.
It was like Crosshair was saying it all over again to Hunter. Don't get too attached. Because this is what he'll get.
CHAPTER EIGHT HERE
Taglist:
@justhavingsomefun1 @totally-not-your-babe @jedipoodoo @gyllord @roam-rs @totallyunidentified @redheadgirl @mrcaptainrex @whore-of-many-hot-men @graciexmarvel @qweenrogerina @arcsimper5 @queenofspades6 @cadihyo @jediknightjana @elthoughtzos @lokigirlszendaya @sleepycreativewriter @moonwrecked @ravenclawbitch426 @waytoooldforthis78 @left-in-the-motel-bar @fic-force-99 @ayyyy-le-simp
THE SERIES IS ALMOST OVER! HOPE YOU'VE ENJOYED IT SO FAR.
#the bad batch#star wars#the clone wars#clone trooper hunter#tbb hunter#bad batch hunter#tbb hunter x reader#tbb hunter x you#tbb hunter x y/n#tbb hunter x senator#crosshair#echo#wrecker#tech#the marauder ship#tbb hunter series#tbb hunter fluff#tbb hunter angst#tbb hunter x fem!reader senator#clone x#clone assassin
71 notes
·
View notes
Note
I wonder how long the team doing on their own without their leader?
Actually, few months.
Numbuh 442 was decommissioned on June 22nd, 1985. After that, Lou took over as leader, and the group went on with only four members.
In September 1985, it was decided to take Sector Ʌ out of service and put 5 sectors around Australia to make work easy for KND (also because they received a lot of joining applications from there after the whole Fire Goddess accident). So, as the last members got decommissioned, the Sector would cease operation.
On March 21st, 1986, Numbuh 443 was decommissioned, and it was decided that Sector Ʌ would, from that moment on, just be used as training grounds for the other Sectors that would protect Australia in the future; Numbuh 444A would think about plan-making and leader actions, Numbuh 445 would help with weapons and fighting training and Numbuh 444B would train pilots and mappists (Even if at that point mappists were starting to get replaced with new age radars and digital maps. Syd had a hard time trying to tell these kids why orientation was important, but they wouldn't listen).
Finally, we arrived in August 1986, the day that ended everything.
After getting a distress call from Sector Z in America, the trio decided to go investigate by themselves, without reporting to Moonbase or anyone else, where they met Father and the Delightfuls for the first time.
During that night, Numbuh 444A disappeared and when the rest of KND arrived, Syd begged to be decommissioned immediately, without saying what exactly happened. Numbuh 444B was decommissioned 4 months before their 13th birthday.
Charlie was deeply hurt by all of that, from Lou disappearing to Syd refusing to tell even her what happened.
Sector Ʌ was taken out of commission the day after and Numbuh 445 was moved to Moonbase as Head of Decommission until September 21st, 1987, when she turned 13 and was decommissioned.
As for Numbuh 444C, he stayed at the treehouse guarding it until his passing in 1999.
Sector Ʌ was slowly forgotten and is now regarded as a myth by the whole KND organization.
16 notes
·
View notes
Text
My first ever Android Smartphone - Busted (Cherry Mobile Jelly) [feat. my Paper Dolls]
DeviantART version → [CLICK ME!]
Hello, August... 🏫🎒 It's been a rough and depressing month for me from nothing to earn funds for myself, to struggling with my life staying at home. 😟😞 Although I do occasionally go outside to get some fresh air when the sun is bright, it remains the same. 😔 I'm still stuck on my mom's slow-performance laptop, and I can't make item reviews because of the aforementioned laptop. 👩💻 Meanwhile, I'm still browsing some job openings, though the only problem was the "lack of trustworthy". I did apply once and I was going to go anyway, however, my mom investigated the details of where the venue at for a schedule, and it turns out that the job that I applied for was a sham... Yeah, I dodged the bullet on going there owning to my flashbacks of what happened in 2019. *Sigh* So much for that... 😟 I wish this type of fraud job would be ended by the time the government and authorities caught red-handed on fake application jobs. Right now, I've already applied for a job by submitting a resume to legit hiring via email, and to this day nobody answered my call. I'm still a helper for my parents' small rug business, although they didn't give me a raise, but small treats and food. Also, I'm selling my scrap computer parts, unfortunately, nobody seemed to be interested in my items... Bummer. 😔
[I want a end my life... But, I refused to kill myself. Not yet... 😟😞]
Should I keep posting and sharing my items on tumblr? 🤔 I'm still thinking about it, but for now this could be my last item... As we hit the first "Ber" month (September 📆), I need to take a break from posting it until my custom PC desktop brought back to life with a brand new GPU Card. 🖥️🔧
Anyway, let's head back to my last item (before I go *semi* hiatus):
• What I have here is my first ever cheap Android Smartphone after I graduated from vocational college [Computer Programing] in 2014. 👨🎓🏫💻 This here is the "Cherry Mobile Jelly". 🤖📱 Actually, it's now simply called "Cherry" which we'll get to that later. Nonetheless, I bought this cheap and small smartphone for ₱ 2,299 💵 from a local trustworthy cellular phone store at the mall, I should it picked the blue color because I loved that color for life 💙, although it is out of stock so I guess I'll settle with green anyway. 🟩📱🤷♀️ (After all, green signifies an android phone, right? 🟩🤖📲 Nonetheless...) As for the specs of this phone, it is pretty low-profile standard considering that this is a budget-friendly smartphone. Here, go see it by click here → [CLICK ME! #1]. Unfortunately, as you can see, my first cheap smartphone ended in 2015 due to poor quality, as I accidentally fell off my phone numerous times causing it to crack the touch screen (not to mention, the battery phone had bloated.), and my Jelly phone ended its life. It was only a matter of time before my old phone was replaced by the outdated "Samsung Galaxy S Duos 2" [GT-S7582] (which was also decommissioned somewhere in 2019). As for the so-called "Cherry" brand, they're still producing smartphones albeit a small ranges because they've already expanded to daily electronic appliances (e.g. slim smart TV, washing machine, air purifier, etc...). Pls, click here to see → [CLICK ME! #2]. One more thing, the only feature really I missed from using the old Cherry Mobile Jelly is the ability to watch TV by raising the mini antenna and opening the TV app, as you've seen on my snapshot. 📺📲😊
• When it comes to comparison with my current Tecno Spark 20 Pro [CLICK ME!] smartphone, well... You noticed the BIG difference. 📱📲 To be honest, I missed holding a small Android smartphone, as holding it could be a very advantage (which is like holding an old MP4 player) over a tall and bulky smartphone, like my aforementioned Tecno mobile brand. 😊 And surprisingly, they're still producing small smartphones albeit in ✌"Made in China"✌ and they're using a vanilla yet recent Android Operating System, unlike Samsung, Huawei, Oppo, Xiaomi, and other giant smartphone brands with their state-of-the-art features and current running Android OS. Maybe someday I'll get my hands on the small Android phone for a nostalgic sake? Who knows? 🤷♀️ For now, though, I guess I'll stick with the taller smartphones. And as for my first ever owned cheap Android phone, it's already a relic of its time. Time for you to return to the memorabilia box. 🙂
Well, that's all for now. If you want to see my previous topic, then please → [CLICK ME!].
Tagged: @bryan360, @shadowredfeline, @leapant, @lordromulus90, @coda-archive, @sammirthebear2k4, @alexander1301
#My Photos#My Photo#MyPhotos#MyPhoto#Photos#Photo#Chowder#Chowder Panini#Paper Dolls#Cherry Mobile#Cherry Mobile Jelly#Tecno#Tecno Mobile#Tecno Spark 20 Pro#Tecno KJ6#Android Smartphone#Smartphone#Mobile Phone#Photography
8 notes
·
View notes
Text
To Secure / Risk It All
Chapter 10 / Epilogue 1
Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7 | Part 8 | Part 9 | Part 10 | Part 11
————
He hated them. No, that wasn’t right. He despised them. Loathed them. Or maybe, no word existed to convey just how much hate he harboured for them.
But he could not show it. Never say it.
He could only keep his face straight as the 05 council looked down on him.
The monitors were mounted to the wall above him on for that purpose. It had to. Of course they wanted to look down on anyone that wasn’t them. They didn’t even have the audacity to show their faces. Instead, they presented themselves as faceless silhouettes, peering down at him.
He hoped they didn’t notice the way his fingers dug into his hands, clasped behind his back.
“You may speak.” One, the leader, spoke, voice distorted.
Steeling himself and without moving an inch, he did.
“If I may be so bold to assume, I take this ‘emergency meeting’ you called is about the escape of SCP-9475, no?”
Even though the action made him want to hurl, he bowed his head. “I must confess my failure in containing and re-capturing SCP-9475. I underestimated their capabilities and the Foundation paid the price. I accept my mistakes come with a price and I am fully prepared to pay.”
He raised his head, looking up at the monitor in front of him. “However, I must stress that my failure is also due to a lack of resources. Their Euclid level, and the legal limitations in capturing that comes with it, restricted my ability to safely re-contain SCP-9475. Hence my request to the council to review SCP-9475’s status. I am positive that with a Keter status and accompanying resources, I can secure and contain SCP-9475 once more and this time without leaving room for any more escape attempts in the future.”
It was silent. Too silent.
He wished he could silence them forever.
“Please explain and elaborate.”
I won’t just kill you. “Research has suggested that SCP-9475’s abilities stem from the frontal and parietal lobes.” I’ll humiliate you. “Now, while removal of those areas is possible, it would be an unnecessary decommissioning.” I’ll will hurt and kill everyone you love. “Instead, I propose a similar containment option as SCP-239, where the SCP is kept in a medically induced coma.” I will break every bone in your body twice. “This way, we can secure SCP-9475 without risk of another containment breach.” I take and destroy everything you have. “Finally, with the research that can be conducted, we could potentially find a way to harness their ability to better contain Keter and perhaps even Apollyon class SCP’s.” And then I will put you out of your misery.
…
…
Why are they silent?
The faceless in front of him leaned forward. “Tell me. What does SCP stand for?”
…Why were they asking asking such an obvious question.
“To protect humanity from anomalies-“
“No. What does our acronym stand for?” They interrupted him.
……Why are they asking stupid questions!?
“………..May I ask-?”
“Answer the question.”
He tried to keep his gaze straight and face emotionless. “…….Secure, Contain and Protect, sir.”
Silence.
He wished he could tear out their eyes. Anything to stop the judging gazes upon him.
Finally, the faceless spoke. “We shall start with the first point. We have accepted your request to review SCP-9475’s status and we have come to the conclusion that Euclid is no longer applicable.”
He couldn’t keep a small smile from forming on his face.
“After discussion, we have decided to revise SCP-9475 status…”
This was it. This was his chance. His chance to-
“…to Archon.”
……… He was dumbfounded.
“What?”
“Archon is a class appointed to SCP’s that the Foundation is either completely unable or should not contain.”
“I know what Archon is.” The words blurted from his mouth before he could stop himself. He stopped, scraped his throat, and continued. “Apologies. But I want to ask why. Archon is reserved for SCP’s that are impossible to contain, such as concepts, or SCP’s that would be detrimental to humanity if contained. SCP-9475 is not a concept and can be contained. It also does not benefit humanity in any way. A Keter class would be more than sufficient.”
The faceless leaned back. “Even for a Keter class, containing SCP-9475 is a high risk-factor. The last attempt to do so resulted in disaster. More specifically a mass breach that you were barely able to re-contain.”
“It won’t happen again.” He stated, no, pleaded. “SCP-9475 will be separated and brought in a medical coma. This will keep them from activating their ability. We-“
The voice of the faceless raised. “I was not finished TALKING!”
He forced his teeth together.
“Conversely, despite SCP-9475’s reality altering abilities, the very nature of the pocket dimension they create means that all consequences of their actions are essentially erased, including memories, bodily harm and even death, as I’m sure you can attest to. This makes their actual risk towards humanity and the Veil minimal. SCP-9475 is no threat to civilians or their understanding of the universe. Granted, it’s not a perfect reset, as prolonged exposure can result in memories being maintained, but that is nothing the Foundation can’t fix themselves.”
No. He would not let this happen.
“This is against everything the Foundation stands for.” He argued. “SCP-9475 is an anomaly. It is not human. We keep other harmless SCP’s contained, as they should. There are containment options available to us. Why are you letting this one go!?”
They were silent. Silent for too long. But he didn’t mind this time. Because they were obviously considering his rightful words. There was no way he could allow them to just roam free. They had to see that. They would agree with him. There was no way they wouldn’t.
The faceless stared at him. Stared into his soul. He fought the chill going down his spine.
“You say that this is against the Foundation’s mission, correct?”
His mouth was dry. Why was his mouth dry? “Yes. Our mission is to Secure anomalies, Contain them and Protect humanity.”
Eyes pierced like daggers through him. He could tell the eyes of the faceless narrowed.
“Wrong.”
That single word caught him off guard, caused him to change his stance. He released the hands behind his back and one of his feet took a single step backwards. What was going on? Has the council gone mad!?
“Our mission is not just to protect humanity from SCP’s. It’s also to protect SCP’s from humanity. That is why we enact humane procedures on contained SCP’s and secure even the harmless ones.”
He pursed his lips to a thin line. “With all due respect, protecting the Veil is protecting humanity.”
For a moment, it seemed another member of council wanted to speak, but the faceless leaned forward again.
“Tell me, why do we keep SCP-085?”
“I don’t-“
“It’s a living drawing on a piece of paper. If we wanted to, we could easily toss her in the incinerator and she would be fully neutralised. So why do we spend Foundation money on her containment, allow personnel to draw items for her and talk to her? She’s a drawing, what kind of information could we gather from her that is helpful to society? So why, why do we keep her contained?”
“Curiosity?”
“No.” The faceless loomed over him. “It’s because we’re not monsters. We care. We care about humans, yes, but we also care about other beings with similar sentience. It’s why we installed rules, it’s why we installed the Ethics Committee.”
The room grew colder.
“An Ethics Committee that you have repeatedly brushed off, lied to and barred excess from your site.”
The cracks started to spring. It was in the way he widened his eyes ever so slightly.
“Oh, did you think we wouldn’t find out? I must admit, it was a good try. But we know and we are not happy.”
No. This couldn’t be happening.
“But that is a matter for later. In conclusion: SCP-9475 is a harmless non-to-minor threat to the Veil that is easily solved with amnestics. Contrary to that, SCP-9475 is near impossible to capture and contain, save for expensive, aggressive, disproportionate and inhumane measures. An Archon classification is more than fitting.”
No. He couldn’t let this happen!
“Are you all blind!?” He roared, the held-back venom finally spewing out. “With SCP-9475 contained, we can potentially get control over the power of reality altering! We can contain SCP’s thought to be uncontainable! Are you content with risking humanity’s safety for a single SCP!?”
There was a SLAM of a hand being brought down on the table.
“Johnathan Snee, I believe you must remember that Lady Luck already smiled upon you when SCP’s nature of undoing their actions saved you from death. Do not push her any further than you already have!”
He wasn’t even aware of the way he had balled his fists, narrowed his eyes or leaned forward until that last word left the faceless’s mouth. Taking back his composure, he fixed his stance, although he failed to look at the monitor directly.
“Facility Director Johnathan Snee, you are guilty of disrupting the Ethics Committee, unlawful experimentation of an SCP, being responsible for the death of said SCP, allowing SCP to break containment, and, if we are to believe some of your staff, abhorrent treatment of c-class and b-class. We shall discuss your full punishment, but do not believe you will be let off easily. For the time being, you are relieved of your duty and will remain in your designated quarters until further notice. You are dismissed.”
The screens turned off one by one, leaving him in darkness. Snee took a deep breath and turned on the lights with the remote, and turned them off when he left the room. He didn’t face anyone. He didn’t talk to anyone. He just walked to his room in the facility and closed the door behind him.
Those bastards. Everything he had worked for, gone in a flash. Gone because of a single, unimportant SCP. Every night of slaving away, every moment of hard work, every step he had clawed on the ladder, all for nothing.
And as he walked into his bathroom, his eyes caught his reflection in the mirror. Caught the faded red mark, like a bruise, right on his forehead. As a reminder of his greatest failure. Of the audacity, the nerve of the man and his so-called ‘friends’ to defy him, to shoot him, when he deserved-
He stopped his fist before it hit the glass.
Calm your mind. Count to ten. Breaking your things isn’t going to fix anything. It will just count against you.
He gripped the sink like a lifeline.
No. What he needed to do was think.
He needed plan B.
Snee took out his phone and walked out of the bathroom, then out the door of his quarters. Immediately, he activated the app, and walked back in.
The cameras would only show an empty room. But that didn’t mean he had all the time in the world.
He closed the door and locked it, and headed immediately for his bed, pulling it aside and reaching into the secret compartment.
Important documents about SCP-9475. Test results he had stolen. Every bit of information he was and was not allowed to have.
He picked out one of the photos. A photo of his former B-class underling. Curt Richy, the man who rebelled against him and stole everything away from him.
But it didn’t matter. His rank didn’t matter. His job didn’t matter. The Foundation didn’t matter. Because he had found something more powerful:
The ability to manipulate reality.
Run as far as you can, little monster. He thought to himself with a smile. Because it doesn’t matter. I will find you again, and I’ll take everything I lost and more. Your powers, my revenge, my victory…
I will secure it all!
———————
Not me trying to finish before it officially ends. I can’t imagine I wrote another chapter before I put links in the previous one lol
One more chapter left! And then I’ll start posting everything to AO3, with some fixes (and maybe some additional prologue???)
#recreyo#recreyo au#recreyo scp#recreyo scp au#scp recreyo#Johnathan Snee#fun fact this is the first chapter I wrote in a different note on my notes app#my writing
26 notes
·
View notes
Text
Image 1: a typical modern electric slime tram, with adorable "streamlining" and an Advanced Steam commuter train.
The steam engine is an Advanced steam engine with the gas generator boiler fired automatically using microcontrollers, with compound cylinders, steam super heaters, etc. The driver controls the locomotive electronically from a cab at either end of the train. Advanced steam engines were developed due to skyrocketing oil prices which drove up the price of electricity and made diesel hydraulics much less cost effective to operate. Old style steam locomotives would not have been considered up to snuff and the maintenance facilities for them had dwindled, but Advanced Steam sought to solve the maintenance and servicing problems. Most advanced steam was utilized for very large scale applications like freight hauls and migration trains, but the concepts could also be employed on smaller scales.
Image 2: Locomotives of the Slaibgloth Coal Mine. These comprise about 30 2-8-0+0-8-2 Garrats, 5 Shays, and 5 "easy" (non-articulated) locomotives utilizing spare engine sets from the Garrats and spare boilers from the Shays.
The Garrats were built in 2346 A.D. and retired in 2379 A.D. (two years ago) for service bringing coal carriages from the coal pits up to the interchange at the Glooiw & North Eastern. It is unusual for a coal burning steam engine to remain in revenue service--the majority that remained in use after the development of Diesel-Hydraulics were decommissioned with railway electrification and the ones that remained were mostly converted to oil burning. The Slaibsgloth steam engines meanwhile persisted right up until the closure of the coal mine. Glooiw & North Eastern has acquired the 40 locomotives. Their fates are uncertain but railway preservation groups remain optimistic.
#Mellanoid Slime Worldbuilding#Train#Steam train#steam engine#tram#trolley#railway#railroad#steam locomotive#steam train#Mellanoid slime worm#Slime Trains
12 notes
·
View notes
Text
Alt National Park Service
People often ask, “What exactly are we resisting?” So, we decided to keep a detailed list. From 2017 to 2021, the Trump administration reversed over 100 environmental regulations, affecting climate policy, air, water, wildlife, and chemical safety. Additionally, more than a dozen other rollbacks were in progress but not finalized by the end of the term, prompting questions about the potential impact of another four years. You might wonder what another four years could look like. Here's a summary of Trumps last four years in office:
- Weakened fuel economy and greenhouse gas standards.
- Revoked California's stricter emissions standards.
- Withdrawn legal basis for limiting mercury from coal plants.
- Exited the Paris climate agreement.
- Altered Clean Air Act cost-benefit analysis methods.
- Canceled methane emissions reporting for oil and gas companies.
- Revised rules on methane emissions from drilling on public lands.
- Eliminated methane standards for oil and gas facilities.
- Withdrew rule limiting toxic emissions from industrial polluters.
- Eased pollution safeguards for new power plants.
- Changed refinery pollution monitoring rules.
- Reversed emissions reduction during power plant malfunctions.
- Weakened air pollution rules for national parks and wilderness areas.
- Loosened state air pollution plan oversight.
- Established minimum threshold for regulating greenhouse gases.
- Relaxed pollution regulations for waste coal plants.
- Repealed hydrofluorocarbon leak and venting rules.
- Ended use of social cost of carbon in rulemaking.
- Allowed increased ozone pollution from upwind states.
- Stopped including greenhouse gas emissions in environmental reviews.
- Revoked federal greenhouse gas reduction goal.
- Repealed tailpipe emissions tracking on federal highways.
- Lifted ban on higher ethanol gasoline blends in summer.
- Extended deadlines for methane emissions plans for landfills.
- Withdrew rule reducing pollutants at sewage plants.
- Dropped tighter pollution standards for offshore oil and gas.
- Amended emissions standards for ceramics manufacturers.
- Relaxed leak monitoring at oil and gas facilities.
- Cut two national monuments in Utah.
- Ended freeze on new coal leases on public lands.
- Permitted oil and gas development in Arctic Refuge.
- Opened land for drilling in National Petroleum Reserve, Alaska.
- Lifted ban on logging in Tongass National Forest.
- Approved Dakota Access pipeline near Sioux reservation.
- Rescinded water pollution rules for fracking.
- Withdrawn rig decommissioning cost proof requirement.
- Moved cross-border project permits to presidential office.
- Altered FERC's greenhouse gas considerations in pipelines.
- Revised ocean and coastal water policy.
- Loosened offshore drilling safety regulations post-Deepwater Horizon.
- Weakened National Environmental Policy Act.
- Revoked flood standards for federal projects.
- Eased federal infrastructure project environmental reviews.
- Ended financing for overseas coal plants.
- Revoked directive to minimize natural resource impacts.
- Revoked climate resilience order for Bering Sea.
- Reversed public land-use planning update.
- Withdrawn climate change consideration in national park management.
- Limited environmental study length and page count.
- Dropped Obama-era climate change and conservation policies.
- Eliminated planning system to minimize oil and gas harm on sensitive lands.
- Withdrawn policies for improving resources affected by federal projects.
- Revised Forest Service project review process.
- Ended natural gas project environmental impact reviews.
- Rolled back migratory bird protections.
- Reduced habitat for northern spotted owl.
- Altered Endangered Species Act application.
- Weakened habitat protections under the Endangered Species Act.
- Ended automatic protections for threatened species.
- Reduced environmental protections for California salmon and smelt.
- Removed gray wolf from endangered list.
- Overturned bans on lead ammo and fishing tackle on federal lands.
- Reversed ban on predator hunting in Alaskan refuges.
- Reversed rule against baiting grizzly bears for hunting.
- Amended fishing regulations.
- Removed commercial fishing restrictions in marine preserve.
- Proposed changes to endangered marine mammal injury limits.
- Loosened fishing restrictions for Atlantic Bluefin Tuna.
- Overturned migratory bird handicrafts ban.
- Reduced Clean Water Act protections for tributaries and wetlands.
- Revoked stream debris dumping rule for coal companies.
- Weakened toxic discharge limits for power plants.
- Extended lead pipe removal time in water systems.
- Eased Clean Water Act for federal project permits over state objections.
- Allowed unlined coal ash ponds to continue operating.
- Withdrawn groundwater protections for uranium mines.
- Rejected chlorpyrifos pesticide ban.
- Declined financial responsibility rules for spills and accidents.
- Opted against requiring mining industry pollution cleanup proof.
- Narrowed toxic chemical safety assessment scope.
- Reversed braking system upgrades for hazardous material trains.
- Allowed liquefied natural gas rail transport.
- Rolled back hazardous chemical site safety rules.
- Narrowed pesticide application buffer zones.
- Removed copper filter cake from hazardous waste list.
- Limited use of scientific studies in public health regulations.
- Reduced corporate settlement funding for environmental projects.
- Repealed light bulb energy-efficiency regulation.
- Weakened dishwasher efficiency standards.
- Loosened efficiency standards for showerheads and appliances.
- Altered energy efficiency standard-setting process.
- Blocked efficiency standards for furnaces and water heaters.
- Simplified appliance efficiency test exemption process.
- Limited environmentally focused investments in 401(k) plans.
- Changed policy on using sand from protected ecosystems.
- Halted contributions to the Green Climate Fund.
- Reversed national park plastic bottle sale restrictions.
5 notes
·
View notes
Text
In the night of 9–10 July, students and other pro-Palestinian protestors present in the camp located at the entrance to the McGill campus found themselves served with an eviction notice. According to the university administration’s press release, the camp represented ‘an increasingly serious threat to health and safety’. A few hours later, cranes, bulldozers and other construction machinery arrived and destroyed the much infrastructure built over a period of 75 days.
On the 1st and 15th of May, the Quebec Superior Court had rejected two applications for a temporary decommissioning injunction. The two parties were to face off again in court on 25 July, but the heads of the university, unwilling to wait for the due process of law, called on Sirco, a private Quebec security company. This decision came because of the breakdown in negotiations between the heads of McGill and Concordia, the city’s two English-language universities – the students of the latter institution having also established their camp at McGill for want of space on their own campus – and their students represented by Solidarity for Palestinian Human Rights (SPHR).
‘This camp will remain historical and revolutionary’, says 20-year-old Ward (pseudo), a Lebanese student in political science and general co-ordinator for SPHR. ‘In Canada, McGill is the equivalent of Columbia in New York. When we saw that they had set up a camp down there, we said to ourselves we must do the same,’ he explains.
10 notes
·
View notes
Text
How to Maintain Data Integrity During Application Decommissioning
Application decommissioning is a critical process that organizations undertake to retire outdated, redundant, or unsupported software applications. While it offers significant benefits, such as cost savings, improved security, and streamlined operations, it also presents challenges—chief among them being the maintenance of data integrity. Ensuring data remains accurate, consistent, and reliable throughout the decommissioning process is essential. Here’s a comprehensive guide on how to maintain data integrity during application decommissioning.
Conduct a Thorough Assessment
Data Inventory
Identify all data associated with the application, including databases, files, and documentation.
Data Dependencies
Determine dependencies between the data and other applications or systems.
Develop a Decommissioning Plan
Timeline
Define clear timelines for each phase of the decommissioning process.
Stakeholders
Identify and involve key stakeholders, including data owners, IT staff, and compliance officers.
Data Migration and Archiving
Data Migration
If data is being migrated to a new system, ensure that the migration process includes data validation checks, such as verifying data completeness and consistency before and after migration.
Data Archiving
For data that needs to be archived, use reliable archiving solutions that support data indexing, searchability, and retrieval while preserving the original data structure and integrity.
Data Cleansing
Removing Duplicates
Eliminate duplicate records to ensure accuracy.
Correcting Inconsistencies
Address inconsistencies in data formats, units, and values.
Implement Data Governance Policies
Data Ownership
Clearly define data ownership and responsibilities for maintaining data quality.
Data Access
Implement strict access controls to prevent unauthorized access or modifications.
Data Audit
Conduct regular audits to verify data integrity and compliance with governance standards.
Validation and Testing
Data Validation
Check that data is accurate and complete after migration or archiving.
Testing
Conduct thorough testing of the new system or archiving solution to ensure it supports the necessary data integrity requirements.
Documentation and Training
Process Documentation
Document each step of the decommissioning process, including data migration and cleansing procedures.
Training
Provide training to IT staff and data users on best practices for maintaining data integrity during and after decommissioning.
Monitor and Review
Regular Audits
Conduct regular audits of the archived or migrated data to identify and address any integrity issues that may arise.
Feedback Loops
Establish feedback loops with stakeholders to continuously improve data integrity practices.
Conclusion
Maintaining data integrity during application decommissioning is a complex but crucial task. By conducting a thorough assessment, developing a detailed plan, implementing strong data governance policies, and ensuring ongoing monitoring, organizations can successfully decommission applications while preserving the accuracy, consistency, and reliability of their data. This not only ensures compliance and operational efficiency but also supports future business needs and strategic goals.
0 notes
Text
Carve-out Chronicles: Nurturing Innovation in the Heart of Legacy Systems
Introduction:
In the dynamic landscape of business evolution, organizations often find themselves at the crossroads of innovation and legacy systems. The intriguing journey of carving out new pathways within these established structures not only presents challenges but also serves as a fertile ground for nurturing innovation. In this blog, we embark on the "Carve-out Chronicles," exploring how organizations can foster a culture of innovation in the very heart of their legacy systems.
The Legacy Conundrum: A Breeding Ground for Innovation
1. Unveiling Hidden Potential: Identifying Innovation Opportunities in Legacy Systems
Delve into the unexplored corners of legacy systems, unveiling hidden potential and identifying innovation opportunities that can redefine the organization's trajectory.
2. Legacy Catalysts: How Carve-outs Ignite the Flames of Creativity
Discuss how carve-out initiatives act as catalysts, igniting the flames of creativity within teams and fostering a mindset that views legacy systems not as constraints but as canvases for innovation.
Nurturing an Innovative Culture
1. Cultural Alchemy: Transforming Legacy Mindsets into Innovation Gold
Explore the concept of cultural alchemy, illustrating how organizations can transform legacy mindsets into innovation gold by fostering a culture that values experimentation and forward-thinking.
2. Inclusivity in Innovation: Bridging Generational Gaps in Legacy Systems
Emphasize the importance of inclusivity in innovation, especially when dealing with legacy systems, showcasing how organizations bridge generational gaps to harness the diverse perspectives necessary for creative solutions.
Success Stories in Carve-out Innovation
1. Case Studies in Creativity: Organizations Redefining Possibilities through Carve-outs
Share success stories of organizations that have successfully redefined possibilities through carve-outs, showcasing innovative solutions that emerged from the heart of legacy systems.
2. Innovation Metrics: Measuring Success Beyond Financial Outcomes
Discuss how organizations can develop metrics to measure the success of innovation in carve-outs, emphasizing the importance of outcomes that go beyond traditional financial benchmarks.
Overcoming Innovation Challenges in Carve-outs
1. Legacy System Innovation Roadblocks: Strategies for Successful Navigation
Address common roadblocks in innovating within legacy systems, providing strategies for successful navigation and highlighting real-world examples of organizations that overcame these challenges.
2. Future-Forward Thinking: Sustaining Innovation Beyond the Carve-out Horizon
Encourage future-forward thinking, discussing how organizations can sustain innovation beyond the immediate scope of carve-out initiatives and embed a culture of continuous improvement.
Conclusion: Carving the Future with Innovation
In conclusion, the "Carve-out Chronicles" underscore the transformative power of innovation within the heart of legacy systems. As organizations navigate the intricacies of carve-out initiatives, they have the opportunity to nurture a culture where innovation thrives, paving the way for a future that seamlessly blends the wisdom of the past with the dynamism of the present. By fostering creativity, embracing inclusivity, and viewing legacy systems as springboards for innovation, organizations can carve a path toward a future where innovation is not just a buzzword but a driving force propelling them to new heights of success.
#carve-out#it application decommissioning#mergers and acquisitions#sap system#system decommissioning#insolvency#legacy system#liquidation#application decommissioning
0 notes
Text
Before focusing on how to decommission legacy applications, it is essential to understand the reasons behind it. There are several factors that lead companies to replace or remove their outdated or legacy applications:
Please click Below link to read more: https://avendata.com/blog/how-to-decommission-legacy-applications
0 notes
Text
A mashup of IDW and Seige canon of Ratchet and Deadlock, meet and run his underground asylum.
Based on Dialogue trees you get from Futomimi and Sakagahi, when you do the Aferlife Bell quest in SMT Nocturne.
For Ratchlock day.
(Next Chapter) || (Last Chapter)
There's a stain shaped like a human.
Work hard, do your best, and eventually you'll get somewhere.
When Ratchet transferred from the highest ranked schooling from Vaporex to the political charged state of Iacon, he expected pointed comments. He expected turned up faces. What he didn't know was how much he would be pushed into being an engineer.
Sure he has some skill in the field, many of his professors have left comments on it but never has he imagined being one. However, Ratchet found that his study to become a medic was going nowhere. Everywhere he went all of the classes would refuse his application, but he didn't give up.
If he wasn't going to be an official student he could still go to classes. When other mechs would sneak out or skip lectures he would slip in. Medic trainees would pay him to do their homework and he took it. All this hard work pays off, he gets the top scores, his engineering career is going well too. When his colleagues get hurt he can repair them better than the campus doctors. Then he graduated...
He gets hired to work on ground bridge operations. It doesn't excite him but it was honest work, and he could save enough money to carry equipment for a first aid kit. Once he was shipped off to the outskirts of the Dead End, that's where he finds his calling.
Since all fast travel in the area was decommissioned, Ratchet was forced to drive out to all locations. It wasn't too bad, but since he was the only one willing to do this job he was on his own. That's when he sees in person just how much Cybertron has abandon.
Streets filled with broken mechs and ruined buildings. There's no hope here, and his white paint lights up against the ash filled air, stains the vision of the city. It was silent until a siren went off in the distance. Despite him knowing the police's pensions for brutality, seeing it with his own eyes still frighten him.
"You're going to be okay." He hears a bot the panic in his voice. "Just hang in there, I'm going to get you help. Just hold on." Ratchet makes it to the voice. It was two bots in the middle of the road, both covered in blood. However, one person is down, closer to death.
"I don't think I can...", said bot also coughs up more blood. "Just wait for me to pass on. Then you can scavenge my parts."
"It's not fair." The mech brakes eye contact, looking to the sky. Then he looks towards the siren lights driving away. "They killed the wrong bot..."
"Let me try to help." Ratchet walks up to two mechs. The back mind is yelling at him, he's a ground bridge operator, an engineer, never even picked ot study medic. He can't do this, but he also can't stand here doing nothing. "I can't promise anything, but please I want to help."
They both look at him with a befuddled faces. He knows they shouldn't trust him but something must have broken because they allow him to help. They let him operate, and by the end of it all they thanked him, and for the first time since he left his home village, he felt proud of himself.
That's when Ratchet knew the direction of where is life is going. He would make money fixing and maintaining public works, taking other jobs, and making as much money as he could to build a clinc. He set it up in the center of Dead End, chosen it to give it resistance the fastest access to him. He worked himself tirelessly between these jobs and for the first time in his life. He managed to find success and happiness.
Do you think my life was a success?
Yes
>No
I see... yeah you might be right.
Just when I thought I achieved happiness, my fortune collapsed like a house of cards.
Then the outside world gotten word about it. The Senate at first only saw the healing of Dead End's bots. That they would start to walk around and they would fix the left over peices of the city. Had enough energy to walk around and wanted to start working.
However, Ratchet soon discovered that this was unwanted. That if Dead End successfully pulled itself together and made it possible to be something, then the fundamental ideology of Functionism would be thrown into question. If that where to happen, what other mechs would go against the class systems set forward by them.
It couldn't stand, so they made sure it didn't, and so they set off a bomb. Framed as an accident during transit from the military bases, they had approved of it being set off. Then they approved of some police officers to do a quick sweep of firing rounds to hit what remained. They're mission wasn't to kill anyone but if the managed too, it wasn't seen as a bad thing.
At the time Ratchet was sent off planet to see if he could assist in fixing a space bridge from Lunar-2 to Tyger Pax. Of course when it played on the news he tried to ground bridge there, but couldn't. His first transporters where destroyed, when he did get back, his clinc as well. Then when he made it home, his house was raided too.
Nothing made him feel so powerless than when he was stopped at the front door. A mech had pinned him against the wall of his assigned room and warned him away from returning to Dead End. That if they found out he went back he wouldn't be able to keep his face.
Worse was when the said mech had his hands wonder all over his body, and said next time he gets sent out he has permission to do as he pleases with him. Ratchet also finds all of his funds were frozen out, and when he does get access to them all of the money had disappeared.
You should be careful. You never know what tomorrow may bring...
After all of that, Ratchet still tries to help. He still returns to assist all the mechs of the city. They still look at him with hopefully eyes, but understanding that they could never crawl out by their own strength. Many where mad at him for even letting them entertain the idea. Others where mad for him, after all it was one thing to steal from bots with nothing on them. It was another to kick the bot who tries to give a hand to someone who needs it.
Most bots however, joined the Decepticons. They believed that if the government had been threatened by their peaceful solution then they would coware at their revolution. All of this would lead to their planet dying, not that the blame could be one sided. The Senate and later the Autobots would fight them to standstill.
Ratchet would find himself in the middle of it. At first he tried to stay neutral but the bots of Dead End where quick to bring up the attack. Then it was shaking down his person and finally braking into his home and ransacking his equipment.
Traitor was branded on his door, then on his frame. When Ratchet returned to work with a still orange smelter on his left hip, his friend Wheeljack, help him join the Autobots. For a time he was safe, the squad he joined even allowed him to repair any bot whom he wanted, even Decepticons were allowed to be fixed.
Do you think my life was a success?
>Yes
No
That's what everybody else thought, too.
...until that one day.
That was until a superior officer had came down for a vist. When they saw Ratchet repair two mechs with purple badges, they made it clear to him this would stop. If he gets caught again they would charge him with treason and he would be place on the enemy list. That's when he knew he had to go.
Being a deserter was a lighter charge than being a traitor. With his life on the line again, Ratchet has to go, because he could never leave a bot to die. In his spark he could never leave a mech to die without trying. He gives Wheeljack his coordinates, he trust that mech to only uses it when absolutely necessary.
Or at least he did.
The next time he sees his former colleague the bot had brought in toe a former bailiff turned Assassin. They force Ratchet to hand over everything on his person. The bots he was traveling with where tied down and put into custody of the Prime.
For the first time in my life, I had the urge to kill.
He was left on the ground, one push away from the cliffside. Wheeljack had saved his life but at the freedom of others. That's when he tells him to never find him again. That if he truly is sorry, he would only give that location to mechs who need it. They both promised something that day and that would be the last time he would speak to him, or it seemed.
So much anger,
As the war went on, Ratchet would travel. He would make a portable ground bridge went to the next battlefields and collect both parts and bots left behind to die. Like a Grim Reaper, he walks the path of death. However, he wouldn't take life he would do his best to keep it.
Rumor about his presence as a super natural entity made it easier to avoid authority. Many bots who believed in apparitions would come with him quietly. When he repaired them all of them would stay by him. When two bots of different factions would meet, it was almost always up to him to keep them civil.
Then he ran into Deadlock. The bot he gained feelings for. At first he didn't recognize him, but in private the mech tells him about the time they first met. That he was standing in the middle of the road in his friend's arm about to die. Then he adimts about the time he almost turned him to Megatron.
But the only way he could place Deadlock to the incidents is when he spoke those words to him. "Come on Doc, don't think like that. Everyone has kindness in their hearts."
That's when Ratchet's spark drops. This was the mech who was sent to capture him. Who knew of his habit of helping injured bots and almost trapped him into the Decepticons. Whenever he looks at Deadlock now, all he sees is a bot who has changed course, and doesn't he deserve a chance at it.
Ratchet of course also has a bad habit of letting mechs who hurt him do it again. So they both come to an agreement, he repairs Deadlock and takes him to back. The mech agrees to help him out with his operations.
So that's what they did. Ratchet would travel around and Deadlock would follow in tow. Keeping him safe and holding down bots when their reflexes kicked in. Later when their party had gotten too big to travel around and the building became to full. Deadlock drove off without a word.
Weeks became months and when two years passed by the mech came back. He tells Ratchet that he managed to find a bombed down theater that still had functional power. It was large enough for housing and medical care. When he shows him Ratchet is so relieved that he kisses him on the spot.
Deadlock field goes haywire but he doesn't reject it. Instead he grabs Ratchet's frame and frags him hard and wild, places him on the stage. With his groveling voice yells into Ratchet's microphone pick ups that he can't wait when the crew comes in. That after a long shift of picking up bots and patching up frames they would do this again, and next time they will have an audience to perform for.
That was the only time they had. As most of it was being too exhausted with fixing the building. Making sure that it look destroyed from the outside, having to only fix the bottom floors without collapsing the building from the top proved to be difficult. Even with the mechs he saved helping out, many issuses of resources and planning was still too much to worry about.
So Deadlock planned to search again. He spends his last night just sitting next to Ratchet. Telling him not worry, and he will comm every day just to reassure him of his safety. Ratchet gives him his ground bridge. Tells him to come back immediately after he finds something he thinks will help and that he will pick up his calls even if he can't talk back.
That was the last time they speak together, because once Ratchet was properly situated he update Wheeljack of his location.
There's a stain shaped like a human.
That's when he finds Impactor and things spirals out of control. Between Wheeljack taking Optimus Prime here, their entourage raising tempers and talks about Megatron abuse of the Matrix. Ratchet has to leave.
Many of his mechs encourage him to stay. Prime has no power here and if they want his help he should force the Autobots to promise to leave them alone. He doesn't answer them, he knows Wheeljack has betrayed him before. That the army has force his hands, but something tells him complying is the best option.
He turns to Impactor, tells him to tell the bigger bots to take care of the sick. Ratchet knows that mech has turned himself around and regained his spark. So it comes to a surprise that the mech follows behind him. Defending him from Elita-One and even sacrificing his own frame by pulling his comm out.
They violated him and still Impactor smiles at him, stays with him and gives his life for him. He sees his spark give out, but never sees his new found love of life leave his body.
That mankin died. He died the instant he became human. You see humans cannot exist in the vortex world...
As he boards the Arc, Ratchet gets a call from Deadlock. When he reached to answer the distance is to far.
#transformers#transformers siege#transformers war for cybertron#maccadam#ratchet#Seige Ratchet#Deadlock#Siege Deadlock#ratchlock#Ratchlock Day#DRAtchet#dritchet#fanfic#valveplug
45 notes
·
View notes
Text
Into the Rift (spiderverse!pacific rim au)
so going into more detail because the actual drawings are coming along really slowly xD (i love drawing robots but coming up with original robot design hard)
The story would be essentially the same as the movies where a mysterious rift opens up in the bottom of the Pacific ocean releasing giant monsters. To combat them, the world governments join together for the good of humanity and create the Jaegers. Those are giant robots piloted by two people through a process called a 'drift'.
The only thing that changes is the characters and the story developed from that idea.
this post has been sitting in my drafts for like a month now oml
(loooooong wordvomit under the cut)
So the jaeger program is basically a stand in for the spider society and all the spiderfolk are pilots or staff. Everyone is also aged up 2 or 3 years to cover international military requirements and such.
and for the sake of the story having a 'pilot shortage' in which only the lucky few being able to actually pilot a jaeger, drifting is much harder and rarer. this leads to the program accepting younger applicants than they normally would. (eg. miles, pav, peni etc)
(character list in order of rank or.. something)
Miguel (34-35) is the stand in for the marshal. I'm not totally sure if he *is* the marshal or not? because he could absolutely just be the pilot manager or the mission overseer. but for now we shall stick with marshal. He primarily serves as the head of the department and representative for the pilot body. He also doubles as a pilot of a gen 1 jaeger (Blue Revenge*) with Peter B Parker, previously Jessica Drew.
Jessica (34-35) is Miguel's ex copilot. She served for two years and during a faux time of inactivity from the rift, she and her husband decided to try for a child. She was called back during the next attack but in the post-fight medical checks, she was ordered to go on maternity leave. She did, for a couple months, but very quickly felt frustrated that she wasn't helping. She moved back into the military base and instead took up a leadership position in combat training. I think her rank would be lieutenant but I don't know enough about the military to make that official.
Peter B Parker (42-43) is a retired pilot. He served as a pilot up until the gen 3 jaegers went into production and was sent home when he got a major back injury. During his time off he started a family in his old New York home and began to forget about the jaegers and the war. He chose to live in ignorant bliss until it all came back when he was summoned back. He brought his entire family, despite the many warnings, and has rather enjoyed his grand return. Currently copilots with Miguel in the Revenge*. Previously piloted the Crimson Core*.
Ben Reilly (24-25) is a jet pilot. Previously a jaeger pilot of the Scarlet Gutter that was decommissioned after it suffered extreme damage in a fight he took solo with a class 2 kaiju. His twin brother was his copilot and died early on in the fight. He currently pilots a fighter jet as backup. The impact of that fight still haunt him and everyone knows to leave him be.
LEGO Spiderman (24-25) and Peter Parkedcar (25-26) are two unrelated pilots that are drift compatible. LEGO Spiderman (Lee Godwin aka LE-GO for short) has a chronic condition with locking joints and Peter Parkedcar is a selective mute. They pilot the Titanium Wall that is essentially just an immovable object to the kaiju's unstoppable force. Yes this is a meme lineup. Laugh.
Peter Porker (31-32) is the head of research. He's john mulaney in all aspects except for occupation. He is more of the morale backbone of the entire operation and spends more time out of the lab making sure to bring a smile to everyone's faces. He wears a cute pig beanie when out and about. He always has candy on him and is famous in the kitchen for hot dogs. No one knows where he gets the hot dogs from, since those are rarely stocked. There's a rumor going around that it's kaiju meat, not beef. Absolutely fascinated kaiju and a biology fanatic.
Margo Kess (20-21) is the head of technology. She's the surveillance guy who takes orders directly from Miguel and is in charge of relaying commands and judging actions on the battlefield. She's a young college graduate- more accurately a child prodigy- and took the first opportunity she had to put her skills to the test. She's very friendly and will always get to know the pilots personally. Drift compatible but has avoided training to not have people learn about her strained home life.
Peni Parker (17-19) is the daughter of the head of engineering. She is just under the required age to actually assume the position but has the most knowledge on jaeger design of anyone else in the program aside from her father. Her father was killed when one of the outposts was destroyed in a kaiju attack. Parentless, the organization arranged for her to stay at the main base, waiting for her 21st birthday so she can acquire an actual rank. Had a personalized jaeger her father had been slowly building, fit for one person, that she's slowly been working on to one day pilot in combat.
Peter Benjamin Parker (Benji or Ben for short) (22-23) was hired as the strategy lead after his impressive work as a police/military investigator. Had a lot of experience with international crime networks and hand picked by Peter B. He was enthusiastically handed over to the Jaeger program after he got just a bit too close to some apocalypse-profiting corruption. No one really knows why, but he's taken more of a liking to pilot training and has shied away from Miguel's leadership team and more towards Jessica and the recruits. He has a good eye for cadets with amazing potential and even applied to be a pilot himself, stepping away almost entirely from any kind of leadership role. Pilots Silver Noir with Hobie(**).
Hobie Brown (20-22) is a pilot. He was recruited early on as one of Britain's undesirables and turned out drift compatible. He was assigned a jaeger that was built and sponsored by the British Government named the Union Jack. Disgusted, he refused to respond to that name and instead calls his jaeger the Stark Screamer. The name has been adopted by command and no one has bothered to correct it. His pilot quit for unknown reasons after only a year on the field and the Screamer was retired until they can find another pilot to partner with him. Has been paired with Benji for the time being.
Gwen Stacy (18-19) is the youngest pilot to date but more than capable of jaeger combat. She was brought in by Jess, despite her father's refusal, and skipped all cadet training except for the essentials and given a jaeger assignment almost immediately. She was picked out when her father, a military rep instead of a cop, was visiting one of the bases that Jess happened to be in. She showed incredible potential in [insert event that im not 100% sure about yet] and was incredibly interested. Originally paired with Hobie because of their similarity in hobby and age. They were drift compatible but she didn't like the Screamer's kit or fighting style and requested a new assignment. She's still best bros with Hobie though. She marks the beginning of the youth recruitment.
Pavitr Prabhakar (17-18) is a cadet in training. He volunteered along with a large number of Indian civilians to chase the fame and glory that surrounded the now-martyred jaegers. Of the hundreds, he and a handful of his peers were selected and he was sent to his specific branch to complete training. He is drift compatible with almost anyone. Having no sense of fear or darkness in his past or his present, he's an incredible asset- if not a little naive. He and Hobie became best friends as soon as they met and has been promised to pilot the Screamer when he completes his training.
Miles Gonzalo Morales (17-18) is a new cadet starting training. He was supposed to be one in a pair but his twin was stuck in Spain with a travel complication. Miles could wait a couple months though and eagerly started training. He was selected because he had an identical twin- which are usually assumed to be drift compatible- but ended up being paired and drift compatible with Gwen. Despite him not having clearance, Gwen and many others think he shows enough potential to pilot a jaeger within the first month of his stay. He is currently assigned to a new jaeger in production: a gen 4 titan named the Clawed Viper***
Mateo Davis Morales (17-18) is a future cadet. He and his twin were split up before highschool for [insert reason i haven't figured out yet here] and he moved to Spain to finish his highschool education and eventually enlist in the jaeger program. However, due to transportation delays and possibly finances, when he and his twin were drafted, Mateo was stuck in Spain until nearly three months later. Just in time for . . . well, the drama (tm).
*Blue Revenge is not final. i don't know if i like it or not but the other option was the blue panther, for the shits and giggles. pretty sure i want to keep the blue but idk. Crimson Core is also a placeholder, but it does sound cooler
**Silver Noir is not final. I want to work in Noir somewhere and make a matte black jaeger but not a lot of words go with 'Noir'
***Clawed Viper is not final. Viper is final, but again, not a lot of words go with 'Viper'
#atsv#atsv au#pacific rim au#miles morales#miles g morales#gwen stacy#pavitr prabhakar#hobie brown#margo kess#peni parker#spiderman noir#peter benjamin parker#spiderham#peter porker#lego spider#man#peter parkedcar#ben reilly#jessica drew#miguel ohara#prowler miles#holy shit that was a lot of writing#not even mentioning the drama ooh spooky...#if you ended up reading this thank you i love you#now indulge my brainworms
29 notes
·
View notes
Text
A mission design for servicing telescopes in space
The fate of telescopes in space is looking better now that they are being designed to be serviceable. Researchers developed a servicing plan that can be applied to future space observatories based on current missions such as the James Webb Space Telescope and the European Space Agency’s Gaia.
“Although the next generation of large space telescopes are being designed with serviceability in mind, there are enormous challenges with implementation,” said Siegfried Eggl, professor of aerospace engineering in The Grainger College of Engineering, University of Illinois Urbana-Champaign.
One issue is distance. Modern space telescopes are stationed at the Sun-Earth Lagrange Point L2, which is about a million miles away from the Earth. It's moving with the Earth, which makes it easier to reach, but still very far away making the transport time consuming and expensive. The relatively quiet, low interference environment at Lagrange Point L2 means missions like Gaia have an enormous impact on astronomy and planetary science, but according to Eggl, it’s worth the trek.
Eggl said, “Gaia is like a rotating cylinder with a solar panel. it is encapsulated, so it hasn’t been damaged, but after a decade out there it’s running low on fuel. Ruthvik Bommena designed a novel concept to add a sort of spider-looking attachment that can extend its life without impeding its data collection. Gaia will be decommissioned soon, so there isn’t enough time to reach it, but the James Webb might still be a possibility because it will be operating for several more years and they may decide to prolong its mission.”
He explained that the James Webb telescope has unshielded, segmented mirrors, some of which have already been damaged when struck by micrometeorites. The entire mirror surface of JWST is six meters in diameter. The next large telescope will be about twice that size.
“We’re trying to stay a step ahead so there is a plan to replace broken mirrors, for example. If we don’t, it’s like buying an expensive sports car, then like throwing it away when it runs out of gas.”
Another aspect Bommena is working is safe proximity operations.
“A spacecraft sent to repair or refuel a telescope needs to brake when it reaches it,” Bommena said. “Using the thrusters to slow down would be like pointing a blowtorch at the telescope. You don’t want to do that to a delicate structure like a telescopic mirror. How do we get there without torching the whole thing?”
Robyn Woollands, who is also professor of aerospace engineering at U of I said one of the main goals they achieved with this work was finding a trajectory to get there cheaply without reliance on large, cost-prohibitive rockets.
“Fortunately, getting there is doable because of some hidden highways in our solar system. We have a trajectory that is optimal for the size of spacecraft needed to repair the JWST,” she said.
Ph.D. student Alex Pascarella developed a novel technique for quick sampling of the solution space that can shorten the computation time.
“The novelty is in how we brought together two separate approaches to trajectory design: dynamical systems theory and optimal control theory,” Pascarella said.
Pascarella said the traditional approach for trajectory design in multibody systems such as the Sun-Earth system, relies on computing the invariant manifolds of an orbit—manifolds are pathways in space that naturally lead the spacecraft to the given orbit. This is a great approach that has been successfully used for decades, both in academic research and real-life applications.
“It becomes a bit challenging when you are trying to rendezvous with a target spacecraft at a specific location in space/time instead of reaching a target orbit and you are dealing with a low-thrust spacecraft whose engine operates for long stretches of time as opposed to a spacecraft with more powerful thrusters that operate for very shorts bursts.
“Our technique is based on a slightly different idea. We first investigate the solution space by propagating a sample of solutions—either without any thrust or with a very simple thrust control law—and we take note of how close they pass to our desired destination,” Pascarella said.
He added that because the type of orbit they are trying to reach spawns manifolds, they know at least some of their initial guesses will come close to the desired orbit.
“After we create a map of initial solutions, we use optimal control theory to generate optimal end-to-end trajectories,” Pascarella said. “Optimal control allows us to find trajectories that depart near Earth, and rendezvous with our space telescope in the least amount of time. The initial sampling of the solution space is fundamental—optimal control problems are notoriously difficult to solve, so we need a decent initial guess to work with.”
Eggl said the plan to repair/refuel Gaia is a complete design that can be implemented. For the James Webb telescope, more engineering is needed.
IMAGE: CAD model of the Gaia spacecraft with service vehicle, post-docking configuration. Credit The Grainger College of Engineering at the University of Illinois Urbana-Champaign
2 notes
·
View notes