Cloud ERP Feasibility Analysis for Multi-Site Hydraulic Servicing Business

HA2042 – Accounting Information Systems

Assessment Task 2: Feasibility Study Report

Weighting: 25% of total course grade (20 marks for written report + 5 marks for group presentation)
Due Date: 5:00 PM Friday, Week 11
Submission: Via Blackboard Turnitin (written report) and Blackboard Groups (group evaluation form by Week 12)
Word Count: 2,500–3,000 words (excluding executive summary, tables, references, and appendices)
Format: Business report format, 12pt font, 1.5 line spacing, APA 7th Edition referencing

Assessment Overview

This assessment requires you to conduct a comprehensive feasibility study for Pressure Hydraulics, a multi-site hydraulic servicing business seeking to modernise its accounting information systems and operational processes. You will apply the TELOS framework (Technical, Economic, Legal, Operational, and Schedule feasibility) alongside contemporary cloud-based ERP evaluation methodologies to develop evidence-based recommendations for system implementation.

The case study involves a business with three existing service centres (Newcastle, Toronto, and Maitland) planning expansion to Coffs Harbour and Gosford, with future east coast growth ambitions. Your analysis must address critical pain points including manual inventory management, outdated pricing systems, inefficient payroll processing, and lack of real-time financial visibility across distributed locations.

Learning Outcomes Assessed

  • LO2: Analyse business processes and identify opportunities for AIS enhancement
  • LO3: Evaluate alternative accounting information system solutions using established frameworks
  • LO4: Develop feasibility assessments incorporating technical, economic, and operational considerations
  • LO5: Communicate professional recommendations supported by evidence-based reasoning

Case Study Context: Pressure Hydraulics

Pressure Hydraulics operates as a decentralised business with independent service centres. Current workflows rely heavily on manual documentation including hard-copy Price Books, handwritten Works Books for scheduling, and paper-based Job Cards. The owner, Allan Taylor, currently spends significant time travelling between sites for monitoring, leaving limited capacity for strategic business development.

Key operational challenges include:

  1. Delayed price updates in hard-copy Price Books leading to revenue loss or missed sales opportunities
  2. Manual Works Book scheduling causing overbooking, idle capacity, and customer miscommunication
  3. Discrepancies between quoted and invoiced amounts due to outdated pricing data
  4. Incorrect component selection for mining industry services resulting in costly return trips and client relationship damage
  5. Fortnightly manual payroll preparation requiring extensive staff time verification
  6. Daily banking reconciliation delays creating cash flow visibility gaps

Allan has identified specific system requirements including centralised stock ordering across all locations, real-time inventory visibility, automated invoice generation, integrated payroll with direct banking, customer relationship tracking for retention marketing, and simultaneous price updates across all service centres.

Your Task

Prepare a professional feasibility study report that evaluates potential accounting information system solutions for Pressure Hydraulics. Your report must demonstrate understanding of SME cloud ERP implementation challenges while addressing the specific technical and operational requirements outlined in the case study.

Required Report Sections

  1. Executive Summary (approximately 250 words)
    • Concise overview of the business problem, proposed solution approach, key findings, and primary recommendation
    • Stand-alone section that provides decision-makers with essential information without reading the full report
  2. Description of the Problem (approximately 400 words)
    • Analysis of current business processes and their limitations
    • Identification of specific pain points across inventory management, pricing, scheduling, payroll, and financial reporting
    • Quantification of business impact where possible (lost revenue, inefficiency costs, opportunity costs)
    • Risk assessment of maintaining current systems versus implementing change
  3. Solution Objectives (approximately 300 words)
    • Clear articulation of functional requirements derived from Allan’s stated needs
    • Alignment of system capabilities with business expansion plans
    • Specific, measurable objectives for the proposed AIS implementation
    • Critical success factors for system selection
  4. Constraints (approximately 200 words)
    • Technical constraints (existing infrastructure, connectivity requirements, hardware limitations)
    • Economic constraints (budget considerations, ROI expectations, cash flow impacts)
    • Organisational constraints (staff capabilities, change readiness, training capacity)
    • Regulatory constraints (Australian tax compliance, data protection, industry-specific requirements)
  5. Development Plans (approximately 400 words)
    • Phased implementation strategy appropriate for multi-site rollout
    • Project timeline with key milestones from requirements gathering to full deployment
    • Resource requirements (internal staff, external consultants, vendor support)
    • Risk mitigation strategies for implementation phases
    • Change management considerations for staff transition
  6. Potential Solutions (approximately 500 words)
    • Evaluation of at least two distinct AIS alternatives (e.g., cloud-based ERP vs. modular best-of-breed approach)
    • Application of the TELOS framework to each alternative
    • Comparison of vendor options relevant to Australian SME market (e.g., Xero, MYOB, QuickBooks, industry-specific solutions)
    • Analysis of how each solution addresses the specific requirements for inventory management, mobile field service, payroll integration, and multi-site coordination
  7. Recommendations (approximately 400 words)
    • Clear statement of preferred solution with justification
    • Implementation roadmap with prioritised phases
    • Expected benefits including quantitative estimates where feasible
    • Critical success factors and ongoing monitoring requirements
    • Contingency planning for identified risks

