Question: Create a Critical Path Method (CPM) Diagram for the table created below. Activity (Node #) Activity Description Duration (Weeks) Predecessor A Perform independent research on
Create a Critical Path Method (CPM) Diagram for the table created below.
| Activity (Node #) | Activity Description | Duration (Weeks) | Predecessor |
| A | Perform independent research on each of the five candidate IR sensors | 1 Week |
|
| B | Perform independent research on each of the five candidate IR sensors | 1.5 Weeks | A |
| C | Develop performance models for both IR sensor candidate sensors | 6 Weeks | B |
| D | Develop a CONOPS to determine how IR / optical sensors are to be used on the X-65B | 8 Weeks | B, C |
| E | Use the CONOPS and IR sensor performance models to develop / run independent performance simulations (4 weeks each) | 8 Weeks | B, C |
| F | Use the outcome of your simulations as an input for a technical review to down select to a single IR sensor | 2 Weeks | E |
| G | Hold the IR sensor review and down select to a single IR sensor | 0.14 Week | E |
| H | Perform research on the Eagle-Eye 2000 optical sensor | 4 Weeks | F, G |
| I | Develop a performance model for the Eagle-Eye 2000 | 2 Weeks | F, G |
| J | Update the performance model for the Tiger-Eye 1000 optical sensor | 0.14 Week | I |
|
K | Use the CONOPS and performance models to develop / run independent performance simulations | 7 Weeks | I, J |
| L | Use the outcome of your simulations as an input for a technical review to down select to a single optical sensor | 2 Weeks | K |
| M | Hold the optical sensor review and down select to a single optical sensor | 0.14 Week | L |
| N | Design a common prototype hardware integration package to allow the selected IR / optical sensor to be mounted in the X-65B. | 10 Weeks | M |
| O | Test the hardware integration package and make required modifications | 2 Weeks | N |
| P | Build three hardware integration packages | 2 Weeks | N, O |
| Q | Design software to integrate the selected IR sensor with the X-65B mission computer | 12 Weks | N, O |
| R | Code IR sensor integration software | 4 Weeks | P, Q |
| S | Perform IR sensor software integration testing with the IR sensor and the X- 65B simulator | 3 Weeks | Q, R |
| T | Design software to integrate the selected optical sensor with the X-65B mission computer | 13 Weeks | N, O |
| U | Code optical sensor integration software | 2 Weeks | T |
| V | Perform optical sensor software integration testing with the optical sensor and the X-65B simulator | 3 Weeks | T, U |
| W | Install IR and optical sensors on the X-65B | 1 Week | S, V |
| X | Perform final IR payload integration testing with the X-65B aircraft and make required changes | 2 Weeks | S |
| Y | Perform final optical payload integration testing with the X-65B aircraft and make required changes | 2 Weeks | V |
| Z | Develop test plan for X-65B live sensor testing | 12 Weeks | W |
| AA | Using the test plan, perform required hazard / safety analysis | 3 Weeks | Z |
| AB | After completing the hazard/safety analysis, attain live sensor testing approval | 6 Weeks | AA |
| AC | Perform X-65B live sensor tests | 2 Weeks | AA, AB |
| AD | Develop live demonstration* plan, based on the outcome of the X-65B live sensor tests | 1 Week | AC |
| AE | Make final changes to sensor payload configurations, based on live sensor tests | 2 Weeks | AC, AD |
| AF | Hold live demonstration* review | 0.28 Week | AE |
| AG | Perform a practice series of dry run demos in preparation for the formal demonstration* | 1 Week | AE |
| AH | Perform live sensor demonstration | 0.14 Day | AF |
| AI | Perform hot wash meeting after demonstration | 0.14 Day | AH |
| AJ | Write final close-out report, based on hot wash | 1 Week | AI |
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
