shar.eprocure.isro.gov.in · web viewcdt-1 sync difference byte-3 upper nibble in ascii cdt-1 sync...

29
ANNEXURE-1 I. TECHNICAL SPECIFICATIONS OF IRIG-B AUTOMATIC CHANGEOVER UNIT: DESCRIPTION: The IRIG-B ACU is an unit which should accept three different IRIG - B universal time codes and three modified IRIG - B count down time codes and tests the quality of the respective time codes continually for various parameters and select one out of them as output for transmission. The following arthe required features if the unit: The IRIG-B ACU should have two separate isolated parts in the same unit. The first one is for automatic selection of one Universal IRIG-B time code from three IRIG-B UT time codes derived from three different timing chains and the second part is for automatic selection of one Count Down modified IRIG-B time code from three modified IRIG-B CDT time codes derived from three different timing chains. The parts should test the quality of the time codes continually for various parameters, display all code status/error details and code selection details and select one out of them as output for transmission Parameters to be checked: o Modulated code level o Presence of carrier o Presence of modulation o Bits and Marker widths o Frame data o Frame length o synchronization with external reference 1PPS o synchronization between three chains o Majority Coincidence check between all the codes. Presence of any error in the above parameters in any chain is sensed, the auto changeover unit immediately should inhibit the passage of faulty time code while outputting the good 1

Upload: dongoc

Post on 31-Mar-2019

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

ANNEXURE-1

I. TECHNICAL SPECIFICATIONS OF IRIG-B AUTOMATIC CHANGEOVER UNIT:

DESCRIPTION:

The IRIG-B ACU is an unit which should accept three different IRIG - B universal time codes and three modified IRIG - B count down time codes and tests the quality of the respective time codes continually for various parameters and select one out of them as output for transmission. The following arthe required features if the unit:

The IRIG-B ACU should have two separate isolated parts in the same unit. The first one is for automatic selection of one Universal IRIG-B time code from three IRIG-B UT time codes derived from three different timing chains and the second part is for automatic selection of one Count Down modified IRIG-B time code from three modified IRIG-B CDT time codes derived from three different timing chains.

The parts should test the quality of the time codes continually for various parameters, display all code status/error details and code selection details and select one out of them as output for transmission

Parameters to be checked:o Modulated code levelo Presence of carriero Presence of modulationo Bits and Marker widthso Frame datao Frame lengtho synchronization with external reference 1PPSo synchronization between three chainso Majority Coincidence check between all the codes.

Presence of any error in the above parameters in any chain is sensed, the auto changeover unit immediately should inhibit the passage of faulty time code while outputting the good code of the other chain to the connected driver units without any loss of time.

Auto changeover unit should have manual bypass facility to through put the time code by-passing the unit in case the unit develops any problem. In manual mode the code output should be available even when the unit is off and it should be possible to select any code to output through a rotary switch.

The unit should have serial and parallel status output interfaces for data system interface. Serial RS232 interface is required for commanding the ACUs from PC to select a particular

code for transmission (if needed) when quality of all the codes are good. The unit should have Ethernet interface for completely monitoring/controlling the unit from

remote location. The unit should have dual power supply with ORed DC output.

1

Page 2: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

INPUTS:Code Inputs : Standard modulated IRIG-B input for UT part and Modified

modulated IRIG-B input for CDT part in single ended form through rear panel BNC’s. Code Input Level 6.5VppModulation Ratio 3:1

1PPS reference : Positive pulse with rising edge being the reference and minimum 10usecs pulse width.

Remote Control Input : Rs232 Interface at 1Hz rate to select a particular code in both the parts of ACU when commanded through PC via 9 pin D type female connector with format as given in table-3.This port is common for both UT & CDT parts.Protocol: Asynchronous mode with 1 stop, 8 data bits, no parity and 19200 baud rate.

Chain No : 2 bit parallel information indicating the ACU chain number through 4 pin circular connector. The input to the connector is configured through external input wiring of the connector. By reading these 2 bits ACU can identify its location.Byte 0 – (0 0) ACU chain-1Byte 1 – (0 1) ACU chain-2Byte 2 – (1 0) ACU chain-3

Network Configuration Input

