SkillsTraining Template (Ver. 2.5 - 10/11/96) for NT Do ...



FCCB White Paper Handbook

and

Training Manual

Blank page

TABLE OF CONTENTS

1. Introduction 7

2. What is the FCCB? 9

General Change Boundaries 11

Facilities Systems Changes 12

Equipment Installation Changes 13

Getting Changes Approved 15

3. FCCB Change Classifications 17

Classifying Changes 18

Change Classification Exercise 22

Equipment Installation Considerations 24

Cost Considerations 25

4. FCCB White Paper Guidelines 26

The White Paper Review Process 27

General FCCB Administration Procedures 30

White Paper Elements 31

White Paper Rejection 37

5. Appendix 1: Environmental, Health, and Safety Issues 39

6. Appendix 2: FCCB Facility Systems Definitions 40

7. Appendix 3: FCCB/ACCB Interrelationships 41

Blank page

FCCB Quick Reference

Regularly needed information

Here’s a guide to some of the key information contained in this handbook.

|To find information about: |see page(s) |

|FCCB change classification matrix |18 |

|FCCB facility system levels and definitions |40 |

|FCCB administration (who do I talk to, when do WP’s have to be submitted,|30 |

|etc.) | |

|Details regarding the information that must be included in each section |31 |

|of a white paper | |

Blank page

Introduction

Course goals

This class on writing Fab Facilities Change Control Board (FCCB) white papers is designed to meet the following goals:

1. Communicate the process for obtaining the appropriate level of approval(s) for a change to any components within a fabs facilities system or for a change to any fab equipment installation.

2. Explain the methodology for classifying FCCB-related changes.

3. Increase the quality and approval rates of white papers when they are presented at the required change control boards.

4. Define and explain the FCCB white paper template.

Course objectives

At the completion of the class, you will be able to:

5. Identify the change control boundaries within the scope of the facilities change control board.

6. Classify changes to facilities systems and to equipment installations correctly

7. Identify examples of good and bad white papers, and write a white paper that conforms to the existing standards.

8. Explain the steps involved with getting a white paper through the approval process, and follow those steps in actual practice.

Intended audience

This class is intended for personnel from the following groups:

9. Fab Engineers and Technicians

10. Site Material and Services (SMS)

11. Intel Corporate Install/Qual (IQ)

12. Facilities Construction Technology (FCT)

13. Contractors supporting all the organizations listed above

Class outline

This class is divided into the following sections:

|Section |Information in the section |

|1: Introduction |What you’re now reading |

|2: What is the FCCB |Charter and scope of the FCCB; general change boundaries;|

| |general white paper approval process. |

|3: FCCB Change Classifications |General change classifications; assessing the criticality|

| |and level of changes for facilities system and equipment |

| |installation modifications; examples and exercises. |

|4: FCCB White Paper Guidelines |Rules; procedures; format; samples of good and bad white |

| |papers; detailed white paper approval process, |

| |flowcharts, and administrative guidelines. |

|5: Appendices: |Supporting information for white papers and associated |

|EHS Issues |groups to include in the approval process. |

|Facilities Matching | |

|FCCB Facility System Definitions | |

What is the FCCB?

Charter/Scope

Primary purpose

The Fab FCCB is responsible for documenting new systems, and controlling changes in facilities and in fab process equipment installations across the virtual factory. Examples of which include:

|Type of change |Span of control |

|Changes to, and differences between, the |Common facility system changes |

|"utilities" in each factory |Master specification changes |

| |Factory plan-of-record changes |

|Changes to, and differences between, |Master packages changes |

|process equipment installations |Location-specific packages changes |

|New factory implementations |Documentation of new critical systems |

| |Facilities matching |

Scope

The fab FCCB is responsible for managing the aspects of CE! listed above for the following structures and processes:*

14. Fabs, sort, fab C4, bridge buildings, fab support labs, and fab central utilities buildings (CUBs)

15. Process 854, 856, 858, 860, 802, 1260, and future 12xx processes

*See FCCB Web address for the current factory/process matrix.

FCCB Objectives

The FCCB attempts to ensure that:

1. Factories that run the same process are designed and operated such that the process "sees" no difference from one factory to the next.

