1、Designation: F 2218 02An American National StandardStandard Guide forHardware Implementation for Computerized Systems1This standard is issued under the fixed designation F 2218; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the y
2、ear of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon (e) indicates an editorial change since the last revision or reapproval.1. Scope1.1 This guide provides assistance in the choice of comput-ing hardware resources for ship and marine environments
3、 anddescribes:1.1.1 The core characteristics of interoperable systems thatcan be incorporated into accepted concepts such as the OpenSystem Interconnection (OSI) model;1.1.2 Process-based models, such as the Technical Refer-ence Model (TRM), that rely on interoperable computinghardware resources to
4、provide the connection between theoperator, network, application, and information; and,1.1.3 The integrated architecture that can be used to meetminimum information processing requirements for ship andmarine environments.1.2 The use of models such as OSI and TRM provide astructured method for design
5、 and implementation of practicalshipboard information processing systems and provides plan-ners and architects with a roadmap that can be easily under-stood and conveyed to implementers. The use of such modelspermit functional capabilities to be embodied within concretesystems and equipment.1.3 The
6、information provided in this guide is understood torepresent a set of concepts and technologies that have, overtime, evolved into accepted standards that are proven invarious functional applications. However, the one universalnotion that still remains from the earliest days of informationprocessing
7、is that technological change is inevitable. Accord-ingly, the user of this guide must understand that such progressmay rapidly invalidate or supersede the information containedherein. Nonetheless, the concept of implementing ship andmarine computing systems based on these functional principlesallows
8、 for logical and rational development and provides asound process for eventual upgrade and improvement.2. Referenced Documents2.1 ASTM Standards:E 1013 Terminology Relating to Computerized Systems2F 1757 Guide for Digital Communications Protocols forComputerized Systems32.2 ANSI Standards:4X3.131 In
9、formation SystemsSmall Computer SystemsInterface-2 (SCSI-2)X3.172 American National Standard Dictionary for Infor-mation SystemsX3.230 Information SystemsFibre ChannelPhysicaland Signaling Interface (FC-PH)X3.232 Information TechnologySCSI-2 Common AccessMethod Transport and SCSI Interface ModuleX3.
10、253 Information SystemsSCSI-3 Parallel Interface(SPI)X3.269 Information TechnologyFibre Channel Protocolfor SCSIX3.270 Information TechnologySCSI-3 ArchitectureModel (SAM)X3.276 Information TechnologySCSI-3 Controller Com-mands (SCC)X3.277 Information TechnologySCSI-3 Fast-20X3.292 Information Techn
11、ologySCSI-3 Interlocked Pro-tocol (SIP)X3.294 Information TechnologySerial StorageArchitectureSCSI-2 Protocol (SSA-S2P)X3.297 Information SystemsFibre ChannelPhysicaland Signaling Interface-2 (FC-PH2)X3.301 Information TechnologySCSI-3 Primary Com-mands (SPC)X3.304 Information TechnologySCSI-3 Multi
12、mediaCommands (MMC)MS58 Information TechnologyStandard RecommendedPractice for Implementation of Small Computer SystemsInterface (SCSI-2), (X3.131.1994) for ScannersNCITS 306 Information TechnologySerial StorageArchitectureSCSI-3 Protocol (SSA-S3P)NCITS 309 Information TechnologySCSI-3 Block Com-man
13、ds (SBC)2.3 IEEE Standards:5100 Standard Dictionary for Electrical and Electronic Terms488 Digital Interface for Programmable Instrumentation1This guide is under the jurisdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibility of Subcommittee F25.05 onComputer Ap
14、plications.Current edition approved Dec. 10, 2002. Published March 2003.2Discontinued 2000. See 1999 Annual Book of ASTM Standards, Vol 14.01.3Annual Book of ASTM Standards, Vol 01.07.4Available from American National Standards Institute (ANSI), 25 W. 43rd St.,4th Floor, New York, NY 10036.5Availabl
15、e from Institute of Electrical and Electronics Engineers, Inc. (IEEE),445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-1331.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.610.7 Standard Glossary for Computer Networking Termi-nology
16、796 Microcomputer System Bus802.11 Wireless LAN Medium Access Control and PhysicalLayer Specifications1003.2d POSIXPart 2 Shell and UtilitiesAmendment:Batch Environment1003.5 Binding for System Application Program Interface(API)1003.b Binding for System Application Programming Inter-face (API)Amendm
17、ent 1: Real-time Extensions1014 Versatile Backplane Bus: VMEbus1101.10 Additional Mechanical Specifications for Micro-computers using the IEEE Std 1101.1 Equipment Practice1155 VMEbus Extensions for Instrumentation: VXIbus1212.1 Communicating Among Processors and PeripheralsUsing Shared Memory (Dire
18、ct Memory Access DMA)1394 High Performance Serial Bus1496 Chip and Module Interconnect Bus: Sbus1394 32-bit Microprocessor Architecture2.4 ISO Standards:41155 Portable Operating System Interface for ComputerEnvironments (POSIX)9945-1 System Application Program Interface (API) Clanguage9945-2 Shell a
19、nd Utilities2.5 TIA/EIA Standard:6568-A Commercial Building Telecommunications CablingStandard3. Significance and Use3.1 This guide is aimed at providing a general understand-ing of the various types of hardware devices that form the coreof information processing systems for ship and marine use.Ship
20、 and marine information processing systems require spe-cific devices in order to perform automated tasks in a special-ized environment. In addition to providing information ser-vices for each individual installation, these devices are oftennetworked and are capable of supplementary functions thatben
21、efits ship and marine operations.3.2 A variety of choices exists for deployment of informa-tion processing devices and greatly increases the complexity ofthe selection task for ship and marine systems. The choice of aparticular device or system cannot be made solely on thesingular requirements of on
22、e application or function. Moderninformation processing systems are usually installed in acomplex environment where systems must be made to interactwith each other. Ship and marine installations add an evenfurther layer of complexity to the process of choosing adequatecomputerized systems. This guid
23、e aims to alleviate this task bygiving users specific choices that are proven technologies thatperform in a complex environment.3.3 Hardware resources used in ship and marine installa-tions are a result of careful consideration of utility andfunction. These resources may require some physical specia
24、l-ization in order to inhabit a particular environment, but they arein no way different from equipment used in shore-basedsituations. Ship and marine computer system configurations,interconnections, and support services are essentially the sameas those found in a land-based network environment and a
25、s aresult, the skill sets of ship and marine information processingsystem users, administrators, and support personnel are inter-changeable with those of shore-based activities.4. Standards Profiles4.1 Standards profiles are sets of specifications bundledtogether to describe the technical standard f
26、or a function or aservice (such as operating systems, network, and data inter-change services), and will include minimum criteria for theinformation and technology that support specific functionalrequirements. Profiles equate to the lowest level process, anddocument agreed-to implementation requirem
27、ents used inbuilding and operating systems. Systems using the samestandards, but different options, will probably not interfacecorrectly. The Technical Reference Model (TRM) is useful forassembling standards profiles across technology categories ofComputing Resources, Information Management, and App
28、li-cations.4.1.1 The TRM identifies and specifies the support services(multimedia, communications, and so forth) and interfaces thatprovide a common operating environment and support the flowof information among enterprise and common support appli-cations. This model represents the computer resource
29、s, infor-mation management, and applications categories and interfaceswith the communication and networking technology categoriesthat are appropriately represented by the ISO Open SystemInterconnect model. The TRM addresses standard profiles thatprovide seamless application support over widely distr
30、ibutedcomputing resources and attendant interfaces between thecomputing resources and other technologies.4.2 Computing hardware resources represent generally con-sists of Central Processing Unit(s) (CPU), Input and Output(I/O) interfaces, main memory, buses, and peripherals. Theexternal environment
31、considerations that affect computinghardware resource selection are security, communications,real-time, and high availability. The computing hardwareresource provides the environment necessary to support appli-cation software. From the perspective of the applicationsoftware, services are provided by
32、 the computing resource,whether the particular services are provided locally or remotelyas part of a distributed system.4.3 The architecture needed to support a typical applicationconsists of computers that perform as clients and servers. Theservers host the primary application software and contain
33、theprocessing power necessary to support multiple users. Serversalso host the data needed to support the application. Thestandard 3-tiered application architecture consists of (1)anapplication server, (2) a data server, and (3) presentation clients(see Fig. 1).4.4 In the future, most application pro
34、cessing software willbe hosted on the server computers. Clients will use presenta-tion software that connects to the servers using a commoninterface. At that time, client computers will likely be less6Available from TIA, 2500 Wilson Boulevard, Suite 300, Arlington, VA22201-3834.F2218022expensive and
35、 tailored to the users individual preferencebecause application interoperability will not be a significantfactor.4.5 Today, however, most application software is hosted onthe client and interoperability among clients is a critical factor.Even within the client-server application architecture, applic
36、a-tion specific software resident on the client is still prevalent.This demands consistency of client workstations across anentire installation to achieve seamless interoperability. Table 1outlines a rationale for the client-server deployment strategy.4.6 Driven by the current state of client-server
37、 technology,the general philosophy for implementing computing resourcesis the concept of homogeneous clients and heterogeneousservers. Homogeneous clients facilitate providing a consistentinterface between the user and the system and make systemsupport and maintenance less complex. Heterogeneous ser
38、verssupport the various computing requirements of applicationsneeded to support ship and marine operations. The sameadvantages that homogeneous clients enjoy can be achieved ifservers are homogeneous as well. Independent of whether ornot the server suite employed is heterogeneous or homoge-neous, it
39、 is important that they perform their function trans-parently to the user (that is, the user neither knows nor caresabout the location, number, or vendor of the server being used.)Requiring servers to be homogeneous would restrict theintroduction of new server technology, choking innovation andpreve
40、nting the installation from taking advantage of advancesin computing such as massively parallel processors.5. Computing Hardware5.1 Computing ResourcesComputing resources consist ofmany computing hardware components and configurations ofthese components. This section covers the various hardwarecompo
41、nents that make up a computing resource system andexamines how these components are commonly configured.FIG. 1 Three-Tiered Application ArchitectureTABLE 1 Client-Server Deployment RationaleRationale for Heterogeneous Servers The server must be tailored to the specific application that may notbe sup
42、portable by computers most prevalent in the marketplace.Many applications work well in their current computing environmentand it is not cost effective to change.It is not practical to have all applications on a common server formultiple reasons including the need to maintain competitionbetween compu
43、ter developers and vendors.Encourages innovation by not restricting the type of computer usedfor the development of applications.Rationale for Homogeneous Clients Allows for a common, consistent user interface.Maximizes interoperability.Minimizes re-training required as users transfer to differentor
44、ganizations within the enterprise.Maximizes the ability to use common support and maintenanceskills, parts and labor; thereby minimizing cost.Maximizes portability of support for applications across theenterprise as well as portability of user skills.Allows for economies of scale in both procurement
45、 (volumediscounts) and support (more focused skill set for help deskpersonnel).F22180235.2 Component TechnologiesThe major hardware compo-nents of Computing Resources are the Central Processing Unit(CPU), one or more backplane buses, main memory (bothRAM and cache), Input/Output (I/O) interfaces, an
46、d peripher-als. This section will examine each of these areas and provideguidance on the selection of these component technologies aspart a computing resource system.5.2.1 CPUThe CPU is the “engine” of the computersystem and, combined with the OS (operating system), formsthe core of the computing re
47、source. Since the OS drives manydecisions concerning the computer resource, a CPU that iscompatible with the OS becomes an overriding factor indetermining the type of CPU. Other than the OS, the mainfactors to consider in determining the type of CPU for thecomputer are processing speed (performance)
48、 and cost. Forcomputing resources, such as servers and multiprocessors,scalability of the number of processors can be a significantfactor in determining CPU.5.2.2 BusThe computer bus connects the different com-ponents of the computer resource together and allows them topass data between them at high
49、 speeds. Computer resourceconfigurations, such as personal workstations, often limit ordetermine the type of bus that will be used. Often there aremultiple buses connected together to allow for multiple typesof component cards or to extend a non-expandable system bus.Considerations in determining the type of bus to use are:number and type of commercial products compatible with thebus architecture, number of parallel data bit lines, clock speed,and cost. Once the appropriate bus architecture is determined,an important computer resource factor becomes how many