Appendices Requirements

Include supporting documentation such as:

  • Vendor comparison matrices or feature checklists
  • Pricing research from software providers (screenshots or quotations)
  • Technical architecture diagrams (if applicable)
  • Sample implementation timelines
  • Reference materials supporting your TELOS analysis

Marking Criteria and Rubric

Criterion Marks Standards
Executive Summary 2 Distinction (1.7–2.0): Concise, comprehensive overview capturing all critical elements; stands alone effectively; demonstrates sophisticated understanding of decision-maker needs
Credit (1.3–1.6): Clear summary covering main points with minor omissions
Pass (1.0–1.2): Adequate summary but lacks depth or clarity
Fail (0–0.9): Missing, incomplete, or poorly structured
Problem Description 3 Distinction (2.5–3.0): Thorough analysis of current systems; clear quantification of business impact; insightful risk assessment; demonstrates deep understanding of operational workflows
Credit (2.0–2.4): Good analysis with some quantification; identifies key issues
Pass (1.5–1.9): Basic description of problems; limited analysis
Fail (0–1.4): Superficial or inaccurate problem identification
Solution Objectives 3 Distinction (2.5–3.0): SMART objectives aligned with business strategy; comprehensive coverage of functional requirements; clear linkage to case study needs
Credit (2.0–2.4): Clear objectives with good alignment to requirements
Pass (1.5–1.9): Adequate objectives but lacking specificity or completeness
Fail (0–1.4): Vague, irrelevant, or missing objectives
Constraints 1 Distinction (0.9–1.0): Comprehensive constraint analysis across all TELOS dimensions; realistic assessment of limitations
Credit (0.7–0.8): Good coverage of major constraints
Pass (0.5–0.6): Basic identification of obvious constraints
Fail (0–0.4): Minimal or missing constraint analysis
Development Plans 3 Distinction (2.5–3.0): Detailed, realistic implementation strategy; appropriate phasing for multi-site rollout; comprehensive risk mitigation; strong change management consideration
Credit (2.0–2.4): Good implementation plan with clear milestones
Pass (1.5–1.9): Basic timeline with limited detail
Fail (0–1.4): Unrealistic, vague, or missing development plan
Potential Solutions 2 Distinction (1.7–2.0): Rigorous TELOS application; thorough vendor evaluation; clear differentiation between alternatives; evidence-based comparison
Credit (1.3–1.6): Good evaluation with clear comparison criteria
Pass (1.0–1.2): Adequate description of alternatives but limited evaluation depth
Fail (0–0.9): Single solution presented or superficial analysis
Recommendations 2 Distinction (1.7–2.0): Clear, justified recommendation; realistic implementation roadmap; quantified benefits; comprehensive contingency planning
Credit (1.3–1.6): Clear recommendation with good justification
Pass (1.0–1.2): Recommendation stated but with limited support
Fail (0–0.9): Missing, unclear, or unsupported recommendation
Presentation and Clarity 2 Distinction (1.7–2.0): Professional business report format; excellent structure and flow; flawless referencing; high-quality appendices
Credit (1.3–1.6): Well-presented with minor formatting or referencing issues
Pass (1.0–1.2): Adequate presentation with some errors
Fail (0–0.9): Poor formatting, structure, or referencing
Logic and Evidence of Research 2 Distinction (1.7–2.0): Strong logical flow throughout; extensive research evident; current sources (2018–2026); appropriate application of AIS theory and frameworks
Credit (1.3–1.6): Good logical structure with solid research base
Pass (1.0–1.2): Adequate research with some logical gaps
Fail (0–0.9): Limited research, poor logic, or outdated sources
Total 20

Sample Answer Guide: Executive Summary

Pressure Hydraulics currently operates with fragmented manual systems across three service centres, creating significant inefficiencies in inventory management, pricing accuracy, and payroll processing that constrain owner Allan Taylor’s capacity for strategic business development. This feasibility study evaluates cloud-based ERP solutions capable of supporting multi-site coordination, real-time inventory visibility, and integrated financial management essential for planned expansion to Coffs Harbour and Gosford. Through application of the TELOS framework, this report assesses two primary alternatives: a comprehensive cloud ERP solution (Xero or MYOB with integrated field service modules) versus a modular approach combining best-of-breed applications. Analysis indicates that a cloud-based ERP system with mobile inventory management capabilities, automated payroll integration, and centralised customer relationship management will deliver operational efficiencies valued at approximately $45,000 annually while enabling scalable growth. The recommended solution involves phased implementation commencing with Newcastle and Toronto sites, followed by Maitland and new locations, with full deployment achievable within six months. Critical success factors include staff training investment, data migration quality, and vendor support commitment. Implementation requires capital expenditure of $35,000–$50,000 with projected payback period of 14–18 months based on labour savings and revenue protection from improved pricing accuracy.

