The document summarizes the development of the Ares I-X Roll Control System (RoCS) for the Ares I-X launch vehicle. The RoCS provided rotational control using a bi-propellant system developed under an Integrated Product Team model. Key aspects included delivering the system on schedule, within budget, and with high quality to support the October 2009 launch. Off-the-shelf and surplus government components were used, including components from decommissioned Peacekeeper missiles, saving over $10 million.
Validation of Spacecraft Behaviour Using a Collaborative ApproachDaniele Gianni
Presentation delivered at the 3rd IEEE Track on
Collaborative Modeling & Simulation - CoMetS'12.
Please see http://www.sel.uniroma2.it/comets12/ for further details.
Validation of Spacecraft Behaviour Using a Collaborative ApproachDaniele Gianni
Presentation delivered at the 3rd IEEE Track on
Collaborative Modeling & Simulation - CoMetS'12.
Please see http://www.sel.uniroma2.it/comets12/ for further details.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Epistemic Interaction - tuning interfaces to provide information for AI support
Unger massey
1. Project Management Challenge 2010
Ares I X Roll Control System Development
A I-X R ll C t l S t D l t
Ron Unger/NASA Marshall Space Flight Center
Ed Massey/Teledyne Brown Engineering
February 2010
www.nasa.gov
Used with permission
2. Ares I-X Roll Control System
Project Management Model
The Ares I-X Roll Control System (RoCS) represents a successful
project management model of a rapid-development, functionally
complex, flight hardware system. The Integrated Product Team
(IPT) model was executed at the RoCS l
d l t d t th R CS level concurrent with the
l t ith th
other Ares I-X IPTs to support the successful Ares I-X launch on
October 28, 2009.
National Aeronautics and Space Administration 2
3. Ares I-X Roll Control System Overview
Description
– Roll Control System provides
rotational azimuth control for:
mitigation against adverse
vehicle roll torques (self-
and aero-induced).
antenna and simulated
crew launch positioning.
Salient Features
– The Roll Control System is an
integral, modular, bi propellant
integral modular bi-propellant
propulsion system installed in
the Ares I-X Upper Stage
Simulator Interstage.
– RoCS utilized off-the-shelf and
Government-furnished
components that have been
harvested from USAF
Peacekeeper Stage IV, then
re-integrated into a system.
National Aeronautics and Space Administration 3
4. The Challenge
Deliver the requisite Roll Control System to Ares I-X:
on time … support April 15, 2009 (original) launch date
within budget … $24 7M budget guideline
$24.7M
and of high quality.
How we did:
RoCS modules delivered to KSC on February 5, 2009, were fully integrated
into U
i Upper S
Stage b A il 26 2009 ( ll off the i
by April 26, (well ff h integration critical path).
i ii l h)
Current cost – over guideline by 3%, attributable to launch date changes
requiring standing team.
Flight hardware accepted by Ares I-X May 27, 2009. All waivers and
verifications closed by July 14, 2009. Noticeably low number of KSC problem
reports were generated for a first article prototype system.
National Aeronautics and Space Administration 4
5. Major Keys to Success
Description Stakeholder Value
Establish small, “badgeless,” accountable team between Efficient decision-making.
contractor and NASA, while maintaining compliance with
governance model/Independent Technical Authorities.
Authorities
Development of early Memorandum of Understanding and Clear lines of responsibilities.
Agreement with USAF and Task Agreement with White Sands Test
Facility.
y
Designing for robustness, anticipating upward movement of loads Structural problems averted over a
levels. series of changing loads.
Early identification and development of waivers
waivers. Waiver acceptance justification built
into test and analysis plans.
Front end load the schedule with design and testing activities, Avoid bow wave of activities and
waiver submittal, and verification closures. related resources availability issues.
Co-location of MSFC Engineering Lead System Engineer to Rapid issue definition and resolution
Teledyne Brown facility. planning.
Maintain cognizance of the end game. Primary and urgent issues resolved
first. Secondary issues pushed down
to lower levels.
National Aeronautics and Space Administration 5
6. Ares I-X Roll Control System Organization
Roll Control System IPT
Ron Unger
NASA MSFC
IPT Lead
PK AXE Test & Stage PK Propellant Tanks
Component Salvaging
USAF / Davis Monthan AFB
NASA / WSTF and Hill AFB
Pyrotechnics Procurement Schedules
NASA/GRC Karen Russell/Teledyne Brown
Resource Office Data Management
NASA/MSFC David Chafee Mike Staton/COLSA
Design Insight System Design Systems Safety &
Lead Ground
& Hardware Engineering Mission
Engineer Operations
Integration & Integration Assurance
Patton Melinda Dave Jennifer
Downey Ed Massey Delacruz Tomasic Spurgeon
Teledyne Brown
Engineering
MSFC Technical Test, Design &
Engineering Support
Contractors
Salvage Support
Resources
Pratt & Whitney/
Rocketdyne
National Aeronautics and Space Administration 6
7. Peacekeeper Hardware Acquisition
MOUA to utilize
Davis-Monthan AFB Hill AFB PK hardware
NASA/MSFC
PK Prop Tanks Peacekeeper Stage IV
Task Agreement to
“harvest” PK hardware
NASA/WSTF Unused Hardware
Decommisioning PK to Scrap
Teledyne Brown Eng
Each RoCS Module utilized The RoCS Team ended up
from PK: with enough hardware for:
g
Two Propellant Tanks Three Flight Modules
Pressurization Subsystem Ground Test Cold Flow Module
Two PK Axial Engines Hot-Fire Engine Tests
Two Propellant Filters Dynamic Tests
Four Pressurant Check Valves Plus Odds and Ends Spares
Pyrovalve Ordnance > $10M Cost Avoidance
National Aeronautics and Space Administration 7
9. Design for Robustness and Growth
Robustness
Implementation of two independent RoCS modules provided system redundancy. Ares
I-X could complete its mission with reduced roll control capability using one module.
In-line mounting configuration minimized opening in Interstage sidewall and provided
rugged platform to support components in the axial direction.
Single regulator with high quality performance selected as most reliable option.
g g g y
Multiple temperature sensors provided back-up for Launch Commit Criteria in case of
sensor failures.
Positive monitoring of Helium tank pressure switch sensor provided immediate
indication of system leak well before launch.
Redundant pyrotechnic trains provided system reliability for initiation. Pyrotechnic
activation of modules shown to be simple and reliable.
Offline fueling of modules reduced impacts to vehicle integration schedule.
Spare RoCS module available as line replaceable unit in case of module failure during
integration flow.
g
National Aeronautics and Space Administration 9
10. Design for Robustness and Growth
Growth
Separate pressurant and propellant systems provided approximately double the
required resources for accomplishing mission profile.
Peacekeeper engines provided capability for growth in thrust requirements.
Module structure was intentionally over-designed to address changing loads.
10
11. Early Identification of Waivers
C i
Coming out of R CS C iti l D i
t f RoCS Critical Design R i
Review (CDR) six waiver
(CDR), i i
situations were identified for Peacekeeper hardware, either against
NASA standards or Ares I-X requirements.
No Vibro-Acoustics Acceptance Testing Planned for Flight Components or Assemblies
Pressure Testing Levels on the Propellant Filter Assemblies
Heritage Pyro Component Quantities not Available to Meet Lot Acceptance Requirements
No Vibro-Acoustics Qualification Testing Planned for Propellant Tanks
No Vibro-Acoustics Qualification Testing Planned for Pyro Valves and Ordnance
Pressure Testing Levels on the Engine Bi-Prop Valve
Drafting of waivers, including Engineering rationale for acceptance
g , g g g p
and the residual risks, began in July 2008.
First three were approved at Ares I-X Control Board September 2008.
Second three came later in verification process as loads matured and test results became
available.
available
Early identification and draft development allowed RoCS to start
“talking up the waivers within the Ares I-X community, so that when
talking up” IX
final product was presented, everyone was on board.
National Aeronautics and Space Administration 11
12. Front-End Loaded Schedule
Dry run procedures with real hardware or physical facsimiles to
work hardware form, fit, function, and procedural bugs out early,
well in advance of handling the flight hardware.
Pressurant and propellant tank Module installation and
filling (with helium and water, translation exercise using
respectively) at KSC’s
KSC s installation tables Interstage lip
tables,
Hypergolic Maintenance Facility mock-up, and RoCS mass
simulator, with KSC personnel
National Aeronautics and Space Administration 12
13. Front-End Loaded Schedule
W k parallel paths, as budget allows, to maintain fall-back options.
Work ll l th b d t ll t i t i f ll b k ti
Use past precedents from prior contracts as models for
documentation – modification of an existing document rather than
generating a new template and/or authoring from scratch.
As such, Teledyne was able to have many of the motherhood documents (Safety Plan,
Quality Plan, Configuration Management Plan, etc., put behind us before new technical
requirements even showed up )
up.)
Engineering Development Unit (one of four units built and intended
for eventual cold flow testing) validated hardware process
development and assembly fit checks before committing to final
fabrication and assembly of flight units (two, plus one flight spare).
13
14. Front-End Loaded Schedule
May‐08
May‐09
Mar‐09
Nov‐08
Aug‐08
Aug‐09
Dec‐08
Sep‐08
Feb‐09
Sep‐09
Apr‐08
Apr‐09
Oct‐08
Jun‐08
Jun‐09
Jan‐09
Jul‐08
Jul‐09
0
10
20
30
mplete
40
% Com
50
60
70
80 EIS Closures
ERD Closures
90 SEI/XCB Closures
Waiver Approvals
100
PSR
PSR AR1
AR1 AR2
AR2
National Aeronautics and Space Administration 14
15. Co-location of MSFC Lead System Engineer to
Teledyne Brown Facility
Greatly facilitated communications between NASA and the
Contractor Team.
Immediate customer interface for the resolution of issues found
during the design, fabrication, assembly, and test flow.
Provided on-site support for interfacing with other IPTs for
resolution of interface issues.
Provided direct customer interface to report status and progress.
Provided immediate direction to keep project on schedule.
Provided for expedited verification closure processing.
National Aeronautics and Space Administration 15
16. Maintain Cognizance of the End Game
This flight was designated as an unmanned test flight A mindset
unmanned, flight.
shift from Shuttle was in order.
The original plan to deliver the modules before the end of 2008
would h
ld have supported th original A il 15, 2009 launch date, and
t d the i i l April 15 l hd t d
was holding through the fall of 2008.
Delivery of fairing aero buffet loads and changing vibro-acoustic
environments in December 2008 delayed completion of component
testing.
Teledyne-provided field modifications to fairings were implemented
y p g p
at KSC in parallel with off-line propellant/pressurant loading of the
modules, minimizing impacts to integration schedule.
National Aeronautics and Space Administration 16
17. Maintain Cognizance of End Game
Work “good enough” options, no need to work optimization for a
eno gh” options ork optimi ation
single test flight
● Better is the enemy of good enough.
• Module installation was cartooned
out in an hour by:
• RoCS IPT Lead (MSFC)
• Interstage Lead (GRC)
• Ground Ops Rep (KSC)
• Mechanical Designer (Teledyne)
• Ground Support Equipment
“ownership” was maintained by
Teledyne
17
18. The End Result
Final RoCS Module
Shipment
February 5 2009
5,
Final Integration
into Interstage
April 26, 2009
Final Acceptance
Review
May 27, 2009
National Aeronautics and Space Administration 18
19. Looking Forward
0 psig
190 psig 79 F 79 F 190psig
0 psig
100FF
79 100F
79 F
Fuel Fuel
1 2 290psia
15 psia 290psia
15 psia
1 2
He
B
He
A 290 psia
15 psia
OFF
79 F
OFF
79 F
290psia
15 psia
1 2 290psia
psia
15 psia 290psia
15 psia
1 2
Oxidizer Oxidizer 100 F
79 F
100F
79 F
190 psig
0 psig 190 psig
0 psig
79 F 79 F
ST
Launch – October 28, 2009
RoCS Performance - Notional
20. Summary
Establish roles and responsibilities
Maintain independence of government Technical Authorities (S&MA and
Engineering) per NASA governance model
Keep team small and focused
A small team of cross-trained individuals with the necessary core
competencies can make decisions quickly and execute plans efficiently
Use proven Systems Engineering processes
Start early, keep the End Game in mind
Design conservatively, wherever possible
conservatively
Develop
Multiple open communications channels while respecting protocol
Ownership
Trust
Friendship
National Aeronautics and Space Administration 20