Spreadsheet Woes – Limited Features For Easy Adoption of a Control Framework

Like it or not, regulations are here to stay and for a company to comply with them, its IT and financial systems will have to be equipped with a suitable control framework. One common stumbling block to such an implementation is a company?s over-reliance on spreadsheets.

Why is it so difficult to adopt controls for a system that’s reliant on spreadsheets? To understand this, let’s pinpoint some of the strongest, most powerful attributes of these User Developed Applications (UDA).

By nature, spreadsheets are the epitome of simplicity: easy to develop, easily accessible and easily altered. All computers in your workplace will most likely have them and everyone in your organization may be sharing them, making their own versions, and storing them in personal folders.

Sad to say though, these strengths are also control weaknesses and constitute the very reasons why spreadsheets require effective risk management.

Easy to develop. Being easy to develop, most spreadsheet systems are created by non-IT users who have limited knowledge on best control practices. Being constantly under time pressure, these ?developers? may also relegate documentation, security, and data verification to the back burner in favour of coming up with a timely report.

Easy to access. Information in a spreadsheet can be opened by practically anyone within the organization?s network. Who accessed what? And when? If anything goes wrong, it would be difficult to identify the culprit, and the failure to pinpoint responsibility for erroneous data could lead to bigger, more costly mistakes.

Easy to alter. Lastly, if the information is easy to access, then it can also be easily altered, consequently making reports more prone to both accidental errors and fraudulent modifications.

The rise of multimillion dollar scandals due to accidental and intentional spreadsheet errors have prompted regulatory bodies to publish guidelines for mitigating spreadsheet-associated risks. These controls include:

Change control
Version control
Access control
Input
Security and data integrity
Documentation
Development life cycle
Backup and archiving
Logic inspection/Testing
Segregation of duties/roles, and procedures
Analytics

In theory, these controls should be able to bring down risks considerably. However, because of the inherent nature of spreadsheets, such controls are rarely implemented effectively in the real world.

Take for example Security and Data Integrity. One of the most common causes of spreadsheet error is due to ?hardwiring?. This happens when values are inadvertently entered into a formula cell, naturally changing the logic of the spreadsheet.

As a way of control, cell locking can be applied on the formula cells to prevent users without the proper authority from making any changes. However, when reporting deadlines approach drawing spreadsheets to the forefront of data processing, more people are given access rights to the locked cells. Ironically, it is during these crunch times, when errors are most likely to happen.

Because the built-in features of a spreadsheet support none of the controls mentioned above, some companies are tempted to purchase control-enabling programs for spreadsheets just to continue using them for financial reporting. But although these programs can integrate the required controls, you?d still be interacting with the same complex and outdated interface: the spreadsheets.

Thus, these band-aid solutions may not suffice because the root cause of these problems are the spreadsheets themselves.

Learn more about our server application solutions and discover a better way to implement controls.

More Spreadsheet Blogs

Spreadsheet Risks in Banks

Top 10 Disadvantages of Spreadsheets

Disadvantages of Spreadsheets – obstacles to compliance in the Healthcare Industry

How Internal Auditors can win the War against Spreadsheet Fraud

Spreadsheet Reporting – No Room in your company in an age of Business Intelligence

Still looking for a Way to Consolidate Excel Spreadsheets?

Disadvantages of Spreadsheets

Spreadsheet woes – ill equipped for an Agile Business Environment

Spreadsheet Fraud

Spreadsheet Woes – Limited features for easy adoption of a control framework

Spreadsheet woes – Burden in SOX Compliance and other Regulations

Spreadsheet Risk Issues

Server Application Solutions – Don’t let Spreadsheets hold your Business back

Why Spreadsheets can send the pillars of Solvency II crashing down

amazon.co.uk

amazon.com

Check our similar posts

The Connection Between Six Sigma and CRM

Six Sigma is an industrial business strategy directed at improving the quality of process outputs by eliminating errors and system variables. The end objective is to achieve a state where 99.99966% of events are likely to be defect free. This would yield a statistical rating of Sigma 6 hence the name.

The process itself is thankfully more user-friendly. It presents a model for evaluating and improving customer relationships based on data provided by an automated customer relations management (CRM) system. However in the nature of human interaction we doubt the 99.99966% is practically achievable.

Six Sigma Fundamentals