2. The process is duplicated in each factory by understanding and controlling process equipment installation changes.

3. Tool installation costs are reduced by working closely with FCT (Facilities Construction Technology) and IQ (Install/Qual).

4. CE! is maintained "long term" for facilities and equipment installation in the virtual factory.

5. Environmental, health, and safety concerns are addressed in each change.

6. Changes are based on data-driven decisions, not personal preference or emotion.

Items not addressed

Other change control boards (PCCB, OCCB, ACCB, BCCB, etc.) are responsible for other aspects of Copy Exactly! (e.g., equipment recipes, equipment qualification, etc.). These topics are not monitored by the FCCB.

16. The white paper format discussed in this presentation applies only the FCCB. The other change control boards listed above may have their own white paper standard.

1 General Change Boundaries

CE! Rules

Copy Exactly! guidelines state that changes to an existing plan-of-record (POR) are only allowed if there are compelling reasons or physical barriers to copying exactly. However, these exceptions must be tested, reviewed, and then approved by the FCCB process to ensure that the proposed changes won’t affect product yield or reliability. Cost, safety, and impact to operations are also included in the FCCB decision. Some examples of a compelling reason to change are:

17. Improvements in environmental, health, safety, or risk management issues

18. Code compliance

19. A particular component is no longer available, at any price

20. A local site requires additional waste treatment, above and beyond the POR

21. A substantial cost savings can be realized by Intel without impacting the process

22. Corrects a known problem and establishes a new POR

23. Physical and geographical constraints

Compelling does not mean

Once a change is established as compelling, the change is documented using a white paper and it is reviewed through the change control process. Therefore, compelling does not mean:

1. That's the way we do it in __________ (plug in the appropriate Intel site)

2. This is the industry standard

3. Personal preference/bias

2 Facilities Systems Changes

Span of control

The following diagram illustrates the boundaries of facilities systems changes in the FCCB structure. The arrows in the diagram below designate the items that are considered facilities system changes. In general:

24. Changes to facilities system include both the base building system and the lateral distribution network.

Figure 1 FCCB Utility Change Boundaries

[pic]

3 Equipment Installation Changes

Span of control

The following diagram describes the boundaries of equipment installation changes in the FCCB structure. The arrows highlight the items that are considered to be within the "equipment installation" boundary. In general:

25. Equipment installation changes begin at the take off point from the lateral and continue to the shell of the process tool.

26. Equipment specific support equipment (e.g., chillers, pumps, etc.) and their connection to the process equipment are included as well.

Figure 2 FCCB Equipment Installation Change Boundaries

[pic]

Considerations

Items to consider when making any change are:

|If….. |Then…. |Example(s) |

|It’s a change to the way we |This is considered a roadmap change and |A new and less expensive water treatment |

|want to build future Fabs |it requires FSCS (Factory Strategic |system is found to work extremely well. |

| |Capability Segment) and FCCB review. | |

|The change affects the |This change may require a Facilities |A new filter is found that works well for |

|materials that we use to build|Technology Spec change. Contact the FT |UPW applications and is less expensive |

|new Fabs |Spec administrator for more details. |than the POR. |

|The change affects the |This change requires review and approval |Changing building systems from UPS power |

|operations of the Fab |by the MOSCS (Manufacturing and Operations|to standard power which will result in |

| |SCS). |additional fab downtime during a power |

| | |outage. |

|The change affects any of the |This change will require review and |A change that affects the AMHS (automated |

|automation systems in the Fab |approval by the ACCB (Automation Change |material handling system) in the Fab. |

| |Control Board) | |

|The change involves a |This is considered a global change. Since|A new high purity valve for inert gases is|

|component that affects more |more than one equipment type is affected, |found which is less expensive and performs|

|than one equipment type |several equipment JETs need to be |better. This component is present in the |

| |notified. The FCCB works with the JEM to |installation of 14 different pieces of |

| |identify the appropriate equipment JETs. |equipment in the Fab. |

|The equipment installation |This is considered a Location Specific |Fab 15 installs a planarization tool in an|

|change is location specific |Package (LSP) equipment installation |area that was originally designed for |

|and is not intended or desired|change and the LSP is authorized to |office space. This requires some unique |

|to change the standard |deviate from the master package. |installation strategies that are not |

