1.    Security of Information

All information, including Metadata, electronic documents and images, is stored in the RecFind 6 Microsoft SQL Server Database, not in insecure flat file systems. In addition, all electronic documents and images are stored as binaries (Blobs) in SQL Server, not native format; they are doubly secure.

The only way anyone can access your data is via the secure RecFind 6 client where access is protected by our industrial strength security system. No one has access to your information unless you authorize it. Plus, the fully customizable Audit Trail means you can track every transaction.

Don’t store your information on insecure shared drives or in insecure applications like Excel or Access; RecFind 6 is the far more secure solution.

Concerned about security, concerned about GDPR? Then store all your information in RecFind 6.

2.    Size of your Data Store, Scalability

The only size restriction for RecFind 6 is the maximum size of a MS SQL Server Database and that is currently 524 PB (Petabyte), 524 thousand billion bytes of information and likely to increase in future versions of SQL Server.

If you are concerned about a system being able to manage all of your data and handle future growth, then store all your information in RecFind 6.

3.    Performance, time to Capture & time to Search

The architecture of RecFind 6 has been optimized for electronic document and image capture (upload), search and download. Upload and download times are also independent of the size of your database.

If you plan on having a large number of users and a large data store and are concerned about performance, then store all your information in RecFind 6.

4.    Full-text Indexing

All textual data stored in RecFind 6 is automatically full-text indexed to facilitate optimum search results. This includes emails, OCR’d images, all documents containing text, and all entered Metadata.

If you need extremely fast and accurate text searches of your data, then store all your information in RecFind 6.

5.    Versioning of electronic documents

All electronic documents stored in RecFind 6 are automatically versioned when captured.

If maintaining an accurate record of all electronic document versions is important to you, then store all your information in RecFind 6.

6.    Reliability, Availability

RecFind 6 is renowned for its robustness and high availability. Situations where a code failure has made RecFind 6 unavailable to users are rarer than hen’s teeth. RecFind 6 runs and does what it says  on the box, day in and day out for 12 months a year.

If reliability and availability is important to you, then store all your information in RecFind 6.

7.    Microsoft Compatibility

All new versions of RecFind 6 are tested against the latest releases of Microsoft products including Windows Desktop, Windows Server, SQL Server and Office. We protect your investment in our products by ensuring that they continue to work in your chosen Microsoft environment.

If ongoing compatibility with Microsoft is a concern, then store all your information in RecFind 6.

8.    Support

We don’t have complicated, multi-tier plans for support; we address each support request as soon as it is received. Support is also FREE to all customers under a current maintenance agreement. We are rightfully renowned for the quality of our support service. Plus, all support is handled by our employees; we DO NOT OUTSOURCE support.

If high quality support is important to you, then store all your information in RecFind 6.

9.    Flexible Licensing & Pricing

We offer multiple licensing & pricing plans including In-Perpetuity, Annual, Subscription, Hosted (SaaS), Not-For-Profit, Site & Organization licenses. Plus, we will work with you to structure a plan to suit your unique needs.

If flexible licensing & pricing plans are important to you, then store all your information in RecFind 6.

10.         Dealing with the owner of the Intellectual Property (IP)

We designed and built the very first RecFind in 1986 and have designed and built every version since then. Please refer to our history of product development. When you deal with us you are dealing with the owners and developers, not a reseller or licensee. No one knows our products better than we do.

If it is important to you to deal with the experts, then store all your information in RecFind 6.

11.         The need to store multiple types of electronic documents & digital assets

RecFind 6 stores and manages any kind of electronic document including emails, plans, CAD drawings plus any kind and size of digital asset. It has been optimized to handle very large digital objects.

If you need to capture and manage any kind and any size of electronic document, then store all your information in RecFind 6.

12.         Unlimited users, Scalability

RecFind 6 can be delivered with a single user license or an unlimited user license and any number of users in between. Its unique architecture is able to support any number of users. The only prerequisite is that you provide adequate server hardware to meet your requirements. There are no inbuilt restrictions in RecFind 6 for either users or the size of the data store.

