Secured manufacturing as a service with the help of digital twin for modular and contract manufacturing scenario

Abstract

Method (100) for transferring a file for a 3D printing process from a manufacturer to a user, wherein the method (100) comprises identifying (S101) a product to be printed at a user's site using a software stack, in particular a secured Manufacturing as a Service, sMaaS, software stack; providing (S102) printing data (18) for printing said object with a 3D printer (4); encrypting (S103) the printing data (18) and generating a printing archive file (5) containing said printing data (18); generating (S104) a modified firmware (12) specific for a selected 3D printer (4) of the user, wherein the modified firmware (12) is contained in the printing archive file (5); providing (S105) the 3D printer (4) with the printing archive file (5), wherein the 3D printer (4) is off-line; and decrypting (S106) the printing data (18) of the printing archive file (5) and using the decrypted printing data (18) for starting the printing process, wherein the method (100) comprises deleting, at least in part, said printing data (18) of the printing archive file (5) once the printing process is completed.

Description

[0001] SECURED MANUFACTURING AS A SERVICE WITH THE HELP OF DIGITAL TWIN FOR MODULAR AND CONTRACT MANUFACTURING SCENARIO

[0002] The present invention relates to a method for transferring a file for a 3D printing process from a manufacturer to a user and to a corresponding system using said method. Also, the present invention relates to a computer program product comprising instructions to cause said to execute the steps of said method.

[0003] Transferring files between a trading partner and a customer can always involve at least some level of risk, especially for transferring files containing sensitive data. When dealing with additive manufacturing, or 3D printing, this issue becomes more important. As matter of fact, 3D printing is continuing to evolve and becoming more commonplace in the business world, so it leads to potential for cybersecurity risks.

[0004] Additive manufacturing poses several unique risks that could have negative consequences for manufacturing companies. Some of the common cybersecurity threats associated with additive manufacturing include a deliberate insertion of defects, which could cause the printed products to fail or malfunction. Another problem can be the intellectual property theft. Hackers can easily reverse engineer a product by scanning it and then recreate it using additive manufacturing. This is a huge issue for companies that have spent years and money developing their products and building up their brand.

[0005] Another serious concern involves data breaches. If a manufacturer’s design files are stolen or leaked, its competitors could gain an advantage. Additionally, the thieves could sell the designs on the black market or use them to produce and sell counterfeit products.

[0006] Additionally, for a quick market / segment entry, original equipment manufacturer may opt for contract manufacturing with a third party vendor. Furthermore, during projects, components details need to be shared with the partners for system integration and final assembly. Also, in the context of transferable digital assets, customers demand the finished product or the completed components of the manufacturer.

[0007] In all the above scenarios, data, information, and the (CAD) models are to be shared between manufacturer and customer. Therefore, control and security of these elements become the highest priority for the companies that want to provide information data on the 3D printing of their products. Further, the encryption of the digitally transferable assets or the Digital Twin is an additional aspect to be taken into account. In this context, the main technical challenges are the lack of trust between the designer / product owner and the manufacturer due to data security, copyright violation, breach of design data, as well as the lack of control over number / volume of production in a contract manufacturing scenario. Also, in varying demography of the world, local manufacturing needs change quickly and many approvals from government, OEMs and product development teams across the globe adhering to standards and regulations are required. Another important issue is the lack of secured transfer which has limited and restricted usage of 3D CAD data which remains in the usable format once the manufacturing process is completed.

[0008] Nowadays, the majority of the 3D CAD file exchange occur over email and cloud storage with password protected exchange. But still the 3D CAD data is in the useable format after the manufacturing process is completed. Few of the manufacturer / 3D printing service provider came up with web portals for uploading 3D CAD data and getting the price / quotation. But largely they are in the control of Web portal owners. In addition, most of these Trust & understanding are taken care by signing a Non-Disclosure Agreement and Memorandum of Understanding documents. However, in certain conditions and local jurisdictions these documents are ignored.

