Laserfiche WebLink
What should CAMAS be? <br />The process of removing functfonality from CAMAS has already begun. Not because it's part of this plan but because we <br />already see the advantage of moving some features to more modern, commercial off-the-shelf software. Business decisions <br />or security and performance of the current feature is compromised to the point that immediate replacement is required. <br />However, contfnuing to reshape our intranet without a plan will eventually risk replacing CAMAS with something we don't <br />want or need. IT strongly believes that involvement by a representatfve group of stakeholders, actfng to advise us in <br />developing a new intranet site is vitally important. <br />Intranet Advisory Committee Concept <br />Purpose: <br />The Intranet Advisory Committee (IAC) is established to provide guidance, recommendatfons, and insights to the IT <br />department regarding the purpose, design, and functfonality of the organizatfon’s future intranet site. The committee will <br />ensure that the intranet meets the diverse needs of all departments, enhances communicatfon, and improves overall <br />efficiency and user experience. <br />Objectives: <br />1. Needs Assessment: Identffy and document the needs and expectatfons of various departments and staff <br />members regarding the intranet. <br />2. Design Input: Provide recommendatfons on the design, structure, and user interface of the intranet to ensure it <br />is user-friendly and effectfve. <br />3. Feature Recommendations: Suggest features and functfonalitfes that should be included to enhance <br />productfvity and collaboratfon. <br />4. Feedback Mechanism: Establish a process for ongoing feedback from staff to contfnuously improve the intranet. <br />5. Adoption and Training: Develop strategies to promote intranet adoptfon and provide training resources to staff. <br />Why is modernizing the County's intranet necessary? <br />CAMAS is built on an aging applicatfon framework which offers many challenges to our organizatfon. <br />• Performance Issues: The existfng ASP.NET applicatfon targetfng .NET 4.7 may suffer from slower load tfmes and <br />less optfmized performance, negatfvely impactfng the user experience. <br />• Security Vulnerabilities: Older platiorms like .NET 4.7 may not receive regular security updates, leaving the <br />intranet site more susceptfble to cyberattacks and security breaches. <br />• Maintenance Challenges: Maintaining and updatfng a legacy system can be more complex and tfme-consuming, <br />as it may lack the support and resources available for newer technologies. <br />• Developer Productivity: The outdated tech stack may hinder developer productfvity due to less efficient tooling, <br />limited libraries, and outdated development practfces. Integration Difficulties: Integratfng the current intranet <br />site with modern tools and services can be challenging, limitfng the functfonality and effectfveness of the <br />applicatfon. <br />• User Experience Constraints: The older framework may not support dynamic and responsive web design as <br />effectfvely, leading to a subpar user experience. <br />• Future Risks: Contfnuing to rely on an outdated technology stack risks the applicatfon becoming increasingly <br />irrelevant and unable to adapt to future technological advancements and business needs.