E) RESPONSE DATES - TIMS Coding Structure Design






There are a number of Key issues for dates in Tenders including: 

A	Multiple dates and times in tenders eg:

	1	Date of Publication
	2	Date tender available
	3	Date Briefing Session
	4	Date questions
	5	Date responses
	6	Date Submission Due

	This requires a code to be allocated to each time and date entity.  The codes allocated
	comply with the UN/EDIFACT principles.  These UN/EDIFACT codes were defined to enable 
	international communication hence are language independent.

B	Time zone and time difference for responses

	Often tender responses require a hardcopy document to be placed in a tender box by a 
	certain	time.  Time zone differences and transport time become important issues for 
	tenders with short completion times particularly for international tenders.

C	Format for dates  02/08/2001, 02 Aug 2001, 2 August 2001 or 08/02/01 ?

	In Electronic Tendering times and dates it is important to ensure that Times and Dates
	are consistent particularly for reports eg current open tenders
	 		
	The use of standard date and time drop-down menus ensures not only consistence with 
	date formats but also the correct electronic transmission of the date and time format
	for each date/time required.


D	Sorting on dates

	A real benefit of using a uniform coding system for dates is the ability to sort
	on that date code. 

	This enables standard PC spreadsheet and database software to be used for receiving 
	information electronically.  A distinct advantage for Small and Medium size Enterprises
	that wish to implement E-commerce applications. 

E	Reducing the amount of information that has to be sent by using agreed codes

	By using an agreed code and format for the electronic transmission of time and dates 
	the time and costs to communicate and receive data is significantly reduced


ISO 8601 International Date and Time Format
Please use any of these formats for Electronic Information Interchange [EII] and E-business
applications. Each field uses the same code for computer-to-computer communication. Please review the 600 year code matrix. Feedback is appreciated as to whether the cycle should be 25 years or 26 years.
YEAR
MONTH
DAY
YEAR
MONTH
DAY
DAY (In Words)
YEAR
MONTH
DAY
DAY (In Words)
DATE CODES
 
Year Month Day Days of the week Weeks of the Year
2000 = aq Jan = a 1 = 1   13 = d 25 = p   M = Mon = Monday   y1 - yq = Wks 1 to 26
2001 = ar Feb = b 2 = 2 14 = e 26 = q T = Tue = Tuesday z1 - zr = Wks 27 to 53
2002 = as Mar = c 3 = 3 15 = f 27 = r W = Wed = Wednesday
2003 = at Apr = d 4 = 4 16 = g 28 = s H = Thu = Thursday
2004 = au May = e 5 = 5 17 = h 29 = t F = Fri = Friday
2005 = av Jun = f 6 = 6 18 = i 30 = u S = Sat = Saturday
2006 = aw Jul = g 7 = 7 19 = j 31 = v U = Sun = Sunday
2007 = ax Aug = h 8 = 8 20 = k  
2008 = ay Sep = i 9 = 9 21 = l
2009 = az Oct = j 10 = a 22 = m
2010 = ba Nov = k 11 = b 23 = n
2011 = bb Dec = l 12 = c 24 = o












Revised: S: 16:00 Fri 10/08/2001 Syd 2089
F: 19:00 Sat 28/04/2001 Syd 2089
Who: lsx
Authorised: sgg
Created: 16:00 Fri 10/08/2001 Syd 2065
By: lsx