How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
I integrate Windward in software solutions and have done so for customers that work in the financial industry. In general, I don't deal with the customer regarding commercial issues related to Windward. The idea is that Windward handles financial contact with the customer and they tell the customer that for training, for integration, or for questions about Windward for their particular application, there is a company available in Europe that can assist them with service training and onsite service. This is what I have been doing for the last five months for a customer in the Netherlands. My company acts as an independent after-sales consulting company. If the customer wants to have training on Windward or the customer wants to have somebody make templates, that's where I come in. An example of one of my customers' use cases for Windward is that if you go to the bank and ask for a loan, they will ask you questions like your name, your birth date, your address, what kind of job you have, how long you worked there, how much money you make a year, etc. At some point, my customer — the bank — will want to print a document for you of five, 10, or 15 pages where everything is written, including all the terms of the loan, so you will have it all on paper. What we do with Windward is we create all these pages and, depending on the input parameters we get from the bank's software, we create a Word or a PDF document which the bank can give to you. Any document that is, in principle, standardized, but each version needs to be a little bit different, can be created with Windward.
I create Windward templates for the Otis Elevator company. These templates are for complicated specifications and proposal documents that our sales reps use for selling elevators. The end result of these Windward templates are documents that perfectly fit the concept of "putting your right foot forward." Our primary use is for the sales reps to build these documents, based upon XML files created in the background on our document server. Our secondary use is for the public to be able to generate elevator specifications from Otis.com.
Our banking industry clients, as they're using our system, have a need to generate documents that give them some flexibility that are unique to the clients' needs and to the circumstances at hand. But at the same time, they want consistency so that they're not breaking any regulations. That's exactly what the Windward team provides us: that ability to have consistent generation of documents, but at the same time to give the end-user some flexibility to create whatever they need to, based on their particular circumstances. Windward is a critical component of our next-gen solution. The solution was built around our legacy environment because we wanted to make sure that we could migrate as many clients over to it as possible, without causing disruption. Windward was a critical component of that functionality. We built it knowing full well that we would want to have Windward be a part of it going forward.
Windward AutoTag is an add-in for Microsoft Word and other products. We use AutoTag to pull in data from our software to create standard documents for all clients, and customized ones as needed.
We use Windward for generating documentation for validation projects. We do computer systems validation. Validation is a software testing methodology used by life sciences companies, and we generate hundreds and hundreds of documents.
Dynamic document generation via API is our primary use case.
It's a good product, it's efficient. We have integrated it in our wealth management product for the last eight years. All our PDF generation, client-advice, client invoices, and letter generation - any document that goes to a client - is generated through Windward in our wealth management solution. The integration works quite well.
We are using Windward to generate documents, as a solution in our application. We have a software editing application and we are using Windward to generate documents for our customers. Our customers are financial institutions and each customer implementation is a use case.
The primary use case is for report automation.
The use case is that we are building a backend application for the tax office here in Curaçao. The tax administration sends out documents to people who need to pay taxes. All the communication, all the letters, are designed using Windward products and are also generated by Windward engines. We are not using it as a report-generation tool. We are using it more as a letter/document generation tool. With the functionality of Windward, we can adjust the documents dynamically to the individual needs of every taxpayer. The "if this then that" functionality in Windward allows us to design the documents dynamically so that there is only information on the document that is relevant to the taxpayer.
Simple and intuitive with a focus on business teams being able to support/maintain reports. It was important for us to aggregate data from external disparate systems and combine it onto a single report. Windward has no limitations on the number of data sources or number of pages a template can have, which made it the obvious choice. Leveraging native capabilities of MS Office (i.e., formatting text, page numbering, resizing images, etc.) saved us a ton of time that we would have spent coding on other platforms.
We are a software company. We put out a payroll and personnel software package. We use it to write all our package reports, and we allow our clients to make their own custom reports with it, as well.
Transforming our reports, that are natively in JSON format, to have a human-readable format associated with them.