[0009] Several solutions are present in prior art facing this problems. For example, business models are known for secured decentralized manufacturing through digitally transferable asset. In particular, distributed manufacturing platforms are used with network-based file exchange, rapid printing based on user instructions and modern connected-logistics. Also, secured communication and data protocol for distributed additive manufacturing are known using HASH key generation, biometric authentication, blockchain and ledger keeping. In particular, ledger keeping, licensing and security encryption can be used for digital rights, licensing, storing 3D CAD data fragment wise, physically unclonable function (PUF) to a product, and generate a non- fungible token (NFT).

[0010] However, all the known solutions fail to address the following problems: i. The user does not have the details and status about the 3D CAD data once manufacturing is completed; ii. Accessibility of 3D CAD data or manufacturing data with or without encryption still have a chance of hacking;

[0011] Hi. Lack of original source for the 3D CAD data since only transferable neutral file is used in the file exchange; iv. The presence of details about the original author, different stages of product lifecycle and the person who accessed the data / machine mac IDs; v. No physical password for a specific 3D CAD data file for manufacturing. Examples of the present disclosure seek to address or at least alleviate the above problems.

[0012] In a first aspect, there is provided a method for transferring a file for a 3D printing process from a manufacturer to a user, the method comprising: identifying a product to be printed at a user’s site using a software stack, in particular a secured Manufacturing as a Service, sMaaS, software stack; providing printing data for printing said object with a 3D printer; encrypting the printing data and generating a printing archive file containing said printing data; generating a modified firmware specific for a selected 3D printer of the user, wherein the modified firmware is contained in the printing archive file; providing the 3D printer with the printing archive file, wherein the 3D printer is off-line; and decrypting the printing data of the printing archive file and using the decrypted printing data for starting the printing process, wherein the method comprises deleting, at least in part, said printing data of the printing archive file once the printing process is completed.

[0013] In a second aspect there is provided a system for transferring a file for a 3D printing process from a manufacturer to a user using the method according to the first aspect, the system comprising: a user interface connected to a server, the user interface being configured to provide an interaction between the user and a software stack, in particular a secured Manufacturing as a Service, sMaaS, software stack, a 3D printer for receiving the printing archive file and printing a product at user’s site, the 3D printer being offline; and transferring means for transferring the printing archive file from the server (3) to the 3D printer.

[0014] In a third aspect there is provided a computer program product comprising instructions to cause the system according to the second aspect to execute the steps of the method according to the first aspect.

[0015] Other aspects and features are defined in the appended claims. Examples of the disclosure may provide a way to transfer information data regarding the 3D printing of a product in a secure manner thereby guaranteeing all the information details to the user regarding the product. Also, the examples of the disclosure may provide a method and a system for controlling a large number of production in a contract manufacturing scenario.

[0016] Examples of the disclosure will now be described by way of example only with reference to the accompanying drawings, in which like references refer to like parts, and in which:

[0017] Figure 1 is a flow chart od the method for transferring files according to an example;

[0018] Figure 2A is a schematic representation of the system for transferring files according to an example;

[0019] Figure 2B is a schematic representation of the server modules according to an example;

[0020] Figure 3 is a schematic representation of the component of the system according to an example;

[0021] Figure 4 is a flow chart of an algorithm for validating the licensed print ready parts using a secure USB according to an example;

[0022] Figure 5 is a flow chart of an algorithm for license generation and secure print artifacts generation according to an example;

[0023] Figure 6 is a flow chart of an algorithm for firmware installation and sMaaS deployment according to an example; and

[0024] Figure 7 is a flow chart of an algorithm of a secured Manufacturing as a Service according to an example.

[0025] A method and a system for transferring a file for a 3D printing process between a manufacturer and a user are disclosed. In the following description, a number of specific details are presented in order to provide a thorough understanding of the examples of the disclosure. It will be apparent however to a person skilled in the art that these specific details need not be employed in order to practice the examples of the disclosure. Conversely, specific details known to the person skilled in the art are omitted for the purposes of clarity in presenting the examples.