|installation design. | |completely standard. |

|The change is such that |This change needs to have buy-in and |A safety issue is uncovered with the |

|existing factories need to |funding from all the affected factories. |current installation design of the |

|retrofit this item | |sulfuric wet bench. |

Note: For any of the additional reviews described above (FSCS, MOSCS, etc.), the FCCB will provide guidance on who to contact to enable the WP author to review their change with these organizations.

4 Getting Changes Approved

Procedures

General procedures for making any of the changes mentioned in this section are as follows:

|Step |Action |

|1 |Identify the classification of the change in order to determine the appropriate |

| |review process. |

|2 |Draft a white paper that details the change. |

| |You may first need to draft a preliminary white paper that explains the change and |

| |details the success criteria. This preliminary white paper must be approved by the |

| |FCCB before the change may be attempted. |

| |The preliminary white paper becomes the final white paper once the change is made, |

| |tested, and results reported back to the FCCB for their final approval. |

|3 |Review the white paper with the appropriate sponsors and pre-FCCB approval bodies and|

| |obtain their support/funding for making the changes. |

|5 |Review the white paper with the FCCB (and PCCB if required) for their final OK. |

|6 |Make the changes. |

|7 |Update any other documents that are effected on account of your change. |

Continued next page.

Simplified approval flow

The steps outlined in the previous tables are illustrated in this flowchart:

[pic]

Remaining items

The remainder of this material discusses the rules used for classifying a change, the elements of an FCCB white paper, and discuss the white paper review process in greater detail.

FCCB Change Classifications

Introduction

Definition

A key element of the FCCB white paper is its "classification". The white paper classification is a number (typically denoted as a roman numeral) that assesses the amount of risk associated with the specified change. The “risk” that we refer to here is risk to the process (i.e., wafer yield or performance) and not risk in the sense of safety or environmental issues. The change classification level becomes the overall "class" of the white paper (e.g., a Class III white paper).

Classification levels

White paper classifications are described below. In addition to assessing the risk of a specific change, the change classification also determines the amount of review and scrutiny the specific white paper requires. In other words, a Class V white paper is reviewed at a relatively low level while a Class III white paper is reviewed at several levels due to its higher risk.

|Classification |Description |General Review Process |

|Class I |Device or Performance Change|Reviewed by other CCBs: Not the FCCB. |

|Class II |Device or Performance Change|Reviewed by other CCBs: Not the FCCB. |

|Class III |Significant Risk |Reviewed at the appropriate JET, FCCB, and then |

| | |the affected PCCB(s). |

|Class IV |Moderate Risk |Reviewed at the appropriate JET, and then the |

| | |FCCB. |

|Class V |Low Risk |Reviewed at the appropriate JET, and then the |

| | |FCCB. |

|Project Team |Very Low Risk |No review required for change. Document at the |

| | |project team level |

Note: The FCCB is only concerned with reviewing the white papers described in the non-shaded rows

1 Classifying Changes

Step 1: System levels

The first step at determing the amount of review a change will need is to identify its criticality. The Fab FCCB separates all the changes it manages into four different criticality "levels" that follow these general guidelines:

|Level |Short Description |Risk Assessment |

|A Level |Items that touch the wafer |Changes to A-level systems potentially have the most |

| | |risk due to their close proximity to the wafer. |

|B Level |Items that provide critical input|Changes to B-level systems carry less risk than A-level |

| |to the manufacturing process |since they are one level removed, but the risk is still |

| |(usually process tools) |substantial. |

|C Level |Items that are critical to |Changes to C-level systems typically have very little |

| |building system operations, but |direct risk to wafers. But problems with a C-level |

| |do not impact the process tools. |system can still stop a Fab from operating or cause |

| | |wafer loss. |

|E Level |Items that impact an |Changes to E-Level systems carry the risk of exceeding a|

| |environmental system |sites chemical or gaseous effluent upper limit, |

| | |impacting the sites operating permits. |

Step 2: Change degree determination

Once you’ve assessed the level of criticality for your white paper, the next step is to determine the degree of the change the system will be undergoing. This is called the change degree. Four different change degrees have been defined for the FCCB.

|Change Degree |Description |Example(s) |