Mac, IP address and port numbers of source and destination should be configurable by the user through RS232 Interface via 9 pin D type female connector. Protocol: Asynchronous mode with 1 stop, 8 data bits, no parity and 9600 baud rate.

OUTPUTS:Modulated Code Buffered Modulated Code Output through rear panel BNC in

Auto Mode. The code should not be regenerated and it should only be buffered by maintaining the time accuracy of less than ±30nano seconds with reference 1PPS. Selected Code connected through band switch to rear panel BNC in manual mode.

Status Output in parallel TTL.

Buffered parallel BCD status output representing all UT & CDT code statuses and transmitting chain details through 25pin D type connector with format as given in Table-1.

Serial Status Output through RS232 Interface.

Serial Status data of ACU at 1Hz rate for data system interface via 9 pin D type female connector (same port which is used for Remote control input and is common for both UT & CDT parts) with format as given in table-2.Protocol: Asynchronous mode with 1 stop, 8 data bits, no parity and 19200 baud rate.

2

Page 3: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

Ethernet Interface For Remote monitoring

Should provide status of all the time code information (UT&CDT) along with status of all the codes, ACU mode, Code selected for transmission in both the parts ACU (UT&CDT), odes like hold/run, advance/retard, preset/reset, power supply voltage levels, modulated code output level and time output from days through msecs as an unicast UDP Ethernet packet at 10Hz rate through RJ45 connector to the user configured IP address (as per format in table-4).

CONTROLS: (Independent controls for both UT & CDT part)Rotary Switch : 4 position Band Switch in front panel to select either AUTO

mode or Code 1 or 2 or 3 in manual mode.Push Button Switch : Miniature push button switch in front panel to select pages in

VFD module.Remote Enable Switch for Network Interface

: Toggle switch in rear panel to enable controlling of ACU from remote location through Ethernet interface.Status data output should be always available through network interface for monitoring at remote location with out any enable control.

DISPLAY:

2x20 char VFD module : VFD display module in front panel for displaying the data information, code status including error details of all the codes in the part (UT/CDT).

Separate display module for UT & CDT part is required.

Each code time information along with status and reason for rejection should be displayed in independent pages selected through push button switch. The first page of VFD should display the overall status of ACU.

LED indication : To indicate DC power supply voltages ( both power supplies and not ored outputs), ACU auto Mode status and code quality of all the time codes for both UT & CDT parts.

Code Transmission : The code transmitted by each part (UT & CDT) should be displayed by two separate seven segment displays of size one inch.

OTHER GENERAL SPECIFICATIONS:Dual Power Input : 230V, 50Hz AC Inputs through 3 pin MS circular connectors

and good quality Fuse holders at rear panel. Fan Instrument cooling fan ( 2 no’s), 230V AC, 50Hz, sound free

type mounted in side panels near power supplies with ventilation holes in both the side panels.

Dimension of unit 19inch rack mountable of height 2U or less.Operating Temperature -10°C to 70°CWarranty : Minimum One year warranty from the date of Supply and

acceptance of the system. Warranty certificate duly signed and 3

Page 4: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

stamped shall be furnished along with the supply of the items.OTHER SPECIFICATIONS:

The following logic should be followed for error checking and code selection for all the time

codes:

Expected code level is 6.5Vpp and if the code level goes below 5.4Vpp it should be

rejected for transmission by displaying “ ---- Code level low” message.

Expected Modulation ratio is 3:1. If it goes beyond 2:1 to 6.1 it should be rejected by

displaying the error message “----- code Modulation failure”.

If carrier loss is detected continuously for 3msecs, the code should be rejected by

displaying the error message “ ---- code failure”.

If error is observed in bit and marker width, immediately the code should be rejected by

displaying “ ---- code bit error/ marker error”.

The current frame data of the code should be checked for expected data by using the

previous frame data and if does not match, the code should be rejected by displaying

the error message “ ---- code Data check error”.

The frame length of each time code should be calculated by using the external reference

1PPS and in case it is not equal to 1 seconds (by allowing error limit of ±50usecs), the

code should be rejected by displaying error message “ ---- code frame length error”.

The Synchronization difference of all the codes with external reference 1PPS should be

