Common use of Oracle Clause in Contracts

Oracle. Oracle MRP system is used in Company HRD organization for management of forecast, net requirement calculations, item master maintenance, inventory management and customer order management and fulfillment. In the interest of robust and timely information sharing with Jabil, it is expected that both Companies will go through the level of work required to enable automated transactions between Oracle and SAP. Jabil is expected to support this work through ensuring that Jabil resources are available according to the agreed upon project timeline, at Jabil’s expense. It is envisioned that enabling limited set of EDI transactions will be necessary threshold requirement in order to successfully complete the Production Start. It is expected that Jabil’s resources will be available on an ongoing basis to support ongoing continuous improvement efforts past Production Start, such as expanded set of EDI transactions, CIS access, to name a few, at Jabil’s expense. Database change management. The important objective of the [*] project is to track any and all changes to the files (electrical or mechanical), tools, fixtures, parts, quality specifications or manufacturing processes. To facilitate meeting this objective, Company has developed ECR/ECN process and adopted a database management tool, Windchill. It is necessary that Jabil also acquire working Windchill knowledge, and adopt Company’s ECR/ECN process. Windchill as a tool supports this system very well. Company will communicate ECR/ECN process to Jabil through Company documents, and Jabil is expected to understand the process and be prepared to participate in it and use it for any and all changes to controlled activities, such as: changes to the files (electrical or mechanical), tools, fixtures, parts or manufacturing processes. There are many activities and responsibilities under XX XX change process. Company will assume most of them. Jabil will be expected to understand overall process, and know how to initiate change through problem report, and then know how to view change after it has been routed through the system. This particular aspect of collaboration will also be practiced by Jabil and Company through scripted and controlled data exchange through Windchill. Jabil is expected to ask permission for any and all changes to database, to include both engineering and quality related documentation and processes. All Jabil input is encouraged but it must be reviewed and approved by Company before it takes effect. Jabil will utilize variety of resources outside of [*] and core [*] team dedicated to Company account, such as tooling/molding resources. It is expected that Jabil will manage all its external relationships, and it is Jabil’s responsibility to ensure that all parties acting on Company’s account on Jabil’s behalf utilize the latest released instance of the database. Failure to do so (resulting in production of outdated parts, or incorrect fixtures, etc.) will be Jabil’s responsibility and Jabil will correct any errors that may arise at their own expense and within acceptable timelines. It is expected that Jabil’s resources will be available on an ongoing basis to support continuous improvement efforts past Production Start, such as active participation in ECR/ECN process through proposing changes through Windchill, redlining documents and models, and in some instances even performing edits directly in a database. The augmented participation will be discussed with Jabil well in advance of expected implementation. Jabil shall maintain its hardware and software setups in support of Company’s business under this Agreement to ensure compatibility with Company’s future system upgrades. Company shall use Commercially Reasonable Efforts to notify Jabil in advance of any system upgrades applicable to the Products under this Agreement. SCHEDULE 2 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] SCHEDULE 3 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] SCHEDULE 4 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY MUTUAL NON‑DISCLOSURE AGREEMENT This MUTUAL NON‑DISCLOSURE AGREEMENT (this “Agreement”), effective as of the date set forth last below, is made by and between the undersigned counter party (the “Counter Party”) and iROBOT CORPORATION (“iROBOT”). In consideration of the mutual agreements and other provisions of this Agreement, the parties hereto agree as follows:

Oracle. Oracle MRP system is used in Company HRD organization for management of forecast, net requirement calculations, item master maintenance, inventory management and customer order management and fulfillment. In the interest of robust and timely information sharing with Jabil, it is expected that both Companies will go through the level of work required to enable automated transactions between Oracle and SAP. Jabil is expected to support this work through ensuring that Jabil resources are available according to the agreed upon project timeline, at Jabil’s expense. It is envisioned that enabling limited set of EDI transactions will be necessary threshold requirement in order to successfully complete the Production Start. It is expected that Jabil’s resources will be available on an ongoing basis to support ongoing continuous improvement efforts past Production Start, such as expanded set of EDI transactions, CIS access, to name a few, at Jabil’s expense. Database change management. The important objective of the [*] project is to track any and all changes to the files (electrical or mechanical), tools, fixtures, parts, quality specifications or manufacturing processes. To facilitate meeting this objective, Company has developed ECR/ECN process and adopted a database management tool, Windchill. It is necessary that Jabil also acquire working Windchill knowledge, and adopt Company’s ECR/ECN process. Windchill as a tool supports this system very well. Company will communicate ECR/ECN process to Jabil through Company documents, and Jabil is expected to understand the process and be prepared to participate in it and use it for any and all changes to controlled activities, such as: changes to the files (electrical or mechanical), tools, fixtures, parts or manufacturing processes. There are many activities and responsibilities under XX XX change process. Company will assume most of them. Jabil will be expected to understand overall process, and know how to initiate change through problem report, and then know how to view change after it has been routed through the system. This particular aspect of collaboration will also be practiced by Jabil and Company through scripted and controlled data exchange through Windchill. Jabil is expected to ask permission for any and all changes to database, to include both engineering and quality related documentation and processes. All Jabil input is encouraged but it must be reviewed and approved by Company before it takes effect. Jabil will utilize variety of resources outside of [*] and core [*] team dedicated to Company account, such as tooling/molding resources. It is expected that Jabil will manage all its external relationships, and it is Jabil’s responsibility to ensure that all parties acting on Company’s account on Jabil’s behalf utilize the latest released instance of the database. Failure to do so (resulting in production of outdated parts, or incorrect fixtures, etc.) will be Jabil’s responsibility and Jabil will correct any errors that may arise at their own expense and within acceptable timelines. It is expected that Jabil’s resources will be available on an ongoing basis to support continuous improvement efforts past Production Start, such as active participation in Portions of this Exhibit were omitted and have been filed separately with the Secretary of the Commission pursuant to the Company’s application requesting confidential treatment under Rule 24b-2 of the Exchange Act — [*] denotes omissions. ECR/ECN process through proposing changes through Windchill, redlining documents and models, and in some instances even performing edits directly in a database. The augmented participation will be discussed with Jabil well in advance of expected implementation. Jabil shall maintain its hardware and software setups in support of Company’s business under this Agreement to ensure compatibility with Company’s future system upgrades. Company shall use Commercially Reasonable Efforts to notify Jabil in advance of any system upgrades applicable to the Products under this Agreement. Portions of this Exhibit were omitted and have been filed separately with the Secretary of the Commission pursuant to the Company’s application requesting confidential treatment under Rule 24b-2 of the Exchange Act — [*] denotes omissions. SCHEDULE 2 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] Portions of this Exhibit were omitted and have been filed separately with the Secretary of the Commission pursuant to the Company’s application requesting confidential treatment under Rule 24b-2 of the Exchange Act — [*] denotes omissions. SCHEDULE 3 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] SCHEDULE 4 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY MUTUAL NON‑DISCLOSURE AGREEMENT This MUTUAL NON‑DISCLOSURE AGREEMENT (Portions of this “Agreement”), effective as Exhibit were omitted and have been filed separately with the Secretary of the date set forth last below, is made by and between Commission pursuant to the undersigned counter party (the “Counter Party”) and iROBOT CORPORATION (“iROBOT”). In consideration Company’s application requesting confidential treatment under Rule 24b-2 of the mutual agreements and other provisions of this Agreement, the parties hereto agree as follows:Exchange Act — [*] denotes omissions.

Oracle. Oracle MRP system is used in Company HRD organization for management of forecast, net requirement calculations, item master maintenance, inventory management and customer order management and fulfillment. In the interest of robust and timely information sharing with Jabil, it is expected that both Companies will go through the level of work required to enable automated transactions between Oracle and SAP. Jabil is expected to support this work through ensuring that Jabil resources are available according to the agreed upon project timeline, at Jabil’s expense. It is envisioned that enabling limited set of EDI transactions will be necessary threshold requirement in order to successfully complete the Production Start. It is expected that Jabil’s resources will be available on an ongoing basis to support ongoing continuous improvement efforts past Production Start, such as expanded set of EDI transactions, CIS access, to name a few, at Jabil’s expense. Database change management. The important objective of the [*] project is to track any and all changes to the files (electrical or mechanical), tools, fixtures, parts, quality specifications or manufacturing processes. To facilitate meeting this objective, Company has developed ECR/ECN process and adopted a database management tool, Windchill. It is necessary that Jabil also acquire working Windchill knowledge, and adopt Company’s ECR/ECN process. Windchill as a tool supports this system very well. Company will communicate ECR/ECN process to Jabil through Company documents, and Jabil is expected to understand the process and be prepared to participate in it and use it for any and all changes to controlled activities, such as: changes to the files (electrical or mechanical), tools, fixtures, parts or manufacturing processes. There are many activities and responsibilities under XX XX change process. Company will assume most of them. Jabil will be expected to understand overall process, and know how to initiate change through problem report, and then know how to view change after it has been routed through the system. This particular aspect of collaboration will also be practiced by Jabil and Company through scripted and controlled data exchange through Windchill. Jabil is expected to ask permission for any and all changes to database, to include both engineering and quality related documentation and processes. All Jabil input is encouraged but it must be reviewed and approved by Company before it takes effect. Jabil will utilize variety of resources outside of [*] and core [*] team dedicated to Company account, such as tooling/molding resources. It is expected that Jabil will manage all its external relationships, and it is Jabil’s responsibility to ensure that all parties acting on Company’s account on Jabil’s behalf utilize the latest released instance of the database. Failure to do so (resulting in production of outdated parts, or incorrect fixtures, etc.) will be Jabil’s responsibility and Jabil will correct any errors that may arise at their own expense and within acceptable timelines. It is expected that Jabil’s resources will be available on an ongoing basis to support continuous improvement efforts past Production Start, such as active participation in ECR/ECN process through proposing changes through Windchill, redlining documents and models, and in some instances even performing edits directly in a database. The augmented participation will be discussed with Jabil well in advance of expected implementation. Jabil shall maintain its hardware and software setups in support of Company’s business under this Agreement to ensure compatibility with Company’s future system upgrades. Company shall use Commercially Reasonable Efforts to notify Jabil in advance of any system upgrades applicable to the Products under this Agreement. SCHEDULE 2 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] SCHEDULE 3 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] SCHEDULE 4 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY MUTUAL NON‑DISCLOSURE NON-DISCLOSURE AGREEMENT This MUTUAL NON‑DISCLOSURE NON-DISCLOSURE AGREEMENT (this “Agreement”), effective as of the date set forth last below, is made by and between the undersigned counter party (the “Counter Party”) and iROBOT CORPORATION (“iROBOT”). In consideration of the mutual agreements and other provisions of this Agreement, the parties hereto agree as follows:

