Hi there and welcome! We are excited that you have chosen Authentise's MES. Here are a number of steps you can go through to make sure your organization is using the system.  To review supported browsers and operating systems for the app, please look here.   1) Getting Familiar By now, you should have had an introduction to the system by our team. You should also have received access to the Showroom and the short video guide. If these have not happened, please get in touch with us.   2) Defining Customizations and Configurations If you have any initial customization needs you will have discussed them with our team prior to this point.  If you have not, please do so. There are several areas that are usually customized. They include: • Editing the order fields • Selecting which alerts are sent • Defining the content of your exported documents (Traveler, Packing Slip, Traceability Report, and Quote) • Other (as defined in your SOW) It might take us a little while to complete them before deployment. Please reach out if you would like additional details.   3) Deployment (optional) If your organization has chosen one of several deployment options other than our cloud, our tech team should have been in touch to discuss the next steps. We have prepared a number of resources for your IT staff to understand the implications of deploying on-site and some of the different options. They are really helpful for everybody - take a look. If our tech team has not spoken with you or your IT team, please let us know so that we can answer any questions.  If you have chosen to go with a cloud deployment and you have not yet gotten your details and first user account, please contact us. Your deployment should be instantaneous once customizations are complete except when you have chosen to use Single Sign-on. This option allows your users to use your existing sign-on provider and requires some additional setup.    4) Access Once your organization has signed up you should receive a message in your inbox prompting you to login in (Note: If you are using a non-cloud deployment, the deployment must be completed before receiving the email to log in). This will have been generated by our team for your bureau. You can log in using flows.authentise.com or your personalized domain name. Your user name is your email address, please let us know if you have any challenges logging in to the system!   5) Bureau Setup Before you can submit your first order, you have to set up your bureau. This is a fairly simple process that we like to do with you. If we have not scheduled time with you to complete this setup, please do reach out for our support.   Bureau setup involves denoting your organization's Workstation Types and their associated Inventories. This information will allow various drop-down selections in the order form and manages many other aspects of the system.   Bureau setup includes the ability to add different types of resources which we recommend creating in the following order: 1. General  • Manufacturer: When you add materials, printers, or post-processors you will need to select their manufacturer. • Locations: Locations help manage Workstation work queues, user access, and Orders.  This is especially helpful when you have more than one location. • Currencies: If you have more than one currency, you will want to define their conversion rates for use in the system. We will establish a default bureau currency during onboarding, which will set its multiplier = 1. For the remaining currency options, set the multiplier with reference to the default bureau currency. 2. Types/Inventory (Workstations & Materials) • Material Types: You can elect to use our templated materials or create your own. We use these material types for creating both Printer Types and Post-Processor Types, so be sure to do this first.  • Printers: First you need to add a printer type and then the printers themselves. If you want to receive data from printers for automatic updates, you will also need to install Echo. Instructions for that can be found here. • Post-Processing Devices: This follows the same process as printers - start with Type and move on to the actual Post Processor workstations. 3. Workflows: Once you have established what equipment and material you have, it is time to define the processes you want your parts to follow. This is a key to ensuring your parts are produced properly and offers you immense control. 4. The others: Shipping and Third Party providers are pretty straight forward and largely optional at the moment. Remember, you can edit your Inventory at any time.   6) Testing  Now it is time to test the system. Go ahead, whirl around: Create an order and some runs. Learn about Statuses and how they change over time.  Confirm if your Machines are reporting correctly into the MES. If you have any problems, contact us. The easiest way to ask about improvements or raise a bug is to do so using our "Report an Issue" button from our application, or email support@authentise.com. How to access our on-site tool to ask about feature requests / improvements or to report bugs   7) Adding Users Your final step is to add the users that you want to add. There are several different permissions levels you can choose from for each user. Do you want them to access only prints related to one location ("local user"), or all locations ("Global User"), manage the service (can add new users and so forth), or only be able to upload an order ("Restricted"). More information on adding users can be found here.   We hope this guide was informative. If you need any more assistance, please don't hesitate to ask.

