@device[x2700] @make[report] @section(Introduction) The Computer Board, via the Joint Network Team, proposes to fund the purchase of a number of Network Level Converters for installation at different UK University sites. The procurement of this equipment is being carried out by the University of Edinburgh Computing Service acting as agents of the JNT. Any eventual contracts for the supply of equipment to meet this Operational Requirement (OR) will be between the suppliers and the University of Edinburgh. Where the words 'shall', 'will', 'must', 'required' or 'mandatory' are used the requirements are mandatory. Where the words 'should' or 'desirable' are used the requirements are desirable. Suppliers must make a point by point response to the mandatory and desirable requirements outlined in the OR. Suppliers must make clear which facilities, if any described in their tender will not be available by the quoted delivery date. @section(Equipment Required) The items required are:- @verbatim[ ? Network Converters ] Suppliers must quote terms under which other sites in the academic community could purchase further converters using Computer Board funds or other funds. Details of any bulk discounts available to individual sites must also be given. Further details are to be found in Section 8. If a manufacturer wishes to supply equipment as an additional item to existing approved products then the add-on cost and any performance consequences must be clearly stated. @section[Network Management] @subsection[General] Suppliers must specify how their equipment would be managed in a multi-supplier situation in order to provide a unified management environment. @subsection[Network Configuration Changes] It must be recognised that network equipment is likely to undergo frequent reconfiguration. Whatever mechanism is adopted by implementors of the network software on attached equipment it should be able to cope with network reconfiguration without necessitating a system reload in order for the changes to take effect. @subsection[Management Protocols] Any interim management protocols which are used by the converter must be based on non-proprietary standards which are in the public domain. Alternatively, the supplier must make two commitments: to place the protocols used in the public domain before the equipment is delivered; and not to modify these protocols subsequently without the agreement of the JNT. @subsection[Title-to-Address Mapping] IT is mandatory that support is provided for application titles conforming to the specifications of the JNT Name Registration Scheme (NRS), reference 9, including support for both standard ('long') and abbreviated ('short') names of an entity without having to configure its DTE address more than once. If this facility cannot be provided on delivery then a commitment to its availability within defined and reasonable timescales must be given. It is desirable that there is support for the NRS remote procedure call protocol (reference 10) to obtain the addressing information corresponding to an application title (in a PAD) or ISO NSAP (in a gateway) and to provide a caching mechanism to retain the most frequently used application titles in order to reduce local configuration requirements. @section[The Converter] @subsection[Overview and Functionality] The purpose of a converter is to convert between 'The Yellow Book - a Network Independent Transport Service' running over X.25 (1980) into the OSI Connection-Mode Network Service. The need for such a converter, including many of its basic functions, are described in the 'Transition to OSI Standards' report. @subsection[The User Interface] It is desirable that the user interface for incoming XXX calls is in line with the recommendations for private PAD implementors given in Annex B of the 'Green Book' (reference 3). In particular, the Terminal-PAD recommendations in section B.6 must be followed. It must also use the concept of the following operating modes: MESSAGE NATIVE TRANSPARENT as described in reference 3. @subsection[Operation and Management] Facilities for configuring the Converter must be provided, including the setting up of name, address and routing tables. Acceptable mechanisms include the use of asynchronous lines, manually via a terminal connected directly to the Converter or through the LAN, local configuration softwared stored in ROM, and downline loading over the LAN. It must be possible to store a new configuration in non- volatile memory. It is highly desirable that provision ismade for an operator to modify address tables without taking the Converter out of service. @subsection[Protocols] he basic protocols to be converted are X.25(1980) on one side, as defined in reference {BT}, and ISO 8208 (X.25(1984)) providing the ISO CONS on the other. The requirements for X.25 (1984) are defined in OSI Requirements Note 1 (ORN 1 - Reference {ORN1}). X.29, TS29 on the Yellow Book Service and other protocols over the Yellow Book Service will be carried on the X.25(1980) side. The ISO 8208 protocol will carry X.29 directly using the Q bit. The 'other protocols' will be carried by the ISO CONS as provided by ISO 8208 (X.25(1984)) instead of over the Yellow Book Service. The description of how to map Yellow Book to the OSI Connection-Mode Network Service are contained in OSI Requirements Note 3 (ORN 3 - Reference {ORN3}). @subsection[Performance and Limitations] The supplier must indicate the values of the following system limits which apply to the proposed system: Possible speeds of individual ports Maximum number of simultaneous calls Guaranteed data and packet throughput for a range of packet sizes and numbers of simultaneous calls. Maximum number of synchronous links supported and any constraints on which protocol set may run on eack link. Any other system limits must also be specified. @subsection[Connection Timeout] It is desirable to be able to timeout connections, clearing them after a period during which no activity has occured. If provided, this feature and its associated timer values must be a configuration option. @section[Maintenance and Support] Suppliers must offer a hardware and software support service for all equipment offered. Each site receiving one or more of the Ethernet Converters and Gateways which are the subject of this OR must have the option of taking out a maintenance contract under which the supplier repairs any hardware fault that might arise in return for a fixed monthly maintenance charge. Suppliers must guarantee toprovide this maintenance service, to those academic community sites which select this option, for a period of ten years from acceptance of the equipment. It is desirable that suppliers also offer the option of hardware maintenance on a time and materials basis; such a service must also be guaranteed for a period of ten years from acceptance of the equipment. Suppliers must also state the terms on which they would make available the necessary documentation, circuit diagrams, training and spare parts so that sites could elect tohave the equipment maintained by their own staff or by independent maintenance contractors. Suppliers should also offer a hardware maintenance service based on a return to factory of faulty components. The maximum delay between recovering a faulty module and delivering a replacement must be quoted. A software support contract must also be offered under which software faults are reported, fixes are provided for all but the most trivial of faults, and customers are supplied with new releases of software. Suppliers must specify the proposed terms of their software support contract. The supplier must confirm that all maintenance and support services apply to all parts of the UK (including Northern Ireland). @section[Procedures and Special Conditions] Tenders are invited for the supply of the equipment listed in section 2. Suppliers may tender for any combination of the four equipment types. Tenders must contain all the information necessary to evaluate the proposals fully. They must include in particular: (a)a hardware and software specification of the equipment offered, in particular the details of the CONS interface must be given; (b)the price per unit of each type of equipment offered; (c)the total purchase price for the complete set of equipment offered; (d)the cost per unit of each of the hardware maintenance options offered in response to section 7 of this OR; (e)the cost per unit of the software support service offered in response to section 7 of this OR; (f)the formula to be used for varying the cost of hardware and software support services during the lifetime of the equipment, and (g)a specification of the warranty conditions associated with the proposed equipment and confirmation that the delivery and acceptance procedures outlined in section 6 above are acceptable. Suppliers are also invited to quote prices for further units of equipment purchase by UK academic community sites. The detailed form of these supplementary offers is left open but might include quantity discounts based on the total number of academic community orders received within twelve months or conditions such as the use of a single agent site for handling all order and invoice administration. However purchases directly by individual sites must be an option that is quoted. All prices quoted must include VAT at the current rate. Prices for the equipment listed in section 2 must be fixed and must cover all costs of 6. Delivery and Acceptance The JNT has nominated the University of Exeter to conduct acceptance tests and evaluate the equipment. All equipment must be delivered to the University of Exeter before 31 October 1986. It is desirable that earlier delivery is proposed. The first item of equipment of each type will be subjected to a preliminary acceptance test consisting of: a functional check that all specified facilities work correctly; a check on the device's performance insofar as this is possible using the service facilities of the University of Exeter; a four week period of normal usage at the University of Exeter. Preliminary acceptance of subsequent items of each type will consist only of the functional check on facilities at the University of Exeter. Following preliminary acceptance, equipment will be shipped (at the University of Exeter's risk and expense) to other academic community sites designated by the JNT. Final acceptance of the equipment will consist of a four week period of normal usage at the destination site. Full details of the acceptance test procedures will be agreed with the selected supplier(s) prior to delivery of the equipment. @section(Maintenance and Support) Suppliers must offer a hardware and software support service for all equipment offered. Each site receiving one or more of the Converters which are the subject of this OR must have the option of taking out a maintenance contract under which the supplier repairs any hardware fault that might arise in return for a fixed monthly maintenance charge. Suppliers must guarantee to provide this maintenance service, to those academic community sites which select this option, for a period of ten years from acceptance of the equipment. It is desirable that suppliers also offer the option of hardware maintenance on a time and materials basis; such a service must also be guaranteed for a period of ten years from acceptance of the equipment. Suppliers must also state the terms on which they would make available the necessary documentation, circuit diagrams, training and spare parts so that sites could elect to have the equipment maintained by their own staff or by independent maintenance contractors. Suppliers should also offer a hardware maintenance service based on a return to factory of faulty components. The maximum delay between recovering a faulty module and delivering a replacement must be quoted. A software support contract must also be offered under which software faults are reported, fixes are provided for all but the most trivial of faults, and customers are supplied with new releases of software. Suppliers must specify the proposed terms of their software support contract. The supplier must confirm that all maintenance and support services apply to all parts of the UK (including Northern Ireland). @section(Procedures and Special Conditions) Tenders are invited for the supply of the equipment listed in section 2. Suppliers may tender for any combination of the four equipment types. Tenders must contain all the information necessary to evaluate the proposals fully. They must include in particular: (a) a hardware and software specification of the equipment offered, in particular the details of the CONS interface must be given; (b) the price per unit of equipment offered; (c) the total purchase price for the complete set of equipment offered; (d) the cost per unit of each of the hardware maintenance options offered in response to section 7 of this OR; (e) the cost per unit of the software support service offered in response to section {?7} of this OR; (f) the formula to be used for varying the cost of hardware and software support services during the lifetime of the equipment, and (g) a specification of the warranty conditions associated with the proposed equipment and confirmation that the delivery and acceptance procedures outlined in section {? 6} above are acceptable. Suppliers are also invited to quote prices for further units of equipment purchased by UK academic community sites. The detailed form of these supplementary offers is left open but might include quantity discounts based on the total number of academic community orders received within twelve months or conditions such as the use of a single agent site for handling all order and invoice administration. However purchases directly by individual sites must be an option that is quoted. All prices quoted must include VAT at the current rate. Prices for the equipment listed in section {? 2} must be fixed and must cover all costs of delivery to the University of Edinburgh and acceptance procedures. @section(Evaluation Criteria) Equipment which does not meet all mandatory requirements specified in this OR will not be considered. Proposals for each type of equipment outlined in section 2 will be considered separately. The extent to which desirable requirements are met will be taken into account. Any prices quoted for subsequent orders placed directly by academic community sites will be taken into account but with a lower priority than the other criteria. The final choice nevertheless remains with the JNT and the Univeristy of Edinburgh who shall not be obliged to disclose the reasons for their choice nor to accept the lowest or any tender. 10. Tenders and Further Information Tenders must be submitted by 6 February 1988 to: Dr L Clyne, 3 copies Mr B A C Gilmore, 3 copies Joint Network Team Computing Services c/o Rutherford Appleton Laboratory University of Edinburgh Chilton J C M B Didcot Mayfield Road Oxon OX11 OQX Edinburgh EH9 3JZ For further detailed technical information please contact Mr B A C Gilmore (Tel: 031- 667 1081 ext 2927). For general technical information and other matters please contact Dr L Clyne (Tel: 0235- 44 6459). @section(References) 1. (Pink Book) "Implementation Details for Protocols on CSMA/CD LANs", JNT/CSMA/CD LAN (85), August 1985. 2. ISO DIS 8802/3 "CSMA/CD Access Method and Physical Layer Specifications" 1985. 3. (Green Book) "Character Terminal Protocols on PSS", SG3/CP (81)/6, February 1981. 4. CCITT Recommendation X28, 1980. 5. ISO DP 8348/DAD2 "Addendum to the Network Service Definition Covering Network Layer Addressing" 1985. 6. ATS "Networking over Asynchronous Lines", CP (83)12, February 1983. 7. British Telecom Technical User Guide 17, February 1984. 8. Simple Screen Management Protocol, JNT, 1985. 9. JNT Name Registration Scheme, Technical Guide, JNT, April 1983. 10. Remote NRS Lookup Protocol - NRS/9.