|Change Degree 1|A change in the OUTPUT or PERFORMANCE of a |A change in the temperature of the delivered |

| |particular system. This would also include |UPW would be a degree 1 change for the UPW |

| |items such as the system reliability. |system. |

|Change Degree 2|A change in the DESIGN, or a DIFFERENT |Design example: |

| |MATERIAL in the wetted stream, of a |A rearrangement of the order of unit operations|

| |particular system which is not expected to |of the UPW system. |

| |affect the performance or output of the |Material example: |

| |system. |A lower grade of stainless steel for high |

| | |purity Nitrogen system laterials |

|Change Degree 3|A change in one or more CRITICAL COMPONENTS |A different high purity UPW valve which has |

| |in a particular system. System controls, |essentially the same specifications as the |

| |software, and monitoring are considered a |prior valve and it is not expected to affect |

| |critical component as well as the valves, |the quality or performance of the UPW system. |

| |fittings, etc. | |

|Change Degree 4|A change in one or more NON-CRITICAL |A change in the distribution pump motor for the|

| |COMPONENTS in a particular system. |UPW system (the motor itself is not in the |

| | |"wetted" stream of the UPW system). |

Determine the change degree

As depicted in the flowchart, the change degree determined by starting at the most critical and working down to the least critical level.

[pic]

Step 3: Final Classification

The final step in determining the review procedures and approvals for a change compares the level of criticality to the change degree in the following matrix:

|LEVELS |

|Change |LEVEL A |LEVEL B |LEVEL C |Level E |

|Degree | | | | |

|1 | | | | |

|Different Output |Class III |Class IV |Class V |Class IV |

|2 | | | | |

|Different Design/Material |Class III |Class V |Class V |Class IV |

|3 | | | | |

|Different Critical |Class IV |Class V |Project Team |Class V |

|Component | | | | |

|4 | | | | |

|Different Non-Critical |Class V |Project Team |Project Team |Project Team |

|Component | | | | |

Multiple changes

In the event of multiple changes, each change must be identified and classified accordingly. However, the overall white paper classification is determined by the "highest" class of all of the changes.

27. For example, if a modification contains one class III and three class IV changes, the overall classification is III.

2 Change Classification Exercise

Directions

The following examples contain changes to facilities system that might appear for approval at any FCCB meeting. Read each case study and write the utility level, change degree, and final classification of the change in the space provided to the right of the example.

Example #1

|Case Study |Write your answers here |

|Changes to the output temperature of the ambient UPW | |

|system. |Level: |

| | |

| |Change Degree: |

| | |

| |Final Classification: |

Example #2

|Case Study |Write your answers here |

|Install a different motor on a PCW pump. | |

| |Level: |

| | |

| |Change Degree: |

| | |

| |Final Classification: |

Example #3

|Case Study |Write your answers here |

|Move the location of a AWN collection tank from the | |

|second floor to the first floor. |Level: |

| | |

| |Change Degree: |

| | |

| |Final Classification: |

(Continued)

Example #4

|Case Study |Write your answers here |

|Add a second AWN tank next to an existing tank to | |

|increase the capacity of the overall system |Level: |

| | |

| |Degree: |

| | |

| |Final Classification: |

Example #5

|Case Study |Write your answers here |

|Upgrade the software package on a bulk chemical | |

|delivery system. |Level: |

| | |

| |Change Degree: |

| | |

| |Final Classification: |

Example #6

|Case Study |Write your answers here |

|Add a new valve supplier to the specialty gas delivery| |

|system. |Level: |

| | |

| |Change Degree: |

| | |

| |Final Classification: |

3 Equipment Installation Considerations

CE! Rules

If changes are made to the installation (based on comparison to the Master package), these must be documented in a white paper

28. CE! begins with the Equipment Master package. Master packages are:

1. standard installation template for a specific tool type

2. owned by Intel’s Central Design organization

3. originally based on the development factory’s reference tool

4. modified over time (via the FCCB process) to become the standard template to which each Location Specific Package (LSP) is compared

4 Cost Considerations

29. The FCCB has added cost considerations to its change criteria.

FCCB White Paper Guidelines

Overview

Purpose and description

