0% found this document useful (0 votes)
20 views6 pages

AON Diagrams for Q2-Q5 Projects

The document outlines clean AON (Activity-on-Node) network diagrams for four projects: site preparation, writing a paper, market research, and a custom order project. Each project includes activity labels, a network diagram, and explanations of the sequence and dependencies of tasks. Key concepts such as burst and merge activities are highlighted for each project, illustrating how tasks can run in parallel or must wait for others to complete.

Uploaded by

Taimoor ali
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views6 pages

AON Diagrams for Q2-Q5 Projects

The document outlines clean AON (Activity-on-Node) network diagrams for four projects: site preparation, writing a paper, market research, and a custom order project. Each project includes activity labels, a network diagram, and explanations of the sequence and dependencies of tasks. Key concepts such as burst and merge activities are highlighted for each project, illustrating how tasks can run in parallel or must wait for others to complete.

Uploaded by

Taimoor ali
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Below are **clean AON (Activity-on-Node) network diagrams** for **Q2–Q5**, with **labels

(ID + activity name)** and a short **explanation** for each. (The activity tables are shown in
your scan on **page 1 and page 2**.)

---

## Q2 — Site preparation (Survey → utilities → excavate → foundation)

**Activity labels**

* **A**: Survey site


* **B**: Install drainage (after A)
* **C**: Install power lines (after A)
* **D**: Excavate site (after B and C)
* **E**: Pour foundation (after D)

**AON network (boxed & labelled)**

```
┌────────────────────┐
│ A: Survey site │
└────────────────────┘
|
┌───────────┴───────────┐
v v
┌────────────────────┐ ┌────────────────────┐
│ B: Install drainage │ │ C: Install power │
└────────────────────┘ └────────────────────┘
\ /
\ /
v v
┌────────────────────┐
│ D: Excavate site │
└────────────────────┘
|
┌────────────────────┐
│ E: Pour foundation │
└────────────────────┘
```

**What’s happening (explain)**

* After surveying (**A**), two jobs can run **in parallel** (**B** and **C**).
* Excavation (**D**) must wait until **both** drainage and power are done.
* Then foundation (**E**) happens after excavation.

**Burst / Merge**
* **Burst:** **A** (splits into B and C)
* **Merge:** **D** (waits for B and C)

---

## Q3 — Writing a paper (Topic → research → draft → finishing tasks → final)

**Activity labels**

* **A**: Identify topic


* **B**: Research topic (after A)
* **C**: Draft paper (after B)
* **D**: Edit paper (after C)
* **E**: Create graphics (after C)
* **F**: References (after C)
* **G**: Final draft (after D, E, F)

**AON network**

```
┌────────────────────┐
│ A: Identify topic │
└────────────────────┘
|
┌────────────────────┐
│ B: Research topic │
└────────────────────┘
|
┌────────────────────┐
│ C: Draft paper │
└────────────────────┘
┌───────┼────────┐
v v v
┌───────────────┐ ┌────────────────┐ ┌────────────────┐
│ D: Edit paper │ │ E: Graphics │ │ F: References │
└───────────────┘ └────────────────┘ └────────────────┘
\ | /
\ | /
v
┌────────────────────┐
│ G: Final draft │
└────────────────────┘
```

**What’s happening (explain)**

* Once the draft (**C**) is done, you can do **editing, graphics, and references in parallel**.
* The **final draft (G)** can only happen after **all three** are complete.
**Burst / Merge**

* **Burst:** **C** (splits into D, E, F)


* **Merge:** **G** (waits for D, E, F)

---

## Q4 — Market research project (Contract → survey/market/data → outputs →


presentation)

**Activity labels**

* **A**: Contract signed


* **B**: Survey designed (after A)
* **C**: Target market identified (after B)
* **D**: Data collection (after B and C)
* **E**: Develop presentation (after B)
* **F**: Analyze results (after D)
* **G**: Demographics (after C)
* **H**: Presentation (after E, F, G)

**AON network**

```
┌────────────────────┐
│ A: Contract signed │
└────────────────────┘
|
┌────────────────────┐
│ B: Survey designed │
└────────────────────┘
┌───────┴───────────────┐
v v
┌────────────────────┐ ┌──────────────────────┐
│ C: Target market │ │ E: Develop │
│ identified │ │ presentation │
└────────────────────┘ └──────────────────────┘
┌───────┴───────┐
v v
┌────────────────────┐ ┌────────────────────┐
│ D: Data collection │ │ G: Demographics │
└────────────────────┘ └────────────────────┘
|
┌────────────────────┐
│ F: Analyze results │
└────────────────────┘
┌───────┬───────────────┬───────┐
v v v
(E) (F) (G)
\ | /
\ | /
v
┌────────────────────┐
│ H: Presentation │
└────────────────────┘
```

**What’s happening (explain)**

* After **B**, you can already start building the presentation material (**E**) while other work
continues.
* **D** is a **merge step** because it needs **B and C** (you need the survey ready and
you must know the target market before collecting data).
* Final presentation (**H**) needs **all three outputs**: the developed presentation material
(**E**), analyzed results (**F**), and demographics (**G**).

**Burst / Merge**

* **Burst:** **B** (splits into C and E), and **C** (splits into D and G)
* **Merge:** **D** (needs B & C) and **H** (needs E, F, G)

---

## Q5 — Custom order project (Standard + custom + software → manufacture → assemble


→ test)

**Activity labels**

* **A**: Order review


* **B**: Order standard parts (after A)
* **C**: Produce standard parts (after A)
* **D**: Design custom parts (after A)
* **E**: Software development (after A)
* **F**: Manufacture custom parts (after C and D)
* **G**: Assemble (after B and F)
* **H**: Test (after E and G)

**AON network**

```
┌────────────────────┐
│ A: Order review │
└────────────────────┘
┌──────────────┬──────────────┬──────────────┬───────────
───┐
v v v v
┌────────────────┐ ┌────────────────────┐
┌────────────────────┐ ┌──────────────────────┐
│ B: Order std │ │ C: Produce std │ │ D: Design custom │ │ E: Software dev │
│ parts │ │ parts │ │ parts ││ │
└────────────────┘ └────────────────────┘
└────────────────────┘ └──────────────────────┘
\ /
\ /
v v
┌────────────────────┐
│ F: Manufacture │
│ custom parts │
└────────────────────┘
|
┌──────────────┴──────────────┐
v v
┌────────────────────┐ (E already running)
│ G: Assemble │ <────── needs B and F
└────────────────────┘
|
v
┌────────────────────┐
│ H: Test │ <────── needs E and G
└────────────────────┘
```

**What’s happening (explain)**

* After order review (**A**), several tasks start **in parallel** (B, C, D, E).
* Manufacturing custom parts (**F**) needs **both** standard parts production (**C**) and
custom design (**D**).
* Assembly (**G**) needs ordered standard parts (**B**) + manufactured custom parts
(**F**).
* Testing (**H**) needs the assembled product (**G**) + software (**E**).

**Burst / Merge**

* **Burst:** **A** (splits into B, C, D, E)


* **Merge:** **F** (needs C & D), **G** (needs B & F), **H** (needs E & G)

---
If you want, I can also rewrite these as a **“Start/Finish” AON** (with explicit Start and Finish
nodes), or I can do **Critical Path + slack** for any of these once you share (or confirm) the
**activity times**.

You might also like