This is relevant ONLY to those deciding to go fully "local" - ie not choosing a private cloud or Managed Services option of deployment. Please check out our summary of deployment options to learn more. The requirements are divided into 2 Sections: • Flows Requirements • Threads Requirements Flows Requirements Requirements for a client-owned data center installation of Flows: • Linux computing resources • These can be virtual machines or bare metal hardware. • Linux OS - Ubuntu / Debian. We provide support and documentation for Ubuntu specifically • The Linux kernel must be version 6.5.x or newer • Total RAM and CPU are usage dependent, 6 virtual CPUs at ~2.0Ghz and 64 Gb total RAM minimum • Network-attached storage • Storage size and IOPS requirements are usage dependent. We recommend 80Gb per node as a minimum • Backups of the stored files and database must be handled by the customer • Permit outgoing HTTPS connections to Authentise • These connections allow us to bill the installation on a per-transaction basis as well as send emails/SMS notifications using our infrastructure • Standard SSL over port 443 at periodic intervals, no customer-owned data is transmitted. • Incoming HTTPS requests over intranet • All services are exposed via HTTPS, so client software must be able to reach the servers over port 443 internally. If the customer has a particular database provider requirement, Flows can be integrated with an existing postgresql (14.x and above) database server and license. Otherwise Flows will allocate some of the NAS and compute resources to running custom postgres on Linux for all of it’s RDBS needs. If you're intending to use Machine Data as part of your application installation, then you will need Echo. Echo is described here, and needs minimal hardware: a very simple windows computer should do the trick. The only important mark is that this computer must sit on the same network as your printer. For certain printers you may need to install it directly on the PC controlling your printer. Additionally if the deployment will be using slicing or design streaming to Stratasys printers: • Windows computing resources • Virtual machines or bare metal hardware • Windows Server 2012 or Windows 10 • 8 Gb RAM, 1 2.0Ghz CPU minimum Flows is architected as a system of microservices that are deployed via containers. This allows for flexibility in allocate computing resources and easy scalability. All deployments of Flows come with a dashboard for monitoring resource utilization to make informed decisions about adding additional capacity to the cluster. This architecture diagram might help: Threads Requirements The technical requirements to host our Threads application locally are as follows:  • Threads Primary Server • Minimum: 4 vCPU, 16GB RAM • Threads DB • Minimum: 2 vCPU, 8GB RAM • AI Service  • Minimum: 8 vCPU, 32GB RAM • GPU: 1+ Nvidia hardware needs discussion/trial • 3D Viewer  • Server: 4 vCPU, 8GB RAM • Database: 2 vCPU, 4GB RAM • Storage: • Shared between all instances • 700GB-1TB • 200+ GB is taken up by AI

Authentise is excited to be able to integrate with Paperless Parts, a cloud-based quoting tool that offers ITAR compatibility. This feature allows the transfer of confirmed orders from the quoting platform directly into Flows for manufacturing. This saves time as users won’t have to recreate their Paperless work in Flows. With the integration enabled, the following steps will allow you to bring orders from Paperless Parts into Flows.  Adding Authentise Flows to Paperless Parts This process will take you through how to add Flows as an integration within Paperless Parts.  1. Login to Paperless Parts 2. Navigate to Settings > Integrations. If this is unavailable to you, you will need to have Paperless Parts permissions upgraded by your Paperless Parts admin.  1. Click “Create Integration” in Paperless Parts and fill out the details as outlined below to create the connection.  Configure Integration Webhook in Paperless Parts The Integration Webhook is needed to enable the data to flow between Paperless Parts and Flows. This section takes you through how to correctly configure the webhook. A demo version can be seen in the image below.  1. Open the newly created Integration in Paperless Parts 2. Go to “Connectivity” 3. In the field Dispatch to URL, enter base URL: https://data.authentise.com  4. After the base URL, add the endpoint data: /paperless-parts-webhook/[Integration ID]/  a. The Integration ID can be found at the end of the integration URL as shown in the image below b. Make sure to include the final /slash/ at the end of the URL, otherwise the webhook will not work correctly.  5. Add Description, such as “Connection to Authentise Flows aMES” 6. In the Event to Dispatch section, under the “Order” entity, select: Order.Status_Change 7. Click “Save Webhook” Set Up & Configure Paperless Parts Integration in Authentise Flows Once you have set up the integration within Paperless Parts, we need to do the corresponding setup within Flows.  1. Login to Flows 2. Go to Organize > Paperless Parts Managed Integrations  3. Click “Add Integration” 4. Add Name of Paperless Parts integration (if you have separate instances of Paperless Parts, you’ll be able to add additional by a different name) 5. Copy and paste Integration ID, API Key, and Signing Secret from Paperless Parts 6. Set Location for non-ITAR and ITAR orders. NOTE: If Stock of a Material doesn’t exist at the specified location, Flows will use the existing logic - we will assign an order to whichever location does have the required material stock. This could potentially void the ITAR location data defined here.  7. Select an Order Creator User, this will be who new orders are attributed to.  8. Click “Save” Test Integration Once the fields have been configured correctly, you can test that the integration is correctly set up by Confirming an Order in Paperless Parts. If everything is correct, you will observe the Order is successfully transferred into Flows.  If you encounter any issues, please reach out to support@authentise.com and one of our team will help you further.  If you have any other applications or services you would like to integrate with Flows, please reach out! We’re always looking for way that we can improve our software and make it seamlessly work with other tools.