Once you’ve determined the correct classification of the change you are making, it’s time to document the elements and get appropriate approval. The White Paper (WP) is the vehicle for documenting and reviewing changes in the FCCB process. It is extremely important that sufficient time and effort be spent by the change owner and/or project team to ensure that the WP is written correctly.

General WP rules

White papers must adhere to the following rules:

30. The white paper must be in the correct format.

5. The PCCB and other change control boards also use "white papers" but they utilize a different format. Make sure you use the current revision of the FCCB White Paper format.

31. Although the white paper needs to be succinct and brief enough to read in a short amount of time, all the sections of the white paper must be completed to a level of detail such that someone can read it on their own and have a very good understanding of:

6. The change being made

7. The compelling reason forcing this change

8. The timing of the change

9. The factories/equipment affected by the change

10. The groups that reviewed the white paper

1 The White Paper Review Process

The standard process

The review process used to approve a white paper depends directly on the type of white paper and its change classification.

|Type |Classification |Procedure |

|Equipment |Class IV and V white |Reviewed initially at the JET and the JIQT, then at the FCCB. |

|installation |papers |Facilities matching WP's (see Appendix 3) are always reviewed through |

| | |the FCCB and will be at least class IV (for both A and B level |

| | |systems). However, if the matching WP contains a change that is a |

| | |class III change (per the matrix), then the overall classification of |

| | |the WP will be class III |

| |Class III white paper |Reviewed first at the JET and JIQT, then at the FCCB, then at the |

| | |affected PCCBs. |

| | |The FCCB may need to route Class III white papers to more than one |

| | |PCCB, which will require more than one PCCB review |

|Facilities |Class V |Reviewed at the project team (or xJET), then sent to the FCCB for |

|Systems | |approval. |

| |Class IV |Reviewed at the project team (or xJET), and then sent to the FCCB for|

| | |approval. |

| |Class III |Reviewed at the project team (or xJET), then the FCCB, and finally on |

| | |to the appropriate PCCB for approval. |

Stages of approval

As outlined in the process illustrated below, white papers typically move through three stages:

[pic]

|Stage |Description |

|Preliminary WP |Outlines the plan that will be followed prior to making a change. This |

| |includes the justification for considering the change (compelling reason), |

| |experiment(s) that will be run, success criteria, etc. |

|Approved Preliminary WP|Gives the "authorization" to run the test/experiment. Once the plan is |

| |executed and the data compiled and summarized, the final WP is written |

|Approved Final WP |With the exception of class III white papers, approved FCCB WP’s are issued|

| |a registration number for tracking purposes. Once the registration number |

| |is assigned, the change(s) can be implemented. |

| |Class III white papers must be approved at the PCCB before being assigned a|

| |registration number. |

Notes: If data already exists and additional experiments are not needed to support a change, a WP may come into the FCCB as a final WP. However, due to the risk associated with this route, the FCCB may decide that additional data is required. The WP originator is then required to write a preliminary WP that contains the new requirements.

Procedural notes

|Description |Additional Details |

|Compelling reason to change? |The “reason for change” is the crux of the WP. Without an acceptable reason for change, the WP |

| |will not be approved. Sometimes the reason for change is simple and unavoidable: site conditions |

| |mandate it, the component is no longer available at any cost, etc. However, most changes are |

| |avoidable so there needs to be a compelling reason for the change: Does the “reward” out weight |

| |the “risk.” Typically, compelling reasons for change of this type improve performance, save a |

| |considerable amount of money, fix a known limitation or problem, improve standardization, reduce |

| |construction time, etc. Personal preference/bias do not constitute a compelling reason without |

| |additional evidence or data. |

|Enough Data? |The WP author needs to decide if adequate data exists to proceed with a final WP or if more data |

| |is required before the final decision is made on the change (preliminary WP). Unfortunately, |

| |there is no single formula to use to answer this question. The overall classification of the |

| |change can assist in the decision since class III changes involve more risk than class V changes. |

| |Therefore, a class III WP requires more data than a class V WP. If it is not entirely clear if |

| |enough data exists, the WP author should consult with WP sponsors or FCCB members for further |

| |direction. |

|Gather data; write final WP; |Its important to compare the data to the success criteria and show that the success criteria was |

|return for review. |met or exceeded. The WP author should use the preliminary WP and simply add the data in the |

