ISSUE MANAGEMENT Issue Management over an Extranet Value Eng

ISSUE MANAGEMENT Issue Management over an Extranet Value Engineering Proposal Any other cause Such as RFI Field Emergency Bulletin/AS Change Create Issue (Stays open until all delegated to other functions) Create as many RFis as needed. Track each RFI until closed. Show status here. Create as many Change Orders as needed. Track ach Change Orde until closed. Show status here Is one or more YES Is one or more RFIs needed? Change Orders needed? YES NO NO Create as many Requests for Quotation as needed. Track each RFQ until closed. Show status here Create as many Discussion Topics as needed. Track each Topic until closed. Show status here. Is one or more RFOs needed? s further discussion needed? YES YES NO NO Create as many Action Items as needed. Track each Action item until closed. Show status here Create as many Work Orders as needed. Track each Work Order until closed. Show status here Is one or more Action items needed? Is one or more Work Orders needed? YES YES NO NO Create as many Clarification Items as needed Track each Item until closed. Show status here Create as many Purchase Orders as needed. Track each Purchase Order untid closed Show status here is one or more AVE clarifications needed? s one or more Purchase Orders needed? YES YES NO NO Issue Management Workflow Logic Diagram

Solution

I disgree with the se up of the Flow chart because of the foloowing reasons:

1. \"Field Emerency\" factor could not be interlinked to a top down-flow. Instead it shall be placed as a bottom-up factor in the given Issue Management diagram.

2. \"Value Engineering\" factor is ideally be placed as an external available solution instead of being as one among the influencing criteria in Issue Management.

3. Also, the flow indicates for the creatation of as many work orders/ purchase orders as the case may be. This could not be an eventuality because the RFI is the deciding factor for this

4. RFI is to be ideally placed below the \"Create Issue\" factor.