[0026] Figure 1 schematically illustrates the steps of a method 100 for transferring a file for a process of 3D printing between a manufacturer and a user, in particular from the manufacturer to the user. At step S101 , a product to be printed is identified by the user at the user’s site using a software stack. For example, the software stack can be a secured Manufacturing as a Service, sMaaS software stack and the user is connected to a server 3 for accessing said software by means of a user interface 2. The product can be identified by selecting a product among a list of possible products or by directly uploading a corresponding CAD model. After the product is identified and eventually payment aspects are verified, printing data 18 are provided at step S102. The printing data 18 are generic data including information relating to the printing of the product using a 3D printer 4. As will be described in detail in the following, the printing data 18 can include data related to the instructions of printing, and to the licenses and contracts referred to the identified product.

[0027] At step S103, the printing data 18 are encrypted and a printing archive file 5 (i.e. a print artifact) is generated. The printing archive file 5 can be for example a ZIP file containing multiple files such as the printing data 18.

[0028] At step S104, a modified firmware 12 is generated specific for a selected 3D printer 4 employed by the user. It is noted that the modified firmware is specific for the selected printer and is contained in the printing archive file 5 together with the printing data 18.

[0029] The 3D printer 4 is provided with the printing archive file 5 at step S105. It is worth to notice that the 3D printer is off-line, meaning that the 3D printer is not connected to any network, in particular is not part to the network to which the server 3 of the user is connected. This increases the security of the transfer process since no external attack can be provided through the network against the data used for the printing.

[0030] At step S106, the printing data 18 are decrypted at the 3D printer 4 site and the decrypted data are used to start the printing process.

[0031] In order to furthermore increase the security of the data transfer, once the printing process is completed, the printing data 18 are deleted. In particular, the printing data 18 are deleted at least in part from a memory used to store said data during the transfer from the server 3 to the printer 4.

[0032] In one example, the printing data 18 of the printing archive file 5 comprise a license file with a unique license key based on the number of products to be printed.

[0033] In one example, the printing data 18 of the printing archive file 5 comprise a print instruction file, for example a G-code, generated based on a CAD model of the product to be printed.

[0034] Figure 2A schematically illustrates a system 1 for transferring file using the method 100 of figure 1 . The system 1 comprises a user interface 2 connected to a server 3, a 3D printer 4 for receiving the printing archive file 5 and printing a product at user’s site, and transferring means 6 for transferring the printing archive file 5 from the server 3 to the 3D printer 4. The user interface 2 is configured to provide an interaction between the user and a software stack. The user interface 2 also acts as an intermediatory between sMaaS software and 3D printer 4. The user interface 2 can be in the form of a desktop client, i.e., it runs natively on user / customer computer; thus, it can access resources connected to computer (e.g.: a USB device). The desktop client can communicate with sMaaS server by making API (application programmable interface) requests. It could use one or more types of API types & protocols available (ex: REST, HTTP, SOAP, RPC, GraphQL, etc).

[0035] The 3D printer 4 is off-line, meaning that is not connected to the server 3 or to the network of the server 3.

[0036] In examples, providing the 3D printer 4 with the printing archive file 5 comprises transferring the printing archive file 5 to a data carrier device 13, in particular a USB device, and coupling said data carrier device 13 with the 3D printer 4 of the user. Accordingly, the transferring means 6 of the system 1 is a data carrier device 13, in particular a USB device, connectable (in a removable way) to the user interface 2 and to the 3D printer 4. In addition or in alternative, providing the 3D printer 4 with the printing archive file 5 comprises using a secure data channel 14, for example protocols like FTP, TCP, etc. Accordingly, the transferring means 6 of the system is a secure data channel 14.

[0037] A software stack overview used according to an example is illustrated in detail in figures 2B and 3.

[0038] The server 2 comprises a plurality of software modules. For example, the server 3 can comprise a user authentication module 7 for authenticating the user; a product module 8 for storing information data on one or more products of the manufacturer; a payment module 9 for handling payment operations; a security and printing module 10 for generating and encrypting the printing archive file 5; and a printer module 11 for transferring the printing archive file 5 from the server 3 to the 3D printer 4.