| |correct parts of the WP along with the data analysis. Also, the preliminary WP number should be |

| |added to the WP on the first page. |

|Implement! |This implies that the final WP is approved, an FCCB horizon number is issued, and the WP author is|

| |authorized to enact the subject change. |

|FCCB approved Class III final|Since a class III WP is not completely approved until its approved by the PCCB, the horizon number|

|WP’s |is not issued by the FCCB until it has been reviewed and approved by the PCCB. |

2 General FCCB Administration Procedures

Details, details, details

Getting white papers to the FCCB:

32. White papers must be submitted electronically via e-mail.

During the FCCB review:

33. The FCCB may issue AR’s (Action Required) for approved white papers. If an item is identified as an FCCB AR, it is issued an owner, an issue date, a due date, and is tracked by the FCCB Administration until closure. Details regarding the FCCB AR Tracking System can be obtained from the FCCB Administrator.

34. Upon approval, the FCCB Administrator issues your white paper a horizon number.

3 White Paper Elements

WP Sections

An FCCB WP has 22 different sections, each of which asks for a particular piece of information. It is important to address each of the sections in an honest and unbiased fashion. For example, in the "Concerns & Considerations" section, plainly state the risks that are involved (to the wafers) in this change. They may be minor, but any change involves risk. A description of the sections follow.

|Sec. |Title |Description/Key Elements |

|0 |None - located at the top |Note whether this is a preliminary or a final white paper. |

| |of page 1 | |

|1 |Horizon Schedule Number |Leave blank until a number is supplied by the FCCB administrator. |

|2 |Title |Be descriptive and succinct and ensure that all facilities and/or |

| | |equipment types are noted. This section will be used for key word |

| | |searches on the web page. |

|3A |Change Classification |This is the overall classification of the WP. If more than one change|

| | |is included in the WP, note the highest change classification here |

| | |(lowest numerical classification). |

|3B |Facilities WP |Note here whether this is an equipment installation or facilities WP. |

| |Equipment Installation |If a block change is required (an equipment installation modification |

| |Block Change |that changes the footprint of the tool), additional approvals are |

| | |necessary. |

|4 |Date |The date that the WP was written. |

|5 |Rev |This is the current revision of the WP. If the WP is modified |

| | |subsequent to a presentation at a JET or other “public” forum, the |

| | |revision number must be updated. |

|6 |Originator/Site |Identify the author of the WP and state which site or organization |

| | |they represent. |

(continued)

WP Sections

Continued from previous page.

|Sec. |Title |Description/Key Elements |

|7 |Sponsors |This is a key part of the WP. Each affected factory should have a |

| | |sponsor listed in this section. If you put someone’s name down as a |

| | |sponsor, its implied that they agree with 100% of your WP. Sending |

| | |someone a e-mail message asking for inputs and not receiving a reply |

| | |is not considered “agreement.” For each person listed, also list |

| | |their site and position. For example, John Nelson, Fab 15, GSS |

| | |Electrical Engineer. |

|8A |Processes Affected |This section can be somewhat confusing. The purpose of this section |

| | |is to note which processes are affected and whether the change affects|

| | |a specific location, all new installations, and/or if retrofits are |

| | |required. Examples: |

| | |If a change is requested for Fab 14 only, the box: Location |

| | |Specific/P856 is checked. |

| | |If the change is requested for all future P856 and P858 factories, and|

| | |it will be retrofitted in all P856 and P858 factories, the four boxes |

| | |P856 and P858 / New Installs and Retrofit are checked. |

|8B |Inter-Process Synergy |Does this change result in synergy between P848, P856, and P858? |

| | |Check the appropriate box (YES, NO, N/A). |

|8C |Synergy Summary |If required, explain the plan that is to be followed to attain synergy|

| | |between all process. |

| | |If synergy is NOT required, justify the decision. |

|9 |Factories Affected |List each of the factories that are affected by this change. |

|10 |Equipment Type or Factory |List each of the equipment types or facilities system that are |

| |Utilities Affected |affected by this change. |

|11 |Review Forums/ Approval |List each of the review forums that have already approved the WP and |

| |Dates |the review forums that are planned. If a group has approved the WP, |

| | |note the date that the approval was granted. If a group has not |

