Con-Ops & Design Alternatives

1. Enterprise Modeling Saad El Beleidy, Peyman Jamshidi, Jared Kovacs, Gabriel Lewis System Engineering & Operations Research, George Mason University Stakeholder Analysis Context Problem, Scope & Need . • IT Solutions Government Contractors • Provide technology or services to government entities • Gain 100% of revenue from successful proposals • Respond to 15-25 proposals a year • 5-10 competitors for each proposal • Must be efficient in time sensitive proposal development process • Key Stakeholders • Directly involved in the solutions development process • Solutions Architects • Capture Managers • Proposal Managers • Primary Stakeholders • Beneficiaries of successful proposals • Executives • Solicitors • Vendors • External Stakeholders • Indirectly impacted by proposed solutions • The public Problem The current process for AoA has notable time-inefficiencies and there is a potential for an improved process with the same performance but lower time consumption. Need There is a need for a system to increase proposal development efficiency by reducing the mean time needed for Analysis of Alternatives (AoA) by at least 33%, and the variability of the same by 25%, while maintaining or increasing AoA proposed solution quality. Results, Conclusion & Future Work Preliminary Simulation Results When testing the As-Is System: Average System Time: When testing Average System Time: % Decrease: Conclusion Based on our preliminary results meeting the need for this problem is very feasible but we currently need to conduct more research to find more applicable alternatives that would impact the system as a whole. Simulation We’ve classified each sub-process of AoA into several categories: Labor Intensive, Decision Making, Experience Recall, Networking. The data collected was for Optimistic, Most Likely & Pessimistic. To account for unlikely situations multipliers were used to form weighted data that helped form the triangular probability distributions to the left. Con-Ops & Design Alternatives • Future Work • Expand scope to include quality of AoA output • Measure quality of AoA output • KepnerTregoe Analysis • Find alternatives that impact AoA output quality • Expand alternatives to meet requirements • Measure time variability of AoA sub-processes • Expand on current alternatives • Explore further alternatives • Simulation • Collect time and complexity data for process level 4 • Model process level 4 • Simulate and validate “As-Is” process model • Simulate alternatives models • Evaluate Alternatives • Develop utility function of AoA time and quality • Analyze results • Develop Recommendations Mission Requirements The systems shall reduce the mean time required for AoA by at least 33% The systems shall reduce variability in mean time required for AoA by 25% The systems shall allow storage of current and retrieval of past technical solution material The systems shall function in various proposal sizes (1 month, 6-months and year-long proposals) The systems shall allow inter-personal coordination on technical solution development efforts Combinations of alternatives are possible to meet mission requirements. Currently, alternatives do not meet need.