[0039] The user authentication module 7 serves to authenticate the users against their credentials (username, password, OTP, 2FA, etc.), and to register new users. Users are able to register themselves. However, authorized manufacturer personnel can register and provide credentials to the user (password & other credentials would be reset by user after first login). In addition, with this module it is possible to verify users, block users via automated systems or manually by manufacturer authorized personnel. Only authenticated and verified users are allowed to perform further interactions / transactions with sMaaS software.

[0040] The product module 8 stores information of available manufacturer products, price, CAD models, print settings / configurations, etc. Not all information available would be visible to the user and only relevant or insensitive information would be visible. Manufacturer’s authorized personnel would have an option to add, edit, hide, delete a product, its price, CAD model, print configurations, etc. User’s uploaded CAD models will not be part of product module 8.

[0041] The payments module 9 takes care of handling payment operations like capturing price, redirecting to payment gateway (UPI, PayPal, Stripe, Square, Razor Pay, Credit Card, Debit Card, Net Banking, etc.), capturing different components of transactions, authenticating payment, etc. In case of large payments (a threshold can be set by the manufacturer), an option to pay using alternative payment mode (like check, direct bank transfer using mechanisms like NEFT, RTGS, IMPS, credit based payment, bulk payment, wallet, etc.) would be provided and payment authentication would be performed by manufacturer authorized personnel.

[0042] The security module 10 generates 'n' licenses for a product (or user’s uploaded CAD model) based on the order placed and payment done by the user. The module also generates unique OTP / authentication code that will be used for the authentication by 3D printer firmware (manufacturer certified) before starting print operation and handles secure key (required for encrypting / decrypting data) generation tasks. This module also handles data encryption task, i.e., encrypting print instructions file (ex: G-code) generated by printer module or encrypting 3D CAD models directly.

[0043] In one example, the method 100 comprises generating an hash code by means of a cryptography algorithm, in particular MD5, used by the modified firmware to validate the integrity of a transferred file. This is carried out by the security module 10.

[0044] The printer module 11 allocates a 3D printer 4 at customer manufacturing site / manufacturer site based on product selected / user uploaded CAD model, print configurations, etc., for printing the selected product / user uploaded CAD model. It also generates print instructions (e.g.: G-code) for a given 3D CAD model based on allocated printer and its configurations. Manufacturer authenticated personnel can add 3D printers, edit their configurations (like print settings), disable / block 3D printer, delete 3D printer, etc. Only 3D printers with manufacturer’s certified firmware would be allowed. This module allows the user / customer to attach a printer to their account by using predefined printer models and configurations. Optionally, customers could change configurations of the printer. The printer module 11 handles creating a custom manufacturer’s certified firmware using printer configurations of an allocated 3D printer, that can then be deployed to the 3D printer and handles deploying / transferring secured / encrypted artifacts containing G-code, printer configurations, licenses, file hashes, etc. received from secure design modules to allocated 3D printer. As already mentioned, transferring secured / encrypted artifacts to 3D printer could be managed in two ways:

[0045] - via Secured Data Channel / Layer 14, thereby using secured network files transferring protocols like FTP, TCP, etc. In this case, the printer module 11 in server 3 will handle the transfer process; and / or

[0046] - via manufacturer’s secured USB device 13. An external storage device like USB device 13 that has a firmware deployed by manufacturer is provided by the manufacturer. Encrypted artifacts would be copied / downloaded / transferred to this device by user using sMaaS software. The firmware deployed on the USB device 13 takes care of decrypting the artifacts and print instruction file (e.g. G-code) using a secret key burnt into the USB device's non-volatile memory during its manufacturing or a dynamically generated one-time key by sMaaS software (received along with artifacts). Based on printer requirement, print instructions could be decrypted line-by- line or all at once.

