American Trim Paul Pellegrini, Director of IT
Vendors / Environment American Trim environment: HP ProLiant DL370 G6 VMware ESXi 5.1 Redhat Linux 5.5 QAD 2010SE (upgrading to 2012SE 04/06) Factivity 3.3A-B2 Progress 10.2A03 (upgrading to 10.2B07 04/06) Factivity & QAD databases are on the same LINUX server; using AI files to keep DB synchronization to a DR site every 15 minutes
Vendors / Environment (Continued) American Trim environment: BravePoint ProStar Software TailorPro Eagle Consulting & Development Cyberscience Cyberquery ACOM Solutions Trubiquity
Decisions Discrete v Repetitive Homegrown v Factivity Automation v highly clerical & lack of controls Brought in QAD Brought in Factivity Decisions
Start from the beginning In 2006 we re-implemented Factivity -Schedules electronic -Introduce Controls / Reporting -100% Terminal Services / Thin Clients
Factivity Environment Client: -VM Windows 2008 Remote Desktop / Terminal Services -Loftware Print Server -Primarily Thin Clients (WYSE) -HP LaserJet / Sato M84Pro Server: -LINUX / Progress
Scheduling
Shop Floor / Available Work Centers
Shop Floor / Dispatch Viewer
Shop Floor / POD
Sticky Notes
Shop Floor / Keypad
Label Sample 4 x 6”
Label Sample 8.5 x 11”
Shop Floor / POD
Shop Floor / Documents
Summary We have 91 seats of Factivity We have 52 Sato bar code printers We license 95 Loftware based printers There are a few Reports used by the shop floor. We have additional reports that we run from QAD that connect to the Factivity database.
Scripts Synchronizing with QAD LINUX Daily scripts -fact_sndentbch -fplbatch -fact_pushschbch -fact_mastbch -fact_wosyncall LINUX Continuous scripts -fact_prodtoqad -cimcontbch -fact_cimerrbch LINUX periodic scripts - fact_mthdelbch
Questions?