We are a third-party logistics company. We work for a lot of people. We've got SEEBURGER Business Integration Suite (BIS) because we needed an SFTP server over 10 years ago. We have a lot of customers at various levels of IT maturity. Originally it all started off with just FTP, but we now use AS2 and SFTP an awful lot, and we're now moving into the API world.

There are some common interfaces here and there but, generally, it's all bespoke to each customer, of which we have about 75 to 80 and that's changing every month. We run in the realm of 800,000 processes a week. There is about a 50-50 split between internal systems talking to it and external customers sending files in.

The solution is on-premise.

We primarily use the solution for content conversion and file transfers. 

We use the solution basically for the integration, mostly EDI, and sometimes API. 

The documents would come out of SAP and then go to SEEBURGER, get transformed, and then be sent to the trading partner. 70% or 80% of the business would be this, and 20% is on the API side where we have very high demands from the logistics side of the business.

The solution is used for B2B integrations and receiving messages securely over the internet.

We primarily use SEEBURGER Business Integration Suite (BIS) for application-to-application integration and for integration with external partners. We have the entire SEEBURGER suite deployed in our external VLANs, and it's primarily responsible for communicating with internal systems as well as external partners. Once we communicate with them, we exchange EDI messages, XML messages, and APIs, and then we convert them to the appropriate ERP format. We have SAP as our ERP as well as IMPulse, and other internal applications. We can merge the data into appropriate format, and then we forward it to the corresponding applications, downstream.

It's completely on-prem. Back in the day, when we started the alliance with SEEBURGER, we bought their entire product and everything was installed on-prem. All our solutions are custom-built by us, as part of our business process needs.

We use it for any interface between two of our business applications, as well as any B2B communication that needs transferring of files, where a big part includes EDI. For any communication or documentation going from one company to another and also needing to do updates with the files, we are able to use SEEBURGER BIS. It is not just transferring the file, but making changes and doing some types of differentiation filtering. We can look up or find the information from other databases and put them together, then send the final document. We use it as a business integration tool.

It's used 24/7/365. Every minute of downtime counts because our actual work depends on SEEBURGER BIS's performance. So far, it has been working fine for us.

We are using SEEBURGER Business Integration Suite (BIS) for any kind of integration, but mainly in the areas of B2B, A2A and API, and even data-lake related topics. We do not have any limitations in using it, so if a special integration demand arises outside the integration patterns described, we can be sure that it is always possible.

It's a hybrid. Some parts are on-premises and other parts in the SEEBURGER Cloud.

We primarily use it for standard EDI practice forecasts, firms, ASNs, invoices, etc. We use everything here, including VDA, EDIFACT, and ANSI, but we are also now having our customers send us drawing files, and then we're sending them off to our engineers.

We use it to connect via EDI with our trading partners within the EU region and with other regions, including, America.

It's an off-premise solution. We have a secure file transfer server where we are placing the files or picking up the EDI, and then they connect and put the files in or take them away. On the SEEBURGER side, we then connect into their portal so we can then see the information about the message flows, etc.

Our primary use case is to send EDI documents between our partners and vendors. We're also starting now to use it as a development tool to translate SAP idocs to EDI messages and vice versa. 

Our primary use case is EDI: commercial messages such as purchase orders from the customer. We send invoices, credit memos, and we also have a small amount of purchase orders going out to our suppliers and their responses come back in. It's B2B. I don't think we're doing anything "wow" or extraordinary. It's quite basic, traditional EDI.

We get a file from our customers such as an XML file, standard ones from GS1, and that's converted to an IDoc which goes into SAP.

It is primarily an EDI translator for us. We have over 1,000 trading relationships running through it, totaling a couple of million documents. We don't just have EDI flowing through the platform. We have XML documents from some partners, and other things flowing inbound and outbound. But the bulk of it is EDI.

Our deployment is on-premise. We went that way because we knew the cost of doing it the other ways was more expensive. And in general, that is the model that we use.

SEEBURGER, along with four or five other big vendors, focuses in the integration space. When you talk about data integration, there are two major aspects of it. There is the transactional messaging side and the batch file-based side. My team is focused on the batch file-based side of things. We have a completely different team (with a different set of software) who does the transactional messaging aspects. We are using it for all secure file transfer use cases throughout the organization with multiple different data patterns: moving data within the company, moving data to and from outside of the company, and ad hoc file transfer. Any type of file-based secure connectivity goes through our team using this product.

Currently, it is on-prem. We have a cloud initiative, which has been rolling for a couple of years now, like most companies. It is on our radar for later this year. We are going to spin up another project to consider either moving to our own AWS or SEEBURGER's AWS and their iPaaS environment.

We're primarily using it for communication and translation of our traditional EDI documents. We're an automotive supplier so a big part of our business is automotive related, but we're also using it for synchronous APIs or web services with some of our customers or trading partners.

Of course, not everything we're doing is EDI. We're doing a lot of distribution of unstructured files, even in our company, transactions between systems. With the mapper, we're doing data transformation as well, to integrate back to our back-end ERP system. We're also using the Message Tracking component, which allows us to confirm what's come in and what has processed.

About 90 percent of our global EDI transaction volume is coming in and out of SEEBURGER Business Integration Suite (BIS).

The reason that we bought the product was that we have a very robust healthcare inventory environment in SAP here at the university. That involves huge inventory, purchase orders with 300 lines, electronic invoices, 856s, 855s. We knew we were going to have to have some standalone EDI ability here. That was the main goal of getting it, which we very quickly accomplished.