[0047] In one example, the system 1 further comprises a 3D CAD data lake 15 for storing files and configuration required for printing 3D CAD models. The 3D CAD data lake 15 is connectable to the server 3. Similarly, a payment gateway 16 can also be present and connectable to the server 3 (shown in figure 3).

[0048] A detailed process flow of the method 100 is illustrated considering the figures 4 to 7.

[0049] In one example, as already mentioned, the method comprises using a data carrier device 13 for providing the 3D printer 4 with the modified firmware and validating the data carrier device 13 at user’s site before generating the printing archive file 5. With reference to figure 4, an algorithm for validating the licensed print ready parts using manufacturer’s secure USB device 13 is shown. This flowchart in figure 4 depicts flow of validating whether USB device 13 inserted is a valid manufacturer USB device 13 or not. The desktop client, once opened, will be constantly checking for any USB device 13 insertion. When a manufacturer’s secure USB device 13 is connected to the computer running desktop client, the program in the desktop client will read the serial number stored in the secure non-volatile memory of the USB device 13 and verify it against the serial numbers of USB devices 13 in sMaaS database / storage. If a match is found, the customer would be allowed to proceed to purchase a license to print product in their 3D printer 4. Passing to figure 5, a flowchart for license and secure print artifacts generation is shown. This figure shows the high-level view of order placement & license generation for 3D printing. In the product dashboard, the customer will be shown manufacturer products that could be 3D printed and an option to upload their own design that they want to 3D print. After product is selected and a value for number of prints is provided, a quotation will be generated. The customer can then pay using payment gateways available or utilize the credit limit set by the manufacturer. After payment is verified, the next step is to generate secure print artifacts comprising printing data 18 like licenses, 3D print instruction files, etc. Based on number of prints customer has purchased, equal number of unique license keys (alphanumeric values) are generated, and a license file is generated for each license key. License file will also contain order ID along with license key and it will be encrypted using secure key corresponding to the manufacturer’s secure USB device 13 inserted. Next, a print instruction file (e.g. G-code) based on a product 3D CAD model will be generated for each license purchased and an order key will be added to first line for verifying before 3D printing is started. Every print instruction file is encrypted by using a license key as secret key (this could be achieved by using cryptography algorithms like AES) for stronger security. Finally, a unique six-digit binary pattern (e.g. 001010) will be generated for use as OTP before 3D printing process starts. This OTP will also be encrypted using a secret key for better security.

[0050] In one example, the generation of the modified firmware comprises selecting a 3D printer 4 based on the product to be printed; and modifying said firmware using a pre-saved configuration of the selected 3D printer 4. With reference to figure 6, a process flow for firmware installation and sMaaS deployment is shown. The flowchart in figure 6 shows the process of deploying 3D printing firmware to manufacturer’s secure USB device 13 after license(s) for 3D printing is purchased by the customer. A base manufacturer’s certified firmware developed will be used and necessary configurations will be modified based on the printer requirements. For example, most of the 3D printers use open-source firmware called Marlin which can be deployed after modifying configurations based on the 3D printer. Similarly, based on the product that has to be printed, a 3D printer (at customer / partner site) will be selected, and its pre-saved configuration are used to modify based firmware and a modified firmware would be generated. This modified firmware would be deployed to manufacturer’s secure USB device 13 by selecting appropriated options (like clicking on 'Deploy to USB' button) in the desktop client. At the end of this process, all necessary artifacts required for 3D printing like 3D printer firmware, licenses, print instructions file, etc., would be present in the manufacturer’s secure USB device 13.

[0051] In one example, the method 100 further comprises generating a unique binary pattern used as a one-time-password for the printing archive file 5. In particular, the method 100 comprises: decrypting the one-time-password using a secure key, wherein in particular the secure key is stored in a data carrier device 13 and wherein the decryption occurs once the data carrier device 13 is coupled with the 3D printer 4; comparing the unique binary pattern derived by the decrypted one-time-password with a corresponding password value provided by the user; and starting the printing process if there is a match between said unique binary pattern and the password value provided by the user or deleting, at least in part, the printing data 18 of the printing archive file 5 if there is no match between said unique binary pattern and the password value provided by the user.

