Skip to main content

Design Activities Confirmation

DAC standards for Design Activities Confirmation. It’s a document that outlines a tool’s scope of work, enabling teams to effectively allocate resources to achieve project objectives. Below is a comprehensive list of Frequently Asked Questions (FAQs) related to creating a DAC in the FCELSPx application. Please review these questions and answers before consulting Basesite for support.

Access​

Can I access FCELSPx on my company's laptop?

Using INTEL and NON-Intel emails, you can now access the FCELSPx application outside the Intel Network. First time users can register their account by completing the Microsoft Authentication.


Application (LSPx)​

How do I create a new DAC in the LSPx application?

  • Log in to the LSPx application as a user from an AE Firm (Ideally will be created by the AE Firm assigned to the tool).
  • Click on the DAC icon on the from the Tool Install Schedule page.
  • Alternatively, navigate to the Tool Details page; click the DAC entry point and "Create New DAC". RP DACs are automatically created for Revisions after zero (0).
  • Complete the required fields in the DAC form, which dynamically adjusts based on the Project Type [TD or HVM] and Tool Event Type [Install, Demo or Convert in place].

Refer to the Training Videos for how to create, submit and complete DACs in the LSPx application.

I cannot create a DAC or see the entry point on the Tool Details page. Who can raise a DAC and who can they send it to?

Any AE Firm user can create the DAC in LSPx. The Tool Install Design Manager also has the permissions to create the DAC. Once created, it is sent to the Tool Owner / Area Coordinator for completion.

Check that you have the correct role in the system on the “My Profile” page. If your role is incorrect, you can assign yourself a correct low-level role and immediately get access.

Can I save a draft of the DAC form and return to it later?

Yes, with the correct permissions. You can save a draft of the DAC form by clicking the "Save Draft" button. At any time, only one (draft or completed) DAC can be saved per tool. You can return to your draft anytime to complete and submit it. If the AE Firm changes, the new company will see the existing saved draft from the previous company assigned to the tool.

What happens after I submit a DAC form?

Once created, the DAC form is sent to the Tool Owner and Area Coordinator associated with the tool for completion. They can update, save changes, and submit the form to the AE Firm for a review.

As a Tool Owner or Area Coordinator, how do I update a DAC form?

After receiving a DAC form, the questions that you see will depend on your Project Type [RP, TD, or HVM] and the Tool Event Type [Install, Demo or Convert in place] selected. You can change the Event Type if it is incorrect from the POR Schedule. Once your revisions are complete, you can save your progress or submit it for the AE Firm to review. Note that the Tool Event Type is irrelevant for the RP DAC.

What should I do if I the Tool Event Type displayed on the DAC form is different?

The Tool Event Type displayed is automatically retrieved from the POR Schedule. If incorrect, click on the “Different to POR Schedule” checkbox and change it appropriately. The DAC form adapts to include specific fields for different Tool Event Types. The Tool Event Type is not displayed for the RP DAC.

How do I know who the Tool Owners, Area Coordinators and AE Design Leads are on my project?

Every DAC displays the Tool Owners, Area Coordinators and AE Design Leads for the tool [if they are assigned correctly on the Stakeholders component]. If someone is missing on the tool, you can escalate to the AE Company Administrator or Design Managers on your project.

What if I have additional comments, questions or concerns above and beyond the list of Tool questions?

Users with access to the DAC can provide additional information in the comments section. Type the "@" symbol to tag someone and they will receive an email notification with your comments.

Can I notify other users that are not directly involved in the DAC?

You can include any active LSPx user on the site to view and receive notifications about the DAC. Simply search for their name under the "Watchers" field.

What can I expect to see in the email notifications?

The email notifications will core information about the tool. You will need to click on the "View DAC" button in the email to view details about the DAC notifications are sent out to the appropriate users with every change in the DAC status.

What does the "Return to Tool Owner" action imply?

If the AE Firm finds issues or requires clarification on the DAC, they can click "Return to Tool Owner," indicating that further revisions are needed. The Tool Owner/Area Coordinator must edit the form accordingly and resubmit it for review.

How is a DAC closed or reopened in the LSPx application?