The basic tenets of the business doctrine and the features that set off are generally accepted to be the following:

Continuous improvement is essential for success

Business processes can be measured and improved

Top down commitment is fundamental to sustained improvement

Claims of progress must be quantifiable and yield financial benefits

Management must lead with enthusiasm and passion

Verifiable data is a non-negotiable (no guessing)

Steps Towards the Goal

The five basic steps in Six Sigma are define the system, measure key aspects, analyse the relevant data, improve the method, and control the process to sustain improvements. There are a number of variations to this DMAIC model, however it serves the purpose of this article. To create a bridge across to customer relationships management let us assume our CRM data has thrown out a report that average service times in our fast food chicken outlets are as follows.

<2 Minutes	3 to 8 Minutes	9 to 10 Minutes	>10 Minutes
45%	30%	20%	5%
Table: Servicing Tickets in Chippy?s Chicken Caf?s

Using DMAIC to unravel the reasons behind this might proceed as follows

Define the system in order to understand the process. How are customers prioritised up front, and does the back of store follow suit?

Break the system up into manageable process chunks. How long should each take on average? Where are bottlenecks most likely to occur?

Analyse the ticket servicing data by store, by time of day, by time of week and by season. Does the type of food ordered have a bearing?

Examine all these variables carefully. Should there for example be separate queues for fast and slower orders, are there some recipes needing rejigging

Set a goal of 90% of tickets serviced within 8 minutes. Monitor progress carefully. Relate this to individual store profitability. Provide recognition.

Conclusion

A symbiotic relation between CRM and a process improvement system can provide a powerful vehicle for evidencing customer care and providing feedback through measurable results. Denizon has contributed to many strategically important systems.?

Contact Us

(+353)(0)1-443-3807 – IRL
(+44)(0)20-7193-9751 – UK

How DevOps Could Change Your Business

Henry Ford turned the U.S. auto industry on its head when he introduced the idea of prefabricating components at remote sites, and then putting them together on a production line. Despite many industries following suit, software lagged behind until 2008, when Andrew Clay Shafer and Patrick Debois told the Agile Conference there was a better way to develop code:
– Write the Code
– Test the Code
– Use the Code
– Evaluate, Schedule for Next Review

The term ?DevOps? is short for Development and Operations. It first appeared in Belgium, where developers refined Shafer and Depois? ideas. Since then, DevOps became a counter movement against the belief that software development is a linear process and has largely overwhelmed it.

DevOps – A Better Way

DevOps emerged at an exciting time in the IT industry, with new technology benefiting from a faster internet. However, the 2008 world recession was also beginning to bite. Developers scampered to lower their human resource costs and get to market sooner.

The DevOps method enabled them to colloborate across organizational boundaries and work together to write, quality assure and performance test each piece of code produced in parallel.
DevOps? greater time-efficiency got them to market sooner and helped them steal a march on the competition.

There are many advantages to DevOps when we work in this collaborative way. Cooperation improves relationships between developers, quality assurers and end users. This helps ensure a better understanding of the other drivers and a more time-effective product.

Summary of DevOps Objectives

DevOps spans the entire delivery pipeline, and increases the frequency with which progress is reviewed, and updates are deployed. The benefits of this include:

? Faster time to market and implementation

? Lower failure rate of new releases

? Shortened lead time for bug fixes and updates

The Psycho-Social Implications of DevOps

DevOps drills through organization borders and traditional work roles. Participants must welcome change and take on board new skills. Its interdepartmental approach requires closer collaboration across structural boundaries and greater focus on overarching business goals.

Outsourcing the detail to freelancers on the Internet adds a further layer of opportunity. Cultures and time zones vary, requiring advanced project management skills. Although cloud-based project management software provides adequate tools, it needs an astute mind to build teams that are never going to meet.

The DevOps movement is thus primarily a culture changer, where parties to a project accept the good intentions of their collaborators, while perhaps tactfully proposing alternatives. There is more to accepting a culture than using a new tool. We have to blend different ways of thinking together. We conclude by discussing three different methods to achieve this.

Three Ways to Deploy DevOps in your?Organisation

If you foresee regular DevOps-based projects, consider running your entire organisation through an awareness program to redirect thinking. This will help non-participants understand why DevOps members may be ?off limits? when they are occupied with project work. Outsourcing tasks to contracting freelancers can mitigate this effect.