calculated and if the difference exceeds ±500usecs, the code can be rejected by

displaying the error message “ ---- code Sync error”. In case if external reference failure

is noticed, the synchronization difference of chain-2&3 can be compared with chain-1

code for taking decision.

If the code quality is good in the all the above parameters, majority coincidence check

should be applied for selecting the code for transmission.

In case if all the time codes are different, no changeover should take place without

affecting the existing transmission and only the error message “ All codes are different”

should be displayed in the first page of VFD.

Dedicated hardware should be employed for testing each code quality and there should

not be any interconnection which may create total failure of the system.

4

Page 5: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

ChangeOver Logic:

Dedicated code selection logic hardware should be there for both UT & CDT parts with

out any interconnection.

Default selection when the unit is switched ON should be code-1 and if code-1 failure is

noticed, it should changeover to code-2 and if code-2 fails, it should changeover to code-

3 and if code-3 fails it should come back to code-1. The selection logic design should

take care of the above.

The final changeover of code should be very fast (<500nS) through analog switch with

out any code loss in the transmission. Two analog switches should be employed in

parallel to take care of single point failure and in case if one analog switch fails, it should

be indicated through display.

Any malfunction in the selection logic circuit should not select more than one code in the

analog switch output. This should be checked and indicated through alarm(buzzer) .

The final selected code for transmission (either through manual or auto mode) should be

displayed through a single 7 segment LED module in the front panel (both for UT &

CDT part).

Table-1 : Status Output in parallel TTL (Data System Interface)

25 pin D type female Signal Description1. CD3 QUALITY Count Down Code -3 quality2. UT3 QUALITY Universal Time Code -3 quality3, UT1 QUALITY Universal Time Code -1 quality4. UT2 QUALITY Universal Time Code -2 quality5. ACU UT SEL ‘A’ ACU UT Selection Address bit 'A'6. ACU UT SEL ‘B’- ACU UT Selection Address bit 'B'7. GND8. CD1 QUALITY Count Down Code -1 quality9. CD2 QUALITY Count Down Code -2 quality 10. ACU CDT SEL ‘A’ ACU CDT Selection Address bit 'A'17. ACU CDT A/M ACU CDT Mode Auto/Manual20. ACU UT A/M ACU UT Mode Auto/Manual25. ACU CDT SEL ‘B’ ACU CDT Selection Address bit 'B'

Table-2 : RS232 Serial Status Data Output format:5

Page 6: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

Byte Data Description Remarks1. In hex 0xde Start byte2. In ascii Tens of Seconds

CDT-1

3. In ascii Units of Seconds 4. In ascii Tens of Minutes 5. In ascii Units of Minutes 6. In ascii Tens of Hours 7. In ascii Units of Hours 8. In ascii Count status upper byte9. In ascii Count status lower byte10. In ascii Hold status upper byte11. In ascii Hold status lower byte12. In ascii Code status byte1-upper nibble13. In ascii Code status byte1-lower nibble14. In ascii Code status byte2-upper nibble15. In ascii Code status byte2-lower nibble16. In ascii ACU mode,selection status upper17. In ascii ACU mode,selection status upper18. In ascii Tens of Seconds

CDT-2

19. In ascii Units of Seconds 20. In ascii Tens of Minutes 21. In ascii Units of Minutes 22. In ascii Tens of Hours 23. In ascii Units of Hours 24. In ascii Count status upper byte25. In ascii Count status lower byte26. In ascii Hold status upper byte27. In ascii Hold status lower byte28. In ascii Code status byte1-upper nibble29. In ascii Code status byte1-lower nibble30. In ascii Code status byte2-upper nibble31. In ascii Code status byte2-lower nibble32. In ascii ACU mode,selection status upper33. In ascii ACU mode,selection status upper34. In ascii Tens of Seconds

CDT-3

35. In ascii Units of Seconds 36. In ascii Tens of Minutes 37. In ascii Units of Minutes 38. In ascii Tens of Hours 39. In ascii Units of Hours 40. In ascii Count status upper byte41. In ascii Count status lower byte42. In ascii Hold status upper byte43. In ascii Hold status lower byte44. In ascii Code status byte1-upper nibble45. In ascii Code status byte1-lower nibble

