Download
1 / 35
350 likes | 456 Views
WFO Planning Tool RFC & FCT. STMicroelectronics Wafer Foundry Outsourcing. Team Members & Roles. Business Objective. Need for medium term forecast of the demand and supply to plan business growth.
E N D
WFO Planning ToolRFC & FCT STMicroelectronics Wafer Foundry Outsourcing
Business Objective Need for medium term forecast of the demand and supply to plan business growth. Improve the correctness in the decision making process of WFO planning team and ST management, by providing the pattern of the demand and supply from ST customers and ST foundries respectively on a one year scale. Improve the productivity and effectiveness of the WFO Planners.
Scope WFO Planning Tool assists WFO planner in bridging Supply demand. Developing a medium term forecast module (FCT) for analyzing the business of the company for future plans and also to enhance the functionality of the current short term forecast module (RFC). Based on the data from FCT, implement the enhancement in the RFC module.
Foundry A (China) ST Group A Product 1 Request Needs/Request Commit Commit ST Group B (Product 3 Needs/ Request Request Foundry B (Malaysia) Business Flow WFO Planning Team
Required System Foundry A (China) Cap-50 ST Group A Product 1 Request - 50 Needs -80 Request - 50 WFO Planning Team Capacity- 50 Commit-50 Commit-80 Commit-50 ST Group B Product 3 Needs -80 Request - 50 Request - 50 Request - 80 Request - 80 Foundry B (Malaysia) Cap-50 Capacity- 50 Capacity- 80 + Cap-30
STM WFO FDY Planning Process –Requirements of RFC and FCT Constrained order by PN CRP Com & CCAR Monthly CRP Request Manual entry I2 / MPS Monthly Visibility 12 Months horizon Weekly orders 17weeks horizon RFC FCT Tool Alloc Commit By PN Request By PN Forecast By Area / Capa Commit by Area / MP / Group Confirmation By Area / Capa Real demand by PN & Capacity Limitation by Area / MP / Group / W Request by PN Commit By PN CCP WFO 7
Development Strategy • Phase-1, Phase-2 activity of project is performed in waterfall model. • Phase-3 is developed using SCRUM methodology. • Total Number of Sprints – 5. • Life time of Sprint – 1 Week. • Developed in Client location, as the tool is tightly integrated with STMicroelectronics internal OrgSec tool. • Client suggested iterative incremental model, as parallel work is being done on the same tool.
Reasons for Choosing SCRUM • Client need to integrate continuously with the current system. • As parallel development work is occurring team expected last minute change requests. • SCRUM provides easy feedback system from client, as client is closely involved in the project progress – vital to project success.
UCMS for RFC 11
Technical Issues During Phase 3 • Issue with design of RFC – In the current application the complete logic is performed in Week17Page. • Issue with setting up Configuration Management System – The clearcase on the system could not be configured. • Issue with Database – Parallel usage of DB led to ‘Lock of the DB Procedures’.
Solution for Technical Issues • Issue with design of RFC – We designed and implemented the enhancement based on the existing structure/design for RFC. • Issue with setting up Configuration Management System – The entire application was divided into modules and split the work individually and integrated using the common shares folder at the end of each day. • Issue with Database – Cleared the issue by defining separate schema for our project, there by ensuring the DB lock do not occur.
Acceptance Procedure • As part of SCRUM Methodology, team delivered the components/deliverables on sprint (week) basis. • The Customer would examine the deliverable and share the feedback with the team. • At the end of project, after the system testing is performed by the team, User performs official Acceptance Testing before the sign off.
Customer Feedback • As the development was performed on client location, the user had a closer view on the daily activity of the team. • The customer identified an issue with deliverable of sprint 1, he raised it during the sprint 3 process. Team rectified the issue during the sprint 4. • User reviewed the team’s System test log, bug tracking system, and performed an informal acceptance testing before signing off the Project Acceptance.
Management Problems – Phase 3 • Tasks from Planned Phase 2 – Detailed Design • Detailed design and system test plan were finished and finalized before the start of coding phase. • Delay in start of Phase 3 – Started on 17/1/2011 but planned to start on 10/1/2011. • Addressed with contingency. Prepared System Test Plan during this period. • Late notice of unavailability of QM. • Cancelled Sprint 2 re-planned the sprints, Additional Sprint.
Management Problems – Phase 3 • Unexpected leaves at the end of January. • Cancelled Sprint 2. • Closure of ST for Chinese New Year (Forced Vacation) • The schedule was delayed. But, have sufficient contingency. • Unavailability of systems at STMicroelectronics. • Two heads on same code, increased effectiveness and reduced the number of bugs in coding phase.
What’s Next??? • The next milestones for WFOPT are envisioned as: • Additional Features on Medium Term Forecast Module. • The next stage of WFOPT would be to develop Long term forecast tool which would be on 2 years to 5 years period on quarters scale. • Similar to the request restriction in RFC based on the capacity value from FCT. The content in FCT could be controlled based on the data from long term forecast tool which would make the tool even more effective.
Lessons Learnt • Resource Planning (Back up) • No Back up for the activities performed by a single assigned resource. • Faced few issues due to sudden unavailability of quality manager. • Customise Process to suit your project. • Implemented SCRUM for the coding phase alone. • Enabled to identify defects early. • Simplified the Integration and User Acceptance activities. • Code Walk Through and Resource Management • Due to constraint in system availability, team engaged two heads on single code. • This reduced defects in coding, thus reduced rework. 29
Plan for Implementation Phase - SCRUM Client Proposal – Iterative Incremental Development. Team’s Proposal – SCRUM. Product Backlog: RFC Functionality. FCT Functionality. Data Transfer between RFC & FCT. Validation/Approval in FCT. Download/Upload data in FCT. Sprint Duration – 1 week. Number of Sprints – 4. 32
Sprint Release Planning Sprint-1 Backlogs RFC Functionality New Parameters for a particular product. Capacity validation using M-FEG data from DB Sprint-2 Backlogs FCT Functionality & Integrate RFC & FCT Attributes for a product to be added. Change in attribute should reflect in RFC. Sprint-3 Backlogs Validate functionality in FCT & Upload, Download Functionality. Validate functionality similar to RFC. Upload and download the data of the particular product from DB. Sprint-4 Backlogs System Testing & Contingency System Testing and test documentation and results. Rectification activity. Contingency.