If you need to support a large number of users, then store all your information in RecFind 6.

13.         Accessibility

The RecFind 6 Web Client provides secure access to your data from anywhere in the world there is an Internet connection and from a variety of browsers and devices including the iPad.

If remote and convenient access is a requirement, then store all your information in RecFind 6.

14.         Ease of Configuration, Flexibility

The RecFind 6 DRM tool, supplied free of charge, makes it easy for you to modify RecFind 6 (Data Model, Business Process, Metadata, Security System, etc.) without ever having to contact us or pay for changes and still have a standard product.

If you have a need to modify your information management solution to your exact and changing requirements, then store all of your information in RecFind 6.

15.         Ease of Integration to other systems

The RecFind 6 Product Suite includes multiple tools to make integration to any other system or data source as quick and as easy as possible. These tools include the DRM, Xchange, The SharePoint Integration Module, the MINI API and the SDK/API.

If you have a need to integrate to other systems and to import data from a variety of data sources, then store all of your information in RecFind 6.

I run a software company and I design and build an enterprise strength content management system called RecFind 6 which among other things, handles all the needs of physical records management.

This is fine if I have a big corporate or government customer because the cost is appropriate to the scale of the task at hand. However it isn’t fine when we receive lots of inquiries from much smaller organizations like small law forms that need a records management solution but only have a very small budget.

A very recent inquiry from a small but successful engineering company was also a problem because they didn’t have any IT infrastructure. They had no servers and used Google email. However, they still had a physical records management problem as well as an electronic document management problem but our solution was way outside of the ballpark.

Like any businessman I don’t like to see business walk away especially after we have spent valuable consultancy time helping the customer to understand the problem and define the need.

We have had a lot of similar inquiries lately and it has started me thinking about the need for a new type of product for small business, one that doesn’t require the overhead and expense of an enterprise-grade solution. It should also be one that doesn’t require in-house servers and a high overhead and maintenance cost.

Given our recent experience building a couple of iOS (for the iPhone and iPad) and Android (for any Android phone or tablet) apps I am of the opinion that any low cost but technically clever and easy-to-use solution should be based around a mobile device like a smart phone or tablet.

The lack of an in-house server wouldn’t be a problem because we would host the solution servers at a data centre in each country we operate in. Programming it wouldn’t be a problem because that is what we do and we already have a web services API as the foundation.

The only challenge I see is the need to get really creative about the functionality and the user interface. There is no way I can implement all the advanced functionality of the full RecFind 6 product on a mobile device and there is no way I can re-use the user interface from either the RecFind 6 smart-client or web-client. Even scaled down the user interface would be unsuitable for a mobile device; it needs a complete redesign. It isn’t just a matter of adapting to different form factors (screen sizes), it is about using the mobile device in the most appropriate way. It is about designing a product that leverages off the unique capabilities of a mobile device, not trying to force fit an application designed for Windows.

The good news is that there is some amazing technology now available for mobile devices that could easily be put to use for commercial business purposes even though a lot of it was designed for light weight applications and games. Three examples of very clever new software for mobile devices are Gimbal Context Aware, Titanium Mobile SDK and Vuforia Augmented Reality. But, these three development products are just the tip of the iceberg; there is literally a plethora of clever development tools and new products both in the market and coming to market in the near future.

As a developer, right now the Android platform looks to be my target. This is mainly because of the amount of software being developed for Android and because of the open nature of Android. It allows me to do far more than Apple allows me to do on its sandboxed iOS operating system.

Android also makes it far easier for me to distribute and support my solutions. I love iOS but Apple is just a little too anal and controlling to suit my needs. For example, I require free access to the file system and Apple doesn’t allow that. Nor does it give me the freedom I need to be able to attach devices my customers will need; no standard USB port is a huge pain for application developers.

I am sorry that I don’t have a solution for my smaller customers yet but I have made the decision to do the research and build some prototypes. RecFind 6 will be the back-end residing on a hosted server (in the ‘Cloud’) because it has a superset of the functionality required for my new mobile app. It is also the perfect development environment because the RecFind 6 Web Services SDK makes it easy for me to build apps for any mobile operating system.