6

Page 7: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

CDT-346. In ascii Code status byte2-upper nibble47. In ascii Code status byte2-lower nibble48. In ascii ACU mode,selection status upper49. In ascii ACU mode,selection status upper50. In ascii CDT-1 frame length byte-1 upper nibble

CDT-151. In ascii CDT-1 frame length byte-1 lower nibble52. In ascii CDT-1 frame length byte-2 upper nibble53. In ascii CDT-1 frame length byte-2 lower nibble54. In ascii CDT-1 frame length byte-3 upper nibble55. In ascii CDT-1 frame length byte-3 lower nibble56. In ascii CDT-2 frame length byte-1 upper nibble

CDT-2

57. In ascii CDT-2 frame length byte-1 lower nibble58. In ascii CDT-2 frame length byte-2 upper nibble59. In ascii CDT-2 frame length byte-2 lower nibble60. In ascii CDT-2 frame length byte-3 upper nibble61. In ascii CDT-2 frame length byte-3 lower nibble62. In ascii CDT-2 Sync difference byte-1 upper nibble63. In ascii CDT-2 Sync difference byte-1 lower nibble64. In ascii CDT-2 Sync difference byte-2 upper nibble65. In ascii CDT-2 Sync difference byte-2 lower nibble66. In ascii CDT-2 Sync difference byte-3 upper nibble67. In ascii CDT-2 Sync difference byte-3 lower nibble68. In ascii CDT-3 frame length byte-1 upper nibble

CDT-3

CDT-3

69. In ascii CDT-3 frame length byte-1 lower nibble70. In ascii CDT-3 frame length byte-2 upper nibble71. In ascii CDT-3 frame length byte-2 lower nibble72. In ascii CDT-3 frame length byte-3 upper nibble73. In ascii CDT-3 frame length byte-3 lower nibble74. In ascii CDT-3 Sync difference byte-1 upper nibble75. In ascii CDT-3 Sync difference byte-1 lower nibble76. In ascii CDT-3 Sync difference byte-2 upper nibble77. In ascii CDT-3 Sync difference byte-2 lower nibble78. In ascii CDT-3 Sync difference byte-3 upper nibble79. In ascii CDT-3 Sync difference byte-3 lower nibble80. In ascii Tens of Seconds

UT-1

81. In ascii Units of Seconds 82. In ascii Tens of Minutes 83. In ascii Units of Minutes 84. In ascii Tens of Hours 85. In ascii Units of Hours 86. In ascii Count status upper byte87. In ascii Count status lower byte88. In ascii Hold status upper byte89. In ascii Hold status lower byte90. In ascii Code status byte1-upper nibble91. In ascii Code status byte1-lower nibble

7

Page 8: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

UT-1

92. In ascii Code status byte2-upper nibble93. In ascii Code status byte2-lower nibble94. In ascii ACU mode,selection status upper95. In ascii ACU mode,selection status upper96. In ascii Tens of Seconds

UT-2

97. In ascii Units of Seconds 98. In ascii Tens of Minutes 99. In ascii Units of Minutes

100. In ascii Tens of Hours 101. In ascii Units of Hours 102. In ascii Count status upper byte103. In ascii Count status lower byte104. In ascii Hold status upper byte105. In ascii Hold status lower byte106. In ascii Code status byte1-upper nibble107. In ascii Code status byte1-lower nibble108. In ascii Code status byte2-upper nibble109. In ascii Code status byte2-lower nibble110. In ascii ACU mode,selection status upper111. In ascii ACU mode,selection status upper112. In ascii Tens of Seconds

UT-3

113. In ascii Units of Seconds 114. In ascii Tens of Minutes 115. In ascii Units of Minutes 116. In ascii Tens of Hours 117. In ascii Units of Hours 118. In ascii Count status upper byte119. In ascii Count status lower byte120. In ascii Hold status upper byte121. In ascii Hold status lower byte122. In ascii Code status byte1-upper nibble123. In ascii Code status byte1-lower nibble124. In ascii Code status byte2-upper nibble125. In ascii Code status byte2-lower nibble126. In ascii ACU mode,selection status upper127. In ascii ACU mode,selection status upper128. In ascii UT-1 frame length byte-1 upper nibble

