If you are an Altair Monarch, Monarch Data Pump, Monarch|ES customer, please contact us for a competitive price to switch to TextPipe Standard or Pro.
Having problems converting files and extracting data? So does DataWatch's consulting team - the sellers of Monarch Data Pump, Monarch|ES and other tools.
Looking for a cost-effective alternatives for Monarch Pro v7, Monarch Pro 8.0, Monarch Data Pump, Monarch|ES for management and extraction of data?
DataMystic's TextPipe Pro is a market-leading alterntive to Altair Monarch.
DataMystic's consulting team can take your existing .dmod or other files, and convert them to an efficient TextPipe representation. Generally speaking the cost of doing this (even with consulting time plus a TextPipe license) is lower than your annual cost of using Monarch Altair.
TextPipe allows to to work with plain text files, legacy reports and mainframe data, creating models with floating traps, and moving output data to a spreadsheet table.
As DataWatch raise its prices above $6000 for a single user license, their customers are scrambling to alternatives such as TextPipe Pro.
Way back in 2007, a single user license for Monarch Standard Edition is priced at $699. A single user license for Monarch Professional Edition is priced at $849. Monarch Data Pump is priced at $8,995 per server for the Standard Edition and $24,995 for the Professional Edition. A single user license for VorteXML Designer is priced at $499 and VorteXML Server is priced at $8,995 per server.
Entry-level Datawatch|ES and Datawatch|BDS systems are priced at $30,000. Entry-level Visual|QSM and Visual|Insight systems are priced at approximately $20,000. An entry-level Monarch|RMS system is priced at $15,000. An entry-level Datawatch|MailManager system is priced at $12,000. An entry-level Visual|HD system is priced for less than $10,000
TextPipe is flexible and easy to use. It also links well with other data sources. While a yearly maintenance contract that includes professional services is available for purchase, the benefits are dependent on an organization's specific needs.
TextPipe is very effective for data mining from legacy reports and extract data from mainframe reports. Advanced features like Scripting Filters and External Lookups provide users with the ability to augment raw data. You can create a "filter list" to automate the data extraction.
If an organization's primary source of data is available in a report format, TextPipe is an excellent solution. It works extremely well for parsing out data from downloaded text files, and can even be used to parse data out of scanned pdf, Word and Excel documents. For power users, it works very well with databases and SQL. For non-technical users who just want to glean data out of a downloaded report, it's very easy to see how it works. For anyone who has ever tried to use Excel to open and parse a text file, TextPipe is sure to provide lasting relief!
Should you find TextPipe beneficial, the next logical step towards creating a great BI environment is TextPipe Server Edition, and TextPipe Engine.
TextPipe is the best alternative to Monarch
TextPipe Lite, TextPipe Standard and TextPipe Pro are all great alternatives to Monarch.
It's nice to have our competitors speaking the praises of our product - see the two emails below:
From: Dee_Moore@datawatch.com
Thank you for getting back to me Simon.
Yes, I converted the file using the two steps.
I just wanted to know if there was a one step process. You know how it
is.........everything has to be done as quickly and efficiently as possible.
The reason I'm evaluating TextPipe Pro is:
I'm always looking for ways to help our
customers process problem files. I do what I can to make their work a little
easier while using our product.
Our product, Monarch, extracts, manipulates,
and exports data in ASCII/ANSI format
only. Being a global company, we see multiple report Fonts and
Formats. I was recently presented with a report in UTF-8. I did find a
work-around for them within our product. By isolating the characters beyond the
ASCII/ANSI range, I created calculated fields to display the correct characters
in ANSI. However, not knowing just what UTF-8 characters will be in a file, the
expression could become quite lengthy. I thought converting the file would be
more prudent.
I was successful converting the file, but I do
have one more question..............
[snip]
Regards,
Dee Moore
Datawatch Technical Support & Model Building
From: Gareth_Horton@datawatch.com
It looks comprehensive.
I am looking at this more as a product to
recommend for our customers that have files that
need pre-processing before using them in our
Monarch product.
I have a heavy workload at the moment, so I can
only dip into it now and then.
If I have any questions, I'll drop you a mail.