1 / 9

Program XYZ Vision

Program XYZ Vision. Problem. Projected maintenance schedules for future XYZ system make long range/long term system XYZ deployment impractical for customer. Without action: XYZ system will meet current requirements but not scale to future upgrades by customer

elia
Download Presentation

Program XYZ Vision

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Program XYZ Vision

  2. Problem Projected maintenance schedules for future XYZ system make long range/long term system XYZ deployment impractical for customer. • Without action: XYZ system will meet current requirements but not scale to future upgrades by customer • This opens the door for competitors to steal future business from us • Affecting future growth, success and longevity of XYZ program • Affecting customer satisfaction, end users, shareholders, company in general 33% increase in deployed hours is impractical Current deployment Requirement 33% increase Impractical Maintenance Hours per week Root Cause: Fundamental flaw in current system architecture design Practical Deployed Hours

  3. Problem: Continued • Architecture flaw is chronic and permeated throughout the design • Details: Each subsystem proposes to build its own custom power system, CPU, Storage and network services as well an engineer services like resource utilization, startup shut down, cooling etc. • This decreases system reliability • Which increases maintenance requirements • Need to fix before next development phase • Leaving design as is will meet current requirements but reliability concerns will require higher maintenance hours in future. • Fixing the problem down the road when the customer requests longer deployment is more expensive – may open door for competitors • Current trends suggest that system XYZ will be required to perform longer missions and support longer deployments • 2011 release of DoD affordability memo suggests: “We may need to start modifying what we have instead of procuring new items to meet current demands” (Fictitious)

  4. Objective Cap the required maintenance at 5 hrs per week (well below the threshold value) • Objective must be attained before entering next development phase to avoid increased costs • The maintenance cap will: • Meet as is requirements • Ensure that future capabilities and requirements will continue to be practical for XYZ system • Help keep us competitive and lock out competitors for future upgrades Maintenance hours per week caped at 5 hrs per week Current deployment Requirement 33% increase Impractical Maintenance Hours per week Practical Deployed Hours

  5. Options • Do Nothing • Pros • Stay on schedule and budget • No churn in requirements • Current prototypes could be reused with little modifications • Meets current requirements • Cons • System not easily scalable in the future • Short sighted • Change it now • Pros • Create a system that scales with projected customer demands • Easier and cheaper to change now because development still in design phase • Cons • Potential schedule slip • Culture shift required • Change it later • Pros • Create a system that scales with projected customer demands • Cons • Changing later in development phase will be more costly

  6. Choices – As Is EDTA3252 EDTA3261 Power Supply CPU Resources Power Supply CPU Resources Storage Network Storage Network Startup/Shutdown Cooling Startup/Shutdown Cooling … … EDTA3258 MDLS2206 Power Supply CPU Resources Power Supply CPU Resources Storage Network Storage Network Startup/Shutdown Cooling Startup/Shutdown Cooling … … Distributed Maintenance Teams not pooling resources no commonality of interfaces

  7. Choices – Common Services/Common Interface Common interfaces Common Services EDTA3252 EDTA3261 Power Supply CPU Resources Storage Network Startup/Shutdown Cooling EDTA3258 MDLS2206 … Common Services Maintenance Team

  8. Comparison of Choices Maintenance hours per week caped at 5 hrs per week 33% increase in deployed hours is impractical Table showing required maintenance at 33% increase in deployment hours Current deployment Requirement Current deployment Requirement 33% increase 33% increase Impractical Impractical Maintenance Hours per week Maintenance Hours per week This choice meets our goal Practical Practical Deployed Hours Deployed Hours

  9. Decision • Fix the problem now • Positions us for the future • Helps us maintain our “incumbent advantage” • Maintain good customer relationship • Common Services/Common Interface • Allows manufacturing cost savings • Maintenance cost savings • Meets 5hr maintenance cap objective

More Related