Unitshave tobe testedupstairsSarah finds atest issue butit's actually adatasheetissueIt's atimingissueTom asksaboutupgradingTestStandHong sendsan e-mailending with"Pleaseadvise."A newoperatorneeds to beadded to thedatabaseChris asks,"Did you puta scope onit?"Paulwants tocleansomethingPE wantsATE tocharacterizethe unitsPE gives youa unit thatdoesn't workComponentEngineeringwants acustom testprogramPaulcomplainsaboutsomethingNPI needshelp withinductanceThe unitspass onretestLisa needsall units fora "verylate" orderRahuldoesn'tbelieve it's acomponentissueOutlookgoesdownEduardawalks intoour area andsays, "Knockknock"Heatherexpeditesan ECOIt took morethan 6 e-mailsto resolve asimpleproblemOperatorused thewrongfixtureQ&Rneeds toclear aflagThe unitsaremanuallyapprovedProductEngineeropens acontainmentfor limitsUnitshave tobe testedupstairsSarah finds atest issue butit's actually adatasheetissueIt's atimingissueTom asksaboutupgradingTestStandHong sendsan e-mailending with"Pleaseadvise."A newoperatorneeds to beadded to thedatabaseChris asks,"Did you puta scope onit?"Paulwants tocleansomethingPE wantsATE tocharacterizethe unitsPE gives youa unit thatdoesn't workComponentEngineeringwants acustom testprogramPaulcomplainsaboutsomethingNPI needshelp withinductanceThe unitspass onretestLisa needsall units fora "verylate" orderRahuldoesn'tbelieve it's acomponentissueOutlookgoesdownEduardawalks intoour area andsays, "Knockknock"Heatherexpeditesan ECOIt took morethan 6 e-mailsto resolve asimpleproblemOperatorused thewrongfixtureQ&Rneeds toclear aflagThe unitsaremanuallyapprovedProductEngineeropens acontainmentfor limits

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