So, I already have the backend functionality, the industrial-strength and scalable relational database and the Web Services API plus expertise in Android development using Eclipse and Java. Now all I have to do to produce my innovative new mobile app is find the most appropriate software and development platforms and then get creative.

It is the getting creative bit that is the real challenge. Wish me luck and watch this space.

We have all heard and read a lot about the Cloud and why we should all be moving that way. I wrote a little about this in a previous post. However, when we look at specific applications like records management we need to think about the human interaction and how that may be affected if we change from an in-house system to a hosted system. That is, how will the move affect your end-users and records management administrator? Ideally, it will make their job easier and take away some pain. If it makes their job harder and adds pain then you should not be doing it even if it saves you money.

We also need to think about the services we may need when we move to the Cloud. That is, will we need new services we don’t have now and will the Cloud vendor offer to perform services, like application maintenance, we currently do in-house?

In general, normal end-user functions should work the same whether we are running off an internal system or a Cloud-based one. This of course will depend upon the functionality of your records management software. Hopefully, there will be no difference to either the functionality or the user interface when you move to the Cloud. For the sake of this post let’s assume that there is a version of your records management system that can run either internally or in the Cloud and that the normal end-user interface is identical or as near-as-such that it doesn’t matter. If the end-user interface is massively different then you face extra cost and disruption because of the need to convert and retrain your users and this would be a reason not to move to the Cloud unless you were planning to change vendors and convert anyway.

Now we need to look at administrator functions, those tasks usually performed by the records management administrator or IT specialist to configure and manage the application.  Either the records management administrator can perform the same tasks using the Cloud version or you need to ask the Cloud vendor to perform some services for you. This will be at a cost so make sure you know what it is beforehand.  There are some administrator functions you will probably be glad to outsource to the Cloud vendor such as maintaining the server and SQL Server and taking and verifying backups.

I would assume that the decision to move a records management application to the Cloud would and should involve the application owner and IT management. The application owner has to be satisfied that the end-user experience will be better or at least equal to that of the in-house installation and IT management needs to be sure that the integrity and security of the Cloud application will at the very least be equal to that of the in-house installation. And finally, the application owner, the records manager, needs to be satisfied that the IT support from the vendor of the Cloud system will be equal to or better than the IT support being received from the in-house or currently out-sourced IT provider.

There is no point in moving to the Cloud if the end-user or administrator experience will deteriorate just as there is no point in moving to the Cloud if the level of IT support falls.

Once you have made the decision to move your records management application to the Cloud you need to plan the cutover in a way that causes minimal disruption to your operation. Ideally, your staff will finish work on the in-house application on Friday evening and begin working on the Cloud version the next Monday morning. You can’t afford to have everyone down for days or weeks while IT specialists struggle to make everything work to your satisfaction. This means you need to test the Cloud system extensively before going live in production. In this business, little or no testing equals little or no success and a great deal of pain and frustration.

If it was me, I would make sure that the move to the Cloud meant improvements in all facets of the operation. I would want to make sure that the Cloud vendor took on the less pleasant, time-consuming and technical tasks like managing and configuring the required IT infrastructure. I would also want them to take on the more bothersome, awkward and technically difficult application administration tasks. Basically, I would want to get rid of all the pain and just enjoy the benefits.

You should plan to ‘outsource’ all the pain to make your life and the life of your staff easier and more pleasant and in doing so, make everyone more productive. It is like paying an expert to do your tax return and getting a bigger refund. The Cloud solution must be presented as a value proposition. It should take away all the non-core activities that suck up your valuable time and allow you and your staff more time to do the core activities in a better and more efficient way; it should allow you to become more productive.

I am a great believer in the Cloud as a means of improving productivity, lowering costs and improving data integrity and security. It is all doable given available facilities and technology but in the end, it is up to you and your negotiations with the Cloud provider.  Stand firm and insist that the end result has to be a better solution in every way; compromise should not be part of the agreement.