How to discover a custom Bluetooth LE device
No, the UUID should be the same for all of your boards. I know why you may think this is odd, but it is the services that looks and act the same, the boards don't have to. But, if your boards will do different tasks, then maybe you could add different, more specific, services to each of them.
To identify which is one and who's the other, you should change the device's name. A common way of doing this is searching for the same UUID from iOS, and then get a list of device names that are broadcasting this specific UUID. If you are using an nRF51822 device, tell your EE that he can have unique names instead of unique UUID's by changing this line in is main.c to easier identify your different boards. 

#define DEVICE_NAME                          "Device_name" // &lt;&lt;-- this line

// In gap_params_init
sd_ble_gap_device_name_set(&amp;sec_mode,(const uint8_t *)DEVICE_NAME, strlen(DEVICE_NAME));


If your device is going to advertise a Bluetooth SIG (Special Interest Group) type of service, the UUID needs to be a 16 bit standardised value from the SIG. These can be found here.  When you are using a chip from Nordic Semiconductor, you'll see that in their libraries, all the service and characteristics definitions are already defined. 

Excerpt from these documentation pages:

#define BLE_UUID_ALERT_NOTIFICATION_SERVICE                      0x1811     /**&lt; Alert Notification service UUID. */
#define BLE_UUID_BATTERY_SERVICE                                 0x180F     /**&lt; Battery service UUID. */


On the other hand, the Nordic UART service is a custom service. To use a custom service, you need to generate a 128 bit random UUID and add this to the service your self. Since your EE has already done that, there is no problem just switching it out.