UT-1129. In ascii UT-1 frame length byte-1 lower nibble130. In ascii UT-1 frame length byte-2 upper nibble131. In ascii UT-1 frame length byte-2 lower nibble132. In ascii UT-1 frame length byte-3 upper nibble133. In ascii UT-1 frame length byte-3 lower nibble134. In ascii UT-2 frame length byte-1 upper nibble

UT-2135. In ascii UT-2 frame length byte-1 lower nibble136. In ascii UT-2 frame length byte-2 upper nibble137. In ascii UT-2 frame length byte-2 lower nibble

8

Page 9: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

UT-2

138. In ascii UT-2 frame length byte-3 upper nibble139. In ascii UT-2 frame length byte-3 lower nibble140. In ascii UT-2 Sync difference byte-1 upper nibble141. In ascii UT-2 Sync difference byte-1 lower nibble142. In ascii UT-2 Sync difference byte-2 upper nibble143. In ascii UT-2 Sync difference byte-2 lower nibble144. In ascii UT-2 Sync difference byte-3 upper nibble145. In ascii UT-2 Sync difference byte-3 lower nibble146. In ascii UT-3 frame length byte-1 upper nibble

UT-3

UT-3

147. In ascii UT-3 frame length byte-1 lower nibble148. In ascii UT-3 frame length byte-2 upper nibble149. In ascii UT-3 frame length byte-2 lower nibble150. In ascii UT-3 frame length byte-3 upper nibble151. In ascii UT-3 frame length byte-3 lower nibble152. In ascii UT-3 Sync difference byte-1 upper nibble153. In ascii UT-3 Sync difference byte-1 lower nibble154. In ascii UT-3 Sync difference byte-2 upper nibble155. In ascii UT-3 Sync difference byte-2 lower nibble156. In ascii UT-3 Sync difference byte-3 upper nibble157. In ascii UT-3 Sync difference byte-3 lower nibble158. In ascii UT-1 Sync difference byte-1 upper nibble

UT-1159. In ascii UT-1 Sync difference byte-1 lower nibble160. In ascii UT-1 Sync difference byte-2 upper nibble161. In ascii UT-1 Sync difference byte-2 lower nibble162. In ascii UT-1 Sync difference byte-3 upper nibble163. In ascii UT-1 Sync difference byte-3 lower nibble164. In ascii CDT-1 Sync difference byte-1 upper nibble

CDT-1

165. In ascii CDT-1 Sync difference byte-1 lower nibble166. In ascii CDT-1 Sync difference byte-2 upper nibble167. In ascii CDT-1 Sync difference byte-2 lower nibble168. In ascii CDT-1 Sync difference byte-3 upper nibble169. In ascii CDT-1 Sync difference byte-3 lower nibble170. In hex 0x0d171. In hex 0x0a Frame end byte

Table-3 : Remote Control Input Data Format(Data System Interface):

Command received Action to be taken in ACUsRemarks

0xe5 followed by 0x71 UT-1 code should be rejected and UT-2 should be selected for transmission in chain-1 ACU.

0xe5 followed by 0x72 UT-2 code should be rejected and UT-2 should be selected for transmission in chain-1 ACU.

0xe5 followed by 0x73 UT-3 code should be rejected and UT-1 should be selected for transmission in chain-1 ACU.

0xe5 followed by 0xa1 CDT-1 code should be rejected and CDT-2 should be selected for transmission in chain-1 ACU.

9

Page 10: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

0xe5 followed by 0xa2 CDT-2 code should be rejected and CDT-2 should be selected for transmission in chain-1 ACU.

0xe5 followed by 0xa3 CDT-3 code should be rejected and CDT-1 should be selected for transmission in chain-1 ACU.

0xe6 followed by 0x81 UT-1 code should be rejected and UT-2 should be selected for transmission in chain-2 ACU.

0xe6 followed by 0x82 UT-2 code should be rejected and UT-2 should be selected for transmission in chain-2 ACU.

0xe6 followed by 0x83 UT-3 code should be rejected and UT-1 should be selected for transmission in chain-2 ACU.

