TIS and Projects Export Control Self-Check
Equipment Modules – Multi-Carrier System 19.0.0
Object-Name / Description (Software Name, or Project Name or Product Name) Object Version
No.: Question Yes No
1. New Project and/or new Product
If Yes: New Project, or product then Project Checklist required
Explanation: For a new project with external Project partners and/or international setup. The
partners-check (DAMEX – E) must be carried out and the project must be checked in regard to
technology-transfer between the Development-Sites.
2. New cross boarder activities (e.g. Development) including transfer of
items?
If Yes: TIS-Checklist is required
Explanation: If there are new cross boarder activities within the development, a new TIS-check
must be carried out to ensure the fulfillment of all applicable internal, national and international
export control regulations.
3. New Partners within the Project, or new single activity/functionality
added?
If Yes: New TIS-Check (TIS-Checklist) required
If new partner updated project check required, too
Explanation: For new Partners a new DAMEX - E check is necessary.
If applicable new checks regarding Technology transfer is required.
If there is new US-involvement (US-Citizen, Greencard-Holder, US-Company, Development site in
US) within the project. This involvement must be considered in a new De minimis-calculation for
the product, the same Is true for new US-Components (HW and/or SW) used within the project /
product.
4. Refactoring – Were new components added or has the technological
base (e.g., other cloud platform) changed?
If Yes: New TIS-Check (TIS-Checklist) required, and / or
If Yes for HW (also incl. FW): A new classification (AL; ECCN) is
required. Therefore, the updated BoM is required.
Explanation: Change of product without of changes regarding the characteristic, which means
purpose/extent of the product is not (or just marginally), but there were changes carried out, which
are necessary for the implementation of certain functionalities. These changes are not, or just
minimally noticeably for the user.
Siemens AG, Internal – Export Control Self Check, V1.4, 24.07.2024 - LC CO DI EX Page 1 of 4
TIS and Projects Export Control Self-Check
Equipment Modules – Multi-Carrier System 19.0.0
Object-Name / Description (Software Name, or Project Name or Product Name) Object Version
5. Product maintenance – Are there Changes/Updates, which represent
more than Bugfixes and Minor-Changes included?
If Yes: please answer question 5.1
If No: Please answer question 6
Explanation: Bugfixes and Minor-Changes do not change the characteristics, function and
components of a product as significantly as this would result in changes within the classification.
5.1 Were new functionalities added/or existing functionalities
modified which change the basic characteristics of the existing
product?
If Yes: New TIS-Check (TIS-Checklist) required, and / or
If Yes for HW (also incl. FW): A new classification (AL;
ECCN) is required. Therefore, the updated BoM is
required.
Explanation: Changes of product by addition of new functionalities, which possibly also
change the purpose/extent of the product (in contrast to 4. Refactoring). E.g. changes are
noticeably for the user, or changes on the architecture, which is possibly not, or just
minimally noticeably.
6. Added/changed Crypto-functionalities?
If Yes for : New TIS-Check (TIS-Checklist) required, and / or
If Yes for HW (also incl. FW): A new classification (AL; ECCN) is
required. Therefore, the updated BoM is required.
Explanation: Crypto-functionalities are listed in the EC Dual-Use REG as well as in the
Commerce Control List. So an addition or the change of crypto functionalities has to be checked.
Siemens AG, Internal – Export Control Self Check, V1.4, 24.07.2024 - LC CO DI EX Page 2 of 4
TIS and Projects Export Control Self-Check
Equipment Modules – Multi-Carrier System 19.0.0
Object-Name / Description (Software Name, or Project Name or Product Name) Object Version
No.: Remarks / Documentation to Questions
1. This is not a new project / product, but a new version (18.0.0) of already existing Equipment
Module – Converting Toolbox
2. There are no new cross border activities. The whole development team is located in Erlangen,
Germany, as well as the system test which is now part of the development team.
3. There are no new partners within the project, comparing to the previous version.
4. There are no significant changes to the product in the context of the explications of the
question number 4.
5. Yes, there are changes that represent more than just bug fixes.
5.1 No, the abovementioned changes do not change the basic characteristics of the
existing product.
6. No added crypto functionalities.
Applicant EX Business Partner (optional)
Stalevski Digitally signed by
Stalevski Darko
Darko Date: 2024.11.28
[Link] +01'00'
Nov 28th 2024, Darko Stalevski ,
Date, Signature Date, Signature
Siemens AG, Internal – Export Control Self Check, V1.4, 24.07.2024 - LC CO DI EX Page 3 of 4
TIS and Projects Export Control Self-Check
Equipment Modules – Multi-Carrier System 19.0.0
Object-Name / Description (Software Name, or Project Name or Product Name) Object Version
Link to TIS-Check List:
[Link]
Link to Project Check List*:
[Link]
Link to DAMEX-E:
[Link]
Link to Overview of LC CO Organization:
[Link]
Definition of:
“Software” is defined for export control purposes as a collection of one or more “programs” or
“microprograms” fixed in any tangible medium of expression, including Firmware.
Link: [Link]
Transfer-and-Technical-Assistance,What-is-controlled,Software
De Minimis: Calculation of US-Share contained in a component, product, software
Link: [Link]
Controls,De-Minimis-Rule
Link to Definition of TIS:
[Link]
*mandatory Partners Check (with DAMEX-E), identify and handle export of items.
Siemens AG, Internal – Export Control Self Check, V1.4, 24.07.2024 - LC CO DI EX Page 4 of 4