| | |reviewed or approved the WP yet, leave the date section blank. |

(continued)

WP Sections

Continued from previous page.

|Sec. |Title |Description/Key Elements |

|12 |Description of Change |This is one of the key sections of the WP. You can either use the |

| | |table provided or delete the table and explain the change using other |

| | |means. Make sure that each change is listed separately. Pay close |

| | |attention to the parenthetical note in this section to ensure that all|

| | |necessary data is included with the change (e.g., part number, |

| | |material type, etc.). |

|13 |Reason for Change |This is a very important section. It is imperative that the author |

| | |discuss the compelling reasons for each change listed in section 12. |

| | |Ensure that the benefits of the change are quantified. Alternative |

| | |solutions which were considered and rejected can also be discussed in |

| | |this section. |

|14 |Additional Impacts |This section details any other impacts that result if this change is |

| | |implemented (cost, operational expense, etc.). It is important to not|

| | |simply write “N/A” in each of these sections. Also, see the FCCB |

| | |Appendix on safety/EHS to determine if there is an environmental or |

| | |safety impact and if other groups will need to review the WP. |

|15 |Concerns and |This section is also commonly misunderstood. It is intended to assess|

| |Considerations |all of the potential risks associated with this change in an unbiased |

| | |and neutral way. Some authors are hesitant to list any concerns in |

| | |this section because they feel that it suggests a weakness with the |

| | |change. On the contrary, by listing all of the potential concerns, |

| | |the audience can be assured that the author has evaluated all possible|

| | |risks. Any change involves risk, albeit sometimes it is quite small. |

| | |The author should try and anticipate all of the concerns that could be|

| | |raised during the WP presentation. Alternative solutions can also be |

| | |discussed in this section as well. |

|16 |Qualification Plan |For each concern listed in section 15, a qualification plan or |

| | |discussion should be listed in this section. Some concerns require |

| | |elaborate plans that may involve wafer testing or other experiments. |

| | |Other concerns may only require some discussion and logical reasoning.|

(continued)

WP Sections

Continued from previous page.

|Sec. |Title |Description/Key Elements |

|17 |Recovery Plan if Approach |If the proposed change is unsuccessful, what will be done? Some |

| |Fails |changes may have the potential to fail several different ways. In |

| | |this case, each failure mode may have a different recovery plan. |

|18 |Specs, Controlled |List any/all documents that will be changed in support of or resulting|

| |Documents, Drawings |from this change. The table is separated into three sections. Note |

| |Affected. |which sections are affected and note the drawing name/number, owner, |

| | |and the approximate date that it will be changed. |

|19 |Data Summary |This section is only completed for final white papers. Use the table |

| | |provided for your data or add additional tables or text. If the data |

| | |are extensive, attach an addendum and reference it from this section. |

|20 |Implementation Plan |Explain how, when, and who will implement the change. It is important|

| | |to note when each factory will make the change and who will “own” the |

| | |implementation. |

|21 |Follow Up and/or Monitor |List everything that must be done after the change is made. Include |

| |After Implementation |owners and due dates. This section is typically filled out to gather |

| | |additional information for future changes or to ensure that the |

| | |existing change worked out as planned. |

|22 |Supplemental Information |Place any additional or supporting information here. |

Additional key notes

All sections of the white paper need to be addressed. Do not delete sections of the white paper that do not apply to the change. If a particular section does not apply to the change, note it as "N/A" and explain why it doesn't apply.

Special considerations for section 8

Section 8 of a white paper deals with the scope of a change as it impacts the virtual factory. Descriptions and examples of each of the three types of changes are listed below.

|Type of change|Description |Example |

|Location |Implies change to a subset of the |P854 is run by Fabs A, B, and C. If the proposed |

|specific |factories for a particular process. |change is going to be made at only Fab B, then the |

| | |change is Location Specific for P854. On the other|

| | |hand, if the proposed change would be made at Fabs |

| | |A, B, and C, then it is not Location Specific. |

|New installs |Implies change to all new installations|P856 is run by Fabs D, E, and F. If the proposed |

| |at all of the factories running the |change will be implemented at Fabs D, E, and F for |

| |noted process. |all future installations, then the box P856/New |