0xe6 followed by 0xb1 CDT-1 code should be rejected and CDT-2 should be selected for transmission in chain-2 ACU.

0xe6 followed by 0xb2 CDT-2 code should be rejected and CDT-2 should be selected for transmission in chain-2 ACU.

0xe6 followed by 0xb3 CDT-3 code should be rejected and CDT-1 should be selected for transmission in chain-2 ACU.

0xe7 followed by 0x91 UT-1 code should be rejected and UT-2 should be selected for transmission in chain-3 ACU.

0xe7 followed by 0x92 UT-2 code should be rejected and UT-2 should be selected for transmission in chain-3 ACU.

0xe7 followed by 0x93 UT-3 code should be rejected and UT-1 should be selected for transmission in chain-3 ACU.

0xe7 followed by 0xc1 CDT-1 code should be rejected and CDT-2 should be selected for transmission in chain-3 ACU.

0xe7 followed by 0xc2 CDT-2 code should be rejected and CDT-2 should be selected for transmission in chain-3 ACU.

0xe7 followed by 0xc3 CDT-3 code should be rejected and CDT-1 should be selected for transmission in chain-3 ACU.

Table-4 : Status Output Data Format through Network Interface:

Byte Data Description Remarks1. In hex 0xde Start byte2. In hex Hold Status Byte ( 0 or 1)

CDT-1

3. In hex Count status Byte (0x09 or 0x50)4. In hex Hours (0 to 99)5. In hex Minutes (0 to 59)6. In hex Seconds (0 to 59)7. In hex Code status byte18. In hex Code status byte29. In hex ACU mode, selection status byte10. In hex Hold Status Byte ( 0 or 1)

CDT-211. In hex Count status Byte (0x09 or 0x50)12. In hex Hours (0 to 99)13. In hex Minutes (0 to 59)14. In hex Seconds (0 to 59)

10

Page 11: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

CDT-215. In hex Code status byte116. In hex Code status byte217. In hex ACU mode, selection status byte18. In hex Hold Status Byte ( 0 or 1)

CDT-3

19. In hex Count status Byte (0x09 or 0x50)20. In hex Hours (0 to 99)21. In hex Minutes (0 to 59)22. In hex Seconds (0 to 59)23. In hex Code status byte124. In hex Code status byte225. In hex ACU mode, selection status byte26. In hex CDT-1 frame length byte-1

CDT-127. In hex CDT-1 frame length byte-2 28. In hex CDT-1 frame length byte-3 29. In hex CDT-2 frame length byte-1

CDT-230. In hex CDT-2 frame length byte-231. In hex CDT-2 frame length byte-332. In hex CDT-2 Sync difference byte-133. In hex CDT-2 Sync difference byte-2 34. In hex CDT-2 Sync difference byte-3 35. In hex CDT-3 frame length byte-1

CDT-3

36. In hex CDT-3 frame length byte-2 37. In hex CDT-3 frame length byte-3 38. In hex CDT-3 Sync difference byte-1 39. In hex CDT-3 Sync difference byte-2 40. In hex CDT-3 Sync difference byte-341. In hex Hundreds of Days ( 0 to 2)

UT-1

42. In hex Days (0 to 99)43. In hex Hours (0 to 99)44. In hex Minutes (0 to 59)45. In hex Seconds (0 to 59)46. In hex Code status byte147. In hex Code status byte248. In hex ACU mode, selection status byte49. In hex Hundreds of Days ( 0 to 2)

UT-250. In hex Days (0 to 99)51. In hex Hours (0 to 99)52. In hex Minutes (0 to 59)53. In hex Seconds (0 to 59)54. In hex Code status byte155. In hex Code status byte256. In hex ACU mode, selection status byte57. In hex Hundreds of Days ( 0 to 2)

UT-358. In hex Days (0 to 99)59. In hex Hours (0 to 99)60. In hex Minutes (0 to 59)

11

Page 12: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

UT-3

61. In hex Seconds (0 to 59)62. In hex Code status byte163. In hex Code status byte264. In hex ACU mode, selection status byte65. In hex CDT-1 frame length byte-1

