Product EOL Request Management -- 2

1.) for coporate internal usage. 2.) authentication by active directory (windows login) and authorize by ADGroup member. 3.) Authorized user can raise the EOL Request. 4.) request will go through the approval process & then assign to Production Planning Team for final action. 5.) multipages: a.) Landing Page / List Page: authorized user will be landed on this page. by default will list out 30 most recent EOL request which user can view into. this page also containing filtering function where user can filter the listed items. b.) AddNew Form: for authorized user to raise / amend request. User can save as draft or submit request here. upon submit, there should be an email notification send to Technical Director for further review. c.) Review / Approving / Commenting Page: after user submit the request, Technical Director will use this page to review then decide "Proceed" or "Not Now". If "Not Now" is chosen, status of the respective request will change to "rejected" and flow end. If "Proceed" is chosen, then system will send email to all four marketing HODs (by a single email distribution list). all Marketing HODs will use the same page to provide thier comment and also either "Agree" or "Disagree" to the request. After all four Marketing HODs review, system and then send email to COO / MD (another Email Distribution List) for final decision. COO or MD can change the "Grace Period" on this page (need to be logged), and either approve or reject this request. d.) Production Planning Team will receive notification upon COO / MD approval and this team need to mark the request as done after performing required action (at another system). 6.) Request Status : i.) Draft ii.) Pending Technical Director iii.) Marketing Review iv.) COO / MD Approval v.) Pending Production Planning vi.) Rejected (by Technical Director or by / COO / MD) vii.) Completed 7.) UserGroup (setup in Active Directory security group): a.) SF_APPWEB1_EOL_CONTRIBUTOR (authorized to raise request) b.) SF_APPWEB1_EOL_TECHDIRECT (user group who can act as Technical Director to review & decide whether proceed or not (action ii mentioned at above) ) c.) SF_APPWEB1_EOL_SALESTEAM_EST (EXPORT SALES TEAM) d.) SF_APPWEB1_EOL_SALESTEAM_LST (LOCAL SALES TEAM) e.) SF_APPWEB1_EOL_SALESTEAM_PST (PROJECT SALES TEAM) f.) SF_APPWEB1_EOL_SALESTEAM_TST (TRANSFORMER SALES TEAM) g.) SF_APPWEB1_EOL_PRODPLANNING (PRODUCTION PLANNING) 8.) all data are to be store in MSSQL table. all user action are to be logged. 9.) ADGroup 'ITPROGRAMMER' have access to all pages. 10.) mailserver: [login to view URL] (no need authentication). Use SQL Mail to send all notification email. 11.) application should be mainly coded in ASP.NET / VB.NET / Javascript / razor / MSSQL and to be host on internal IIS server