We are an automotive parts supplier and we exchange purchase orders, releases, shipment forecasts, as well as ASNs—shipment notifications, one of the most important documents—invoices, and some non-EDI files. We support North America and South America, but we have colleagues in Europe and Asia as well. We are communicating with most of the automotive companies: Ford, Volvo, Magna, Chrysler and we use SEEBURGER Business Integration Suite (BIS) for transactions in the automotive field.

We also use the translator, BIC 6 Converter, and most of the protocols for communication: AS2, FTP, SFTP, HTTP, OFTP, FTPS. We also communicate with some banks.

We use it mostly for data integration. We use a module from SEEBURGER called Managed File Transfer or MFT. We move about 30,000 to 50,000 files in a week in our company. The files are moved intracompany but they also move between our company and our external partners. We also have a bunch of stuff on Amazon. We use SEEBURGER Business Integration Suite (BIS) to integrate our data center with Amazon file transfers.

We use the solution to tap and transform traffic. 

SEEBURGER BIS monitors our system servers, i.e., the internal and external communications. It monitors that everything works fine. When I need to configure new trading partners, they take care of the customer map. They already have an existing catalog of customers, and I work with them to build a process map. On their end, they build the map for the customer using specific coding, then we do the same in SAP. This is what they monitor. 

It is in the cloud, but hosted by SEEBURGER. They maintain the process via Message Tracking and other applications.

This is just to transfer files securely within the Mylan network, and a few instances from the outside too. It is just to transfer files. Like a postman, it moves the files between the systems with no data transformation

We have the on-premise solution and are only using one feature of this product. Most of our solutions are on-premise, as our security team prefers it that way.

We use the product to process for our EDI/B2B platform. It supports various transaction formats including X12, EDIFACT, cXML and xCBL. We also use the product to handle various communication protocols, including AS2, FTP, HTTP and PGP encryption.

We use SEEBURGER Business Integration Suite (BIS) as a service. While we were not really using their software, we might be using their software internally to provide a service. Effectively, we're using them as an integration partner.

We use SEEBURGER BIS for electronic data transmissions (EDI). It does a lot of work on our behalf in terms of the mapping and on some of the integrations which are required between us and third-parties. 

We have an integrated ERP system which talks directly to the SEEBURGER systems. Therefore, we don't necessarily have any manual interaction since this is a completely automated system which talks to the SEEBURGER back-end systems.

The company has been using the solution for three years now. I have been onboard for one year.

We are using the managed services, which is cloud-based, and SEEBURGER Business Integration Suite (BIS) manages this part for us. We do have a modified or hybrid managed services model. We do our own mapping internally, but everything else is through the cloud and SEEBURGER Business Integration Suite (BIS) services.

My primary use case for this solution is for transferring EDI documents between customers and suppliers of the heavy truck industry.

We are using it mainly for EDI with a wide variety of trading partners. We do a lot of EDI transactions with a lot of our customers and vendors, as well as a few healthcare providers.

We have a lot of transactions, but we don't really have that big of a load. On a daily basis, we have around 2,000 transactions.

Our primary use case for it is as an integration tool. We've got lots of systems. We are a service company in warehousing and transport and we've got a lot of customers. We are a 3PL company so we do transport for a lot of the big retailers. All of this has to be integrated. We've got small applications running everywhere, so any data which flows through from one application to another requires SEEBURGER Business Integration Suite (BIS).

Warehousing is our major function. We get orders from our clients, retailers that you know. Some of them use EDI, some use API, and some use web services. They come through our system and they get formatted into our standard warehouse management system, which is Manhattan. Order information has to be formatted in the Manhattan XML format.

On the transport side, there are different applications. We have Freighter which does the load planning and then there is route planning which is a separate application hosted by Paragon. The route planning information goes from the orders which we received to the Paragon system, and the orders also go to Freighter for load planning.

In addition, there is information from the warehouse system that has to go back to our big retail customers, such as stock received, dispatch confirmation, receipt confirmation, and any stock adjustments. There are different types of interfaces which go back and forth between our customers and our warehouse management systems.

There is some B-to-B integration and then we have application-to-application as well. For example, the warehouse management system might talk directly to the transport system, which is web-service or API-driven. Sometimes they can't do it themselves, so SEEBURGER Business Integration Suite (BIS) will step in to capture the data from the warehouse management system. It will do the API service to communicate with another system and get the results and push them. So it acts as a gateway for everything coming in and out of our company, a secure gateway.

Many of our customers still use file transfer, so we use SFTP a lot. Most of the interfaces are migrating to web services, SOAP or API. Those are the latest but we still have a lot of SFTP used.

It is hosted by us, internally.

It's our EDI translator. We use it daily, it's on-prem. It's SEEBURGER Business Integration Suite (BIS) 6 and we've been using it for eight or nine years.

We use it for our EDI. 

It's primarily for receiving orders from some of our customers and we then issue invoices to those customers via EDI. We also dialogue with our logistics companies who will be shipping the orders to the customers. We send messages to our logistics companies telling them about new products or batch changes or an order which needs to be sent out to this customer by that date. That logistics company will then confirm back to us when they've done so and that kicks off another process, which is the invoice. It's end-to-end in a lot of ways.

EDI with automotive businesses is our primary use case.

We use the solution for EDI and file swaps, but it will be used for all integrations going forward.

• We use it for handling partner setup, dealing with XML, EDI transactions, and mapping.
• We can do job scheduling, process designing, AS2, FTP, and SFTP setup in it.
• We can use it to script and monitor processes.