UT-166. In hex CDT-1 frame length byte-2 67. In hex CDT-1 frame length byte-3 68. In hex CDT-2 frame length byte-1

UT-2

69. In hex CDT-2 frame length byte-270. In hex CDT-2 frame length byte-371. In hex CDT-2 Sync difference byte-172. In hex CDT-2 Sync difference byte-273. In hex CDT-2 Sync difference byte-374. In hex CDT-3 frame length byte-1

UT-3

75. In hex CDT-3 frame length byte-276. In hex CDT-3 frame length byte-377. In hex CDT-3 Sync difference byte-178. In hex CDT-3 Sync difference byte-279. In hex CDT-3 Sync difference byte-380. In hex UT-1 Sync difference byte-1

UT-181. In hex UT-1 Sync difference byte-2 82. In hex UT-1 Sync difference byte-3 83. In hex CDT-1 Sync difference byte-1

CDT-184. In hex CDT-1 Sync difference byte-2 85. In hex CDT-1 Sync difference byte-3 86. In hex 0x0d87. In hex 0x0a Frame end byte

Note: Count status Byte : 0x09 for Count down and 0x50 for count up Hold status Byte : 0x01 for Hold and 0x00 for Run 3 Frame length byte’s range: 0 to 9999999 ( hex equivalent of frame length in hundred nSecs with byte-1 as lower) 3 Sync difference byte’s range: 0 to 9999999 (hex equivalent of sync difference with out sign in hundred nSecs with byte-1 as lower) Code Status Byte-1 Format (Same for both UT & CDT part):

Bit Value Signal Data Details0 EC Flag (Carrier) 0 – Good 1- Bad1 LC Flag (Information) 0 – Good 1- Bad2 Code Level Flag 0 – Good 1- Bad3 Sync Flag 0 – Good 1- Bad4 DataCheck Flag 0 – Good 1- Bad5 Majority Flag 0 – Good 1- Bad6 Frame Length Flag 0 – Good 1- Bad7 Bit_Marker Flag 0 – Good 1- Bad

Code Status Byte-2 Format (Same for both UT & CDT part):12

Page 13: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

Bit Value Signal Data Details0 Bit Error Flag 0 – Good 1- Bad1 Marker Error Flag 0 – Good 1- Bad2 UT1 sync Flag 0 – Good 1- Bad3 UT2 sync Flag 0 – Good 1- Bad4 UT3 sync Flag 0 – Good 1- Bad5 CDT1 sync Flag 0 – Good 1- Bad6 CDT2 sync Flag 0 – Good 1- Bad7 CDT3 sync Flag 0 – Good 1- Bad

13

Page 14: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

II. GENERAL TERMS AND CONDITIONS:

This indent proposal is based on two part bid, Part-1 technical and unpriced part of the work and Part-2 Priced commercial part.

Documents Comprising the Bid

Bids shall be arranged in the following order.Part – I Technical and Unpriced Commercial Part

Technical and unpriced commercial part shall comprise the attachments as follows:

(a) Submission of bid letter along with one set of proposal document duly signed and stamped as token of acceptance

(b) All the annexures enclosed in proposal duly filled, signed and sealed

(c) Unpriced copy of schedule of prices with all other commercial terms and conditions duly filled (Prices to be kept blank), signed and stamped

(d) Audited balance sheet including profit and loss account for last three financial years showing annual turn over

(e) Latest income tax clearance certificate.

(f) List of projects in hand & completed during last 3 financial year indicating the name of client, contract person, contract value, nature of work, work completed, work balance, name of Consultant, month & year of commencement & completion etc.

(g) Any other relevant document, bidder desires to submit.

Part – II Priced Commercial Bid

Priced commercial bid shall contain schedule of prices duly filled in, signed and stamped. No deviations, terms and conditions, assumptions, conditions, discounts etc. shall be stipulated in price bid. Department will not take cognizance of any such statement and may at their discretion reject such bids.

Bid submission

Bids duly filled in by the Bidder should invariably be submitted as stipulated in the Letter inviting bid.

Part – I Techno-Commercial Part of the Bid for the Work

Part – II Price Part of the Bid for the Work

a) Department may open Part – I of the bid on the due date of opening subject to meeting the minimum evaluation criteria. Price Bids (Part-II) of technically and commercially acceptable offers shall be opened at a later date.