[0052] With reference to figure 7, a complete process flow diagram of secured Manufacturing as a Service is shown. For print process to start, the customer should plug the USB device 13 into a valid 3D printer 4. After USB device 13 is plugged in, the 3D printer 4 would boot up using the firmware in the USB device 13. Artifacts like license files, OTP would be decrypted using the secure key stored in secure non-volatile memory of USB device 13. After actual OTP is decrypted, the firmware will wait for customer to enter the OTP displayed in the desktop client at the end of the purchase process. OTP will be entered using keypad if available, otherwise switches connected to an analog to digital converter will be used and converted pattern (binary) will be read by firmware to match against the actual OTP. A limit switch 17 is shown for example in figure 3. If they don't match, printing process won't proceed and after a predefined number of trails (e.g. five), all the print artifacts, licenses would be destroyed. If OTP is valid and matches, next step is to decrypt license files using the secure key stored in secure nonvolatile memory of USB device 13. Each decrypted license file will be read by the firmware to get license key and order ID. License key will then be used to decrypt the encrypted print instructions file and order ID embedded in first line of print instructions file will be matched against order ID in license file. If order IDs match, firmware will start the printing process. This will be repeated for 'n' licenses available and after print is complete, the corresponding license file and print artifacts would be deleted.

[0053] It is noted that the modified firmware 12 is a software that is stored on the USB memory or in case no USB device 13 is used, it is stored on the printer memory. All the other data (printing data 18) would also be stored on the same memory as the firmware 12 but may be in different partition. As software modules in the modified firmware 12 know where data is stored, they are able to delete the files / data from that memory.

[0054] In one example, the method further comprises generating a configuration file with all the printing information formatted as per Asset Administration Shell, AAS, standards, afterthe printing process is completed. In particular, the AAS - a key concept in industry 4.0 - is a standardized digital representation of a physical asset, machinery, product lifecycle, etc. The firmware deployed by sMaaS software for 3D printing process can capture necessary details of machine, parameters & configurations used for 3D printing, environmental conditions (like temperature, humidity of manufacturing site, etc.) during printing process. After the printing process is complete, the customer can plug the USB device 13 back to the computer where sMaaS desktop client is open and the parameters captured and stored in the USB device 13 would be read by the software to generate a file with all the printing information formatted as per AAS standards, which can then be downloaded by customer for their future use.

[0055] By using the present method 100 and by employing the present system 1 the following advantages can be achieved:

[0056] - A digital thread as per Asset Administrative Shell file for Manufacturing and accessibility details as a configuration file can be provided;

[0057] - The Manufacturing Firmware (Operating system for 3D Printer) can be generated with required security and transferred to specific machine with 3D CAD data embedded on the firmware. In case of any attempt to alter or access the file, the firmware will lock the process;

[0058] Licensing or Digital rights are integrated with AAS config file and can be used as per the license number; - The AAS file contains product lifecycle history and can be used for operations and service if it is a smart product;

[0059] - The AAS file or configuration file contain details from design and the machine IDs where it is used at different product life cycle;

[0060] - A Manufacturing machine limit switch or any other format / clicks are used to initiate the printing;

[0061] - A USB hardware certified by the manufacturer is provided containing firmware and encryption to print the parts offline.

[0062] Although a variety of techniques and examples of such techniques have been described herein, these are provided by way of example only and many variations and modifications on such examples will be apparent to the skilled person and fall within the spirit and scope of the present invention, which is defined by the appended claims and their equivalents.

Claims

CLAIMS1 . Method (100) for transferring a file for a 3D printing process from a manufacturer to a user, the method (100) comprising: identifying (S101) a product to be printed at a user’s site using a software stack, in particular a secured Manufacturing as a Service, sMaaS, software stack; providing (S102) printing data (18) for printing said object with a 3D printer (4); encrypting (S103) the printing data (18) and generating a printing archive file (5) containing said printing data (18); generating (S104) a modified firmware (12) specific for a selected 3D printer (4) of the user, wherein the modified firmware (12) is contained in the printing archive file (5); providing (S105) the 3D printer (4) with the printing archive file (5), wherein the 3D printer (4) is off-line; and decrypting (S106) the printing data (18) of the printing archive file (5) and using the decrypted printing data (18) for starting the printing process, wherein the method (100) comprises deleting, at least in part, said printing data (18) of the printing archive file (5) once the printing process is completed.

