flex

Title : ICT Software Control Document Number : OPS-ENG-3-317-00

Document Owner : FangJi Zhu Effective Date : 9/2/2012

ICT Software Control

Ramon Rivera / Francisco Duran / Jose Pacheco / Manuel Ruiz / Jose Becerra
•

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Document Title: Document No.: Organization:
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
ICTOwner
Document Software Control
: FangJi Zhu OPS-ENG-3-317-00 Advanced Engineering Group
Effective Date : 9/2/2012

Revision: Document Owner: Effective Date:

A Jose Becerra 2012-10-31

AUTHOR NAME APPROVER TITLE DEPT NAME DATE

Jose Becerra Test Engineering Manager Advanced Engineering 2012-09-14

Group

AUTHOR’S MANAGER NAME APPROVER TITLE DEPT NAME DATE

Juan Coronado VP1, Design & E ngineering Advanced Engineering 2012-09-30

Group

AEG VP NAME APPROVER TITLE DEPT NAME DATE

Murad Kurwa Advanced Engineering Group VP Advanced Engineering 2012-10-31

Group

REVISION HISTORY

REVISION DESCRIPTION OF ORIGINATOR RELEASE DATE

CHANGE

A First Document release Jose Becerra 2012-09-03

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Objective
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

To provide an overview to implement an ICT software control method.

To document a method that can be taken as reference to control ICT

software, considering below main 3 areas :
1. Program Reception and Acceptance.
2. Debug, ECO´s Control and Changes Tracker log.
3. ICT LAN Implementation.

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Agenda
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

1. ICT Software Acceptance.

i. Software Acceptance Flow Diagram
ii. Fixture Guideline and Checklist
iii. GR&R study
iv. Board Grader and QSTATS Cp &Cpk studies
v. Test coverage report
vi. Autofile set up
2. ICT SW Revision Control.
i. Flow Diagram
ii. Program backup
iii. Update Software control log
iv. Classification of minor and mayor changes
v. Change Validation
vi. Users Definition to control System Rights.
vii. Automatic Changes Notification.. Baselining Tool.
3. ICT LAN implementation.
4. Conclusion and Next Steps
4

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Best Practice Objective
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Site: Flex Guadalajara North Campus and Flex Austin Texas

Project Description (Objective): To document a method that can be taken

as reference to control ICT Software, considering main 3 areas : 1. Program
reception and acceptance; 2. Debug, ECO control and changes tracker log; 3.
ICT LAN implementation.

Applicable Station :

Screen Printer (SP) SW Automation (SW Auto)

Pick and Place (PnP) Automatic Insertion (AI)

Reflow Oven (Oven) Tooling Development (TD)

Wave Solder (WS) Critical Repair (CR)

HW Automation (HW Auto) Other X

5

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

ICT SW Control for Agilent using Unix.

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Team Picture
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Jose Pacheco / Francisco Duran / Ramon Rivera Andy Widodo Manuel Ruiz
Flex Guadalajara B10 team Flex Austin Texas
7

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Developed Team
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Team Role Members Name Job Title Contact information Location

Leader Ramon Rivera Test Staff Engineer [email protected] B10 GDL

North
Campus

Co-Lead Francisco Duran Engineering Sr. [email protected] B10 GDL

Manager North
Campus

Co-Lead Jose Pacheco Test Staff Engineer [email protected] B10 GDL

North
Campus

Co-Lead Manuel Ruiz Test Manager [email protected] Austin

Texas
Campus

Co-Lead Jose Becerra AEG Test Manager [email protected] AEG Test

Manager

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. i. Software Acceptance Flow Diagram
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

The main focus for define the steps to follow in the process ICT SW acceptance- Focus on the
Agilent ICT 30XX machines that operate on HP Ux operative systems.
The general steps listed below was defined as general recommendation process in Flextronics,
for this reason some steps can not apply for all test process and additional steps could be
requested by specific customer.
The software acceptance applies for a new program coming from programming house or get an
used program from another CM, on both cases acceptance criteria must be fulfilled.

Golden unit Once

Straing pass test, Pass installed Pass
Gage or with test pass
FEA Testplan and the GR&R
testorder study

Fail Fail