b) Department reserves the right to reject any or all the Bids without assigning any reasons thereof.

14

Page 15: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

MINIMUM CRITERIA FOR QUALIFICATION

S.No CRITERIA Vendor Compliance

(YES*/NO)

1.1. The firm should be registered with Registrar of companies and Sales/Trade tax/Service Tax department. Copies of PAN Number/TAN number/Sales Tax number along with registration certificate /service tax number along with registration certificate and Income-tax clearance certificate/Returns for last 03 years must be attached.

Firm should provide the following details to confirm the above criteria:

a) Provide PAN Number / TAN Number / GST Registration Number.

b) Provide Registration Certificate as proof of registration.

c) Provide Income tax return for last 3 years / Income tax clearance certificate.

1.2. Establishment of the firm must be more than 4 years old as on 01-12-2017 and the company turn over should be more than 1 crore.

Firm should provide the following details to confirm the above criteria:

a) Provide proof to confirm that the firm is 4 years old.b) Provide proof to show that company turnover is about 1

crore on an average for last 2 years.c) Provide balance sheet, profit and loss, audited balance

sheet for last 3 years.

1.3. Should have at least 2 Yrs experience in the field of “Design, Fabrication and supply of Digital systems”

1.4. Vendor/supplier shall submit other information in the enclosed supplier evaluation format. The bid submitted without the evaluation format will not be considered for evaluation.

*if YES please support with valid documents as proof.

15

Page 16: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

Supplier Evaluation Format

SDSC SHAR seeks response to the following questionnaire for assimilating data which would be used for evaluating the capability of the supplier for executing th e referred work. Hence, the supplier is requested to provide only genuine data and any discrepancy found at a later point of time may result in rejection of the supplier from purchase process. Furnishing of data cannot be construed as automatic qualification for participation in the tender. Questionnaire should be signed by a responsible and authorized person of the Company / Agency.

S.No Description Vendor Response

1 Name of the company :

2 Type of the Company(Proprietary/Pvt.Ltd/Public Ltd/ Joint Venture) provide Registration code

:

3 Registered address :  

4 Name & Address of the Office of the Chief Executive of the Company

:

5 Contact person for this tender with name & address and contact number

:   

6 Locations of the Branches of Company (if any)

:

7 From which is year the Company is in operation

:

8 Current Annual turn-over of the company :

9 The Profit & Loss Account details for the last 3 years which is duly audited and Submitted as part of the Annual Report.

:   

` in Lakhs only 2013-14 2014-15 2015-16

Total assets (i) :

Current assets (ii) :

Total liabilities (iii) :

Current liabilities (iv) :

16

Page 17: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

S.No Description Vendor Response

Net Worth (i-iii) :

Working capital (ii-iv) :

Turnover ` in lakhs :  

Profit/Loss ` in lakhs :

10. The major lines of business: :

11. Manpower details : Description Qty Remarks

Admin&Acct

Design & Analysis

Workmen (floor)

Supervisor

a. Vendor to fill in correct information as asked. Providing any false information, shall be liable to reject the parties

b. Vendor is requested to furnish all the asked information as applicable. As each & every information carries certain weightage during evaluation of offers. In absence of any information, it may ultimately will reflect in overall assessment of the offer

c. Vendor to attach separate sheet as Annexure where ever required to furnish the required information. Please attach your product catalogues/ leaflets and relevant technical information in support.

17

Page 18: shar.eprocure.isro.gov.in · Web viewCDT-1 Sync difference byte-3 upper nibble In ascii CDT-1 Sync difference byte-3 lower nibble In hex 0x0d In hex 0x0a Frame end byte Table-3: Remote

Details of last two years experience of vendor/supplier in executing similar type of work which are completed

Sl.No

Full postal address of the

client with Contact Person

Description of the work

Value of the work

(Rs. in Lakhs)

Completion Time as per

PO

Actual period of

completion

Reasons for delay

 1            

 2            

 3            

 4            

 5            

Note: In order to consider as valid experience, all the experience has to be supported with the completion certificate and purchase order

Signature of Authorised Person with Seal

18