2. Method (100) according to claim 2, wherein providing (S105) the 3D printer (4) with the printing archive file (5) comprises: a. transferring the printing archive file (5) to a data carrier device (13), in particular a USB device, and coupling said data carrier device (13) with the 3D printer (4) of the user; and / or b. using a secure data channel (14).

3. Method (100) according to any one of claims 1 to 2, wherein the generation of the modified firmware comprises: selecting a 3D printer (4) based on the product to be printed; and modifying said firmware using a pre-saved configuration of the selected 3D printer (4).

4. Method (100) according to any one of claims 1 to 3, wherein the printing data (18) of the printing archive file (5) comprise a license file with a unique license key based on the number of products to be printed.

5. Method (100) according to any one of claims 1 to 4, wherein the printing data (18) of the printing archive file (5) comprise a print instruction file, for example a G-code, generated based on a CAD model of the product to be printed.

6. Method (100) according to any one of claims 1 to 5, further comprising generating a unique binary pattern used as a one-time-password for the printing archive file (5).

7. Method (100) according to claim 6, further comprising decrypting the one-time-password using a secure key, wherein in particular the secure key is stored in a data carrier device (13) and wherein the decryption occurs once the data carrier device (13) is coupled with the 3D printer (4); comparing the unique binary pattern derived by the decrypted one-time-password with a corresponding password value provided by the user; and starting the printing process if there is a match between said unique binary pattern and the password value provided by the user or deleting, at least in part, the printing data (18) of the printing archive file (5) if there is no match between said unique binary pattern and the password value provided by the user.

8. Method (100) according to any one of claims 1 to 7, further comprising generating a configuration file with all the printing information formatted as per Asset Administration Shell, AAS, standards, after the printing process is completed.

9. Method (100) according to any one of claims 1 to 8, further comprising using a data carrier device (13) for providing the 3D printer (4) with the modified firmware and validating the data carrier device (13) at user’s site before generating the printing archive file (5).

10. Method (100) according to any one of claims 1 to 9, further comprising generating an hash code by means of a cryptography algorithm, in particular MD5, used by the modified firmware to validate the integrity of a transferred file.11 . System (1) for transferring a file for a 3D printing process from a manufacturer to a user using the method (100) according to any one of claims 1 to 10, the system (1) comprising: a user interface (2) connected to a server (3), the user interface (2) being configured to provide an interaction between the user and a software stack, in particular a secured Manufacturing as a Service, sMaaS, software stack, a 3D printer (4) for receiving the printing archive file (5) and printing a product at user’s site, the 3D printer (4) being offline; andtransferring means (6) for transferring the printing archive file (5) from the server (3) to the 3D printer (4).

12. System (1) according to claim 11 , wherein a. the transferring means (6) is a data carrier device (13), in particular a USB device, connectable to the user interface (2) and to the 3D printer (4); and / or b. the transferring means (6) is a secure data channel (14).

13. System (1) according to any one of claims 11 to 12, wherein the server (3) comprises: a user authentication module (7) for authenticating the user; a product module (8) for storing information data on one or more products of the manufacturer; a payment module (9) for handling payment operations; a security and printing module (10) for generating and encrypting the printing archive file (5); and a printer module (11) for transferring the printing archive file (5) from the server (3) to the 3D printer (4).

14. System (1) according to any one of claims 11 to 13 further comprising a 3D CAD data lake for storing files and configuration required for printing 3D CAD models.

15. A computer program product comprising instructions to cause the system (1) of any one of claims 11 to 14 to execute the steps of the method (100) of any one of claims 1 to 10.

Images