New ICT Yes Fail Board

Take Corrective
Fixture & Function Grader with
Acton to correct
Program at al ok? Cp and Cpk
the abnormality above 1.67
Flextronics

Fail
Full Pass
BOM No
Coverage
Fixture or Release & Pass report as per
Program Create coverage
repair AutoFile expected as
BOM
Server Auto File 9

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. ii. Fixture Guideline and Checklist
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Fixture Guideline and Checklist (some point as examples)

q Include Testjet
q Avoid Testjet to touch PCBA
q Safety
q Maintenance
q Vacuum leakage
q Dimensions
q Edges
q Request Autofile No Generation

10

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iii. GR&R Study
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

GR&R Study

11

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Board Test Grader

Run Board Test Grader after you have completed and debugged your tests. Board Test Grader
uses one known-good board to run its grading routines. The utility relies upon statistical analysis
and multiple test executions to determine marginal tests.
Board Test Grader results are written to report files. Each test category creates its own report file.
A summary report file summarizes the results of all of the categories. You can use the reports to
keep a permanent record of your board test performance (for comparison with future tests, for
fixture and test maintenance). You also can use these reports as acceptance criteria for releasing
or accepting a board development project.

Test Types
Board Test Grader evaluates the following types of Agilent in-circuit tests:
Pins
Shorts
Preshorts
Analog in-circuit tests
Digital in-circuit tests
Analog functional tests

Limitations
Board Test Grader does not support tests with variables in Basic (common on mixed tests).
It does not support Agilent Polarity Check tests.
12

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Running Board Test Grader in Pushbutton Debug

In Pushbutton Debug, select Test Grader Macros from the Macros menu to see the Board Test Grader
macros (Figure 1). They are:
Generate Test Coverage Report
Set Board Information
Create Grading Config
Create Grading Testplan
Grade Tests
1 Use Set Board Information to select which board
version or board on the panel to use during the Board
Test Grader process.
2 Select Create Grading Config to create a config.bdg
file.
3 Modify the config.bdg file according to your
requirements.
If you do not edit config.bdg, default values are used
and all tests and grading methods are run.
If you do not want a test type to run, you must set the
test type to False.
For example, if you want to test every test type except
digital quality test, change the following statement:
Digital_Incircuit_Quality_Test = True to the following:
Digital_Incircuit_Quality_Test = False When Board
Test Grader runs, it omits the digital quality test
commands in testplan.bdg. It also does not create a
report file associated with digital quality tests.
The config.bdg file contains comments to help you edit
it.
4 Select Create Grading Testplan to generate the
Board Test Grader testplan.
The testplan is created from your original testplan and Figure 1 Test Grader Macros in Pushbutton Debug
the config.bdg file. It contains the BT-BASIC commands 13
to grade your in-circuit and analog functional tests.

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Running Board Test Grader in a BT-BASIC Window

Follow these steps to run Board Test Grader in a BT-BASIC window:

1 msi to the local board directory.
2 Set the board information (select which board version or board on the panel to use) as follows:
get basic "deubg/board/Test_Grader_Macros/setinfo" / run
3 Create a config.bdg file by typing:
Grade tests; configuration
execute "perl deubg/board/Test_Grader_Macros/modify_config.bdg"
4 Modify the config.bdg file according to your requirements.
If you do not want a test type to run, you must set the test type to False.
The config.bdg file contains comments to help you edit it.
5 Generate the Board Test Grader testplan by typing:
execute "perl deubg/board/Test_Grader_Macros/create_testplan.bdg"
The testplan is created from your original testplan and the config.bdg file. It contains the BT-BASIC commands to
grade your in-circuit and analog functional tests.

Do not edit config.bdg after testplan.bdg is created. If you need to edit

config.bdg, create a new testplan.bdg.

6 Run the Board Test Grader testplan by typing:

get "testplan.bdg" | run This grades the tests specified in config.bdg.
7 Generate the reports by typing:
grade tests; report This creates the grading reports in the /<board_directory>/bdg_data directory.

14

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Data Files
The data files, listed in below Table 1, contain information from running the grader that will be provide to the Test engineers users the values of CP,
CPK mean std dev. From testplan.bdg. Most of the data files (with the exception of *_ver_fau.dat) use standard or customized logging
commands.

