THE APPLE TRACK

ERBy: Benjamin Krause, Debbie Russell,

Greg Williams, Jongmin Lee, & Jeewon Moon

OUTLINE Project Introduction, Objective &

Background Details of Tasks Future Plans for Project Recommendations Conclusion Question

TEAM MEMBERS

Benjamin KrauseDebbie RussellGreg WilliamsJongmin LeeJeewon Moon

INTRODUCTION, OBJECTIVE & BACKGROUND

Introduction:Small scale fruit/vegetable producers have limited

options to convenient production/inventory managing tools

Objective:Create a small ERP system for small

fruit/vegetable producers, helping to manage inventory, starting from the time the crop is picked all the way until it is sold.

Background:Ben has worked for an apple orchard for the past

11 years.

APPLE TRACKER PROCESS

Send Bins to Field (1)

Field (2)

Send Bins to Cooler (3)

Grade & Package (4)

SYSTEM VISION DOCUMENT

INTRODUCTION &PROBLEM DESCRIPTION

IntroductionFruit/Vegetable Market –many small

operatorsMost serve local communitiesSocietal shift toward local/organic produce

= growth for this market Problem Description

Traceability of cropsNeed to be more efficient

SYSTEM CAPABILITIESBUSINESS MODEL

System Capabilities Collecting and storing information about Apple Bins/Apple

Variety Tracking Bins using a barcode/scanner system Sorting and grading, including waste measurement,

management, and complex assignment of produce properties Easily move fresh produce between cool rooms Minimizing waste and shrinkage using the new inventory

process system

Business Model Charge the customer a license fee, which may include a set number

of hours of support, and some minor customization modifications Charge the customer a developer fee, which will allow their IT

personnel to make changes to the system. Charge the customer a license fee, with an additional fee charged at

cost plus reasonable profit, for customization beyond simple replacing of logos or names

BUSINESS BENEFITS

Short Term immediate knowledge of quantities available for sale,

cider-making increased ability to project profits and available cash

Long Term monitor health of trees by tracking yearly yields track which varieties produce/sell better experimenting with different care methods to see which

produces best yield

STAKEHOLDERS Internal:

Debbie Russell Greg Williams Ben Krause Jongmin Lee Jeewon Moon Orchard Owner Manager

External: None

Operational: Manager Apple Graders

Executive: Orchard Owner

FURPS+

FUNCTIONAL REQUIREMENTS Bin tracking include:

number of bins location of each bin (field, storage, retail) date the bin was picked who picked the bin (multiple pickers) variety of apple picked row(s) used

Row tracking include: number of rows in the orchard, number of trees in each row variety of trees in each row

Grading tracking include: Yield (number of bushels) of each grade (1st –

Retail, 2nd baking/cooking, Juice, or Trash) Grader (multiple graders)

USABILITY REQUIREMENTS

System needs to be easy to learn and intuitive Allows users to complete tasks efficiently

without presenting unnecessary problems or obstacles

System assists in the prevention of user errors and allows error recovery

System contains consistent, easy navigation System does not have to support multiple

languages User documentation – Online help screens Printer friendly screens Client logo present on each page, links back to

home page

RELIABILITY REQUIREMENTS

Data Recover Support 20x7 support – System will go offline

from 1:00am until 5:00am to allow for database to perform routine backup and maintenance

Maintenance Releases, Bug Fixes, Patches, Updates

Unlimited Support Incidents Improved Tracking Accuracy with Barcode

System

PERFORMANCE REQUIREMENTS

Accuracy: Database accuracy must be at 95% regarding apple tracking

Response time: Scan of bin, must occur within 5 secondsUser update must occur within 10 seconds

Recovery time: for database (during season) must occur within 12 hours

Efficiency: Server must allow for up to 10 connections at a time

Resource usage: Server must allocate double memory capacity during peak picking months (August – November)

SECURITY PERFORMANCE Authorized users will have encrypted

user id and password Web system will use HTTPS System will log a user off after 1-hour of

inactivity

DESIGN REQUIREMENTS Web application must be written in PHP Relational database written in MySQL

IMPLEMENTATION REQUIREMENTSImplementation Languages:

PHP MySQL

Policies for Database Integrity: Reconciliation routines (checksums, hash, totals, record counts) will be

used to ensure software has not been modified Integrity verification programs such as consistency and reasonableness

checks used to look for evidence of data tampering, errors, and omissions

System performance monitoring will be used to analyze system performance logs in real time to look for availability problems, including active attacks and system/network slowdowns and crashes.

Any suspected violations of data integrity, denial of service, compromises of data – sold or used in unauthorized fashion, loss of accountability or damage to any part of the system shall be reported to the application manager/supervisor.

A sign-on warning shall be displayed at the time of logging on and a sign-off warning at the time of logging off for a security application.

Platform Support: Any OS/browser

INTERFACE REQUIREMENTS Every user will login with an ID and password

using authorized PC System will provide:

menu, help, command, monitoring, service map, and statistic windows

make visible and audible alarm when it receives an error and provide recognition, inquiry, and deletion capacity to the users

be able to receive tracking system’s resource and service condition in a real-time basis and indicate it through UI

commands necessary to operate the Apple Tracker in a manageable form

apple variety tracking data in relation to their inventory

PHYSICAL REQUIREMENTS Server (1) Firewall and Router (1) Computer (1) Wireless Printer (1) Barcode Scanner Barcodes

APPLE TRACKER SUBSYSTEMS

SUBSYSTEMS & EVENTS

APPLE GRADING SUBSYSTEM

BIN TRACKING SUBSYSTEM

REPORTING SUBSYSTEM

ENTITY RELATIONSHIP

DIAGRAM (ERD)

ERD

ACTIVITY DIAGRAMS

AD: CREATE BIN

AD: Create Employee, Create Cold Storage, Create Row

AD: Update Employee

AD: UPDATE ROW, UPDATE COLD STORAGE

AD: BINS TO FIELD

AD: Bins to Cooler

AD: Grade Apples

AD: Print Report

USER INTERFACE

DESIGN SPECIFICATIONS

Log on credentials decide access Manager/Owner Picker/Grader

Screens very similardifferent only in number of menu options

HTML Forms PHP MySQL database Optimized for small screens

users may use small scanner or phone to access

CREATE/EDIT EMPLOYEE

SEND BIN TO FIELD

GRADE APPLES

PRINT REPORT

DESIGN CLASS DIAGRAM (DCD)

DESIGN CLASS DIAGRAM

FUTURE PROJECT PLANS

Greg, Debbie and Ben plan to use this project in 449W, pending project approval

End Goal: Go Live in the Fall of 2014 at Plymouth Apple OrchardsMaybe sell it?

OVERALL EXPERIENCE & LESSONS LEARNED

Good communication among team members is vital

KISS (keep it simple, stupid) Having an excellent project manager is

critical Setting & sticking to internal deadlines Extensive project planning is required for

project completion Changes/Improvements will always have to

be made throughout the course of the project

RECOMMENDATIONS Designing efficient and strong IT

infrastructure will be a core competence.

Improve effectiveness from implementation.

Thoroughly understand business infrastructure and manufacturing operations

CONCLUSION Identified inefficient traceability of

current Plymouth Orchard’s system Solved difficult traceability of small

scale farms while cultivating crops Built desire to adapt Information

Technology in order to provide efficiency to small and medium sized fruit/vegetable growers

QUESTIONS?