Presentation is loading. Please wait.

Presentation is loading. Please wait.

Program XYZ Vision. Problem Projected maintenance schedules for future XYZ system make long range/long term system XYZ deployment impractical for customer.

Similar presentations


Presentation on theme: "Program XYZ Vision. Problem Projected maintenance schedules for future XYZ system make long range/long term system XYZ deployment impractical for customer."— 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 Maintenance Hours per week Deployed Hours Current deployment Requirement 33% increase Impractical Practical 33% increase in deployed hours is impractical Root Cause: Fundamental flaw in current system architecture design

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 Deployed Hours Current deployment Requirement 33% increase Impractical Practical Maintenance hours per week caped at 5 hrs per week

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 EDTA3258 MDLS2206 EDTA3261 Distributed Maintenance Teams not pooling resources no commonality of interfaces Power Supply CPU Resour ces Storage Networ k Startup /Shutd own Cooling … Power Supply CPU Resour ces Storage Networ k Startup /Shutd own Cooling … Power Supply CPU Resour ces Storage Networ k Startup /Shutd own Cooling … Power Supply CPU Resour ces Storage Networ k Startup /Shutd own Cooling …

7 Choices – Common Services/Common Interface Common Services Power Supply CPU Resources StorageNetwork Startup/Shut down Cooling … EDTA3252 EDTA3258 MDLS2206 EDTA3261 Common Services Maintenance Team Common interfaces

8 Comparison of Choices ServiceRequired Maintenance (As Is Option) Required Maintenance (Common Serices) Power0.8hr * 41hr CPU0.1hr * 4.5hr Network1.5hr * 42hr Other1.5hr * 41.5hr Total15hr5hr Table showing required maintenance at 33% increase in deployment hours Maintenance Hours per week Deployed Hours Current deployment Requirement 33% increase Impractical Practical 33% increase in deployed hours is impractical Maintenance Hours per week Deployed Hours Current deployment Requirement 33% increase Impractical Practical Maintenance hours per week caped at 5 hrs per week This choice meets our goal

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


Download ppt "Program XYZ Vision. Problem Projected maintenance schedules for future XYZ system make long range/long term system XYZ deployment impractical for customer."

Similar presentations


Ads by Google