Table 1 Data files

File Data
pins.dat Pins data
pre_sho.dat Preshorts data
sho.dat Shorts data
ana_inc_vac_off.dat Analog incircuit vacuum off data
ana_inc_qua.dat Analog incircuit quality data
dig_inc_vac_off.dat Digital incircuit vacuum off data
dig_inc_qua.dat Digital incircuit quality data
dig_inc_pow_sup.dat Digital incircuit power supply sensitivity data

dig_inc_spe.dat Digital incircuit speed sensitivity data

dig_inc_ver_fau.dat Digital incircuit verify faults data
ana_fun_vac_off.dat Analog functional vacuum off data
ana_fun_qua.dat Analog functional quality data
ana_fun_pow_sup.dat Analog functional power supply sensitivity data

ana_fun_spe.dat Analog functional speed sensitivity data

ana_fun_ver_fau.dat Analog functional verify faults data

15

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Data Files Board Grader Results

The data files, listed on the last slide provide the statistical results. ana_inc_qua. rpt The information
from running the grader that will be provide to the Test engineers users the values of CP, CPK mean std
dev. From testplan.bdg. Most of the data files (with the exception of *_ver_fau.dat) use standard or
customized logging commands.

-------------------------------------------------------------------------------
AGILENT 3070 BOARD TEST GRADER Wed Jun 06 10:59:19 2012 page 1 Date & Time
Analog Incircuit Quality REPORT
-------------------------------------------------------------------------------

Board Path: ./
Ref Board Serial #: Board1
Date of Data generation: Wed Jun 6 10:56:28 2012
Designator
Number of test runs (in config.bdg): 10
Number of tests: 110
Report Flags:
F = Test failed
M = Mean not centered 66.67%
C = Coefficient of producibility too small 10.00
Data:
Designator ---Programmed---- --------Computed--------- # Flg Com
Nom Low High Mean StdDev CPK CP Bad Ref CPK,CP, StdDev
c117 200n 170n 230n 202n 11.8p 783 845 0 ...
c130 1.60u 1.04u 2.16u 1.76u 8.73n 15.3 21.4 0 ...
c131 6.20u 4.65u 7.75u 5.90u 8.86n 47.1 58.3 0 ...
c133 47.2u 33.0u 61.4u 43.1u 8.97n 375 526 0 ...
c138 35.1u 24.6u 45.6u 35.9u 39.6n 81.7 88.6 0 ...
16

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Ensure that the flag

"QSTAT_MODE" equals
"HISTO"

17

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Find line “Analog Sample

Rate” to set number of
samples needs to run a
Statistics Report.

Next variable “Log_Path”

shows the route where will
be saved all measurements.

18

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Before that Start runs

Qstats Tool just first time
the system needs learn all
measurements of a Good
know board to calculate
limits values; add next line
“learn on”.
Place the Board into the
ICT Fixture, runs the
testplan and start the
“learn” press F1 on the
keyboard; on screen will
change “test title” to
“Learning”.

19

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

In order to have a good

Statistical Study we need
to apply the Qstats tool
variables “ Histo” in the
testplan the time that we
need to evaluate,
example: per shift, day,
week, etc.
Press the “pb qstats”
button to start the
Statistical Tool.

20

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Select “Report Type”

“Histogram.

Select the Board to

evaluate.

Click Run Report

button.

21

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. iv. Board Grader and Cp&Cpk Studies
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Finally the Histogram will

appear with Statistical
values as CP, CPK,
standard Deviation, Mean,
etc

Typically Cpk must be > 1.67.

Cpk below 1.67 may consider an
additional test debug.

22

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. v. Test Coverage Report
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Running Test Coverage on a Standard Testplan (Unix)

To run Test Coverage on a standard testplan:

1 Place your fixture on the testhead.

Make sure it is locked. (It is not necessary to have a board on the fixture,
because no vacuum is applied.)

2 msi to your board directory.

3 To start Pushbutton Debug, execute the following BT-BASIC statements:

load board
debug board

4 Generate a Test Coverage Report.

From the Macros menu, select Test Grader Macros followed by Generate
Test Coverage Report.

