Intel Supplier IAO Transformation
Welcome to the Intel Supplier IAO Transformation Site
Intel is undertaking a systems transformation. Systems and processes are being transformed to improve ease of doing business and streamline our supply chain. At this site, you will find helpful information to facilitate the transition.
General Timeline
Impacted Intel suppliers began receiving information as of Q3 2025. This transformation will be rolled out in several releases. Suppliers will receive specific messages from Intel throughout the transformation with actions and instructions as needed.
Please direct all questions to: supplier.iao.transformation@intel.com
Frequently Asked Questions
View the full PDF or choose from the topics below.
IAO Supplier Transformation
IAO stands for IDM 2.0 Acceleration Office, a program to accelerate Intel's IDM 2.0 strategy by transforming systems and processes to industry standards, improving business connectivity across Supply, Demand, Accounting, and Inventory Management.
The Intel ERP change is companywide covering planning, order management, inventory, and procurement functions. Each business supply chain (ex: outsource manufacturing, assembly test, capital) has varying amounts of change from minor to significant changes requiring IT development. Individual suppliers are expected to engage with the Intel team to understand their specific impacts and commit to supporting Intel’s transformation. Watch for emails from Intel and/or E2Open regarding details of the change.
Benefits include:
- Fewer out-of-cycle schedule change requests
- Standardized procurement models
- Increased use of industry standards
- Process efficiency and supply chain optimization
For specific suppliers, yes. Refer to faq #2.
No, SIRFIS will continue as the Supplier Collaboration application / interface for Capital Equipment.
Next Steps and Commitment Timelines for the Supplier
- Read the Welcome Email from Intel and/or e2open.
- Review the content and identity if there are changes required to your supplier ERP systems to support the defined business process and technical changes. If the changes are only to create supplier users account on the e2open portal, this is considered no IT system changes and categorized as a user account onboarding activity only.
- Provide commitment to the IAO program timeline and confirm your understanding of the changes by clarifying if there are IT/ERP systems changes.
Defined in the email received from Intel and/or e2open. Commitment dates vary based on the business supply chain involved and a supplier’s engagement with Intel.
Defined in the email received from Intel and/or e2open. Commitment dates vary based on the business supply chain involved and a supplier’s engagement with Intel.
As early as Q3 2026.
As early as Q4 2026.
Required details include:
- First Name
- Last Name
- Job Title
- Phone Number
- Email Address
Yes, multiple end users can be assigned to ensure all stakeholders are engaged.
Capital Equipment Procurement Processes
This program does not impact Capital Equipment POs. SIRFIS will continue as the Supplier Collaboration application / interface for Capital Equipment. Service fees will be processed through Ariba PO.
No change to SIRFIS related processes.
No change to SIRFIS related processes.
No change to CSI (4200) process.
No change to Intel Payment Tracker on the Intel Supplier Portal. Invoicing will not flow through e2open SCP Portal. Pay-Upon-Consumption Settlement will shift from SIMI Reconciliation to SAP Consignment Settlement.
Yes, invoicing on B2B will continue to work.
Yes, Intel Supplier Web will remain unchanged. For suppliers that did not onboard to e2open to execute business processes, they will continue to use Intel supplier hub.
Intel Supplier hub with the same login credentials supplier users currently use will continue.
Any minor change to applications like WebPO will be communicated in Q1 ‘26.
Capital POs and invoicing continues with the current Intel Supplier Hub.
Yes. If this B2B is currently on OpenText, RosettaNet PIPs, or EDI Standard, (depending on the PO type, for Capital 4200 PO, Ariba 350 PO), those will continue to stay on the B2B PIPs. Spares 700 POs will be transmitted via e2open with the new integration development, testing, and Go Live as a key piece of the supplier engagement program. Suppliers looking for M2M connections with Intel should discuss this with your Intel account manager for consideration and prioritization post IAO program completion.
e2open Supply Collaboration Portal (SCP) Expected Changes
SCP facilitates real-time collaboration between Buyer and Suppliers, enabling:
- PO responses
- ASN creation
- Warranty claims management
- Alerts on PO, ASN, and Warranty records
Yes, the e2open IAO Onboarding Team will conduct training events. You will receive recordings, a user manual, FAQ document, and micro videos.
For ITC and UAT, you will receive an email invitation with a test account. For production, registration is required via invitation from e2open.
Only registered users can access the e2open portal. Supplier end users receive registration/login details as part of the onboarding process. Supplier end users will generate their own username and password using the invitation link and use the credentials to log in to the portal.
No, each registration is linked to the email address used for the invitation. It is critical that users and appropriate contact information be provided when requested in Q2 ’26 for a smooth and efficient onboarding process.
Supplier end users are e2open managed users.
Currently two-factor authentication (2FA) is not enabled for e2open SCP. e2open will send an invitation link to suppliers to log in to the SCP application. Supplier end users will generate their own username and password using the invitation link and use the credentials to log in to the portal.
You will need to apply via Intel Supplier Portal. Once the application is received, an invitation will be sent. Detailed steps will be provided through email in Q3/Q4’26.
Intel Supplier Portal and e2open are two different portals. You do not need to reapply for access to the Intel Supplier Portal. This will remain and is where all suppliers will manage their invoice and payment processes, no changes because of IAO program.
For e2open access, you must submit a request through Intel Supplier Portal. However, this only initiates approval for setting accounts and access for e2open directly.
If you already have an existing e2Open account, you may use that account. If you cannot login with the existing e2open account, in Q3/Q4 2026, the e2open onboarding team will work with you to reactivate your account. Please send an email to e2open.iao_onboarding@wisetechglobal.com with the email address that was used to access e2open.
Yes. There is no specific app that may be used. Users can login and access e2o on a phone using a mobile browser.
Each end user will have a unique account in e2open.
Each end user will need to login with a unique username and password that they create.
Parent Accounts can be used to consolidate different Vendor Numbers. in e2open. Parent Accounts are created by e2open and access to the Parent Account can be granted by e2open as required.
Check your spam/junk folder for emails from doNotReply@e2open.com. If not received, contact e2open.iao_onboarding@wisetechglobal.com.
Email the e2open IAO Onboarding Team at e2open.iao_onboarding@wisetechglobal.com, including your company name in the subject line.
Templates include:
- PO Commit
- Shipping Notice
- VMI Shipping Notice
- Warranty Claim Response
Yes, tasks can be done directly on the application, with options for bulk actions.
Use templates for bulk actions. UI-based actions allow direct interaction, while Excel templates enable offline work and reuploading.
Yes. Emails can be filtered by module (e.g., PO-related alerts) and end users can select a filter to subscribe to specific alerts.
Go Live dates vary based on the business supply chain involved and a supplier’s engagement with various Intel’s sites around the globe. The first Go Live date is in Q2 2027 with subsequent releases around the globe happening in Q4 2027 and Q1 2028. Engage the supplier onboarding teams if questions on Go Live dates remain.
Some suppliers will experience multiple releases from Q2 2027 through Q1 2028. This is referred to as a straddle. Because the straddle impacts are situational and may affect suppliers in unique ways, the team will collaborate directly with identified suppliers to assess straddle impacts and requirements.
If you currently use SIMI, during the straddle period, you need to use E2Open and SIMI simultaneously until the full transition happens.
This question is specifically targeted at the Spares and Factory Indirect Materials supply chain processes. Yes, expedites become POs, SIMI and WIINGS applications will be retired.
ASNs will be uploaded by sellers/shippers in e2open for PO lines. ASNs are now required for WHs to receive materials. SANs (Shipment Acknowledgement Numbers from WIINGS) will no longer be needed.
Expedite ZEXP PO will be created for Machine Down Wait Part (MDWP). Standard NB PO will be created for expedite part request with Request Date that matches the need date of the maintenance activity.
ePart or Expedite will be part of a new PO process. ePart POs will have a new PO number series allowing them to be easily identified. SIMI will retire.
Expedite will have a PO series and ZEXP to highlight the variations and urgency of the POs. These will be visible on the e2open SCP Dashboard and Exceptions pages. e2open email filtering can be used to receive notifications on new expedite requests.
Intel buyers will work with suppliers for order changes.
Suppliers currently interacting with Intel using M2M (Machine to Machine) messaging are targeted to continue. New requests for M2M integration will not be entertained until after the IAO program is completely deployed.
Specifically, for Spares and Fab/AT indirect material suppliers there is a period between Release 3 (Q2 2027) and Release 5 (Q1 2028) when transaction will need to be completed H2M (Human to Machine). This is necessary because we cannot send the same PO, ASN, etc. messages with as-is content AND to-be content at the same time.
WIINGS will be replaced by SAP architecture. SIMI will be retired, and supplier collaboration will be transitioned to e2open.
Most likely not, but it will be taken up as part of the cutover planning in 2026.
There's conversion activity that will be executed with the program Go Live in which existing POs will be closed and new POs will be opened and transmitted via e2open. In addition, PO history will remain available at supplier.intel.com.
Current reports are being revamped and will be shared later.
Impacted purchase orders will be the 700xx spares POs. There are no e2open changes planned for series 4200 PO’s.
Inventory Report with ROP and Min/Max data will be transmitted to suppliers via e2open for the Pay upon Consumption method.
View the full PDF for a visual sample.
Note: Clicking the ’Current alerts list’ link in the email will take you to the e2open SCP application, where you can view the exception records and download them using the ’Download’ button on the page.
As part of the first phase of implementation, there will only be Human-to-Machine (H2M) method available. Suppliers designated to move back to M2M will receive functional spec in Q4 ’26 with Go Live expected inQ1 ’28.
View the full PDF for a visual sample.
During the IAO release straddle, for sites that are yet to be on new processes, current processes like SIMI and B2B will continue to work.
Beginning in Q2 of 2027:
- Ronler Acres, Aloha, Chandler sites, Suppliers will collaborate with Intel via e2open H2M.
- For the remainder of sites, SIMI and existing B2B transmission will continue to work.
View the full PDF for a visual sample.
Access to the e2open test environment will be provided in mid 2026.
They are stable; the frequency of changes should be minimal.
Mih will fully EOL with SAP S/4HANA implementation. All 3PL inventory reporting will pass from the Chem 3PL WMS, through OES4, into Intel’s SAP.
No, alerts are built to work the same way across all the suppliers who subscribe to it.
No, the filters, saved search, bookmarks, customized view (PSDs, page sections/ sequence of the fields) are all user specific. They cannot share with another user. Everyone will have to do these settings on their own.
No. For any changes needed in the order, please collaborate with the buyer.
Yes, it is possible.
There are no major changes planned for suppliers. Intel factory is responsible for declaring contamination and completing an eCUDL (Chemicals Used Decontamination Label) form for any item being sent out for repair. Before shipment, Intel EHS (Environmental Health and Safety) either signs off on the eCUDL form or sets up a Hazardous Profile, ensuring everything is properly validated. The completed eCUDL form will travel with the item as it moves to the suppliers’ repair center.
In support of Intel’s IAO deployment objectives, e2open has granted temporary authorization for Intel partners to use automation scripts (including RPA tools) on the e2open collaboration platform. This is a temporary measure to facilitate the Human-to-Machine (H2M) transition while a comprehensive Machine-to-Machine (M2M) solution is being implemented.
Conditions for automation script usage:
- E2open will not provide implementation guidance, technical support, or testing assistance for Intel partner-developed automation solutions.
- Usage will be monitored, and e2open reserves the right to restrict or revoke access if usage volumes exceed expectations or impact platform performance.
- Intel partners are responsible for their own script setup, management, and limitations.
- Platform changes in the future may disrupt script operations. E2open will not address resulting issues.
- Credentials must not be stored in plain text within scripts, and e2open assumes no responsibility for security risks from non-compliance.
- Authorization expires 12 months from platform go-live; any continued use will require re-evaluation and written reauthorization.
PO Response Using E2open SCP
The impacted PO types start with 700xx and SIMI orders, which will be retired and replaced by new PO types below that will be transmitted via E2open.
To view the table, please view the full PDF.
Confirming a purchase order is the best practice.
You will get an email notification (no PDF attachment) whenever a new PO is released. You can subscribe to email alerts in the e2open SCP application.
Blanket PO will remain for bulk chemicals/gases procurement only.
Attaching documents or files is not possible. When committing to a PO notes may be added.
Yes, splitting PO promises or commitments at the line level is allowed.
Yes, the PO can be exported in PDF format.
The terms and conditions are part of the PO view, and you are implicitly accepting them while committing your delivery i.e., you do not need to click somewhere else.
Webinars are recorded, and they are shared with all the attendees. Suppliers can forward the recording to others who handle POs in their company. In the first half of 2026, E2open will share a test account and provide access to its testing environment, allowing suppliers to explore the functionalities demonstrated. Send the contact details of the person responsible for handling POs in the company to e2open.iao_onboarding@wisetechglobal.com to receive future communications from the E2open onboarding team.
Accepting a purchase order is the best practice.
If the required date on a PO changes, exception or email alerts will be triggered and reflected on the E2open dashboard. If an acceptance and ASN already exist, the acceptance will be voided, and you must re-accept the PO for the remaining quantity. The ASN remains unchanged for previously shipped items.
Yes, take that PO discussion offline with the buyer to update the PO.
Promise date is the promised delivery date for the PO line item.
There is no difference. PO created in S/4HANA will flow to e2open.
Yes, look at Plant and Receiving site.
When downloading PO records and committing changes:
- Accepting a PO (with or without changes) immediately updates its state to Accepted or Accepted with Changes.
- Overlaps after 15 minutes do not affect the PO again.
- During downloading, you must choose records in New state; POs already accepted cannot be downloaded or re-accepted.
No, there is no indicator to show this in e2open.
For items managed by Intel resources on consignment (Procured via MRP), standard PO with NB code will be used. For items managed by VMI suppliers on consignment, VMI PO with ZVMI code will be used.
VMI Collaboration Using E2open SCP
No change to the frequency of consigns payment. Engage commercial point of contact for Consignment Settlement frequency changes.
The Recon process is transitioning to PO based payment. This will follow the OEM VMI Planning & Procurement (Pay Upon Consumption) model.
Pay Upon Consumption model will default to follow existing recon cadence. Engage commercial point of contact for Consignment Settlement frequency changes. Verification of unsettled transactions before invoice creation remains part of process (same as today).
VMI inventory report is the new output and can be viewed and downloaded from e2open SCP. Intel will generate the invoice based on the items / quantities consumed. List of transactions(consumptions) that are settled / not settled can be viewed / shared.
Yes, all stock reports will be available through the e2open SCP Portal.
ASN (non-VMI / VMI) Creation Using E2open SCP
A shipment signal (ASN) should be sent when a shipment leaves the supplier dock indicating a shipment is on the way and expected to arrive on a specific date.
Intel Warehouse will not receive shipment if an ASN is not submitted. ASN is a key piece of data needed to give Intel the ability to put together a forward-looking Supply / Demand analysis.
Refer to the ASN template shared in https://knowledge.e2open.com/knowledgecenter/intel/wp-content/uploads/sites/19/2025/09/ASN-for-non-VMI-POs.xlsx.
No, the only difference is how the data is entered into e2open SCP. If it is a bulk upload, then you can use the Excel template. If it is one ASN at a time, you can use the data entry in the portal.
For non-VMI ASN, edit capability is not allowed in e2open SCP once submitted. User will need to cancel the ASN and resubmit. VMI ASN can be edited or cancelled.
Yes.
ASN must be uploaded/submitted in e2open to allow Intel to receive the shipment.
All ASN details must be entered directly into e2open following the H2M process starting in Q2 2027. Intel will start to transition some suppliers to e2open M2M in Q2 of 2028.
- This is only for the impacted 700 series PO type and SIMI order. For POs that are outside of this scope, the existing processes will continue.
All good receipts for inventory POs must be delivered to the WH. If a GR is not recorded in the warehouse, then inventory is not updated creating an error in our supply chain processes potentially both inventory, invoicing, and payment processes.
Yes, Suppliers will receive a response against VMI shipment whether a purchase order was created successfully.
Intel requires suppliers to create ASN on the e2open portal. Suppliers could create ASN to a 3rd-party warehouse if suppliers choose to.
It depends on your procurement model. For Pay Upon Receipt model, inventory receipts will be settled against an applicable PO. Suppliers are required to submit invoices via Intel Supplier Portal WebInvoice. For Pay Upon Consumption model, SAP’s standard “Consignment Settlement” process will be used to periodically settle all movements from Supplier Consigned inventory to Intel.
It can be created as soon as a new PO is published, however it is recommended you commit to the PO first.
You should be able to ship against multiple POs in an ASN if the receiving site is the same.
Cross site transfers are not in e2open scope. Cross site transfers will be facilitated in SAP S/4HANA.
- Expedite: Buyer can convert expedited PR to STR (Stock Transfer Request) if inventory is available on another site. STR is converted to STO (Stock Transfer Order)
- Regular (non-priority) Cross site transfers: STO will be created manually as needed.
Carriers will not be turned away however ASN are to be submitted to allow the process to function effectively.
Shipment Tracking ID is a mandatory field with values that can be entered HAWB/BOL/HBL or Carrier Order number.
Warranty Claim Response Using e2open SCP
At claim creation, S/4HANA will automatically use the contracted entity’s warranty start and end dates to populate
the claim. There will be reminder alert emails for open warranty claims.
Yes, warranty repair is done through the warranty claims process.
Yes, if they have access to the portal.