PE wantsATE tocharacterizethe unitsOperatorused thewrongfixtureIt took morethan 6 e-mailsto resolve asimpleproblemPaulcomplainsaboutsomethingProductEngineeropens acontainmentfor limitsThe unitsaremanuallyapprovedLisa needsall units fora "verylate" orderOutlookgoesdownComponentEngineeringwants acustom testprogramPE gives youa unit thatdoesn't workUnitshave tobe testedupstairsPaulwants tocleansomethingEduardawalks intoour area andsays, "Knockknock"It's atimingissueSarah finds atest issue butit's actually adatasheetissueHeatherexpeditesan ECOTom asksaboutupgradingTestStandA newoperatorneeds to beadded to thedatabaseNPI needshelp withinductanceThe unitspass onretestRahuldoesn'tbelieve it's acomponentissueQ&Rneeds toclear aflagChris asks,"Did you puta scope onit?"Hong sendsan e-mailending with"Pleaseadvise."PE wantsATE tocharacterizethe unitsOperatorused thewrongfixtureIt took morethan 6 e-mailsto resolve asimpleproblemPaulcomplainsaboutsomethingProductEngineeropens acontainmentfor limitsThe unitsaremanuallyapprovedLisa needsall units fora "verylate" orderOutlookgoesdownComponentEngineeringwants acustom testprogramPE gives youa unit thatdoesn't workUnitshave tobe testedupstairsPaulwants tocleansomethingEduardawalks intoour area andsays, "Knockknock"It's atimingissueSarah finds atest issue butit's actually adatasheetissueHeatherexpeditesan ECOTom asksaboutupgradingTestStandA newoperatorneeds to beadded to thedatabaseNPI needshelp withinductanceThe unitspass onretestRahuldoesn'tbelieve it's acomponentissueQ&Rneeds toclear aflagChris asks,"Did you puta scope onit?"Hong sendsan e-mailending with"Pleaseadvise."

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