23

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. v. Test Coverage Report
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

What the Generate Test Coverage Report macro does

The Generate Test Coverage Report macro performs the following actions:
1 Creates a new testplan called testplan.cov.
The existing testplan file is copied to the file testplan.cov, then is modified to allow testplan.cov to run the tests that measure
test coverage accuracy. The modifications:
Run all of the device tests (except pins and shorts) without ever applying vacuum or power to the board.
Prevent testplan.cov from exiting early due to any test failing.
The changes made differ slightly for a panelized vs. standard board.
Every line in testplan.cov that is altered is marked with the comment ! COVERAGE.

2 Executes the testplan.cov file while reporting all failures to the testcoverage_fail.dat file.
For panelized boards, you must specify (via the standard operator interface) which board or boards should be considered in
the coverage report. Any number of boards is acceptable by the test coverage tool. However, if more than one board is
selected, all devices on these boards are reported within the same report; they are not separated by individual board
numbers. Therefore, we recommend you select a single board for a report, then repeat the process for as many other boards
as desired.
If an error (or break) occurs, the testplan.cov file detects this and prevents a new report from being completed. An error
message reminds you that you cannot simply edit testplan.cov that is in the BT-BASIC window. Instead, you must edit the
testplan file. (See Running Test Coverage on a Custom Testplan.)

3 Creates the report file, testcoverage.rpt.

This is created by comparing devices that failed (in the testcoverage_fail.dat file) to the board topology in board.o. For
panelized boards, only the devices on the board(s) selected are considered (as explained in step 2). Any device that has
failed is considered tested. (See Interpreting the Test Coverage Report.)

4 Removes the intermediate files testplan.cov and testcoverage_fail.dat.

This prevents the directory from becoming cluttered with temporary files.
Test Coverage does not alter any standard files in the board directory. 24

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. v. Test Coverage Report
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Test Coverage Report Sample

25

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. v. Test Coverage Report
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Test Coverage Report Sample (Raw Data)

26

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. v. Test Coverage Report
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Test Coverage Report Sample ( Windows Environment Graphics)

27

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. vi. Autofile Fixture Wiring
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Assign on server fixture program autofile

Define the Autofile number that be unique for each released mass production fixture, by default the fixture vendor follow
the fixture files specifications and the board file define this number. Each Administrator should update the number if needed
On the wiring in-side of the fixture on the control card section ( On the highest control of the fixture ) .

Is a Binary code The valid range of autofile codes is 11 to 4094.

66 AF0/ Autofile 0
67 AF1/ Autofile 1
68 AF2/ Autofile 2
69 AF3/ Autofile 3
70 AF4/ Autofile 4
71 AF5/ Autofile 5
72 AF6/ Autofile 6
73 AF7/ Autofile 7
74 AF8/ Autofile 8
75 AF9/ Autofile 9
76 AF10/ Autofile 10
77 AF11/ Autofile 11
78 GND Autofile Ground
28

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
1. ICT SW Acceptance. vi. Autofile Set Up
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

AutoFile Definition During Test Development:

FIXTURE IDENTIFICATION
The autofile function returns the value of the current autofile code.
The autofile function identifies the fixture currently on the testhead by reading the autofile code wired into the fixture. The
autofile function points to the corresponding board directory so that the proper files can be automatically loaded. The valid
range of autofile codes is 11 to 4094.

Specifies a numeric code to automatically identify the fixture that is loaded on the testhead. This can be a number from 11 to
4094. If no autofile is specified, the fixture generation software automatically assigns the first available value starting at 4094
and decreasing to 11. The fixture generation software uses this value to add the necessary wiring to the fixture. The fixture
generation software also creates a corresponding file under $AGILENT3070_ROOT/autofile/<autofile value>. This file
contains the name of the board and the absolute path to the board directory. For example:
ps_board $AGILENT3070_ROOT/boards/ps_board For multiple-board fixtures, you need to edit the autofile file to include
a listing for each board on the fixture. For example:
board_1 $AGILENT3070_ROOT/boards/board_1 board_2 $AGILENT3070_ROOT/boards/board_1 board_3
$AGILENT3070_ROOT/boards/board_1 Note that QuickPress uses two transfer probes to change the Autofile number
only when the top plate is engaged. This allows the software to determine when to proceed with the board test.

