Incident Management and Request Management Input to A1.1Problem Management KEDB Input to A1.6A1.1 Define Type of Knowledge A1.2 New Knowledge - Is this duplicate Knowledge? - Yes, go to A2.2 Notify Author reason for Denial Go to Incident Management for closure - No, go to A1.6 Edit/Maintain/Store then go to A2.1 Post Knowledge/Notifications sent to IT Community then to Incident Management for closureA1.3 Modified Knowledge - Is Author the Owner of the existing article? - Yes, go to A1.6 Edit/Maintain/Store then go to A2.1 Post Knowledge/Notifications sent to IT Community then to Incident Management for closure - No, go to A1.5 Send E-mail to Owner. Owner approves or denies - Approve, go to A1.6 Edit/Maintain/Store then go to A2.1 Post Knowledge/Notifications sent to IT Community then to Incident Management for closure - Deny, go to A2.2 Notify Author reason for Denial then go to Incident Management for closureA1.4 Retired Knowledge - Is Author the Owner of the existing article? - Yes, go to A1.6 Edit/Maintain/Store then go to A2.1 Post Knowledge/Notifications sent to IT Community then to Incident Management for closure - No, go to A1.5 Send E-mail to Owner. Owner approves or denies - Approve, go to A1.5 Edit/Maintain/Store then go to A2.1 Post Knowledge/Notifications sent to IT Community then to Incident Management for closure - Deny, go to A2.2 Notify Author reason for Denial then go to Incident Management for closureA2.1 Post Knowledge/NotificationsA2.2 Notify Author reason for DenialAt end of Procedure, Go to Incident Management Process (Closure Procedure)