Recent research on AIS implementation in SMEs emphasises that compatibility with existing workflows represents the strongest predictor of successful adoption, suggesting Pressure Hydraulics should prioritise solutions offering configurable workflows that mirror current Job Card and Works Book processes during initial transition phases. Studies indicate that external competitive pressure and top management support substantially influence implementation outcomes, positioning Allan Taylor’s direct involvement as a critical success factor for this project. The integration of cloud-based payroll with automated superannuation compliance and single-touch payroll reporting has become standard practice for Australian SMEs, with platforms like Xero and MYOB now offering real-time labour costing capabilities that directly address Pressure Hydraulics’ fortnightly manual payroll burden. Furthermore, mobile service inventory systems demonstrate proven efficacy in field technician environments, with research showing significant improvements in first-time fix rates when technicians maintain accurate vehicle stock visibility through smartphone applications.

Students approaching this assessment should recognise that feasibility studies require balanced evaluation rather than predetermined conclusions; while cloud ERP solutions offer compelling integration benefits, they may present operational challenges during transition periods that warrant careful risk assessment. Common misconceptions include assuming that technology alone resolves process issues without accompanying workflow redesign, or underestimating the change management required for field technicians accustomed to paper-based Job Cards. When evaluating vendor solutions, consider not only current pricing but data portability and exit costs, as SMEs frequently face migration challenges when scaling beyond initial SaaS platform capabilities. The TELOS framework should be applied rigorously rather than as a checklist; for instance, operational feasibility demands honest assessment of staff digital literacy across all three current sites, while economic feasibility requires modelling both best-case and conservative scenarios for revenue protection through pricing accuracy improvements.

References

Alshirah, M., Alshirah, A., Lutfi, A., & Al-Khasawneh, A. L. (2022). Business sustainability of small and medium enterprises during the COVID-19 pandemic: The role of AIS implementation. Sustainability, 14(9), 5362. https://doi.org/10.3390/su14095362

Hall, J. A. (2011). Accounting information systems (8th ed.). Cengage Learning.

Lee, C., Kim, H. F., & Lee, B. G. (2024). A systematic literature review on the strategic shift to cloud ERP: Leveraging microservice architecture and MSPs for resilience and agility. Electronics, 13(14), 2885. https://doi.org/10.3390/electronics13142885

Lutfi, A., Alshirah, M. H., & Alshirah, A. F. (2024). Evaluating AIS implementation to improve accounting information quality: The prospect in Jordanian family SMEs in the post-Covid-19 age. Journal of Family Business Management. https://doi.org/10.1108/JFBM-08-2024-0194

Zhang, L., Chen, Y., & Wang, X. (2022). Informatization of accounting systems in small- and medium-sized enterprises based on artificial intelligence-enabled cloud computing. Wireless Communications and Mobile Computing, 2022, Article 6089195. https://doi.org/10.1155/2022/6089195

  1. HA2042 Accounting Information Systems Assignment 2 Pressure Hydraulics Feasibility Study 2026
  2.  Write a 2,500–3,000-word feasibility study report for HA2042 Accounting Information Systems evaluating cloud ERP solutions for Pressure Hydraulics multi-site hydraulic servicing business. Apply TELOS framework to analyse technical, economic, legal, operational, and schedule feasibility for inventory management, payroll integration, and pricing system modernisation. Submit via Blackboard by Week 11.

Compose a 10–12 page business report assessing accounting information system alternatives for an expanding hydraulic service company with three existing and two planned locations. Evaluate cloud-based ERP solutions using established feasibility frameworks, develop implementation recommendations, and support analysis with current vendor research and academic sources.

Complete a professional feasibility study analysing AIS solutions for Pressure Hydraulics, applying the TELOS framework to evaluate technical capabilities, economic viability, and operational fit for multi-site cloud ERP implementation supporting business expansion.

 

Assessment: HA2042 Assessment Task 3

Week 12–13: System Design Documentation and Risk Assessment

Building upon your feasibility study recommendations, Assessment Task 3 requires you to develop detailed system design documentation for your recommended AIS solution. You will create data flow diagrams (DFD) for the proposed inventory management and payroll processes, design database schema for customer and stock management, and conduct a comprehensive risk assessment addressing cybersecurity, data integrity, and business continuity considerations. The assessment includes a 15-minute individual presentation defending your design decisions against alternative approaches, with submission due Week 13. This task evaluates your ability to translate feasibility recommendations into implementable technical specifications while demonstrating understanding of internal controls and information security requirements for distributed business operations.