------------------------------------------------------------------------------
3070 FIXTURE TOOLING REPORT Wed Nov 2, 1988 07:59:06 PM PAGE 2 /boards/sample/fixture/summary
------------------------------------------------------------------------------
Fixture Type : Cassette Fixture
Size : Bank2
Top Probes Allowed : ON
Autofile : 4094
Metric Units : OFF
WireWrapping : Manual
-------------------------------------------------------------------------------
29

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
2. ICT SW Revision Control Acceptance. i. Flow Diagram
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Start

Deos
change is a Mayor
It is
necessary minor or
to debug or mayor
change ICT change Change ICT
Software
Minor Software

A
Revision

Backup the Changes

program Validation Fail
* Cp and Cpk
* Negative
test

Pass
Apply Software
changes
Debug the SW
Changes A
Backup and
update master
file
Update SW
control Log
Testplan and
log Consider to be running using:
• Software backup process
End • Adequate permission by password control

30

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
2. ICT SW Revision Control Acceptance. ii. Backup
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

Software and files may get damage or corrupted due to several

reasons lost when a user accidentally deletes or overwrites a file,
or misuses of a command, a power failure or hard disk crash.

A disaster recovery plan, with backup disks and tape's

recommended to protect system and data against failures,
corrupted data, or accidental deletion of files or at least get back
to work with the previous program so if that is required.

Prerequisites
• Experience administering UNIX systems.
• Administrator log on privileges.

One important responsibilities of the system administrator is to

implement an effective backup strategy.

31

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
iii. Update SW Control Log
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Document the changes and keep control of them is important

because:
• Know the description of the change
• Validate that it is always the last review which is running.
• In the future to know which program is more compatible with the new
revisions or if you have to create a completely new one.
• Create a History
• Quality requirements

Changes are recoment to be documented on:Testplan. Software control log

Implementation of Log to keep track of changes in the Testplan.

The name and Revision of the testplan will be added in the tesplan header “Change History
Part”, should also be shown in detail the changes made in each of the revisions. 32

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
iv. Changes Classification
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Recommended classification for changes in the ICT software:

1.Minor Changes: Debug MOA on parameters: re, ed, wa, ar, co, ico, fr, Guards
added in wire circuitry, add Power Reset, Limits of testjets minimum of 30%. These
changes does not need to change of ICT Software Revision.
2.Major Changes: Test Logic, change component limits, Add or Remove
Components, Programming software (Device programmed), Voltage Levels, these
changes will require a new revision number in the “title BT - Basic Windows”.

33

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
2. ICT SW Revision Control Acceptance. v. Changes Validation
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

To Ensure that ECO is Finally and Correctly applied, we need to

complete the Following:
• Uptade log Track with Cp and Cpk values.
• Run a GR & R study by “variables” to ensure that the parameters "CP"
and "CPK" are above the 1.6 . The Statistical Tool “Minitab” can used to
determine the performance to release ICT after Program modification or
QSTATS within ICT system
• Negative tests: if the implementation of ECO were added or removed
components, negative testing is required, example placing components of
different values, missing component, to ensure that ICT is able to detect a
wrong measurement.

34

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control
vi. Users to Control Rights
Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Password protection is designed to keep the notes safe from outsiders who can
make changes in programs, that are not part of the plan, or some other part of the
team, resulting in failure of the same, for this reason must assigned different
passwords.

35

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control
vi. Users to Control Rights
Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Initially ICT program is

administered by a standard user
"user1".

During adjustment of parameters of

a component in the test, there is
not user control that person
modified the software.

36

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control
vi. Users to Control Rights
Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Using the tools of "SAM" (System Administration

Manager), we can create users for each technician
and test engineer.

In the Section “Accounts for Users and

Groups” we can Create and Manage
users account of each person that
modify the parameter of ICT programs.

37

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
vi. Users to Control Rights
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

The creating each

user, the "SAM“ tool
allows to record the
name, permissions,
group, user id and the
location of ICT.

38

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
vi. Users to Control Rights
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Each User will be

a different
password.

39

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control
vi. Users to Control Rights
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

