Why is there no Wet dress rehearsal this time? I remember OFT-1 did one... Or is there one planned for today?
Just because there's a job req out there doesn't mean the job isn't being done now. People are in acting roles all the time when people retire or get promoted and they haven't found a permanent replacement immediately.
We learned at the news conference Boeing is going open the Starliner door on the pad and then close it and seal it again. Not an exact quote but something like, "Our guys will go up there and open the door."
Quote from: AstroWare on 01/01/1970 12:00 amWhy is there no Wet dress rehearsal this time? I remember OFT-1 did one... Or is there one planned for today?To expand on Jim's laconic reply: ULA conducted a WDR for the new Atlas V variant (N22) prior to OFT 1. ULA do not regularly conduct WDRs (or static fires) for every single launch - that's a SpaceX thing - though they may do it for Atlas V variants. Since a N22 WDR has already been conducted (to test the new DEC systems, mainly), there is no need for one for OFT 2. Quote from: psionedge on 01/01/1970 12:00 amJust because there's a job req out there doesn't mean the job isn't being done now. People are in acting roles all the time when people retire or get promoted and they haven't found a permanent replacement immediately.And even when a post is already going to be filled internally by the person in the acting role, it will often be advertised externally (and internally) anyway as a matter of course. Quote from: SoftwareDude on 01/01/1970 12:00 amWe learned at the news conference Boeing is going open the Starliner door on the pad and then close it and seal it again. Not an exact quote but something like, "Our guys will go up there and open the door."The door is accessed via the crew access arm (CAA). The CAA seals to the exterior of the capsule around the door (like the access arms for any other crewed vehicle I can think of) so opening the door is to a conditioned interior space, not just flapping about in the breeze. Since crew being able to open the door and enter the capsule is a rather important part of crewed launch, exercising that capability is not exactly surprising behaviour.
The context of my part of this is that I don't think Boeing is trying to practice or learn anything operationally except that the door works or not.
The WDR is primarily, but not exclusively for the LV only. It also tests the interfaces between the LV and the spacecraft. Given Boeing's recent history with Starliner's LV/Spacecraft interface screwups, I believe a WDR would be appropriate, if only for the interfacing. In my opinion of course.
https://twitter.com/ulalaunch/status/1526992552100089860QuoteFueling of the #AtlasV first stage is underway at Space Launch Complex-41. The launch team is pumping 25,000 gallons of storable, room-temperature RP-1 fuel, a highly refined kerosene, into the rocket for Thursday's #Starliner launch. bit.ly/av_oft-2Pic by @nasahqphoto
Fueling of the #AtlasV first stage is underway at Space Launch Complex-41. The launch team is pumping 25,000 gallons of storable, room-temperature RP-1 fuel, a highly refined kerosene, into the rocket for Thursday's #Starliner launch. bit.ly/av_oft-2Pic by @nasahqphoto
Is OFT-2 using the same capsule as OFT-1? Or is this the first flight of this capsule? I understand they plan to build (2) but idk which one this one is.
I know, right?I honestly think they just don't care for more tests, and they figure they'll find out during flight. "Damn the torpedoes" and all that.
... Recall that the actual launch can be stopped any time up to nearly T-0, so it is on effect the same as a WDR, and it is uncrewed.
QuoteThe context of my part of this is that I don't think Boeing is trying to practice or learn anything operationally except that the door works or not.Jeez, man - TRIM YOUR QUOTES.And what you “believe” has no direct connection to reality. Every launch operation involves practice - repetition, process, and routines are deadly-important when mission- and especially life-critical functions are involved. You want everyone involved to have zero question or hesitation about what they are supposed to do and why, not have them fumbling around trying to remember if one latch gets opened before another, or if a hose is supposed to be pressurized before it’s connected or after.So every repetition is important, no matter what you believe.
The Commercial Crew Program within Space & Launch is seeking a Flight Management and Integration First Line Manager (Level K) based at Kennedy Space Center, FL.
Primary ResponsibilitiesDevelop and release of Flight Test unique documentation including test definition (TDD), requirements (TRD), procedures and report.Coordinate Flight Test unique milestone reviews.Coordinate Test as You Operate (TAYO) exception approval.End-to-End Test and CEIT requirements development and planning.Staff Test Director console as member of Mission Support Team.Integration and delivery of products for DRD 104, 109 and Flight Test Readiness Review (FTRR).Lead Flight Execution Team for Test Flights and PCMs, providing day to day decisions and ensuring issue resolution to maintain progress to plan per Flight Production Schedule.Mission and cargo requirements integration, documentation (MRD) and reviews.Coordinate agendas for SMMT meetings.Integrate plans and products for and execution of PCM payment Milestones Reviews.Update, maintain and release contract deliverables.Mission Support Room management including BMCC/MSR integration and operation, Mission Support Team training & certification, Sim/Rehearsal planning & execution.Develop and executes project and process plans, implements policies and procedures and sets operational goals.Work with functional and business unit management to acquire resources for projects and processes, provide technical management of suppliers and lead process improvements.Implement plans to ensure business, technical and customer requirements are achieved.Assign authority and responsibilities to employees to execute the plan.Reviews plans' execution, makes appropriate adjustments, and resolve issues.Monitor appropriate metrics to ensure performance to plan.Develop workgroup, project or operational goals, objectives and related metrics to ensure alignment with Company vision/strategy.Generate requirements and analyze technical approach, statement of work, labor and deliverables for workgroup, projects or process to ensure a quality product is received.Interface directly with external customers and suppliers to clarify technical requirements and issues.Develop and maintain relationships and partnerships with customers, stakeholders, peers, partners and direct reports.Provide oversight and approval of technical approaches, products and processes.Manage, develop and motivate employees.Coach, counsel, mentor and provide developmental opportunities and job assignments to enhance employee performance and expand capabilities.Provide on-going developmental feedback.Recognize contributions of individuals and teams to improve employee satisfaction and retain a skilled and motivated workforce.Convey organizational messages to facilitate the accomplishment of workgroup, project or process goals.Proactively communicate with employees, peers and customers. Keep others informed by communicating project status, conducting and participating in team meetings, providing presentations and listening to employee concerns and suggestions.Enforce company rules and policies regarding ethical behavior, safety, security, use of company property, time charging, etc.
Quote from: clongton on 05/19/2022 01:17 pmThe WDR is primarily, but not exclusively for the LV only. It also tests the interfaces between the LV and the spacecraft. Given Boeing's recent history with Starliner's LV/Spacecraft interface screwups, I believe a WDR would be appropriate, if only for the interfacing. In my opinion of course.A WDR is a rehearsal for events up to t0. The previous OFT issues occurred after staging, and were not caught by the WDR that was conducted (as expected, because the issue was confined to the spacecraft, and occurred after separation, so the LV was not involved or at fault). Unless there are expected to be brand new LV issues introduced since OFT-2 (i.e. no) an additional WDR would not be of any practical benefit, but would risk a recurrence of the now known valve corrosion issues until that design flaw can be mitigated more permanently.
Quote from: edzieba on 05/19/2022 03:09 pmQuote from: clongton on 05/19/2022 01:17 pmThe WDR is primarily, but not exclusively for the LV only. It also tests the interfaces between the LV and the spacecraft. Given Boeing's recent history with Starliner's LV/Spacecraft interface screwups, I believe a WDR would be appropriate, if only for the interfacing. In my opinion of course.A WDR is a rehearsal for events up to t0. The previous OFT issues occurred after staging, and were not caught by the WDR that was conducted (as expected, because the issue was confined to the spacecraft, and occurred after separation, so the LV was not involved or at fault). Unless there are expected to be brand new LV issues introduced since OFT-2 (i.e. no) an additional WDR would not be of any practical benefit, but would risk a recurrence of the now known valve corrosion issues until that design flaw can be mitigated more permanently.Well, to play devil's advocate here (not really my opinion I think I'd have made the same call)A WDR doesn't just check design issues. Stuff breaks all the time, even on stable designs. And it can break anytime too. I don't have a list of all the items that can't be checked until the pad... I bet the list is small but non-zero. For example, what about a GSE valve issue? These have been found during terminal counts before. Scenario 1: No WDRStarliner is integrated and rolled to pad for launch. Launch scrub. 2 day delay = 2 day additional environmental exposure. Scenario 2: WDR *before* Starliner integrationOnce starliner is ready for integration, booster stack performs WDR. Valve issue discovered. 2 day delay. Then starliner is integrated and launched. No additional environmental exposure. There is also PR aspects of a launch attempt scrub vs. a WDR scrub...There is also scheduled risks. If you have a hard launch window (say ISS is very busy) you may not want to risk a launch attempt scrub if it means waiting a week or more for the next window. (VIF isn't a controlled environment I learned recently...) And always cost. WDRs cost money. But So do Scrubs. Which costs more and who incurs the cost is beyond me! I'm just an engineer. That's what program managers are for.