Oracle. Oracle MRP system is used in Company HRD organization for management of forecast, net requirement calculations, item master maintenance, inventory management and customer order management and fulfillment. In the interest of robust and timely information sharing with Jabil, it is expected that both Companies will go through the level of work required to enable automated transactions between Oracle and SAP. Jabil is expected to support this work through ensuring that Jabil resources are available according to the agreed upon project timeline, at Jabil’s expense. It is envisioned that enabling limited set of EDI transactions will be necessary threshold requirement in order to successfully complete the Production Start. It is expected that Jabil’s resources will be available on an ongoing basis to support ongoing continuous improvement efforts past Production Start, such as expanded set of EDI transactions, CIS access, to name a few, at Jabil’s expense. Database change management. The important objective of the [*] project is to track any and all changes to the files (electrical or mechanical), tools, fixtures, parts, quality specifications or manufacturing processes. To facilitate meeting this objective, Company has developed ECR/ECN process and adopted a database management tool, Windchill. It is necessary that Jabil also acquire working Windchill knowledge, and adopt Company’s ECR/ECN process. Windchill as a tool supports this system very well. Company will communicate ECR/ECN process to Jabil through Company documents, and Jabil is expected to understand the process and be prepared to participate in it and use it for any and all changes to controlled activities, such as: changes to the files (electrical or mechanical), tools, fixtures, parts or manufacturing processes. There are many activities and responsibilities under XX XX change process. Company will assume most of them. Jabil will be expected to understand overall process, and know how to initiate change through problem report, and then know how to view change after it has been routed through the system. This particular aspect of collaboration will also be practiced by Jabil and Company through scripted and controlled data exchange through Windchill. Jabil is expected to ask permission for any and all changes to database, to include both engineering and quality related documentation and processes. All Jabil input is encouraged but it must be reviewed and approved by Company before it takes effect. Jabil will utilize variety of resources outside of [*] and core [*] team dedicated to Company account, such as tooling/molding resources. It is expected that Jabil will manage all its external relationships, and it is Jabil’s responsibility to ensure that all parties acting on Company’s account on Jabil’s behalf utilize the latest released instance of the database. Failure to do so (resulting in production of outdated parts, or incorrect fixtures, etc.) will be Jabil’s responsibility and Jabil will correct any errors that may arise at their own expense and within acceptable timelines. It is expected that Jabil’s resources will be available on an ongoing basis to support continuous improvement efforts past Production Start, such as active participation in Portions of this Exhibit were omitted and have been filed separately with the Secretary of the Commission pursuant to the Company’s application requesting confidential treatment under Rule 24b-2 of the Exchange Act — [*] denotes omissions. ECR/ECN process through proposing changes through Windchill, redlining documents and models, and in some instances even performing edits directly in a database. The augmented participation will be discussed with Jabil well in advance of expected implementation. Jabil shall maintain its hardware and software setups in support of Company’s business under this Agreement to ensure compatibility with Company’s future system upgrades. Company shall use Commercially Reasonable Efforts to notify Jabil in advance of any system upgrades applicable to the Products under this Agreement. Portions of this Exhibit were omitted and have been filed separately with the Secretary of the Commission pursuant to the Company’s application requesting confidential treatment under Rule 24b-2 of the Exchange Act — [*] denotes omissions. SCHEDULE 2 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY [*] SCHEDULE 3 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY Portions of this Exhibit were omitted and have been filed separately with the Secretary of the Commission pursuant to the Company’s application requesting confidential treatment under Rule 24b-2 of the Exchange Act — [*] SCHEDULE 4 TO MANUFACTURING SERVICES AGREEMENT BETWEEN JABIL AND COMPANY MUTUAL NON‑DISCLOSURE AGREEMENT This MUTUAL NON‑DISCLOSURE AGREEMENT (this “Agreement”), effective as of the date set forth last below, is made by and between the undersigned counter party (the “Counter Party”) and iROBOT CORPORATION (“iROBOT”). In consideration of the mutual agreements and other provisions of this Agreement, the parties hereto agree as follows:denotes omissions.