A DAC is closed when the AE Firm finds it satisfactory and clicks "Review to Close" button. This action finalises the DAC, confirming the tool's scope of work. Once closed, it cannot be edited nor can comments or attachments be added. This signifies the completion of the design activities confirmation process for the specified tool. However, the AE Firm or Design Manager can reopen the DAC if required. An example of when this could happen is when the AE Firm assigned to the tool changes after the initial closure.

Is there a record of who made changes on the DAC?

Yes, once created, visit the DAC History tab under the Activity section of a DAC form

Who can cancel/delete a DAC?

Any user from an AE Firm can delete the DAC when it is in the "AE DRAFT" status.

The Tool Owner, Area Coordinator and Design Manager can delete a DAC once it has been sent.

If deleted, the DAC is removed from the system, and all relevant stakeholders will be notified. A deleted DAC cannot be reopened but must be recreated if needed.

Why are the questions on my DAC form different? How do I raise an issue with the workflow?

There is only one workflow for the DAC. However, the questions that has to be answered will depend on the Project Type [RP, TD, or HVM] and the Tool Event Type [Install, Demo or Convert in place] selected. The Tool Owner and Area Coordinators can change the Event Type if it is incorrect from the POR Schedule. Each combination of DAC Type and Tool Event Type has been tailored to meet specific requirements and objectives, resulting in different steps or information requirements in the workflow.

What happens to the RP DACs that were created before LSPx?

There is no plan to migrate RP DACs that were created before the feature introduction to LSPx. You can manually create the first RP DAC in LSPx for new revisions issued on or after the release date (March 5, 2025). All existing DAC revisions before this feature release are labelled with “NO DAC in LSPx” status. Once the first DAC is created, subsequent RP DACs will be automatically generated without manual intervention. For existing revisions that do not have a DAC before the release date, the first DAC created in LSPx will be considered the first and display the Tool Go-By field


Business Process​

What is the due date for returning the DAC?

The DAC Return Due Date is the day the DAC must be closed by. It varies between projects and is automatically set to x working days before the Pedestal Design Start or Tool Install Design Start Date. The earliest of the two dates is used for the calculation. Refer to the User Guides for the the appropriate durations for your project

Where can I find help or support for using the DAC feature in the LSPx application?

Review the Training materials and contact your Company Administrator for intial support. For feature/enhancements requests, please discuss it with your TI Design Manager for approval. For business process questions/concerns, reach out to DAC Trainers on your site. If it's a bug, you can raise a ticket within the application or contact the LSPx Support Team.

What is the difference between RP, TD and HVM?

RP and TD focus on innovation, developing new technologies, and optimising processes, necessitating a DAC form that emphasises design readiness for groundbreaking tools and technologies. The RP DAC is not needed before the TD DAC. In HVM, the emphasis shifts to mass production efficiency, scalability, and quality, requiring a DAC form that ensures designs are innovative but also practical and reliable for high-volume manufacturing. This differentiation ensures that the DAC effectively addresses the unique challenges and checkpoints relevant to each phase.

  • The Reference Package (RP) is a standardised baseline or template Copy Exactly IDs (CEIDs) developed based on previous tool installations or proven designs. It includes guidelines, specifications, safety standards, installation procedures, and other key technical details that are known to work well for a given tool or system.

  • Technology Development (TD) is a crucial stage for developing innovative fabrication methods, material utilisation, and process integration to facilitate the production of cutting-edge semiconductor tools. TD aims to advance semiconductor technologies' capabilities, focusing on enhancements in tool performance, cost reduction, and manufacturing efficiency.

  • High Volume Manufacturing (HVM) follows TD and is where the technologies developed are implemented to construct semiconductor tools on a large scale. The emphasis during HVM is on the scalability, quality consistency and efficiency of the production process. The objective is to ensure that the innovative technologies developed during TD can be mass-produced with consistent quality and high yield rates.

  • Intel's TD sites are Aloha, Chandler, Ronler Acres, and Santa Clara. The others are classed as HVM sites.

Who owns the 3D Blocks?

3D blocks are part of the Tool Install Central Engineering (TICE) scope of work. They are generally managed by one of the AE firms or a sub-contractor.


FCEConnect​

What happened to FCEConnect?

The FCEConnect application has now been sunset. All issue types (DAC, DCR, ROD, and SDD) have been migrated to the FCELSPx application in 2024.