There are three implementation models associated with DevOps although these are not mutually exclusive.

? Use systems thinking. Adopt DevOps as company culture and apply it to every change regardless of whether the process is digital, or not

? Drive the process via increased understanding and feedback from key receivers. Allow this to auto-generate participative DevOps projects

? Adopt a continuous improvement culture. DevOps is not only for mega upgrades. Feedback between role players is paramount for success everywhere we go.

You can use the DevOps concept everywhere you go and whenever you need a bridge to better understanding of new ideas. We diminish DevOps when we restrict its usefulness to the vital role it plays in software development. The philosophy behind it belongs in every business.

Proactive Preventative Maintenance: How IoT and Field Service Management Software Helps

FieldElite, our mobile workforce management software, has been key to several industries? return on investment. Whether it’s for plumbing, electrical, property management, cleaning, and maintenance, FieldElite has provided data centralisation for efficient management of these business activities.

Field service management software is important to utilise current workload, and also helps resolve future issues. We’re talking about a proactive approach to preventative maintenance.

How exactly do field service managements help in preventative maintenance?

The answer lies in how field service management is interlinked with IoT in predicting future jobs for the mobile service industry.

What is IoT?

Simply put, the Internet of Things (IoT) is a network of devices and sensors connected to the internet. These ?things? (e.g. your smartphone or smartwatch) enable data to be sent and be received without human intervention.

Fundamentally, IoT is about devices being connected to the internet to allow remote monitoring.

For many years now, remote monitoring for IT infrastructure has been widely used.

What’s new that we’re experiencing right now is even the smallest devices ? individual light bulbs and sensors ? can have a network and internet connection, allowing entire systems to be monitored in great detail.

Implementing IoT and accessing data can be challenging for most service organisations. However, when combined with predictive analytics and field management software, it can have a huge potential impact on individual businesses and the service industry as a whole.

What is Preventative Maintenance?

Preventive maintenance refers to regular, routine maintenance to help keep equipment up and running, preventing any unplanned downtime and expensive costs from unanticipated equipment failure.

The goal of preventative maintenance is to decrease the likelihood of a machine or an equipment’s failure by performing regular maintenance.

Preventative management can be very complex, especially for companies with a fleet of equipment or customers. It requires careful planning and scheduling of maintenance on equipment before there is an actual problem.

Also, preventive maintenance is evolving. It’s not just about scheduling the same work every month to prevent failure anymore. Today, working smarter with better information about equipment conditions is critical to ensure maintenance is effective.

That’s where IoT and field service management software, like FieldElite, comes in. Together, they organise and carry out preventive maintenance needs for service industries.

How IoT and FieldElite Helps in Preventative Maintenance

With FieldElite and IoT technology, you get the best in preventive maintenance management.

Evaluation of equipment or machines ? the condition of machines or equipment is evaluated in order to predict when maintenance needs to be performed.
Automated work order ? automated time-based work order creation
Full condition-based plans allows you to do the following:
- Right-size your maintenance work
- Lower costs
- Extend the life of your or customer?s assets

Quicker reporting ? due to its efficient and automated nature, IoT and field service management software can reduce a field technician?s average report time from two weeks to two days, therefore boosting your cash flow!

That’s the most important result a mobile service management software can produce (in connection with preventative maintenance). It’s cost-saving! This can be achieved over routine or time-based preventive maintenance, as tasks are only performed when they are needed.

The Internet of Things (IoT) and field service management software is changing field service as we know it.

Companies who adapt and utilise these technologies will benefit the most from the resulting competitive advantage of preventative maintenance.

Start elevating every field service experience now!

Our field service software, FieldElite helps you:

Accepts jobs in the field
Automate appointment scheduling
Manage scheduled jobs
Get real-time visibility into all operations
Have a clear and easy viewing of job locations
Resolve field service calls faster
Enable mobile workers to get the job done right
Keep customers updated at every step
Create quotations and accept payments
Analyse efficient reports from field technicians
Helps in proper preventative maintenance management.

Learn how to schedule jobs to field workers with ease. Check out FieldElite!

CONTACT US

We seek to understand your technology and business challenges
We tailor a demonstration of our platform and solutions to align to your specific needs
We answer any questions and make sensible recommendations

(+353)(0)1-443-3807 – IRL
(+44)(0)20-7193-9751 – UK