After creating users, if a technician modified parameters in

any subtest, will be registered with your User ID, time,
date.

40

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex2. ICT SW Revision Control Acceptance.
Title : ICT Software Control
vii. Automatic Change Notification
Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Enhanced Log Records for the Agilent In-Circuit Test System:

“Baselining” is a tool that we can use in ICT to detect if program has been
modified, exist a Log Record where after the files (Subtest) of the objects
produces are learned by Baselining with CRC number calculated. Next file
explains how can we use this Log recording tool.
When a test program change is detected during production, a log record is
generated detailing this change event so that the change can be properly
reviewed. Using a change control process, such an event may either be accepted
or corrective action may be taken.

41

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
3. ICT LAN Implementation
Title : ICT Software Control
Document Owner : FangJi Zhu
--- Why to have a LAN? Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

To have an structure to use ICT

fixtures in any ICT machine is
necessary create a exclusive
server to contain all the programs
ICT SERVER
used in production floor
LOCAL
VLAN

Generate a directory per project

and inside a directory per family

ICT1 ICT2 ICT3 ICT..N

General project Family
directory
42

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
3. ICT LAN Implementation
Title : ICT Software Control
Document Owner : FangJi Zhu
--- Prerequisites Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

1. All the ICT’s have to be standardized in order to can used every ICT fixture in any ICT
machine, If this is not possible you can divided in 2 main groups
• Half's
• Full's

2. You need a local Vlan

3. Fixture identification
Region/Country/site/project/Family/model
Example: Ams – mx – gdln – eqx – L5xxx – RFID

43

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
3. ICT LAN Implementation.
Title : ICT Software Control
Document Owner : FangJi Zhu
--- Server Set up Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

•Setting server service

1. Log in to the server as root
4. Set the direction contains the test plans
And the direction contains the Auto files

2. In a Shell window type sam

Then access to the next address

To put the direction click left button and click

3. Then double click in Exported Local File Systems in Add exported file System

44

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
3. ICT LAN Implementation.
Title : ICT Software Control
Document Owner : FangJi Zhu
--- Autofile Set up Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

In order to use all the ICT fixture in any ICT that you have in your site you need to create a
Autofile , one per every existent ICT fixture

1. You need list the numbers assigned to every fixture

When the fixture is mounted in the ICT type in a basic windows auto file to get the number

2. Once you have all the autofiles created into the server in the direction var/hp3070/autofile
compress and generate a general .tar file
3. Send all autofiles to every ICT. (using ftp)
4. Put the file .tar into var/hp3070/autofile
• and uncompress in all the ICT machine
5. When the general .tar file is already uncompress
• you can mounted in any ICT any ICT fixture and
• will get the test program automatically

45

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
3. ICT LAN Implementation.
Title : ICT Software Control
Document Owner : FangJi Zhu
--- Autofile Generation
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

1. Mount the fixture at the ICT

2. In a basic window type Autofile

The result number will be the name for the autofile

- Open a shell window

- In var/hp3070/autofile generate de autofile

- Type vi filename

- Inside type the server direction contains the test program for that fixture

Family and project

Direction contains test program
- Save and quit
46

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Title : ICT Software Control Document Number : OPS-ENG-3-317-00
Document Owner : FangJi Zhu Effective Date : 9/2/2012

Conclusion and Next Steps

47

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
Conclusion and Next Steps
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

• We have seen in this document general recommendations to be used as

guideline for ICT Software control
• New Models of fixtures should be requested with usage of ICT fixture
guideline.
• New software should be accepted using acceptance process
recommended
• ICT software control consider 3 main stages:
1. ICT software acceptance
2. IST Software revision control for Debug and ECO implementation
3. ICT LAN Implementation

Next Step:
• Develop a demon to automatically compare resident program on ICT and
compare vs Master program located into server, if differences are found
macro will overwrite using master program and notify to system
administrator that changes was detected and corrected.
48

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM

flex
We will continue to deliver!
Title : ICT Software Control
Document Owner : FangJi Zhu
Document Number : OPS-ENG-3-317-00
Effective Date : 9/2/2012

49

Sylvester Flad - 9/20/2016 9:38:05 AM Last Modified: 9/20/2016 9:37:00 AM