i-Tree Continuing Operations

Integration of new science (e.g. growth equations), new background data (e.g. weather), etc. into existing software. Continuing software development due to desktop/server software changes and bug reports. Routine server operations. Ongoing maintenance of all platforms. The tasks below are critical for day-to-day operations, or “keeping the lights on” for continuing delivery of the current version of i-Tree via all the associated tools and Support mechanisms. i-Tree consists of 6 core tools, 10 supporting tools, and 3 research tools with live Support.

Online Tool Servers (four physical and seven virtual servers)

  • Why: Required systems administration to keep all i-Tree tools functional.
  • Completion Date: Year-round tasks.
  • Outcomes/Impacts: Meet increasing demand of increasing usership.
  • Addressing a request(s): Keep the tools functioning in a performant and reliable manner.
  • Examples:
    • We employ a dedicated processing server for i-Tree Eco calculations; after 12 years, its disks and fans have begun to fail.
    • Ongoing Linux and Windows Operating System updates and security patches.
    • Regular memory and disk glitches to which all servers are prone.
  • Planned work:
    • Application dependency audits & updates (Django, etc.), stack & geospatial stack reconciliation (GDAL, etc.), development environment version upgrades (Python, etc.)
    • Multi-year operating system version progression testing & planning to avoid security issues (CentOS 7 to Rocky 8, etc.).
    • Multi-year hardware coordination and progression planning
    • Container cluster management and upgrades (Docker, etc.)
    • Open-Source service upgrades (GeoServer, etc.)
    • On demand security alert responses for new vulnerabilities (“log4j”, etc.)
    • On demand outage responses due to power failure, internet outage, and device restarts
    • Backups for servers and applications (content and source code)
    • Hosting (currently provided free of charge by Davey Corporate IT - no costs billed to date). Auxiliary diesel power generator; inbound/outbound internet access; domain registration management; credit-card level security implementation; regular penetration testing. Our online growth has added a notable burden as these types of IT services have increased in cost for Davey.
    • Gradual migration of on-premise virtual servers to cloud-based architecture.
    • Research and implement software/hardware updates & coordinate with developers.
    • Plan and manage additional server capacity (new servers, cloud services).

Online Databases (these serve Eco, Hydro, and all online tools)

  • Why: Background data that drives all of i-Tree; example: pollution rates by location.
  • Completion Date: Year-round tasks.
  • Outcomes/Impacts: Expansion and updates of i-Tree.
  • Addressing a request(s): Steady requests for more current data to derive more current tree benefits and new locations.
  • Planned work:
    • On demand USFS data additions and revisions
    • Weekly backups and on demand restoration from such
    • Yearly infrastructure upgrades (PostgreSQL, MySQL, etc.)

i-Tree Engine Software (this serves all online tools)

  • Why: This is the server-side calculation programming for most i-Tree online tools.
  • Completion Date: Year-round tasks.
  • Outcomes/Impacts: Performance improvement and scientific updates.
  • Addressing a request(s): Increased i-Tree usership and USFS Northern Research Unit science changes
  • Planned work:
    • Horizontal scaling of input, processing, database, and response layers
    • Maintain correctness with i-Tree Eco while enhancing features available.
    • Vertical scaling through refactoring of data bottlenecks

i-Tree Engine

  • Why: Steady improvement in translation of the science and calculations from i-Tree Eco flagship to the online environment.
  • Completion Date: Ongoing: dependent on USFS research outcomes and resource allocations with regard to work on other tools, work plan priority changes, activities (townhalls, etc.) and unforeseen events (server crashes, etc.)
  • Outcomes/Impacts: Improved performance of most online i-Tree tools.
  • Addressing a request(s):
  • Planned work:
    • New state/primary boundary layer to add to Landscape's Location API
    • Single call of database queries
    • Adjust for any new USFS Science changes to i-Tree Eco
    • Add benefit adjustments for urban, rural, and mixed delineations

Online Tools Software Updates (tool software code)

  • Why: Regular updates to individual online tools’ programming.
  • Completion Date: Monthly updates throughout the year.
  • Outcomes/Impacts: Smooth operation and user experience.
  • Addressing a request(s): Required by non-stop changes in device and web browsers.
  • Planned work:
    • On demand, emergent compatibility issues due to third party device and web browser changes beyond our control (AKA externally induced “bugs”)
    • Begin research on cloud-based hosting
    • Example: Adobe removes all support for their "Flash" plugin in 2020; i-Tree Design reports must be reprogrammed with a modern alternative.