ࡱ>    M ubjbj== %x WW%pL"l l &  .f.f.f8ff g\ UFrr4-c?ѢTTTTTTT$X ZUV {U_ U4___ V R(_T_P_VFH 3 6V 2 f I |Y.f3&R(F2 KUHU- [@[2_  Attachment A Technical Specifications List Of Abbreviations AC Alternating Current ANSI American National Standards Institute ASN Abstract Syntax Notation ATM Asynchronous Transfer Mode AUI Attachment Unit Interface BNC Bayonet Neill Concelman (connector) [electronics] CAD Computer Aided Design (sometimes seen as CAD/CAM) CAE Computer-Aided Engineering || Common Application Environment CASE Computer Aided Software Engineering CPU Central Processing Unit CRT Cathode Ray Tube DAC Dual Attached Concentrator DAS Dual Attached Station DAT Digital Audio Tape DBMS DataBase Management System (rdbms for Relational) DMA Direct Memory Access DPI Dots per Inch DS3 Digital Signal (level) 3 DVT Digital Video Tape ECAD Electronic Computer Aided Design EIA Electronic Industries Association FDDI Fiber Distributed Data Interface FIPS Federal Information Processing Standards GByte Gigabyte GIS Geographic Information System GUI Graphical User Interface HiPPI High Performance Parallel Interface HPGL Hewlett Packard Graphics Language HSSI High Speed Serial Interface Hz Hertz (cycles per second) ICMP Internet Control Message Protocol IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force I/O Input/ Output IP Internet Protocol IPI Intelligent Peripheral Interface ISO International Standards Organization LAN Local Area Network MAC Medium Access Control MAU Medium Attachment Unit Mbit Megabit MByte Megabyte Mbps Megabits per Second MFLOPS Millions of Floating Point Operations Per Second MIB Management Information Base MIC Media Interface Connector MIPS Million Instructions Per Second msec Milliseconds NASA National Aeronautics and Space Administration NASTRAN NAsa STRuctural ANalysis NFS Network File System NI Network Interface NTP Network Time Protocol NTSC National Television Standards Committee OODBMS Object-Oriented Database Management System OC3 Optical Carrier 3 (155 Mbps SONET rate) OSHA Occupational Safety and Health Administration OSI Open System Interconnect Pbyte Petabyte PC Personal Computer PHIGS Programmers Hierarchical Interactive Graphics System PHY Physical Layer Protocol PMD Physical Media Device RAM Random Access Memory RDBMS Relational Data Base Management System RFC Request For Comments RFP Request For Proposal RMON Remote Monitor/Monitoring ROM Read-Only Memory SAC Single Attached Concentrator SAS Single Attached Station SMP Symmetric MultiProcessing SMT Surface Mount Technology SONET Synchronous Optical NETwork SPEC Standard Performance Evaluation Corporation SQL Structured Query Language TBD To Be Designed/Determined TByte Terabyte TCP Transmission Control Protocol UDP User Datagram Protocol VC Virtual Circuit VHS Video Home System (VCR) VP View Processor VDT Video Display Terminal WAIS Wide Area Information Server WAN Wide Area Network WORM Write Once, Read Many time 1. Introduction Section 1 provides a general overview of the structure of these technical specifications. 1.1. Background The computer facilities at NASA are being systematically enhanced by incorporating the latest in state-of-the-art computer system technologies. These improvements will enable NASA to remain at the leading edge in scientific and engineering processing performance and capabilities and to provide the user community of researchers and engineers with the most advanced and powerful computer tools available. In support of this activity NASA is establishing Indefinite Delivery/Indefinite Quantity contracts of scientific and engineering computer systems and supporting equipment. The computer systems will provide computational and graphics capability to the scientific and engineering disciplines supporting NASAs core missions. The specifications presented in this document represent a comprehensive set of requirements intended to provide a complete environment for computational analysis by NASA engineers and scientists. 1.2. Requirements Structure The very broad range of NASAs functions in space, earth science, aeronautics, manned flight, mission operations and other activities, results in an equally broad range of computational requirements and consequently a requirement for a broad range of UNIX based computer systems and support equipment. The requirements are structured in a way that clarifies NASAs needs and categorizes the requirements on the basis of application functions. This structure is defined through two categories: Category A consists of a set of functional computer system classes; Category B consists of complementary products and services that enhance and support the computer system functions. This procurement is for 14 competition areas consisting of 9 Category A computer system classes, and 5 Category B supporting equipment classes. Each of the classes has specific requirements and functional tasks that must be met by the offerings in that class. However, the potential usage of any class is broad and may be based on a variety of applications beyond the specific class definition. These class groupings are to ensure that the Government has a sufficient set of the best available tools for given tasks. The class groupings do not imply either exclusive product offerings by the contractor nor do they restrict the Government from making best value judgments as to which class to use to meet their specific requirements. 1.2.1. Category A Structure The prelude to the requirements includes the definitions of each computer system class used to identify the general set of applications or environments that distinguish each class. The class definitions intentionally have overlap to ensure that there are no major gaps in requirements. Class definitions are given in Section 2 of this document. Each of the nine computer system classes is still broad and may represent a variety of applications beyond the specific class definition, yet these groupings produce enough commonality of requirements that applications in a class can share the same hardware platform. Some of the classes are clearly linked to specific functional tasks such as CAD, CAE, or Graphics. Other classes may be more general purpose in nature and are distinguished through a number of factors, including performance requirements. Each class represents not a single specific computer system, but instead represents a family of systems with a range of capabilities. In order to simplify requirements, each class is represented by two base systems. Within each class, the two systems are differentiated by factors specific to the class with each referred to as a subclass. These subclasses are identified as a and b and are always referred to with the class number. For example, class 3/b is computer system Class 3, subclass b. These base systems are generally distinguished by performance, upgradability and growth potential and define the minimum range of family of systems that should be provided on the contract. It is anticipated that systems will be made available on the contract through the Available Components list which are compatible with the base systems but which also both fill in and expand upon the requirements fulfilled through the base systems. To ensure a certain level of commonalty exists across all platforms in all computer system classes and to maximize the Open Systems Environment, a set of general requirements referred to as the Core Specifications have been developed. The core specifications apply to all classes and must be met by all computer system class proposals, unless an exception is noted within a Class specification. The class specific requirements are combined with the core specifications to produce the nine separate computer system specifications In general, application software such as CAD packages, databases, visualization software, etc. must be supported on the computer systems, but need not be provided (i.e. are not mandatory deliverables) unless specifically noted in the mandatory deliverables list in Attachment B. These are referred to as non-mandatory software. A set of mandatory add-on equipment and upgrades is identified in each class to allow for system enhancements. Each class also includes an available components list consisting of desirable items and other software and hardware which provides depth and breadth to the vendors offerings, such as computer systems in ranges of sizing and functions that complement the basic subclass systems and non-mandatory software. 1.2.2. Category B Structure The category B classes consist of a set of capabilities that span across all computer system classes. This requirement creates five additional competition areas in this RFP: 1) Server Support Devices, 2) High-end Network Devices, 3) Computer Security Tools, 4) Mass Storage Devices, 5) Advanced Video and Display tools. Each class has a set of mandatory specifications. In addition, each class includes an available components list consisting of desirable items and other software and hardware that provide depth and breadth to the contract. 1.3. Structure of This Document This section describes the section layouts of the technical specifications 1.3.1. Category A Computer System Classes The Core Specifications, which apply to all Category A classes, are presented in Section 3. The specific requirements associated with each class and derived from the applications to be supported are presented in Section 4. 1.3.2. Category B Classes Requirements for this category are described in separate sections. Category A requirements do not apply to these classes. Server Support Devices requirements are described in Section 5. High-end Networking requirements are described in Section 6. Computer Security Tools requirements are described in Section 7. Mass Storage Device requirements are described in Section 8. Advanced Video and Display tools requirements are described in Section 9. 1.4. Performance Measurement Performance benchmarks are used to evaluate the appropriateness of the proposed equipment. These performance requirements represent a minimum sizing of the requirement for a class and are based on the estimated performance levels required by applications in the class, and in part based on our best estimate of general technology levels that are expected to be available in the time frame of this solicitation. A minimum performance is specified in terms of a variety of benchmarks which may include: NASA specific benchmarks, a CPU performance benchmark (SPEC Benchmark Suite), NASA I/O benchmarks (mallards) and others as determined. In summary, the benchmarks are designed/selected to focus on the particular strengths required of individual classes rather than being applied in blanket form across all classes. For most subclasses a SPECmark and SPECrate value is given. In those cases, the SPECmark value refers to uniprocessor systems and the SPECrate value to multi-processor systems. 1.5. Terminology Key terms are described in this section and more general definitions are provided in Section 1.6. 1.5.1. Provides / Support Two key terms in the technical specifications are: provide and support. Use of the term provide indicates a product, service, or capability that is either a mandatory or, if modified by the term desirable, a desirable deliverable item. All mandatory deliverable products, services and capabilities are identified in the Delivery Lists in Attachment B. A mandatory deliverable is either part of the base system, a separate add-on line item, or a separate upgrade line item. If an item is identified in the technical section as needing to be provided and is not listed in Attachment B as a separate add-on or upgrade line item, it is included as part of the Base system. Note that the term provide implies an item is either a part of every delivered base system or is a separately orderable line item. This distinction is made in the Delivery Lists in Attachment B. For example, a FORTRAN compiler must be provided (as indicated in Section 3.3.2.5.a.). But the Delivery Lists indicate that the FORTRAN compiler is a separately orderable line item and it is estimated that only a certain percentage of the base systems will be purchased with a FORTRAN compiler over the life of the contract. Use of the term support indicates a product, service, or capability which the systems must be capable of fully utilizing but which are not part of either the mandatory or desirable deliverable list. When support is used in reference to a software product, a version of the product that can execute on the system must be available in the commercial and/or public domain arena. Supported products, services, or capabilities can be part of the available components list. 1.5.2. Deliverables The delivery lists use abbreviated terminology for clarity in enumerating delivery items. The complete specifications for these delivery items are fully described in Sections 3 through 10. As an example, the delivery list identifies the operating system as a deliverable and the full set of specifications for that operating system is given in Section 3 as amended by Section 4. This includes items such as file system, system administration, shells, etc. Deliverables are divided into mandatory and non-mandatory categories: 1.5.2.1. Mandatory Deliverables Each of the separate class specifications produces a separate set of mandatory deliverables for each class. These delivery requirements are specified in Attachment B of this RFP. The deliverables are divided into a Base Deliverable, and Add-on / Upgrade Deliverables. The Base Deliverables represent the minimum system configuration to be delivered for each equipment category. Add-on deliverables are mandatory line items that may be added to the Base deliverable at the discretion of the end-user. Upgrade deliverables are mandatory line items which upgrade; e.g. additional disk and/or memory, the Base deliverables at the discretion of the end-user. 1.5.2.2. Non-mandatory Deliverables Non-mandatory deliverables are items that go beyond the mandatory deliverables. Non-mandatory deliverables are identified through the available components list and include desirable features, additional technology and other software and hardware that provide depth and breadth to the offering. 1.5.3. Minimums / Desirables / Advanced Technology / Additional Technology All technical specifications fit into one of four categories: minimum mandatory; desirable feature; advanced technology, or additional technology. If a technical specification is not explicitly identified as advanced technology, additional technology or a desirable feature, it identifies a minimum mandatory that must be met. Alternatively, if a technical specification is identified as advanced technology, additional technology or a desirable feature, it is not a minimum mandatory but a technology, item or feature that the Government deems to have value if available. If a technical section contains the term desirable, then the section identifies a feature that the Government desires but which the vendor is not required to provide or support. If a technical section contains the term advanced technology, then the section identifies advanced capabilities that provide the Government with significant added benefit. These are typically features that are either at the cutting edge of technology or for which standards (industry or de-facto) are still forming. A technical requirements section may contain the term additional technology. This designation identifies a basic capability that is intended to provide the Government with added value if the additional technology is provided in the Available Components list. Typically, additional technology indicates broad grouping of technology that, if included in the Contractors offerings, will provide the opportunity for one-stop solution shopping. For example, network technology is an additional technology in the Mass Storage Devices class as network products are an integral feature of many mass storage systems. 1.6. Assistive Technology All workstations available and procured through this Contract must be technically capable of supporting commercially available and appropriate technology to ensure that Federal employees with disabilities will have access to and use of that technology unless a department or agency exception to this requirement exists. 1.7. Definitions To clarify meaning of some terms used in this specification, some definitions are given here. Add-ons:Add-ons are mandatory line items which may be added to the Base deliverable at the discretion of the end-user. Additional TechnologyA basic capability that is intended to provide the Government with added value if the additional technology is provided in the Available Components list.Advanced TechnologyAdvanced capabilities that provide the Government with significant added benefit.Available Bus Slots:The number of unused bus slots available for expansion after satisfying the requirements of the minimum mandatory deliverables and the maximum disk storage requirements for the base computer system.Available ComponentsNon-mandatory deliverables including desirable features, additional technology and other software and hardware that provide depth and breadth to the offering.Binary Compatibility:Within a class (and across subclasses in the class), source code, object code, libraries, and linked or loaded executables, which are not device dependent, can be freely transported from any computer system in the class to any other system in the class and execute successfully without modification.Base SystemsThe systems which must meet the minimum mandatory specifications and be provided for on the ContractCategory: A grouping of classes based on similar objectives and/or overall structure Class: A grouping of technological requirements based on common functionality Class Specific SpecificationsSet of technical specifications which specific to the given classComputer Room Environment:Facilities in which special environmental factors are maintained, such as controlled temperature and humidity, where noise is not limited by office requirements, and in which reliable power systems are available and/or are at levels other than the standard 110 volt, 60 Hz. Computer System:A computer workstation or serverCore SpecificationsSet of technical specifications which are included in all requirements within the specified category, class, or groupDesirable FeatureA feature that the Government desires but which the vendor is not required to provide or supportMallards:Unit of measurement in nasa-io benchmark that produces a disk I/O performance index measured in Mallards.Mandatory DeliverablesProducts which must be included in the Contract in order to meet the mandatory requirements of the classMandatory SpecificationsSet of technical specifications which must be meet by the mandatory offeringsNon-Mandatory DeliverablesProducts which go beyond the mandatory deliverables, are identified through the available components list and include desirable features, additional technology and other software and hardware that provide depth and breadth to the offering. Non-Mandatory Desirable Feature:A capability that is desired by the Government but not required.Office Environment:A human work area providing moderate environmental conditioning but with limited capacity to support or provide unusual power or temperature/humidity requirements and one which may be easily upset by equipment emitting excessive heat and/or noise. Open Bus Architecture:A bus with multivendor support. This means that there is an industry published specification to enable third party connectivity. Open Systems Environment:The comprehensive set of interfaces, services, and supporting formats, plus user aspects, for interoperability or for portability of applications, data, or people, as specified by information technology standards and profiles. Source: IEEE P1003.0 POSIX Committee. Provide:Indicates a product, service, or capability that is either a mandatory or, if modified by the term desired, a desirable deliverable item. SPECmark:The SPEC benchmark suite measures overall system CPU performance such as:The term such as is used to list example products which are known to meet the stated capability and for which products which also meet the stated capability may be substituted.SupportIndicates a product, service, or capability which the systems must be capable of fully utilizing but which are not part of either the mandatory or desirable deliverable list.Upgrades:Upgrades are mandatory line items which upgrade; e.g. additional disk and/or memory, the Base deliverables at the discretion of the end-user. Virtual File SystemA virtual file system is an abstraction of a physical file system implementation. It provides a consistent interface to multiple file systems, both local and remote. This consistent interface allows the user to view the directory tree on the running system as a single entity even when the tree is made up of a number of diverse file system types. The interface also allows the logical file system code in the kernel to operate without regard to the type of file system being accessed 2. Contract Definitions Section 2 provides general paragraph descriptions of the various SEWP classes. 2.A. Category A: Computer System Classes This Section provides general paragraph descriptions of the SEWP classes in Category A. 2.A.1. Class 1: CAE/CAD Electronic Circuit Design Computer Systems These computer systems will be used for the development of electronic devices including: Custom analog chips, custom and semi-custom Ultra Large Scale Integration (ULSI) Application, Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and High speed digital, analog and mixed signal Printed Circuit Boards (PCBs). Specific functions include: transistor level design, simulation and characterization, Verilog/VHDL Registered Transfer Logic (RTL) design and simulation, gate level simulation, static timing analysis, ASIC place and route, PCB place and route, and PCB signal integrity analysis An extensive network of computer systems utilizing the Cadence tool suite, the Synopsys tool suite, and CAE/CAD software is currently in use at NASA. Licenses are maintained on a license server while the individual applications are run on the users local system. The tool suites are usually located on a server but may also be installed locally. New systems must be compatible with the existing systems and tool suites. Each system must be fully compatible and interoperable with the Cadence and Synopsys tool suites. Class 1/b systems may be used for RTL design and simulation, while class /1a systems may be required for the remaining functions. When used as a server, these systems may require mass storage. 2.A.2. Class 2: CAE/CAD Mechanical Design Computer Systems These computer systems will be used to support mechanical engineering tasks including structural analysis, mechanical design, and thermal analysis. To accomplish this support, these computer systems must be able to run a wide suite of engineering application software packages including commercial MCAD software, structural analysis programs such as NASTRAN, and analysis pre- and post processing tools. High speed, double precision floating point performance is required together with fast, high resolution, 3D color graphics. Systems in this class are considered turnkey with minimal applications development. The class 2/a systems may also be used as code or data servers for the low-end systems. 2.A.3. Class 3: Mass Storage Server These Unix-based servers will be used to run high-end hierarchical mass storage systems, storing and retrieving hundreds of gigabytes of data each day, 24 x 7. Fast networking such as HiPPI and Gigabit Ethernet will be used to access the data. Data will be stored initially on high-performing RAIDed disk subsystems and then copied to high-performing tapes within robotic libraries or optical jukeboxes. It is staged back to disk automatically upon retrieval. Users expect stores and retrieves to be accomplished within seconds. These systems are anticipated to be used in conjunction with mass storage devices as defined in Class 13. 2.A.4. Class 4: Database Server These computer systems will be used to house large data volumes and large databases. Applications are typically based on commercial DBMS packages. Historically these DBMSs have been relational (RDBMS) but this system should also support object oriented databases (OODBMS). Typical use of this class would be to maintain a data base of spacecraft mission parameters, catalogs of telemetry data sets, catalogs of derived science data sets, and ancillary data. In addition, this class would typically provide capability for document scanning and archival and digital libraries. When used with a DBMS, this class would most typically operate in a client/server architecture with this class providing the server function. The client function would be provided by other computer system classes, and existing servers and workstations on the NASA LANs. The critical features of this class are high level of transactions per second, high volume of network traffic, fast disk access, large amounts of memory (RAM), high volume of memory to disk transfers, and large amounts of secondary storage. It is perceived that the Data Server will most likely reside away from the users work area in a location easily accessible to many LAN users. System should be capable of running Internet information servers, examples would be WAIS and World Wide Web (WWW). 2.A.5. Class 5: High-performance Visualization Computer Systems These computer systems will be used to provide the highest quality in the visual representation of data to the user. Typical applications from the Earth and Space sciences communities are manned and unmanned spacecraft studies, launch and deployment sequences, and data analysis. Earth and space scientists require the ability to transform volumetric data at high rates to view different perspectives quickly. Additionally, photo realistic representations of data such as the planet Earth with full texture maps are needed to accommodate the overlay of geophysical parameters obtained from spacecraft observations. Three dimensional simulations of the Earth system that generate many gigabytes of data are performed on NASA supercomputers. Visualization and understanding of these simulations on high performance 3D graphics computer systems is mandatory to review the expected data volumes generated from the simulations and correlated with large amounts of data obtained from spacecraft sensors. Applications from the robotics communities include modeling the space station and robotic assembly and the space shuttle and arm assembly, and virtual reality. A critical need to support the real-time modeling of these vehicles is the high speed animation of these vehicles and their antennas (or arms), where the antennas (or arms) move independently of each other. Computer systems must be able to display large numbers of polygons per second to meet the animation needs of the robotics community as well as providing a high degree of graphical representation of the objects displayed. 2.A.6. Class 6: High Performance Compute Servers The Compute Server class of systems and services will be used to provide systems able to perform very compute-intensive traditional optimized applications such as modeling, and mathematical analysis. Applications include but are not limited to atmospheric and oceanographic modeling, ocean color or crustal dynamics studies, ozone and sea-ice mapping, radio astronomy, high-energy astrophysics applications, flight dynamics computations, and fluid flow dynamic process modeling. The critical features of this class are high compute capability, fast primary storage and network communications, and large data storage capability. 128-bit arithmetic may be needed to support these requirements. This class of system will most likely reside away from the users work area and be accessed primarily over the network. This class will include hardware systems and peripherals, software and software licenses, and hardware and software maintenance services including analyst support. 2.A.7. Class 7: Science and Engineering Research Computer Systems These computer systems will be used to support scientific and engineering research tasks including data conversion and data plotting. These systems will be used to research a variety of scientific and engineering issues such as engineering equations with thermodynamics and transport properties for simulating, analyzing compressor/combustion/turbine data, climate modeling techniques, and data analysis from Space and Earth satellite systems. These computer systems must be able to run several type of engineering application software packages including commercial MCAD, ESS, DAQ, Easyplot, and IDEAS software, and structural analysis programs such as NASTRAN. They must also support major scientific application software packages such as IDL, IMSL and SAS. 2.A.8. Class 8: Earth Science Computer Systems The Earth Science class of systems and services will be used to provide systems able to perform compute and I/O intensive optimized applications such as modeling, data processing, and mathematical analysis. Applications include, but are not limited to, simulating the Earths climate, modeling a variety of processes in the atmosphere, ocean, or land, processing large quantities of spacecraft data and reducing them to usable information, and assimilating spacecraft data into models. Systems in this class will run a large variety of COTS applications in the areas of data/image processing (e.g. IDL/ENVI, Matlab), Geographic Information Systems (e.g. ArcInfo), integrated environments (e.g. Mathematical), etc. The critical features of this class are high compute capability, fast primary storage and network communications, and large data storage capability. Systems in this class may at times also support high-end real-time functions. These computer systems will also be used to provide the highest quality in the visual representation of data to the user. Many Earth science applications will require the ability to transform volumetric data at high rates to view different perspectives quickly. Three dimensional simulations of the Earth system generate many gigabytes of data. Visualization and understanding of these simulations on high performance 3D graphics computer systems is mandatory to review the expected data volumes generated from the simulations and to correlate these with large amounts of data from spacecraft sensors. This class will include hardware systems and peripherals, software and software licenses, and hardware and software maintenance services. 2.A.9. Class 9: Space Science Computer System The Space Science class of systems and services will be used to provide systems able to perform very compute-intensive optimized applications such as modeling and mathematical analysis. Applications include but are not limited to simulating space plasmas, magnetofluids, and the galactic and extragalactic source regions of radio and high-energy electromagnetic emissions; modeling of the solar interior and atmosphere; reducing large quantities of spacecraft data to useable information; and combining spacecraft data with modeling codes. The critical features of this class are high compute capability, fast primary storage and network communications, and large data storage capability. Systems in this class may at times also support high-end real-time functions in cooperation with computer systems performing primary data ingestion from spacecraft and other missions. These computer systems will be used to provide the highest quality in the visual representation of data to the user. Many space science applications will require the ability to transform volumetric data at high rates to view different perspectives quickly. Three dimensional simulations of the Sun-Earth system, of the Sun, and of galactic and extragalactic objects generate many gigabytes of data. Visualization and understanding of these simulations on high performance 3D graphics computer systems is mandatory to review the expected data volumes generated from the simulations and to correlate these with large amounts of data from spacecraft sensors. This class will include hardware systems and peripherals, software and software licenses, and hardware and software maintenance services. 2.B. Category B: Complementary Products & Services Categories This Section provides general paragraph descriptions of the SEWP classes in Category B 2.B.1. Class 10: Server Support Devices This class consists of Input and Output peripherals and other equipment which support and complement the full implementation of UNIX based computer systems throughout NASA. These items may be purchased by the Government separately from the computer systems but rely on standards and standard interfaces to ensure interoperability with the computer systems. Included in this class are both printers, multifunction machines and plotters for outputting textual and graphical files; X terminals and other low-end client systems to allow user connectivity to a full range of computer systems; scanners to allow inputting of information from hard-copy forms; and PDAs (Personal Digital Assistants) and UNIX portables to allow mobile access to individuals computing needs. 2.B.2. Class 11: High-End Networking This class consists of a range of network equipment in support of the full implementation of UNIX based computer systems in the NASA network environment. These items may be purchased by the Government separately from the computer systems but rely on standards and standard interfaces to ensure interoperability with those systems. The base technologies for NASA LANs are Ethernet, FDDI and ATM. Hardware, including hubs, switches, routers, NFS routers, concentrators and diagnostic tools, and software including network management are included in this class. Due to the wide range of the current installed NASA network systems and the variety of function and performance requirements, a key requirement in this class is the depth and breadth of the available equipment. 2.B.3. Class 12: Computer Security Tools This class consists of hardware and software needed to support a full implementation of computer systems and infrastructure in the NASA network environment. These items may be purchased by the Government separately from computer systems but rely on standards and standard interfaces to ensure interoperability with the computer systems and the supporting networks. Items in this class will include password tools, firewalls, auditing tools, intrusion detection systems, encryption capabilities, monitoring tools, remote access and authorization tools. 2.B.4. Class 13: Mass Storage Devices This class consists of storage devices; e.g. Hard disks and Tape systems which can be used by computer systems in Category A. While it is anticipated that products in this class will be purchased for use with any of the Category A systems, this class is particularly concerned with providing mass storage I/O devices for use with Mass Storage Servers as defined for Class 3: Mass Storage Server. 2.B.5. Class 14: Advanced Video and Display Tools This class consists of a range of equipment in support of digital television image production and related imaging and display tools. The Government may purchase these items separately from computer systems, but rely on standards and standard interfaces to ensure interoperability with those systems. The hardware in this class includes High Definition (HD) and Standard Definition (SD) Digital TV (DTV) equipment for video acquisition, production, post-production, distribution, and display. It is essential that this class include products which meet the Digital Television Standards for NASA (NASA-STD 2818 dated April 4, 2000). Additionally, the increasing complexity and volume of scientific data benefit from paradigms for interaction and visualization that are much closer to normal human interaction in the physical world. These paradigms require immersion and stereoscopic viewing for three-dimensional data, tracked and/or haptic devices with high degrees of freedom, and audio processing systems for data sonification. These devices act as input/output peripherals to developmental computer systems. 3. Category A: Computer System Core Specifications Section 3 provides the core technical specifications for all Category A: Computer System Class Equipment. 3.1. Introduction This section provides a general overview of the core specifications. 3.1.1. Purpose The purpose of this section is to define the Core Specification requirements for high performance computer systems to support technical scientific or engineering tasks at NASA facilities. 3.1.2. Background One of the key objectives of this procurement is to support and enhance the established UNIX based Open Systems Environment within NASA. That Open Systems Environment must extend over nine different computer system classes. The potential exists to award contracts for computer systems to nine different vendors and could result in nine (or more) different operating systems. To minimize the potential diversity in the computer system environments, a Core Specification is provided to maximize the uniformity (and Openness) of environments across all classes. The Core Specifications apply to the base and mandatory products for all classes of computer systems, unless a deviation to the Core Specifications is noted in the Class Specific Sections. Each class will also have its own unique specifications that are identified in Section 4. 3.1.3. Requirements The vendor computer system base and mandatory offerings shall meet all mandatory specifications provided in this Section (3) unless a deviation to the Core Specifications is noted in the Class Specific Section (4). These systems are intended to meet the NASA requirements over the life of the contract. The use of an indefinite quantity contract will enable acquisition of systems and services, as required, via delivery orders. 3.2. Hardware This section describes the core hardware specifications. 3.2.1. Chassis and Central Processing Unit (CPU) Requirements Each system shall provide: all required peripherals, memory and I/O subsystems as specified in the core and class specific requirements. the ability of the system to automatically reboot itself following a system crash or power interruption. a minimum CPU word size of 64 bits. advanced CPU technology, including higher order bit architecture, (advanced technology). for multiprocessor computer systems, the technology associated with the multiprocessing functions; e.g. symmetric versus non-symmetric, memory utilization, etc. (advanced technology). floating point arithmetic hardware for 32-bit and 64-bit floating point numbers with a format in compliance with the IEEE floating point standard [IEEE 754-1985(R1990)]. Advanced memory management capabilities (including address space) (advanced technology) the following error condition handling: all possible operation codes shall produce documented results. the CPU shall be capable of detecting floating point arithmetic overflows/underflows in compliance with the IEEE 754 floating point standard. It shall be possible to disable and enable the floating point arithmetic overflow/underflow interrupts. the CPU shall be capable of detecting memory access violations, illegal instruction execution, and privileged instruction usage by non-privileged users. The CPU or OS shall interrupt program execution on detection of any of these conditions. detection and reporting of memory errors. a power-up self test that as a minimum checks the processor, memory and configurable peripherals and reports any problems. flexibility and expandability, each computer system shall have an Open Bus Architecture. Advanced forms of Bus Architecture providing improved topology, performance, load-handling, advanced memory interconnectivity, robustness, high performance connectivity and/or other features which improve functionality, flexibility, and expandability (advanced technology). All system unit upgrades shall be field installable. Whenever required expansion capacities exceed the capability of the system unit chassis (memory, disk, processors, tape units, etc.), a compatible expansion chassis shall be provided. Expansion chassis shall have similar physical appearance to system unit chassis and provide power for expansion elements when appropriate. Advanced error reporting and handling techniques for any or all system components (advanced technology) 3.2.2. Data Storage Components Hard disk storage shall be provided with each system. The storage requirements are class specific. Each system shall provide at least 1 SCSI III controller [ANSI X3.253-1998] or Ultra-SCSI controllers or Fibre Channel controller which fully supports connection to internal and external SCSI devices. Add-on SCSI devices which must be provided are noted in the class specific sections. An option for either Fibre Channel or SCSI connections (desirable) Advanced versions of SCSI and other standard I/O controller technologies capable of greater configuration flexibility and higher throughput, can replace SCSI/Fibre Channel controllers whenever SCSI/Fibre Channel is required (advanced technology). Each system shall provide optional 8-mm magnetic tape systems. Each system shall provide optional 4-mm DAT magnetic tape systems. Each system shall provide at least a 12x-speed CD ROM drive. All storage devices shall be field installable. All storage devices shall provide hard error detection (resulting in a non-recoverable failure) and all such errors shall be reported to the system logs. All storage devices shall provide detection of all errors (recoverable and non-recoverable) (desirable) 3.2.3. Communication Interfaces Each computer system shall provide the network interfaces as defined in Section 3.4. Each computer system shall provide at least one free RS-232 serial interface port with the following capabilities: use one of the following standard or commonly accepted connectors: 25 pin [EIA RS-232-C]; RJ-11; DB-9; or DIN-8. Communication I/F - 56 Kbs RS-232 interface. Each subclass b system shall provide 1 Centronics compatible DB25 parallel port. 3.2.4. Hardware User Interfaces Each computer system shall provide a keyboard, mouse and graphic monitor with the following capabilities: keyboard - A detachable and ANSI compatible [ANSI X3.64/R1990] keyboard. mouse - A mouse with three buttons. This device shall permit the user to address individual screen pixels. alternate pointing devices such as a trackball available as a separately orderable option to the mouse (desirable). a graphics controller a graphics monitor with at least the following capabilities: vertical scanning frequency of at least 72 Hz noninterlaced. capable of being powered down without disrupting the system. all subclass b systems must provide an optional 19 inch or greater or greater monitor. all subclass a systems must provide an optional 21-inch or greater monitor. Energy Star compliant (desirable) 3.2.5. Operating Environment Power requirements: all office environment computer systems shall operate on 108 to 125 volts single-phase at 60 Hz (+/-1%) with a maximum amp rating of less than 15 Amps. computer systems identified for computer room environments shall be capable of operating on 108 to 125 volts or 216 to 240 volts single-phase at 60 Hz (+/-1%), individually determined by the Government for each computer system at the time of order. 3.3. System Software This section describes the core system software specifications. 3.3.1. Overview This section describes required functions and features that normally are performed by the system software. The operating system software shall support the hardware. The system software shall support a set of development tools and utilities to augment the capabilities of the operating system and the required language processors. These software tools shall provide fast, efficient mechanisms to develop application programs, backup and restore files, debug programs, and supply other useful system functions. 3.3.2. Operating System The operating system shall be UNIX 95 branded with delivery of a copy of the Open Group branding certificate provided with the proposal. UNIX 98 branding may be substituted for the UNIX 95 requirement (desirable) POSIX [IEEE POSIX 1003.1-1990]; compliant. The Government will accept the vendors self certification for POSIX compliance The operating system shall include the capabilities, functions and services as specified in the following sections. 3.3.2.1. Resource Management The following resource management features shall be provided: The operating system shall be responsible for coordination and management of the systems resources including processor, memory, peripherals and communication subsystems. The operating system shall allow the simultaneous use of these multiple system resources by various users/programs while at the same time protecting each users resources from other users, avoiding resource deadlocks, and allowing interprocess communications. The operating system shall provide memory and process memory management functions including program segmentation, relocation, and protection. Advanced implementations of system resource, memory, and program management (advanced technology). 3.3.2.2. Kernel Services The Kernel shall provide the following services and capabilities in addition to the UNIX 95 requirements: Remote Procedure Calls (RPC), [RFC 1057]. An interactive crash dump analyzer (desirable). 3.3.2.3. File System The operating system shall provide a sophisticated local file system and a network file system. The following specific file systems shall be provided: a file system with the following minimum capabilities: hierarchical structure. file system control; e.g. inodes (disk file information), and user data information shall be interleaved on the disk. redundant storage of critical file system structure information on the disk. asynchronous, non-blocking file I/O. non-buffered (synchronous) file I/O. blocked file I/O. Compatible file systems which support the above requirements in part a) with demonstrable advanced capabilities and/or performance (advanced technology) the Network File System (NFS) Version 3 [RFC 1813]; other advanced multiplatform networked file systems, such as the Andrew File System and the Distributed File System, or capabilities which improve the basic NFS functions (advanced technology). 3.3.2.4. Software User Interfaces The operating system shall provide all of the following user interfaces and user interface tools: the System V Bourne Shell, Berkeley C Shell, and the Korn Shell. the X Consortium Athena X Window System Version 11, Release 6 or greater. This shall include the X Window System Protocol, X Version 11; Xlib - C language X Interface; X Toolkit Intrinsics - C Language Interface; and the Portable Compiled Format or Bitmap Distribution Format. Conversion tools between various formats (desirable) MIT Athena Widget Set Open Software Foundations Motif or CDE Motif, Motif Window Manager (MWM) or Desktop Window Manager (DTWM), Motif widgets and widget functions, and the Motif X-Toolkit with C programming language bindings. graphical system user interface (often referred to as a Desktop) such as CDE, VUE, or equivalent (desirable). 3.3.2.5. Programming Environment Each system shall provide: An ANSI compliant [ANSI X3.9-1978] FORTRAN 77 compiler which shall include: run time libraries. a FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. An ANSI compliant [ANSI X3.198:1992/R1997] FORTRAN 90 compiler may be provided in place of the FORTRAN 77 compiler (desirable) an optional 1 user license an optional 10 user license an optional site license (desirable) An ANSI compliant [ANSI/ISO 9899-1990] C compiler which shall include: run time libraries. a C source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. an optional 1 user license an optional 10 user license an optional site license (desirable) An ANSI compliant C++ compiler which shall include: run-time libraries. use the native C and/or C++ libraries to the maximum extent possible. Libraries provided shall accurately mirror the native C library functions. a C++ source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. Display of original names of source code variables (desirable). an optional 1 user license an optional 10 user license an optional site license (desirable) ANSI compliance [ANSI 14882:1998] (desirable) Graphics debug interfaces and other tools or capabilities which enhance the coding, testing, and execution of FORTRAN, C, and/or C++ programs (advanced technology). A system linker utility. The link utility shall be able to link object code from the FORTRAN, C and C++ compilers to form an executable file. The user shall not have to perform tasks other than compiling and linking to form an executable file from a combination of C, C++ and FORTRAN source code. System libraries that: provide user access to a timer with millisecond resolution and allow user setting of the system clock to a millisecond resolution. provide the ability for user processes to share memory. support the socket interface for the Internet Protocols IP, ICMP, TCP, and UDP. The ability to create and add custom device drivers. The ability to dynamically configure and load custom device drivers into the kernel without requiring the system to be rebooted (desirable). Access to functional source code and examples (desirable). Text processing programs, including nroff and troff. A source code control system such as the Revision Control System (RCS) or Source Code Control System (SCCS). A Postscript file previewer to allow the review of postscript files on the graphics monitor prior to printing (desirable). 3.3.2.6. System Administration Each computer system shall provide: the complete backup of all secondary storage (any device containing a file system which is mounted and run by the system) including raw (non-file structured) disk partitions to a tape drive (as specified in 3.2.2.c. and 3.2.2.d.) with the additional capability for incremental backup of file structured disk partitions the ability to manage the system remotely, including the ability to: install the complete operating system and computer system software from a local tape or CD ROM drive or from over the network. restore the system disk from a copy stored on a remote system. (desirable) perform unattended scheduled automatic system backup. delivery and installation of software from tape (as specified in 3.2.2.c. and 3.2.2.d.) or CD ROM (as specified in 3.2.2.e.) 3.3.3. System Software License Each computer system shall be a multiuser system. The operating system license shall be available in two licensing levels for all systems: a 2-user license defined as allowing 2 users, one possibly remote, to be logged in simultaneously an unlimited license defined as allowing an unlimited number of users to be logged in simultaneously, where 1 or more may be logged in through the console and the rest are connected through either an Ethernet connection (as required in section 3.4.2.a.) and/or FDDI connection (as required in section 3.4.2.b.). In addition to the operating system license, each computer system shall provide: a central license manager. 3.4. Network Capability This section describes the core network capability specifications. 3.4.1. General Each of the systems will be connected to Local Area Networks. All computer systems shall support an Ethernet and a FDDI interface. Network interfaces compatible with campus network technologies shall be supported. Native support of Internet Protocols (IP) is required for compatibility with existing network and computing platforms. 3.4.2. Network Interface The network interface shall include a controller/interface necessary to provide the physical and media access interface between the computer system and the NASA LANs. The requirement for Ethernet and FDDI interfaces implies the option of purchasing either a FDDI or Ethernet connection, but not necessarily providing both on the same system, unless it is explicitly stated in the class specific requirements that the systems must have the ability to provide both an Ethernet and FDDI connection. Each system shall: provide an IEEE 802.3, ISO 8802/3 100Base-T Ethernet interface in the base systems. an embedded interface (i.e. it does not require an external transceiver) in the base systems (desirable) Options for other physical Ethernet interfaces (desirable). provide an ANSI standard Fiber Distributed Data Interface (FDDI) adapter [ANSI X3T9.5]. The FDDI adapter shall comply with all appropriate ANSI standards for FDDI: ANSI FDDI X3T9.5 Station Management (SMT) specification (version 7.3 or greater) ISO 9314-3 FDDI Physical Medium Dependent (PMD) standard. PMDs which must be supported and one of which must be provided are: multimode fiber (PMD); twisted pair (TP-PMD) (unshielded twisted pair support is only required for office environment subclasses). All other PMDs, e.g. single mode fiber(SM-PMD), low cost fiber (LCF-PMD), unshielded twisted pair where office environment not required, etc. (desirable) ISO 9314-1 FDDI Physical Protocol (PHY) standard ISO 9314-2 FDDI Media Access Control (MAC) standard all computer systems shall provide FDDI as either Single Attachment Station (SAS) cabling, or Dual Attachment Station (DAS) cabling. Both SAS and DAS cabling shall be supported. This requirement may be met with a DAS that can be configured as SAS. Separate SAS and DAS interfaces (desirable). A Data Link Layer protocol providing Logical Link Control [ISO 8802/2]. support for other advanced networking capabilities such as Gigabit Ethernet (advanced technology). 3.4.3. TCP/IP Protocols And Software Internet protocols (IP) and network software necessary to utilize the network interface discussed above and compliant with the following specifications shall be provided: Internet Protocol (IP) [RFC 791], with full routing capability including subnetting The Internet Control Message Protocol (ICMP) [RFC 950]. Transmission Control Protocol (TCP) [RFC 793]. Application program interface to TCP and IP layer protocols. File Transfer Protocol (FTP) [RFC 959]. TELNET Virtual Terminal Protocol [RFC 854]. Address Resolution Protocol (ARP) [RFC 826]. User Datagram Protocol (UDP) [RFC 768]. Simple Mail Transport Protocol (SMTP) [RFC 821]. MIME [RFC 2046]. Host extensions for IP multicasting [RFC 1112]. TCP extensions for high performance [RFC 1323]. The following protocols shall be supported: gated with OSPF V2 or later 3.4.4. Other Network Protocols and Software All computer systems shall provide the following additional protocols and network software: A sufficient set of the Simple Network Management Protocol (SNMP) [RFC 1157] to act as a network agent and conforms the structure for Management Information Bases (MIB) [RFC 1155] that would allow a network connected SNMP management station to query the status and condition of the system. The following protocols shall be supported: Point-to-Point (PPP) Protocol [RFC 1661]; Compliance with RFC 1332 , RFC 1662 and RFC 1663 (desirable). 3.5. Documentation The contractor shall provide complete sets of operator, programmer, software system, utility, installation, and user manuals. The contractor shall also provide other necessary documentation for all hardware and software delivered under this contract in accordance with the contractors product line documentation standards. If the contractors software and/or hardware documentation is written other than described below, an alternative set of manuals shall be provided. The manuals shall include, but not be limited to, the documentation described in the following paragraphs. All provided documentation shall be available either on line or in hardcopy. On-line documentation must be readable via a GUI interface with intelligent search capabilities and must have the ability to be easily printed in readable form on a local Postscript printer. Documentation be available both on-line and in hardcopy form (desirable). 3.5.1. Hardware Documentation The hardware documentation shall include: System hardware manuals detailing specifications for system architecture, CPU, memory, and peripheral devices Interface manuals detailing all electrical and mechanical aspects of system interfaces, e.g. I/O channels, peripheral devices, and communication interface devices. 3.5.2. Software Documentation The software documentation shall include: Reference manuals detailing all elements and operations of all delivered language processors, text editors, I/O handlers, operating system, system generation, system architecture, software tools and utilities, configuration management, and performance measurement software. Reference manuals detailing command language, communication software, input/output system, error handling, and diagnostic software. Computer reference and system programmer manuals detailing every machine instruction and all programming considerations. Problem determination and debugging guides. A guide to writing device drivers. Documentation of known problems and/or suspected system errors. Introductory manuals for new users to the operating system and computer system environment. An on-line introductory tutorial for new users (desirable). 3.5.3. Other Manuals The contractor may include any other manuals and program descriptions that would be considered helpful to the Government. 3.6 Security All computer systems must provide the following security related technology: port-blocking software such as tcp-wrappers and portmapper sending all system level logs to a centralized log-host server All computer systems must support the following security related technology: Secure shell client and server software, protocol 1 and protocol 2 such as F-Secure public domain versions of secure shell such as OpenSSH (desirable) Intrusion detection software such as TripWire PGP email encryption enhanced methods of identification and authentication (such as biometric and physical card-keys) (advanced technology) fine-grained access control features for operating system services such as C2 security (and more stringent security standards) (advanced technology) security audit tools (advanced technology) enhanced password change software, including the capability to add a user defined dictionary, minimum requirements for password rules, etc (advanced technology) anti-theft and tracking tools such as CompuTrace (desirable) 3.7 Computer Systems Specialists To assist in product recommendations, installation, and support of computer systems products the following specialists shall be provided: Operations Systems Security Specialist Provides technical knowledge and analysis of information assurance, to include applications; operating systems; Internet and Intranet; physical security; networks; risk assessment; critical infrastructure continuity and contingency planning; emergency preparedness; security awareness and training. Provides analysis of existing systems vulnerability to possible intrusions, resource manipulation, resource denial and destruction of resources. Provides technical support and analysis to document organizational information protection framework, and supports policy and procedures preparation and implementation... Bachelors degree from an accredited college or university with a curriculum or major field of study which provides substantial knowledge useful in operating large, complex IT projects to support integrated systems. Experience Requirements: Seven years of substantial experience in systems operations. Computer Systems Engineer Tests and analyzes all elements of the computer systems facilities including power, software, mass storage devices, communications devices, computer systems and terminals and for the overall integration of the enterprise network. Responsible for the planning, design, installation, maintenance, management and coordination of the storage systems. Monitors and controls the performance and status of the storage resources. Utilizes software and hardware tools, identifies and diagnoses complex problems and factors affecting storage performance. Maintains technical currency and studies vendor products to determine those which best meet client needs. Provides guidance and direction for less experienced storage support technicians. Educational Requirements: Bachelors degree from an accredited college or university in computer science, information systems, engineering or a mathematics-intensive discipline or an applicable technical training certificate from an accredited training institution. Experience Requirements: Seven years of increasingly complex and progressive experience in computer system/network engineering. Includes two years of specialized experience related to the task. Technician Provides high level functional and IT analysis, design, development, integration, documentation, and implementation assistance on problems which require a thorough knowledge of the related technical subject matter for effective system deployment. Participates in all phases of systems development. Applies principles and methods of the functional area to difficult problems in technical areas to arrive at automated solutions. Designs and prepares technical reports and related documentation, and makes charts and graphs to record results. Prepares and delivers presentations and briefings as required by the task order. Educational Requirements: High school graduate or equivalent. Experience Requirements: Ten years of intensive and progressive experience in functional or IT analysis/programming of subject matter closely related to the work to be automated. 4. Category A: Computer System Class Specific Specifications For each class, contractors are required to meet both the core requirements defined in the Computer System Core Specification, (see Section 3) and the additional mandatory requirements defined for that class (provided in each of the subsections that follow). If there is a conflict in requirements between the Class Specification and the Core Specification, the Class Specification shall always take precedence. 4.1. Class 1: CAE/CAD Electronic Circuit Design Computer Systems This section describes the CAE/CAD Electronic Circuit Design Computer Systems class specific requirements. 4.1.1. Purpose The purpose of this section is to define the specific requirements for the Electronic CAD Circuit Design Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 1 computer systems over and above, or in place of the core specifications defined in Section 3. 4.1.2. Hardware Configurations This class of computer systems is comprised of a Level 1 computer system (1/a) and a Level 2 computer system (1/b). These systems are differentiated by the application required to be supported. Level 2 systems are typically used for schematic capture while Level 1 systems are used for simulations and Printed Circuit Board (PCB) route and place operations and may function as servers for systems similar to those specified for 1b. 4.1.2.1. Class 1/a and 1/b Computer Systems All Class 1 computer systems (Class 1/a and 1/b) shall provide the following minimum capabilities, unless noted as desirable: binary compatibility between Class 1/a and 1/b. at least 256 simultaneously displayable colors from a palette of at least 16 million available colors and monitor with a minimum of 1.2 million displayable pixels. a graphics monitor with at least 1600x1200 dpi @ 76 Hz (non-interlaced) 0.25 mm pitch (as a replacement to the core requirement Section 3.2.4.d.1.) 4.1.2.2. Class 1/a High-End Computer System The Class 1/a high-end computer system shall provide the following minimum capabilities, unless noted as desirable: a minimum memory of at least 2 GBytes memory expandable to at least 4 GByte. Error Detecting/Correcting (ECC) Memory. hard disk storage with a minimum of 18 GBytes of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 60 GByte. 3 available bus slots (2 available slots if Ethernet connection is embedded in the system). ability to simultaneously connect the system to both FDDI and Ethernet to support 1000-Base-T 2 CPUs The subclass 1/a computer systems must support: the following mass storage systems (including locate, mount, read and write tapes or disks in the jukeboxes). For the supported jukeboxes, the system must support a storage capacity of at least 10 GByte, expandable to at least 60 GBytes: magneto-optical drives and jukeboxes worm optical drives and jukeboxes digital linear tape (DLT) drives, and jukeboxes 8 mm tape drives, and jukeboxes 4 mm tape drives, and jukeboxes CDROM drives and jukeboxes Recordable CD Drive (desirable) 4.1.2.3. Class 1/b Low-End Computer System The Class 1/b low-end computer system shall provide the following minimum capabilities, unless noted as desirable: a minimum memory of at least 1 GBytes memory expandable to at least 2 GBytes. hard disk storage with a minimum of 8 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 36 GByte. operate in an office environment. 2 available bus slots (1 available slot if Ethernet connection is embedded in the system). able to support recordable CD capability (desirable) 21-in or greater graphics monitor (as a replacement to the core requirement Section 3.2.4.d.3.) 4.1.3. Application Software All Class 1 computer systems (Class 1/a and 1/b) shall support the following software: The following Cadence Design Systems CAE logical and physical design and simulation tools: . Allegro, Concept-HDL, Verilog-XL, Verilog-NC and Analog Artist The following Synopsys Design and Simulation Tools: Design Compiler, VSS, Prime Time, VHDL/Verilog Compiler, Tetra Max OPEN GL (desirable) 4.1.4. Performance Benchmarks This section describes the performance values required for the Class 1 computer systems. 4.1.4.1. Performance for Class 1/a The maximum allowed time for the Synopsis benchmark for the class a computer system is 45 minutes. The minimum SpecRate values for the class a computer system is: 290 SPEC CINT95rate 410 SPEC CFP95rate The minimum NASA I/O value for the class a computer system is 100 mallards 4.1.4.2. Performance for Class 1/b The maximum allowed time for the Synopsis benchmark for the class b computer system is 60 minutes. The minimum Spec values for the class b computer system is: 18 SPEC CINT95 20 SPEC CFP95 The minimum NASA I/O value for the class b computer system is 100 mallards Table 1 CLASS 1 Performance and Capacity Requirements PERFORMANCE: SynopsisCINT95CFP95mallardsSubclass(a)45 min290 (Rate)410 (Rate)100Subclass(b)60 min1820100 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandSlotsCPUsSubclass(a)2 GB4 GB18GB60GB32Subclass(b)1 GB2 GB8GB36GB21 4.2. Class 2: CAE/CAD Mechanical Design Computer Systems This section describes the CAE/CAD Mechanical Design Computer Systems class specific requirements. 4.2.1. Purpose The purpose of this section is to define the specific requirements for the mechanical computer aided design (CAD) and computer aided engineering (CAE) Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 2 computer systems over and above, or in place of the core specifications defined in Section 3. 4.2.2. Hardware Configurations This section describes the computer system hardware configurations required for the Class 2 systems. Two basic system configurations are required: a 2/a system and a 2/b system. Table 2 defines the performance and disk/memory capacity requirements for this class. 4.2.2.1. Class 2/a and 2/b Computer System All Class 2 computer systems (Class 2/a and 2/b) shall provide the following minimum capabilities, unless noted as desirable: binary compatibility between Class 2/a and 2/b. operation in an office environment. a second SCSI III, Ultra-SCSI, Fibre Channel compatible interface optionally ordered for one of the available bus slots at least 16 million simultaneously displayable colors and a monitor with a minimum of 1.2 million displayable pixels. a 3-D graphics system supporting double-buffered 24 bit images with a 24 bit Z-buffer support for Windows NT OS as an option to UNIX 95 (desirable) [Core Specification 3.3.2.5.a replaced by]: A FORTRAN 90 compiler, ANSI compliant [ANSI X3. 198-1992]. The FORTRAN compiler shall include: run time libraries. FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. an optional 1 user license an optional 10 user license 4.2.2.2. Class 2/a Computer System The Class 2/a computer system shall provide the following minimum capabilities, unless noted as desirable: a minimum memory of at least 512 MBytes memory expandable to at least 2 GB. hard disk storage with a minimum of 8 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). internal disk storage expandable to at least 18 GByte disk storage expandable to at least 64 GByte. at least 2 CPUs at least 3 available bus slots Error Detecting/Correcting (ECC) Memory (desirable). 4.2.2.3. Class 2/b Computer System The Class 2/b computer system shall provide the following minimum capabilities, unless noted as desirable: a minimum memory of at least 256 MBytes memory expandable to at least 1 GB. hard disk storage with a minimum of 8 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 32 GByte. at least 2 available bus slots 4.2.3. Application Software This section describes the commercial application software packages that are required to run on the Class 2 computer system systems. The following CAD software packages shall be supported: MSC NASTRAN or other commercially available NASTRAN. MSC NASTRAN is a commercially available software product from the MacNeal Schwendler Corporation MSC PATRAN CAE tool. PATRAN s is a commercially available software product from the MacNeal Schwendler Corporation SDRCs I-DEAS Master Series family of CAE/CAD tools. IDEAS Master Series is a commercially available software product from Structural Dynamics Research Corporation. CADSIs DADS CAE tool. DADS is a commercially available software product from CADSI. Parametric Technologys Pro/E package. Pro/E is a commercially available software product from Parametric Technology. OPEN GL MATLAB. MATLAB is a commercially available software product from The MathWorks Inc 4.2.4. Performance This section describes the performance values required for the Class 2 computer systems. 4.2.4.1. Performance for Class 2/a The maximum allowed CPU time for the NASTRAN benchmark for the class a computer system is 11 minutes. The minimum allowed overall composite score for the SPEC Pro-E benchmark for the class a computer system is 2.3 The minimum SpecRate values for the class a computer system is: 320 SPEC CINT95rate 480 SPEC CFP95rate The minimum NASA I/O value for the class a computer system is 150 mallards 4.2.4.2. Performance for Class 2/b The maximum allowed CPU time for the NASTRAN benchmark for the class b computer system is 28 minutes. The minimum allowed overall composite score for the SPEC Pro-E benchmark for the class b computer system is 1.7 The minimum Spec values for the class b computer system is: 10 SPEC CINT95 12 SPEC CFP95 The minimum NASA I/O value for the class b computer system is 150 mallards Table 2: CLASS 2 Performance and Capacity Requirements PERFORMANCE: NASTRANPro-ECINT95CFP95mallardsSubclass(a)11 min2.3320 (Rate)480 (Rate)150Subclass(b)28 min1.71012150 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandSlotsCPUsSubclass(a)512 MB2 GB8GB64GB32Subclass(b)256 MB1GB8GB32GB21 4.3. Class 3: Mass Storage Servers This section describes the Mass Storage Server class specific requirements. 4.3.1. Purpose The purpose of this section is to define the specific requirements for the mass storage servers as described in Section 2. The following hardware and software specifications are required of these Class 3 computer systems over and above, or in place of the core specifications defined in Section 3. 4.3.2. Hardware Configuration This class of computer systems is comprised of a 3/a computer system and a 3/b computer system. These systems are differentiated mainly by capacity. Both systems need to support mass storage devices. 4.3.2.1. Class 3/a and 3/b Computer Systems All Class 3 computer systems (Class 3/a and 3/b) shall provide the following minimum capabilities, unless noted as a desirable: binary compatibility between Class 3/a and 3/b. operation in a computer room environment. option for either Fibre Channel or SCSI Controllers (replaces 3.2.2.b.1.) All Class 3 computer systems (Class 3/a and 3/b) shall support the following minimum capabilities, unless noted as a desirable: Hierarchical Mass Storage Systems: 1. UniTree. UniTree is a commercially available software product from UniTree Software Inc (UTSI) 2. One other hierarchical mass storage system with the ability to at least: locate, mount, read and write(except CD-ROMs) tapes or disks in the jukeboxes. support UNIX native file system user calls and commands, e.g. ls, touch, etc. support access at hard disk storage speed to the most frequently/recently accessed files. vault media and provide a means of notifying the operator to retrieve a vaulted media when an old file is requested. employ a nameserver and tapeserver or similar means for locating files on media. utilities for backup and recovery of critical databases repacking function (repack tapes to remove deleted files) logging major activities of software components for system monitoring. write multiple tape copies of a file scalable up to at least 10 Pbyte, providing the user a way to build up to full use of the mass storage system write multiple tape copies of a file simultaneously write multiple simultaneous streams of new data EMC RAID arrays Other Ultra-SCSI and fibre-attached disk and RAID arrays (desirable) STK 9840, IBM 3590 E1A, STK 3490E, and STK D3(Redwood) tape drives Other Ultra-SCSI and fibre-attached tape drives (desirable) STK 9310 (Powderhorn) and IBM 3494 robotic libraries Other robotic libraries (desirable) Optical jukeboxes SAN Technology multiple server capabilities (server functions spread over multiple machines) as described in the IEEE Mass Storage Reference Model; support for higher scalability (e.g. storage capacity up to 100 Pbyte) and other advanced functions / capabilities for the hierarchical storage management system (advanced technology) 4.3.2.2. Class 3/a Computer System The Class 3/a computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 8 GBytes memory expandable to at least 12 GBytes 1 TB of RAID 3 or RAID 5 disk hard disk storage with a minimum of 16 GBytes of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). Disk storage shall be expandable to at least 64 GBytes. This requirement is exclusive of the requirement for a mass storage and RAID disk system. Disk storage shall have mirroring capability at least 16 available bus slots. 8 CPUs expandable to at least 12 CPUs In addition to the core network interfaces described in section 3.4.2., class 3/a systems shall provide the following network interfaces: HiPPI Class 3/a systems shall optionally provide the following network interfaces either in place of or in addition to the HiPPI requirement: Gigabit Ethernet ATM OC12 4.3.2.3. Class 3/b Computer Systems The Class 3/b computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 4 GBytes memory expandable to at least 6 GBytes 300 GB of RAID or JBOD disk hard disk storage with a minimum of 8 GBytes of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). Disk storage shall be expandable to at least 32 GBytes. This requirement is exclusive of the requirement for a mass storage and RAID disk system. Disk storage shall have mirroring capability at least 8 available bus slots. 4 CPUs expandable to at least 6 CPUs In addition to the core network interfaces described in section 3.4.2., class 3/b systems shall provide the following network interfaces: ATM OC3 4.3.3. Application Software All Class 3 computer systems (Class 3/a and 3/b) shall support the following software: database client libraries (allowing database applications to run on the computer systems while accessing remote database servers) on both class 3/a and 3/b computer systems including, but not limited to Sybase Oracle Informix Ingres database servers (running the actual database instance on the system) on Class 3/a computer system including, but not limited to: Sybase Oracle Informix Ingres 4.3.4. Performance Benchmarks This section describes the performance values required for the Class 3 computer systems. 4.3.4.1. Performance for Class 3/a The minimum allowed rates for the NASA Unitree based benchmark for the class a computer system are: 8.5 MB/s puts 12 MB/s gets 8 MB/s migrates 9 MB/s stages The minimum SpecRate values for the class a computer system is: 650 SPEC CINT95rate 775 SPEC CFP95rate The minimum NASA I/O value for the class a computer system is 350 mallards 4.3.4.2. Performance for Class 3/b The minimum allowed rates for the NASA Unitree based benchmark for the class b computer system are: 7.5 MB/s puts 10 MB/s gets 6 MB/s migrates 7 MB/s stages The minimum SpecRate values for the class b computer system is: 250 SPEC CINT95rate 400 SPEC CFP95rate The minimum NASA I/O value for the class b computer system is 250 mallards Table 3: CLASS 3 Performance and Capacity Requirements PERFORMANCE: Unitree putUnitree getUnitree migrateUnitree stageCINT95CFP95mallardsSubclass(a)8.5 MB/s12 MB/s8 MB/s9 MB/s650 (Rate)775 (Rate)350Subclass(b)7.5 MB/s10 MB/s6 MB/s7 MB/s250 (Rate)400 (Rate)250 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandSlotsCPUsCPU expandSubclass(a)8 GB12 GB16GB64GB16812Subclass(b)4 GB6 GB8GB32GB846 4.4. Class 4: Network Data Server Computer Systems This section describes the Network Data Server Computer Systems class specific requirements. 4.4.1. Purpose The purpose of this section is to define the specific requirements for the Network Data Server Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 4 computer systems over and above, or in place of the core specifications defined in Section 3. 4.4.2. Hardware Configurations This class of computer systems consists of a class 4/a network data server and a class 4/b network data server (4/b). These machines are differentiated by the system and database performance and the amount of mass storage supported. 4.4.2.1. Class 4/a and 4/b Computer Systems All Class 4 computer systems (Class 4/a and 4/b) shall provide the following minimum capabilities, unless noted as a desirable: have scalable processing (user can incrementally add processing power). Error Detecting/Correcting (ECC) Memory. at least 256 simultaneously displayable colors from a palette of at least 16 million available colors and monitor with a minimum of 1.0 million displayable pixels. ability to simultaneously connect the system to both FDDI and Ethernet optional interfaces in addition to the core SCSI/Fibre Channel specification: Option for either Fibre Channel or SCSI ATM other high performance interfaces (in addition to supporting a standard SCSI interface) such as the SMD [ANSI X3.91M-1987] or the High Performance Parallel Interface (HiPPI) [ANSI X3.T9/88] (desirable) Network File System (NFS) hardware and/or software performance enhancement (desirable). binary compatibility between 4/a and 4/b systems (desirable) a virtual file system manager (desirable). [Core Specification 3.3.2.5.a replaced by]: A FORTRAN 90 compiler, ANSI compliant [ANSI X3. 198-1992]. The FORTRAN compiler shall include: run time libraries. FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. an optional 1 user license an optional 10 user license Java Interpreter CD Read / Write Drives (desirable) 4.4.2.2. Class 4/a Computer System The Class 4/a computer systems shall provide the following minimum capabilities: minimum memory of at least 1 GBytes. memory expandable to at least 2 GBytes. hard disk storage with a minimum of 16 GBytes of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). Disk storage shall be expandable to at least 900 GBytes. This requirement is exclusive of the requirement for a mass storage system. Disk storage be expandable to 2 Tbytes (desirable) at least 2 additional SCSI III, Fibre Channel or higher performance host adapter interfaces. at least 16 available bus slots (15 available slots if Ethernet connection is embedded in the system). at least 2 CPUs expandable to at least 24 CPUs expandable to at least 30 CPUs (desirable) at least 2 RAID devices (supporting RAID levels 0, 1, and 5).: one with at least a 100 GB disk array one with at least a 1000 GB disk array Support for RAID levels 2, 3 and 4 (desirable) Advanced fault tolerance, additional redundancy (e.g., redundant drive controllers, power supplies, SCSI controllers, etc.), disk swap capabilities (e.g., the ability to replace a failed drive without shutting down, the ability to easily swap out drives with higher capacity drives, etc.), and the extent to which implementation is software or hardware based (advanced technology). dual-ported (i.e. connectivity to 2 or more host systems) external peripheral storage devices (desirable). 4.4.2.3. Class 4/b Computer System The Class 4/b computer systems shall provide the following minimum capabilities, unless noted as a desirable: minimum memory of at least 256 MBytes. memory expandable to at least 512 MBytes. hard disk storage with a minimum of 8 GBytes of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). Disk storage shall be expandable to at least 120 GBytes. This requirement is exclusive of the requirement for a mass storage system. at least 1 RAID device (supporting RAID levels 0, 1,and 5) with at least 50 GB disk array support for RAID level 3 (desirable) an optional second SCSI III, Fibre Channel or higher host adapter interface at least 5 available bus slots (4 available slots if Ethernet connection is embedded in the system). at least 1 CPU expandable to at least 6 CPUs expandable to at least 8 CPUs (desirable) operation in an office environment (desirable) 4.4.2.4. Mass Storage Systems In some instances, this Class will be configured to host large digital archives or as large file servers. To meet this requirement, storage management systems that integrate with the computer system and support multiple mass storage systems as noted in 4.4.2.4.a through 4.4.2.4.d must be supported. The subclass 4/b computer systems must support the following storage systems: digital linear tape (DLT) drives and desktop jukebox 8 mm tape drives and desktop jukebox 4 mm tape drives and desktop jukebox The subclass 4/a computer systems must support (including availability of functions described in Section 4.4.2.4.d.) the following mass storage systems: magneto-optical disk drives and jukeboxes CD-ROM (read-only) disk drives, and jukeboxes digital linear tape (DLT) drives, and jukeboxes 8 mm tape drives, and desktop jukeboxes 4 mm tape drives, and desktop jukeboxes DVD drives The subclass 4/a computer systems must support one or more of the following mass storage systems (desirable): STK 9840 robotic device IBM 3590/3590E robotic device multiple media types (e.g. ADIC) jukebox other state-of-the-art drives, and desktop jukeboxes other state-of-the-art jukeboxes The jukeboxes must attach to the computer systems with at least a SCSI III interface. The following sizes of jukeboxes must be supported for magneto-optical, CD-ROM and DLT media: for a large library system with a storage capacity of at least 1 TByte, expandable to at least 100 Tbytes; and for all supported jukeboxes, a small library system with a storage capacity of at least 10 GByte, expandable to at least 60 GBytes. the file management storage system must be hierarchical, such as UNITREE or EPOCH. The hierarchical storage management software must have the ability to: locate, mount, read and write(except CD-ROMs) tapes or disks in the jukeboxes. ability to support UNIX native file system user calls and commands, e.g. ls, touch, etc. support access at hard disk storage speed to the most frequently/recently accessed files. vault media and provide a means of notifying the operator to retrieve a vaulted media when an old file is requested. employ a nameserver or similar means for locating files on media. utilities for backup and recovery of critical databases repacking function (repack tapes to remove deleted files) logging major activities of software components for system monitoring. The hierarchical storage management system should be scalable up to at least 50 TB providing the user a way to build up to full use of the mass storage system. dual (or multiple) tape copies of a file; multiple server capabilities (server functions spread over multiple machines) as described in the IEEE Mass Storage Reference Model; support for higher scalability (e.g. storage capacity up to 1 Pbyte) and other advanced functions / capabilities for the hierarchical storage management system (advanced technology). 4.4.3. Application Software In many cases this Class would operate a relational data base management system in a client/server architecture. This system may be configured to operate only as a data server supporting clients on other network nodes, or with both client and server on the same computer system. Therefore, the Class 4 computer systems shall support: relational database servers (running the actual database instance on the system) on Class 4/a computer system including, but not limited to: Sybase Oracle Informix Ingres object oriented database server such as Versant, ObjectStore, ONTOS 4.4.4. Performance Benchmarks This section describes the performance values required for the Class 4 computer systems. 4.4.4.1. Performance for Class 4/a The minimum allowed TPC tpmC value for the class a computer system is 6000. The maximum times for the NASA Sybase based database on the class a computer system are: 170 sec for the small database load time for tables and indices 25000 ms for the small database query time 3100 sec for the large database load time for tables and indices 200000 ms for the large database query time The minimum SpecRate values for the class a computer system is: 480 SPEC CINT95rate 320 SPEC CFP95rate The minimum NASA I/O value for the class a computer system is 350 mallards 4.4.4.2. Performance for Class 4/b The minimum allowed TPC tpmC value for the class b computer system is 2000 The maximum times for the NASA Sybase based database on the class b computer system are: 300 sec for the small database load time for tables and indices 33500 ms for the small database query time 5500 sec for the large database load time for tables and indices 240000 ms for the large database query time The minimum Spec values for the class b computer system is: 15 SPEC CINT95 24 SPEC CFP95 The minimum NASA I/O value for the class b computer system is 150 mallards Table 4: CLASS 4 Performance and Capacity Requirements PERFORMANCE: tpmCSmall db bcp loadSmall db queryLarge db bcp loadLarge db queryCINT95CFP95mallardsSubclass(a)6000170 sec25000 ms3100 sec200000 ms320 (Rate)480 (Rate)350Subclass(b)2000300 sec29000 ms5500 sec240000 ms1524150 CAPACITY Mem.Mem. ExpandDiskDisk ExpandSlotsCPUsCPU expandSubclass(a)1 GB2 GB16GB900GB16224Subclass(b)256 MB512 MB8GB120GB516 4.5. Class 5: 3-D Graphics Computer Systems This section describes the High Performance Visualization Computer Systems class specific requirements. 4.5.1. Purpose The purpose of this section is to define the specific requirements for the High Performance Visualization Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 5 computer systems over and above, or in place of the core specifications defined in Section 3. 4.5.2. Hardware Configurations This section describes the computer system hardware configurations required for the Class 5 systems. Two basic system configurations are required: a 5/a system and a 5/b system. Table 2 defines the performance and disk/memory capacity requirements for this class. 4.5.2.1. Class 5/a and 5/b Computer System All Class 5 computer systems (Class 5/a and 5/b) shall provide the following minimum capabilities, unless noted as desirable: binary compatibility between Class 5/a and 5/b. a second SCSI III, Ultra-SCSI, Fibre Channel compatible interface optionally ordered for one of the available bus slots at least 16 million simultaneously displayable colors and a monitor with a minimum of 1.2 million displayable pixels. a 3-D graphics system supporting double-buffered 24 bit images with a 24 bit Z-buffer support for Windows NT OS as an option to UNIX 95 (desirable) 4.5.2.2. Class 5/a Computer System The Class 5/a computer system shall provide the following minimum capabilities, unless noted as desirable: a minimum memory of at least 1 Gbytes memory expandable to at least 4 GB. hard disk storage with a minimum of 9 Gbyte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). internal disk storage expandable to at least 18 Gbyte disk storage expandable to at least 64 Gbyte expandable to at least 4 CPUs. a second 3-D graphics display capability (desirable). at least 3 available bus slots. Error Detecting/Correcting (ECC) Memory (desirable). operation in a computer room environment. 4.5.2.3. Class 5/b Computer System The Class 5/b computer system shall provide the following minimum capabilities, unless noted as desirable: a minimum memory of at least 512 Mbytes memory expandable to at least 2 GB. hard disk storage with a minimum of 9 Gbyte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 32 Gbyte. at least 2 available bus slots expandable to at least 2 CPUs operation in an office environment. 4.5.3. Graphics Controller and Monitor This section describes the technical requirements for the computer systems graphics controller and monitor. 4.5.3.1. Class 5/a and 5/b Computer System Graphics All Class 5 computer systems (Class 5/a and 5/b) shall provide the following minimum graphics capabilities, unless noted as a desirable or advanced technology: 24 bit z buffering. Gouraud and flat shading. four sample (jittered or regular) anti-aliasing. an overlay plane. diffuse, ambient, emission and specular lighting characteristics with a minimum of 5 simultaneous lights. digitizing graphics tablet. RGB (red, green, blue) 60 or 72 hz video output that will allow the use of video projectors and the adaptation of other video equipment. advanced graphics and image generation capabilities in such areas as: texture mapping, lighting/shading/shadowing, underlays/overlays, hidden surface removal, object primitives, display lists, antialiasing, transparency, surface properties, etc (advanced technology) video capability for virtual reality imaging (e.g., support for booms, head mounted displays, etc.); advanced multimedia capabilities such as inputting, outputting, and editing MPEG, audio, and raw video; flexible and programmable video outputs (e.g., resolution, format/timing, number of graphics channels, stereo, composite, etc.) (advanced technology) advanced graphics peripherals such as complex/advanced input devices (e.g., spaceball, 3D-mouse, dial box/button box); output devices (e.g., 16 bit stereo audio support); display technologies (i.e. beyond standard CRT); 3D and stereographic systems such as Fakespace BOOM, non-VGA head-mounted displays, head-tracked and non-head-tracked stereo glasses (advanced technology) 16-bit stereo audio processing card with voice quality speakers (desirable): 4.5.3.2. Class 5/a High-end Computer System Graphics The high-end system (5/a) shall additionally provide the following minimum capabilities, unless noted as a desirable: alpha-blending (color blending). a minimum of 32 bit color planes with full double buffering. 48 bit color (RGBA) planes (desirable) minification / magnification filters for texture mapping (linear, constant and smooth) with texture sizes of at least 512 x 512. Field sequential (180hz) video signal output At least a 32 bit z buffer (desirable) at least 8 bit alpha planes (desirable) draw at least 1,000,000 randomly oriented 10 pixel polylines per second in floating point coordinates transformed, scaled, clip tested, and anti-aliased. draw at least 400,000 polygons per second based on 100 pixel polygons, Gouraud shaded with at least one light source, transformed, clipped, and 24 bit Z buffered using floating point coordinates (excluding back faced, culled polygons). 4.5.3.3. Class 5/b Low-end Computer System Graphics The low-end system (5/b) shall additionally provide the following minimum capabilities, unless noted as a desirable: a minimum of 24 bit color planes with at least 12 bit double buffering. minification / magnification filters for texture mapping (linear, constant and smooth) with texture sizes of at least 256 x 256 draw at least 500,000 randomly oriented 10 pixel polylines per second in floating point coordinates transformed, scaled, clip tested, and anti-aliased. draw at least 150,000 polygons per second based on 100 pixel polygons, Gouraud shaded with at least one light source, transformed, clipped, and 24 bit Z buffered using floating point coordinates (excluding back faced, culled polygons). 4.5.4. Application Software This section describes the commercial application software packages that are required to run on the Class 5 computer system systems. The following Visualization software packages shall be supported: Performer or other commercially available data visualization software product IDL Maya by Alias/Wavefront or Lightwave by Newtek animation software OPEN GL 4.5.5. Performance Benchmarks This section describes the performance values required for the Class 5 computer systems. 4.5.5.1. Performance for Class 5/a and 5/b Both the class 5/a and class 5/b systems must meet or exceed the following SPEC GL benchmark values: From clear times: (Immediate, RGB, full screen, color buffer, depth buffer): 337 M pixels / sec (CallList, RGB, full screen, color buffer, depth buffer): 336 M pixels / sec From fill rates: Quads (CallList, RGB, Z, 3D, smooth) 381M pixels/sec Quads (CallList, RGB, Z, 3D, 64x64 RGB trilinear modulated texture, smooth) 412M pixels/sec From TexImage.rgb: TexImage (Immediate, RGB, ubyte, 2048x2048) 130M texels/sec TexImage (Immediate, RGBA, ubyte, 2048x2048) 106 texels/sec TexImage (Immediate, RGB, ubyte, 2048x2048, mipmapped) 128M texels/sec TexImage (Immediate, RGBA, ubyte, 2048x2048, mipmapped) 96.5M texels/sec From OPClist.rgb, BgnEnd.rgb, or Triangles.RGB: Triangle Strip (Immediate, RGB, Z, smooth, 3D): 7.39M triangles/sec Triangle Strip (Immediate, RGB, Z, 1 infinite light, smooth, 3D): 7.34M Triangle Strip (Immediate, RGB, Z, 1 infinite light, textured, smooth, 3D): 4.59M triangles/sec 4.5.5.2. Performance for Class 5/a The minimum Spec values for the class a computer system is: 16 SPEC CINT95 22 SPEC CFP95 The minimum NASA I/O value for the class a computer system is 150 mallards 4.5.5.3. Performance for Class 5/b The minimum Spec values for the class b computer system is: 13 SPEC CINT95 20 SPEC CFP95 The minimum NASA I/O value for the class b computer system is 150 mallards Table 5: CLASS 5 Performance and Capacity Requirements PERFORMANCE: CINT95CFP95mallardsSubclass(a)1622150Subclass(b)1320150 CAPACITY Mem.Mem. ExpandDiskDisk ExpandSlotsCPUsCPU expandSubclass(a)1 GB4GB9 GB64 GB314Subclass(b)512 MB2 GB9 GB32GB212 4.6. Class 6: Compute Servers This section describes the Compute Servers class specific requirements. 4.6.1. Purpose The purpose of this section is to define the specific requirements for the Computer Servers as described in Section 2. The following hardware and software specifications are required of these Class 6 computer systems over and above, or in place of the core specifications defined in Section 3. 4.6.2. Hardware Configurations This class of servers is comprised of a family of two subclasses: a top-of-the-line Compute Server subclass (6/a) and a high-end Compute Server subclass (6/b). These systems, while differentiated by performance and capacity are both intended for use by highly compute intensive code. 4.6.2.1. Class 6/a and 6/b Computer Servers All Class 6 computer systems (Class 6/a and 6/b) shall provide the following minimum capabilities, unless noted as a desirable: X/Open Base 95 branded with delivery of a copy of the X/Open branding certificate with proposal. [replaces core specification 3.3.2.a] UNIX 95 or UNIX 98 branding and may be substituted for the Base 95 requirement (desirable). the capability of performing 64-bit and 128-bit floating point arithmetic [replaces core specification 3.2.1.e] be capable of reading/writing IEEE 754 floating point standard values. perform 64-bit and 128-bit floating point arithmetic in hardware (desirable) [Core Specification 3.2.1.b is not required for Class 6] Each system shall provide 3480/3490 tape systems [replace core specification 3.2.2.c and 3.2.2.d] support for other high performance tape systems (desirable) [Core Specifications 3.2.3.b and 3.2.3.c are not required for Class 6] binary compatibility between Class 6/a and 6/b (desirable). operate in an computer room environment. In addition to Resource Management Core Specifications (Section 3.3.2.1) Class 6/a and 6/b servers must provide: Any process shall be able to access at least 80% of physical memory within a shared memory node in which a node is defined to be a unit of 1 to N central processing units directly attached to some amount of physical memory. Batch queuing system POSIX 1003.2d compliance (desirable) Techniques for system resource; memory; and batch program management including batch queuing and scheduling, priority and resource control; and executing program management including dynamic priority handling. [Core Specification 3.3.2.5.b.3., 3.3.2.5.b.4., 3.3.2.5.b.5. replaced by]: a C compiler unlimited system license In addition to File System Core Specifications (Section 3.3.2.3) Class 6/a and 6/b servers must provide: the capability to create file systems and individual files in excess of 10 GB. [Core Specification 3.3.2.5.a replaced by]: A FORTRAN90 compiler, ANSI compliant [ANSI X3. 198-1992]. The FORTRAN compiler shall include: run time libraries. a FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. automatically optimize code to best utilize the hardware architecture; e.g., parallelization and vectorization ability to clearly list all instances of vectorization, parallelization or other optimizations. an unlimited system license Optional FORTRAN 77 compiler, ANSI compliant [ANSI X3.9-1978] (desirable). [Core Specification 3.3.2.5.c.4, 3.3.2.5.c.5., 3.3.2.5.c.5. replaced by]: a C++ compiler unlimited system license [Core Specification 3.3.2.5.d replaced by]: Advanced versions of compilers and advanced compiler features which enhance architecture specific performance, software tuning, modularity, functionality, etc.; and tools or capabilities (such as graphics debug interfaces) which enhance the coding, testing, and execution of programs Advanced versions of compilers may be substituted for the mandatory versions (advanced technology).. [Core Specification 3.3.2.5.g, 3.3.2.5.h,, and 3.3.2.5.j deleted]: [Core Specification 3.3.3.a , and 3.3.3.c deleted]: [Core Specification 3.4.2.b.5.and 3.4.2.b.6 replaced by]: all servers shall provide FDDI Dual Attachment Station (DAS) cabling. . the capability to directly attach to HIPPI and ATM networks. [Core Specification 3.4.4.b is not required for Class 6]: [Core Specification 3.6.e. is not required for Class 6]: Error Detecting/Correcting (ECC) Memory. 4.6.2.2. Class 6/a Compute Server The Class 6/a compute server shall provide the following minimum capabilities, unless noted as a desirable: minimum memory of at least 32 GBytes memory expandable to at least 64 GByte. hard disk storage with a minimum of 500 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 1000 GByte. minimum of 64 CPUs expandable to at least 256 CPUs. 4.6.2.3. Class 6/b Compute Server The Class 6/b compute server shall provide the following minimum capabilities, unless noted as a desirable: minimum memory of at least 16 GBytes memory expandable to at least 32 GByte. hard disk storage with a minimum of 200 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 500 GByte. minimum of 32 CPUs expandable to at least 128 CPUs. 4.6.3. Hierarchical Storage Management System In some instances, this Class will be configured to host large digital archives or as large file servers. To meet this requirement, a hierarchical storage management systems (HSM), such as UniTree or Data Migration Facility that integrate with the server and support multiple mass storage systems must be provided. the software must have the ability to: locate, mount, read and write tapes or disks in the jukeboxes. ability to support UNIX native file system user calls and commands, e.g. ls, touch, etc. support access at hard disk storage speed to the most frequently/recently accessed files. vault media and provide a means of notifying the operator to retrieve a vaulted media when an old file is requested. employ a nameserver or similar means for locating files on media. utilities for backup and recovery of critical databases repacking function (repack tapes to remove deleted files) logging major activities of software components for system monitoring. dual (or multiple) tape copies of a file; multiple server capabilities (server functions spread over multiple machines) as described in the IEEE Mass Storage Reference Model; and other advanced functions / capabilities (advanced technology). The servers must support the following mass storage systems: 3480/3490 tape drives, and jukeboxes The servers must support one or more of the following mass storage systems (desirable): D3 (e.g. STK) drives, and jukeboxes VHS tape drives, and jukeboxes NTP (e.g. IBM) drives, and jukeboxes multiple media types (e.g. ADIC) jukebox other state-of-the-art drives, and stackers (desktop jukeboxes) other state-of-the-art jukeboxes large library systems with storage capacity of at least 5 Tbytes, expandable to at least 100 Tbytes must be supported The hierarchical storage management system should be scalable up to at least 500 TB providing the user a way to build up to full use of the mass storage system. scalability up to the 1 Pbyte range (advanced technology) 4.6.4. Analyst Support An option for on-site analyst support shall be provided: Applications Systems Analyst/Programmer .Formulates and defines system scope and objectives. Prepares detailed specifications for programs. Designs, codes, tests, debugs and documents programs. Works at the highest technical level of all phases of applications, systems analysis and programming activities. Provides guidance and training to less experienced analysts/programmers. Educational Requirements: Bachelors degree from an accredited college or university with a curriculum or major field of study which provides substantial knowledge useful in managing large, complex AIS projects, is closely related to the work to be automated, and/or in a computer science, information system, a physical science, engineering or a mathematics-intensive discipline. Experience Requirements: Seven years of increasingly complex and progressive experience in performing systems analysis, development, and implementation of business, mathematical, or scientific setting using a variety of information technology resources. Has experience with current technologies and, where required for the task, emerging technologies. 4.6.5. Performance Benchmarks This section describes the performance values required for the Class 6 computer systems. 4.6.5.1. Performance for Class 6/a and 6/b The benchmarks provided include a set of optimized application codes from several NASA sites. These codes represent the type of work which will be performed on systems in this class. A suite of 6 application codes is provided. A description of the requirements for running the codes is given in the table below: CodeMemory (MB)Copiesdycore41.569lrl138.9102raf3131.72lrl8137.75mr2389.814rs1452.62 Both class 6a and 6b systems shall complete the entire workload as listed above in 2300 wall clock seconds. The minimum NASA I/O value for the class a and b computer systems is 150 mallards Table 6: CLASS 6 Performance and Capacity Requirements PERFORMANCE: Application wallclock (sec)mallardsSubclass(a)2300150Subclass(b)2300150 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandCPUsCPU expandSubclass(a)32 GB64 GB500GB1000GB64256Subclass(b)16 GB32 GB200 GB500GB32128 4.7. Class 7: Science and Engineering Research Computer Systems This section describes the Science and Engineering Research Computer Systems class specific requirements. 4.7.1. Purpose The purpose of this section is to define the specific requirements for the Science and Engineering Research Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 7 computer systems over and above, or in place of the core specifications defined in Section 3. 4.7.2. Hardware Configurations This class of computer systems is comprised of a subclass 7/a and subclass 7/b. These systems are differentiated by capacity, software capabilities and mandated OS. Both computer systems need to support a wide suite of software tools a variety of operating environments. 4.7.2.1. Class 7/a and 7/b Computer System All Class 7 computer systems (Class 7/a and 7/b) shall provide the following minimum capabilities, unless noted as a desirable: operate in an office environment at least 16 million simultaneously displayable colors and a monitor with a minimum of 1600x1200 resolution DVD drives CD Read/writable drives (desirable) at least 5 available bus slots 1.44 MB Floppy Drive 4.7.2.2. Class 7/a Computer System The Class 7/a computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 256 MByte memory expandable to at least 1 GBytes. hard disk storage with a minimum of 10 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 200 GBytes a 3-D graphics system supporting double-buffered 24 bit images with a 24 bit Z-buffer [Core Specification 3.3.2.5.a replaced by]: A FORTRAN 90 compiler, ANSI compliant [ANSI X3. 198-1992]. The FORTRAN compiler shall include: run time libraries. a FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. an optional 1 user license an optional 10 user license optional Windows based OS 4.7.2.3. Class 7/b Computer System The Class 7/b computer system shall provide the following minimum capabilities, unless noted as a desirable: Linux-based OS. [replaces core specification 3.3.2.a] optional Windows based OS a minimum CPU word size of 32 bits [replaces core specification 3.2.1.c.] 3D Sound Card 56 Kbps fax/data modem capability fax/data modems with ISDN capability (desirable) a minimum memory of at least 128 MBytes memory expandable to at least 768 MBytes. hard disk storage with a minimum of 10 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 20 GBytes 4.7.3. Application Software This section describes the commercial application software packages that are required to run on the Class 7 computer system systems. 4.7.3.1. Class 7/a Application Software The Class 7/a computer system shall support the following software: IDL Interactive Data Language ESRIs ARC/INFO GIS software. ESRIs ARCView software. IMSL Math Library (MATH, STAT and special functions for both C and FORTRAN) SAS Matlab Mathematica AutoCAD MSC NASTRAN database client libraries (allowing database applications to run on the computer systems while accessing remote database servers) including, but not limited to: Sybase Oracle Database servers (running the actual database instance on the system) on Class 3/a computer system including, but not limited to: Sybase Oracle 4.7.3.2. Class 7/b Application Software The Class 7/b computer system shall support the following software (each is a separate desirable): IDL Interactive Data Language ESRIs ARC/INFO GIS software. ESRIs ARCView software. IMSL Math Library (MATH, STAT and special functions for both C and FORTRAN) SAS Matlab Mathematica AutoCAD MSC NASTRAN database client libraries (allowing database applications to run on the computer systems while accessing remote database servers) including, but not limited to: Sybase Oracle Axum V.5.0 Slidewrite Scientific Work Hyperchem Win 95 EES- Software for Windows Easyplot Windows NT/95 MACSYMA, NUMKIT, PDEASE 2D 4.7.4. Performance Benchmarks This section describes the performance values required for the Class 7 computer systems. 4.7.4.1. Performance for Class 7/a The maximum allowed time to run the wmr29pc chemical kinetics code on the class a computer system running a Windows OS is 75 sec. The minimum Spec values for the class a computer system running a UNIX OS is: 15 SPEC CINT95 20 SPEC CFP95 The minimum NASA I/O value for the class a computer system running a UNIX OS is 100 mallards 4.7.4.2. Performance for Class 7/b The maximum allowed time to run the wmr29pc chemical kinetics code on the class b computer system running a Windows OS is 100 sec. The minimum Spec values for the class b computer system running a UNIX OS is: 10 SPEC CINT95 12 SPEC CFP95 The minimum NASA I/O value for the class b computer system running a UNIX OS is 100 mallards Table 7: CLASS 7 Performance and Capacity Requirements PERFORMANCE: wmr29pcCINT95CFP95mallardsSubclass(a)75 sec1520100Subclass(b)100 sec1012100 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandSlotsSubclass(a)256 MB1 GB10 GB200 GB5Subclass(b)128 MB768 MB10 GB20 GB5 4.8. Class 8: Earth Science Computer Systems This section describes the Earth Science Computer Systems class specific requirements. 4.8.1. Purpose The purpose of this section is to define the specific requirements for the Earth Science Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 8 computer systems over and above, or in place of the core specifications defined in Section 3. 4.8.2. Hardware Configurations This class of computer systems is comprised of a subclass 8/a and subclass 8/b. These systems are differentiated mainly by capacity. Both computer systems need to support a wide suite of software tools for UNIX based environments. 4.8.2.1. Class 8/a and 8/b Computer System All Class 8 computer systems (Class 8/a and 8/b) shall provide the following minimum capabilities, unless noted as a desirable: binary compatibility between Class 8/a and 8/b optional availability of a Linux-based OS (desirable) CD Read/writable drives (desirable) Error Detecting/Correcting (ECC) Memory. DLT tape drives provide an option for Gigabit Ethernet [Core Specification 3.3.2.5.a replaced by]: A FORTRAN 90 compiler, ANSI compliant [ANSI X3. 198-1992]. The FORTRAN compiler shall include: run time libraries. a FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output an optional 1 user license an optional 10 user license All Class 8 computer systems shall support the following minimum capabilities, unless noted as a desirable: DVD drive (desirable) AIT Tape Drive (desirable) 4.8.2.2. Class 8/a Computer System The Class 8/a computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 1 GByte memory expandable to at least 4 GBytes. hard disk storage with a minimum of 18 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 2 Tbytes at least 16 million simultaneously displayable colors and a monitor with a minimum of 1600x1200 resolution a 3-D graphics system supporting double-buffered 24 bit images with a 24 bit Z-buffer optionally rack-mountable and run headless (with serial console and no keyboard/monitor required) dual CPU Approach for clustering multiple computers, particularly approach for shared file system across a cluster (advanced technology) The Class 8/a computer system shall support the following minimum capabilities, unless noted as a desirable: hot-swappable, RAID disk arrays. journaled filesystems 4mm DAT jukeboxes 8mm jukeboxes DLT jukeboxes 4.8.2.3. Class 8/b Computer System The Class 8/b computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 512 MBytes memory expandable to at least 2 GBytes. hard disk storage with a minimum of 18 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 200 GBytes at least 16 million simultaneously displayable colors and a monitor with a minimum of 1280x1024 resolution operate in an office environment 4.8.3. Application Software All Class 8 computer systems (Class 8/a and 8/b) shall support the following software: ImageWorks package from PCI Geomatics of Ontario, Canada IDL Interactive Data Language ENVI Splus ESRIs ARC/INFO GIS software. ESRIs ARCView software. IMSL Math Library (MATH, STAT and special functions for both C and FORTRAN) SAS Word processors such as: Framemaker Matlab Mathematica database client libraries (allowing database applications to run on the computer systems while accessing remote database servers) on both class 8/a and 8/b computer systems including, but not limited to: Sybase Oracle 4.8.4. Performance Benchmarks This section describes the performance values required for the Class 8 computer systems. 4.8.4.1. Performance for Class 8/a The maximum average runtime for the NASA IDL benchmark performing two simultaneous runs, each running 50 iterations, is 1000 sec. The minimum SPECrate values for the class a computer system is: 250 SPEC CINT95rate 360 SPEC CFP95rate The minimum NASA I/O value for the class a computer system is 100 mallards 4.8.4.2. Performance for Class 8/b The maximum average runtime for the NASA IDL benchmark performing two simultaneous runs, each running 50 iterations, is 11000 sec. The minimum Spec values for the class b computer system is: 16 SPEC CINT95 22 SPEC CFP95 The minimum NASA I/O value for the class b computer system is 100 mallards Table 8: CLASS 8 Performance and Capacity Requirements PERFORMANCE: IDL runtimeCINT95CFP95mallardsSubclass(a)1000 sec250 (Rate)360 (Rate)100Subclass(b)11000 sec1622100 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandCPUsSubclass(a)1 GB4 GB18GB2 TB2Subclass(b)512 MB2 GB18GB200 GB1 4.9. Class 9: Space Science Systems This section describes the Space Science Computer Systems class specific requirements. 4.9.1. Purpose The purpose of this section is to define the specific requirements for the Space Science Computer Systems as described in Section 2. The following hardware and software specifications are required of these Class 9 computer systems over and above, or in place of the core specifications defined in Section 3. 4.9.2. Hardware Configuration This class of computer systems is comprised of a subclass 9/a and subclass 9/b. These systems are differentiated mainly by capacity. Both computer systems need to support a wide suite of software tools for UNIX based environments. 4.9.2.1. Class 9/a and 9/b Computer System All Class 9 computer systems (Class 9/a and 9/b) shall provide the following minimum capabilities, unless noted as a desirable: binary compatibility between Class 9/a and 9/b (desirable) Error Detecting/Correcting (ECC) Memory. Efficient multi-tasking, including foreground process priority. [Core Specification 3.3.2.5.a replaced by]: A FORTRAN 90 compiler, ANSI compliant [ANSI X3. 198-1992]. The FORTRAN compiler shall include: run time libraries. a FORTRAN source language compatible symbolic debugger with capability to read core dumps. Shall display source code, program variables (including register contents), debugger commands, and debugger output. an optional 1 user license an optional 10 user license Hot swappable disks (desirable) 4.9.2.2. Class 9/a Computer System The Class 9/a computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 2 GByte memory expandable to at least 8 GBytes. hard disk storage with a minimum of 20 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 1 Tbytes graphics capability of at least: 32 bit z-buffer, texture mapping and alpha blending; 500,000 100-pixel polygons/sec monitors as required in Core Specification 3.2.4.d must also be: stereo-ready minimum of 1900x1200 resolution at least 16 million simultaneously displayable colors 2 CPUs minimum of 1 Gflops per CPU Approach for larger, efficient storage; improved graphics performance; parallelizing compiler, including the use of distributed memory and remote CPUs; desktop 100GB backup device (advanced technology) The Class 9/a computer system shall support the following minimum capabilities, unless noted as a desirable: DVD drives (desirable) 4mm DAT, 8mm, or DLT jukeboxes or other suitable large-volume backup devices 4.9.2.3. Class 9/b Computer System The Class 9/b computer system shall provide the following minimum capabilities, unless noted as a desirable: a minimum memory of at least 128 MBytes memory expandable to at least 1 GBytes. hard disk storage with a minimum of 5 GByte of available user space remaining after installation of all minimum required software as specified in the delivery list (operating system, system swap space, on-line system documentation, linker, drivers, X windows, etc.). disk storage expandable to at least 20 GBytes graphics capability of at least: 24 bit z-buffer, monitors as required in Core Specification 3.2.4.d must also be: minimum of 1024x768 resolution at least 16 million simultaneously displayable colors operate in an office environment minimum of 1 Gflops per CPU 4.9.3. Application Software All Class 9 computer systems (Class 9/a and 9/b) shall support the following software: Open GL IDL Interactive Data Language IMSL Math Library (MATH, STAT and special functions for both C and FORTRAN) 4.9.4. Performance Benchmarks This section describes the performance values required for the Class 9 computer systems. 4.9.4.1. Performance for Class 9/a The maximum allowed total real time for the NASA Space Science Benchmark is 43 minutes The minimum SPECrate values for the class a computer system is: 250 SPEC CINT95rate 360 SPEC CFP95rate The minimum NASA I/O value for the class a computer system is 100 mallards 4.9.4.2. Performance for Class 9/b The maximum allowed total real time for the NASA Space Science Benchmark is 53 minutes The minimum Spec values for the class b computer system is: 15 SPEC CINT95 20 SPEC CFP95 The minimum NASA I/O value for the class b computer system is 100 mallards Table 9: CLASS 9 Performance and Capacity Requirements PERFORMANCE: Space Science BenchmarkCINT95CFP95mallardsSubclass(a)43 minutes250 (Rate)360 (Rate)100Subclass(b)53 minutes1520100 CAPACITY: Mem.Mem. ExpandDiskDisk ExpandCPUsSubclass(a)2 GB8 GB20 GB1 TB2Subclass(b)128 MB1 GB5 GB20 GB1 4.10. Summary Class Specific Requirements To clarify relationships between classes, many (but not all) of the requirements are summarized in the following tables. Table 10: Binary Compatibility within Class Class123456789Desirable ---X-X--XMandatory XXX-X--X Table 11: Office Environment Requirements Class123456789 Subclass (a)-R----R--Subclass (b)RR-DR-RRR D = Desirable R = Required Table 12: Memory Error Detection/Correction (ECC) Requirements Class123456789Subclass (a)RD-RDR-RRSubclass (b)---R-R-RR D = Desirable R = Required Table 13: Capacity Requirements Summary MemMem. ExpandDiskDisk ExpandSlotsCPUsCPU Expand1(a)2 GB4 GB18GB60GB321(b)1 GB2 GB8GB36GB212(a)512 MB2 GB8GB64GB322(b)256 MB1GB8GB32GB213(a)8 GB12 GB16GB64GB168123(b)4 GB6 GB8GB32GB8464(a)1 GB2 GB16GB900GB162244(b)256 MB512 MB8GB120GB5165(a)1 GB4GB9 GB64 GB3145(b)512 MB2 GB9 GB32GB2126(a)32 GB64 GB500GB1000GB642566(b)16 GB32 GB200 GB500GB321287(a)256 MB1 GB10 GB200 GB57(b)128 MB768 MB10 GB20 GB58(a)1 GB4 GB18GB2 TB-28(b)512 MB2 GB18GB200 GB-19(a)2 GB8 GB20 GB1 TB-29(b)128 MB1 GB5 GB20 GB-1 5. Category B: Computer System Support Devices This section specifies equipment needed to support a full implementation of computer systems in the NASA network environment. These items may be purchased by the Government separately from the computer systems but rely on standards and standard interfaces to ensure interoperability with the computer systems. 5.1. X Terminals X Terminals are graphical devices attached directly to the network and operate as X Servers to X Clients operating on conventional computer systems. Two X Terminal configurations shall be offered. Each shall support the Core X Terminal requirement as well as requirements unique to each X Terminal configuration. 5.1.1. Core X Terminal Requirements All X Terminals shall provide the following minimum capabilities: keyboard - A detachable ANSI compatible [ANSI X3.64] alphanumeric keyboard. mouse - A mouse with at least three buttons. This device shall permit the user to address individual screen pixels. graphic monitor - All graphic monitors shall be color devices with the following capabilities: RGB (red, green, blue) video output that will allow the use of video projectors and the adaptation of other video equipment. a graphics controller capable of at least 256 colors simultaneously displayable from a palette of at least 16 million available colors. X Window Server software (X-11R6 or greater) a serial interface as described in Section 3.2.3.b. an Ethernet network interface as specified in Section 3.4.2.a. and a sufficient set of Internet Protocols (IP) (as specified in Section 3.4.4) as required to support X Window Server software services and connectivity to X Clients on the network. A parallel interface a Simple Network Management Protocol (SNMP) agent [RFC 1157; RFC 1213] for remote monitoring Energy Star compliant both a ROM based and host based boot X11 security/authority support (desirable) SLIP support (desirable) Support for the following server ext