| | |Installs would be checked. This column does not |

| | |address existing installations - see Retrofit |

| | |below. It should also be noted that if the New |

| | |Installs box is checked, this implies that a new |

| | |standard is being proposed - this will likely |

| | |affect the Master Package for equipment |

| | |installation WP’s or the Master Spec for utility |

| | |WP’s. |

|Retrofit |Implies change to existing |P854 is run by Fabs A, B, and C. If a change is |

| |installations at all of the factories |required on all existing installations at Fabs A, |

| |running the noted process, i.e., remove|B, and C, then the P854/Retrofit box would be |

| |the existing installation and replace |checked. |

| |it with the new installation. This | |

| |differs from the New Installs column in| |

| |that it only affects existing | |

| |installations and does not address new | |

| |installations | |

Section 8 flowchart

[pic]

4 White Paper Rejection

Common reasons for rejection

White papers are rejected for a variety of reasons. Sometimes the FCCB or FJET does agree with a particular change due to technical or strategic reasons. However, the majority of white papers are rejected because they are not written properly. A list of common reasons that white papers are rejected in the FCCB are listed below:

35. Wrong WP format

36. Missing key sponsors and/or review groups

37. Missing approval dates from review groups

38. Inadequate reason for change (reason not "compelling")

39. Stakeholders "agree to disagree" on CE! issues (not acceptable in most cases)

40. Inadequate or missing implementation plan

41. Additional impacts are not documented properly (cost, etc.)

42. Concerns/considerations are not fully documented

43. Qualification plan is missing or inadequate

44. Wrong revision of the white paper was submitted for review

45. Affected documents are not listed in the WP

46. Sponsors have not given any indication that they agree or disagree (no response is not ground for consent).

47. “Synergy” section not adequately addressed

48. “Recovery Plan If Approach Fails” section is not adequately addressed. (It is important to document what will be done if the proposed change does not work out as planned.)

Appendix 1: Environmental, Health, and Safety Issues

Safety guidelines

Some changes that are proposed to the FCCB involve environmental, health, or safety issues that may not directly impact the wafer process but are still important to consider. The additional impacts section of the FCCB white paper has line items which are meant to specifically address these issues. The following guidelines were extracted from the P854 PCCB Handbook to assist WP owners in identifying and addressing potential EHS issues. If in doubt about whether or not an FCCB change has an EHS impact, contact the FCT EHS group for assistance.

|Impacts |Examples |

|Environmental |Changes in quantities of production material or water use |

| |A chemical substitution or change |

| |Change in the quantity or way a production material or waste is disposed |

| |of, drained or exhausted from a process or preventive maintenance. |

|Safety/Health |Ergonomics: change location or position of controls and other areas |

| |requiring employee interface |

| |Change after safety engineering approval of equipment or install |

| |Change to the way a production material is stored, handled, or delivered |

| |Changes involving lasers, radiation, RF, UV, electric power or other |

| |hazardous energies |

| |Change in exhaust ventilation |

| |Changes to PM methods, safety controls, or protective equipment |

| |Change to a more combustible construction material |

| |Change to a method of heating a process material |

The potential impacts of any safety change needs review by site or FCT EHS representation site safety or the safety JET.

Appendix 2: FCCB Facility Systems Definitions

[pic]

Appendix 3: FCCB/ACCB Interrelationships

ACCB?

The ACCB is the Automation Change Control Board. It controls changes to software and hardware in much the same manner as the FCCB. Occasionally facilities or equipment changes interact with elements controlled by the ACCB. A few examples are listed below. When this occurs, approval from the ACCB is also required before the change can move forward.

49. Automated Material Handling System (AMHS) components:

11. Lot box and reticle stockers

12. Lot box openers

13. Overhead rails

14. Diffusion/Litho interbay rails

50. Computer room components and systems

15. VAX computers/systems

16. NCR computers/systems

51. X-terminals in the cleanroom

52. Station controllers in the cleanroom

53. Uninterruptable Power Supplies (UPSs) associated with any items listed above.

-----------------------

Description: FCCB White Paper Handbook and Student Guide

Course Title: Writing FCCB White Papers

Course Code: PTD007692

Revision Date: 05/10/99

Revision No.: 7

Item No.: 07692A

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download