Balance the needs of users who want to keep their data as private as possible, and the larger organization that would like to use this data for analysis, while staying within the legislative boundaries.
Health and safety in the workplace is an issue which concerns most employers, small and large. Legislation is in place to ensure workplace incidents are recorded and reported and employers and employees are supported, both practically and financially. In order to comply with this, companies need to keep clear records and, as these systems often contain personal and confidential data, such as social security numbers and personal health information, it is vital that system access is tightly secured. The Parklane solution is a system customers can trust; one that keeps this data organized, safe and in one place. In addition, there is the comfort of knowing data is protected against unauthorized access and inadvertent data corruption which is common in spreadsheets.
Balancing the needs of a user who wants to keep their data as private as possible, and the larger organization that would like to use this data for analysis, while staying within the legislative boundaries, is a challenge Parklane was looking to solve, as Lee Males, Executive Vice President at Parklane, explains: “Our solution is designed so that one version satisfies all the market segments we service: different government departments; healthcare organizations; education; manufacturing companies etc. While we provide thousands of standard reports within our application, we found that customers would also like the ability to prepare their own custom-made reports through tools such as SAP Crystal or Cognos. It would give them control over their own data and the ability to use the data set in different ways.”
He adds: “We deduced that a relational database would serve these needs. Our application is RM/COBOL-developed, using traditional data files, and we looked at rewriting this to a relational dataset to satisfy our reporting needs. With hundreds of programs included in our application, we estimated it would take four developers four years to complete the reengineering work required. Our RM/COBOL platform is very stable and we really don’t want to put customers through a major conversion so we looked for an alternative solution.”