This document describes an SFDCP project which includes a PostgreSQL database server, RedHat Linux web and application servers, and Python and PostgreSQL database clients. It allows for order administration, production line clients accessed through a web browser, and reporting. Benefits over other solutions include no expensive hardware requirements, flexibility and customizability, easy maintenance, and the ability to continue using existing local tools and reports.

1. SFDCP – sfdc project
A brief introduction

2. Database Server
RedHat Enterprise Linux
PostgreSQL database
Web server
RedHat Linux
Apache Web Server
Python
PostreSQL database client
Production Line Clients
Web Browser
Office Tools, Settings
Web Browser
PostgreSQL DB connection
XMLHTTP/Ajax
XMLHTTP/Ajax
Auto-Checkpoint server
RedHat Linux
Python
PostgreSQL database client
PostgreSQL DB connection
File I / O
-Database server HW: IBM x346, 2xCPU, 6x36GB SCSI (O/S: Raid1, DB: Raid1E)
-Database / Web server / Auto-Checkpoint service can be installed on the same machine.
-Production clients, BOM administration, Order administration, Route settings, Reporting : all are web based
-possibility to connect to 3rd
party applications with Auto-Checkpoint service via file I / O.
3rd
party apps
Access to Auto-Checkpoint
server file system
System Overview

3. Technology: Python, JavaScript, HTML, SQL
-Easy to maintain or debug
-New functions can be developed and added quickly.
-no installation needed on client’s side

4. Process Route Configuration
-Dynamically define new route
-Predefined checkpoint types: AddPart, Pass/Fail, Sample, GetData
RemovePart, ReplacePart, Palletize, Ship, etc.
-once the routing is defined the line clients are automatically set up for use

5. Order Administration
-Release order with serial numbers generated by rule
-Release order with given list of serial numbers
-Manually set order status when needed (ie. Killed, hold)

6. Production Line Clients -call for operator identification first
-can be run in more instances
-hyperlink set in the “Clients” tab once the checkpoint is defined in the system route

7. Product Administration
-model definition: parts with alternatives, grouped according to the route setup.
-part definition: p/n, description and full format as regular expression
-possibility to read part data from SAP dump file

8. -WIP reports by order/location/serial
-Lookup in system by unit/model/order/location
-Scorecard / hourly data
-unit history
Reporting

9. Documentation
-database setup script with comments
-server settings different from default values included
-message board function for failure reporting
-software codes are human-readable, commented

10. Usage and feedbacks
- 9200 units processed in the Acer/PackardBell rework
-Peak load about 800/day : no measurable effects of workload
-Minor problems (scanned data, user errors) corrected
-User satisfaction survey after closure: feedbacks are positive

11. Actual status
 The existing COPS BOM is migrated into SFC for test & debug
purposes (~ 10K PN / part groups)
 Pilot build with current product was done within this SFC
 Connection to IBM test system working.
 Label printing already developed, some of the labels already done
and using variable data from unit’s BOM

13. Benefits to the existing SFC solutions
 No expensive server (like IBM pSeries, ) required
 No licensing for OS and DBM (hence both reliable and common)
 Majority of clients only require a browser, OS-independent,
performance-efficient.
 Flexible and fully customizable.
 Easy to maintain and expand
 SFC tailored for the customers specific needs.
 All the locally developed tools/reports -which were developed during
the last 8 years to make the factory’s work efficient - could still be used.
 User-friendly interface, possibility to use local language
 Fast & robust
 Closed system, behind corporate firewall, no access to the internet
 Developers know the customer, product and processes for ~10 years.
 Same technology as the customers current test environment.
 Need & support in the same time zone