PE wantsATE tocharacterizethe unitsA newoperatorneeds to beadded to thedatabasePaulwants tocleansomethingThe unitspass onretestUnitshave tobe testedupstairsChris asks,"Did you puta scope onit?"ProductEngineeropens acontainmentfor limitsPE gives youa unit thatdoesn't workQ&Rneeds toclear aflagRahuldoesn'tbelieve it's acomponentissueThe unitsaremanuallyapprovedPaulcomplainsaboutsomethingOutlookgoesdownTom asksaboutupgradingTestStandOperatorused thewrongfixtureIt's atimingissueIt took morethan 6 e-mailsto resolve asimpleproblemLisa needsall units fora "verylate" orderNPI needshelp withinductanceComponentEngineeringwants acustom testprogramHong sendsan e-mailending with"Pleaseadvise."Eduardawalks intoour area andsays, "Knockknock"Sarah finds atest issue butit's actually adatasheetissueHeatherexpeditesan ECOPE wantsATE tocharacterizethe unitsA newoperatorneeds to beadded to thedatabasePaulwants tocleansomethingThe unitspass onretestUnitshave tobe testedupstairsChris asks,"Did you puta scope onit?"ProductEngineeropens acontainmentfor limitsPE gives youa unit thatdoesn't workQ&Rneeds toclear aflagRahuldoesn'tbelieve it's acomponentissueThe unitsaremanuallyapprovedPaulcomplainsaboutsomethingOutlookgoesdownTom asksaboutupgradingTestStandOperatorused thewrongfixtureIt's atimingissueIt took morethan 6 e-mailsto resolve asimpleproblemLisa needsall units fora "verylate" orderNPI needshelp withinductanceComponentEngineeringwants acustom testprogramHong sendsan e-mailending with"Pleaseadvise."Eduardawalks intoour area andsays, "Knockknock"Sarah finds atest issue butit's actually adatasheetissueHeatherexpeditesan ECO

Test Engineering BINGO - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. PE wants ATE to characterize the units
  2. A new operator needs to be added to the database
  3. Paul wants to clean something
  4. The units pass on retest
  5. Units have to be tested upstairs
  6. Chris asks, "Did you put a scope on it?"
  7. Product Engineer opens a containment for limits
  8. PE gives you a unit that doesn't work
  9. Q&R needs to clear a flag
  10. Rahul doesn't believe it's a component issue
  11. The units are manually approved
  12. Paul complains about something
  13. Outlook goes down
  14. Tom asks about upgrading TestStand
  15. Operator used the wrong fixture
  16. It's a timing issue
  17. It took more than 6 e-mails to resolve a simple problem
  18. Lisa needs all units for a "very late" order
  19. NPI needs help with inductance
  20. Component Engineering wants a custom test program
  21. Hong sends an e-mail ending with "Please advise."
  22. Eduarda walks into our area and says, "Knock knock"
  23. Sarah finds a test issue but it's actually a datasheet issue
  24. Heather expedites an ECO