下载文档原格式
电子证书认证系统GFA CA 3.0技术白皮书White Paper公司：北京国富安电子商务安全认证有限公司GFA E-commerce Security CA CO.,Ltd.地址：中国北京经济技术开发区荣华中路11号本白皮书的内容是北京国富安电子商务安全认证有限公司关于电子证书认证系统的技术说明书。
本材料的相关权力归北京国富安电子商务安全认证有限公司所有，白皮书中的任何部分未经本公司事先书面同意，不得增删、改编、转印、影印、复印及传播。
如欲获取最新相关信息，请访问本公司网站，您的意见和建议请发送到本公司邮箱。
国富安网站：电子邮箱：gfasupport@All rights reserved.2目录1产品简介 (5)2产品结构 (6)3工作原理 (8)3.1证书签发系统设计 (8)3.2证书注册系统设计 (9)3.3密钥管理系统设计 (13)3.4证书在系统间的安全传输 (15)3.5技术标准 (16)4系统流程设计 (18)4.1系统初始化流程 (18)4.2系统角色的建立 (19)4.3系统工作流程介绍 (20)4.4证书管理工作流程 (21)4.4.1证书申请与审核 (21)4.4.2签发下载 (22)4.4.3证书更新 (23)4.4.4证书注销流程 (24)4.5密钥管理工作流程 (24)4.5.1密钥生成流程 (25)4.5.2密钥分发流程 (25)4.5.3密钥更新流程 (26)4.5.4密钥注销流程 (27)4.5.5密钥恢复流程 (28)5产品功能设计 (30)5.1认证中心（CA Server） (30)5.1.1证书管理 (30)5.1.2模板管理 (31)5.1.3权限管理 (32)35.1.4机构管理 (33)5.1.5证书归档和证书统计 (33)5.2注册中心（RA Server） (34)5.2.1证书管理 (34)5.2.2用户管理 (35)5.2.3DN规则管理 (35)5.2.4模板管理 (35)5.3密钥管理中心（KM Server） (35)5.3.1密钥管理 (36)5.3.2机构管理 (36)5.3.3权限管理 (37)5.3.4密钥恢复和司法取证 (38)6产品主要技术特点 (40)7系统配置要求 (43)7.1硬件环境 (43)7.2软件环境 (43)7.3技术指标 (43)8产品部署方式 (44)41产品简介国富安数字证书认证系统（简称GFA CA系统）是对生命周期内的数字证书进行申请、审核、签发、注销、更新、查询的综合管理系统。
TECHNOLOGY MOVES FAST. WE MOVE FASTER.* Under Construction / ** Authorized for ConstructionSUBMARINESUse of DoD visual information does not imply or constituent DoD endorsement.LOS ANGELES CLASS> SSN 717 Olympia > SSN 719 Providence > SSN 720 Pittsburgh > SSN 721 Chicago > SSN 722 Key West> SSN 723 Oklahoma City > SSN 724 Louisville > SSN 725 Helena> SSN 750 Newport News > SSN 751 San Juan > SSN 752 Pasadena > SSN 753 Albany > SSN 754 Topeka > SSN 756 Scranton > SSN 757 Alexandria > SSN 758 Asheville> SSN 759 Jefferson City > SSN 760 Annapolis > SSN 761 Springfield > SSN 762 Columbus > SSN 763 Santa Fe > SSN 764 Boise> SSN 765 Montpelier > SSN 766 Charlotte > SSN 767Hampton> SSN 768 Hartford > SSN 769 Toledo > SSN 770 Tucson > SSN 771 Columbia > SSN 772 Greeneville > SSN 773CheyenneVIRGINIA CLASS> SSN 774 Virginia > SSN 775 Texas > SSN 776 Hawaii> SSN 777 North Carolina > SSN 778 New Hampshire > SSN 779 New Mexico > SSN 780 Missouri > SSN 781 California > SSN 782 Mississippi > SSN 783 Minnesota > SSN 784 North Dakota > SSN 785 John Warner > SSN 786 Illinois> SSN 787 Washington > SSN 788 Colorado > SSN 789 Indiana> SSN 790 South Dakota > SSN 791Delaware> SSN 792 Vermont > SSN 793 Oregon*> SSN 794 Montana*> SSN 795 Hyman G Rickover*> SSN 796 New Jersey*> SSN 797 Iowa*> SSN 798 Massachusetts*> SSN 799 Idaho*> SSN 800 Arkansas*> SSN 801 Utah*> SSN 802 Oklahoma*> SSN 803 Arizona*> SSN 804 Barb*> SSN 805 Tang**> SSN 806 WAHOO**> SSN 807 (Unnamed)**> SSN 808 (Unnamed)**> SSN 809 (Unnamed)**> SSN 810(Unnamed)**FAST ATTACK (SSN)SEAWOLF CLASS> SSN 21 Seawolf > SSN 22 Connecticut > SSN 23Jimmy CarterGUIDED MISSILE (SSGN)OHIO CLASS> SSGN 726 Ohio > SSGN 727 Michigan > SSGN 728 Florida > SSGN 729GeorgiaBALLISTIC MISSILE (SSBN)OHIO CLASS> SSBN 730 Henry M Jackson > SSBN 731 Alabama > SSBN 732 Alaska > SSBN 733 Nevada > SSBN 734 Tennessee > SSBN 735 Pennsylvania > SSBN 736 West Virginia > SSBN 740 Rhode Island > SSBN 741 Maine > SSBN 742 Wyoming > SSBN 743 Louisiana > SSBN 737 Kentucky > SSBN 738 Maryland > SSBN 739 Nebraska> SSBN 826 USS Columbia**> SSBN 827USS Wisconsin**CAPABILITIES> Integrated C5ISR Systems - Integrated & AutomatedCommunications - Navigation & Management - Alarm & Announcing Systems - Bridge & Navigation Systems > Tactical Information Assurance Solutions> EW / SIGINT Systems > Ship Control & Propulsion Systems > Crypto, Key Management & Network Security Solutions > Automatic Information Systems> Defense & Security Unmanned Surface Vehicles (USV)> Commercial & Scientific USVs > Unmanned Vessel Conversion > Aluminum-Water Power Solutions > UUV Fuel Cell C5 SYSTEMS> Integrated Platform Management Systems > Nuclear Power Plant Simulators> Space Robotics Operations Training> Battle Damage Control System > Submarine Systems / Training > Visual Landing Aids / Naval Handling Systems > Mine Warfare Systems > Maritime EW / RF Mics > Electronic Systems & I ntegration> Underwater Communications > Multi-domain Situational Awareness> Hydrographic Systems> Defense & Security Unmanned Surface Vehicles (USV)> Commercial & Scientific USVs > Unmanned Vessel Conversion INTERNATIONALUse of DoD visual information does not imply or constituent DoD endorsement.CRUISERS (CG)TICONDEROGA CLASS> CG 52 Bunker Hill > CG 53 Mobile Bay > CG 54 Antietam > CG 55 Leyte Gulf > CG 56 San Jacinto> CG 57 Lake Champlain > CG 58 Philippine Sea > CG 59 Princeton > CG 60 Normandy > CG 61 Monterey> CG 62 Chancellorsville > CG 63 Cowpens > CG 64 Gettysburg > CG 65 Chosin > CG 66 Hue City > CG 67 Shiloh > CG 68 Anzio > CG 69 Vicksburg > CG 70 Lake Erie> CG 71 Cape St. George > CG 72 Vella Gulf > CG 73Port RoyalGUIDED MISSILE FRIGATE (FFG)FFG 62 Constellation**FFG 63 Congress**LITTORAL COMBAT SHIP (LCS)> LCS 1 Freedom> LCS 2 Independence > LCS 3 Fort Worth > LCS 4 Coronado > LCS 5 Milwaukee > LCS 6 Jackson > LCS 7 Detroit> LCS 8 Montgomery > LCS 9 Little Rock> LCS 10 Gabrielle Giffords > LCS 11 Sioux City > LCS 12 Omaha > LCS 13 Wichita > LCS 14 Manchester > LCS 15Billings> LCS 16 Tulsa> LCS 17 Indianapolis > LCS 18 Charleston > LCS 19 St Louis > LCS 20 Cincinnati > LCS 27 Nantucket*> LCS 28 Savannah*> LCS 29 Beloit*> LCS 30 Canberra*> LCS 31 Cleveland**> LCS 32 Santa Barbara**> LCS 34 Augusta*> LCS 36 Kingsville**> LCS 38 Pierre**DESTROYERS (DDG)ARLEIGH BURKE CLASS> DDG 51 Arleigh Burke > DDG 52 Barry> DDG 53 John Paul Jones > DDG 54 Curtis Wilbur > DDG 55 Stout> DDG 56 John S McCain > DDG 57 Mitscher > DDG 58 Laboon > DDG 59 Russell> DDG 60 Paul Hamilton > DDG 61 Ramage > DDG 62 Fitzgerald > DDG 63 Stethem > DDG 64 Carney > DDG 65 Benfold > DDG 66 Gonzalez > DDG 67 Cole> DDG 68 The Sullivans > DDG 69 Milius > DDG 70 Hopper > DDG 71 Ross > DDG 72 Mahan > DDG 73 Decatur > DDG 74 McFaul> DDG 75 Donald Cook > DDG 76 Higgins > DDG 77 O’kane > DDG 78 Porter> DDG 79 Oscar Austin > DDG 80 Roosevelt> DDG 81Winston S Churchill> DDG 82 Lassen > DDG 83 Howard > DDG 84 Bulkeley > DDG 85 McCampbell > DDG 86 Shoup > DDG 87 Mason > DDG 88 Preble > DDG 89 Mustin > DDG 90 Chafee > DDG 91 Pinckney > DDG 92 Momsen > DDG 93 Chung-hoon > DDG 94 Nitze> DDG 95 James E Williams > DDG 96 Bainbridge > DDG 97 Halsey> DDG 98 Forrest Sherman > DDG 99 Farragut > DDG 100 Kidd > DDG 101 Gridley > DDG 102 Sampson > DDG 103 Truxtun > DDG 104 Sterett > DDG 105 Dewey > DDG 106 Stockdale > DDG 107 Gravely> DDG 108 Wayne E Meyer > DDG 109 Jason Dunham> DDG 110 William P Lawrence > DDG 111 Spruance> DDG 112 Michael Murphy > DDG 113 John Finn> DDG 114 Ralph Johnson > DDG 115 Rafael Peralta > DDG 116 Thomas Hudner > DDG 117 Paul Ignatius > DDG 118 Daniel Inouye*> DDG 119 Delbert D Black*> DDG 120 Carl M Levin*> DDG 121 Frank E Petersen Jr*> DDG 122 John Basilone*> LCS 21 Minneapolis/St. Paul*> LCS 22 Kansas City > LCS 23 Cooperstown*> LCS 24 Oakland > LCS 25 Marinette*> LCS 26 Mobile*> DDG 128 Ted Stevens*> DDG 129 Jeramiah Denton**> DDG 130 William Charette**> DDG 131 George M Neal**> DDG 132 Quetin Walsk**> DDG 133 Sam Nunn**> DDG 134 John E Kilmer**> DDG 135 (Unnamed)**> DDG 136 (Unnamed)**> DDG 137 John F Lehman**> DDG 138 (Unnamed)**> DDG 139 (Unnamed)**DDG ZUMWALT CLASS> DDG 1000 Zumwalt> DDG 1001 Michael Monsoor > DDG 1002 Lyndon B Johnson*SURFACE COMBATANTSAIRCRAFT CARRIERSAIRCRAFT CARRIERS (CVN)NIMITZ CLASS> CVN 68 Nimitz> CVN 69 Dwight D Eisenhower > CVN 70 Carl Vinson> CVN 71 Theodore Roosevelt > CVN 72 Abraham Lincoln > CVN 73 George Washington > CVN 74 John C Stennis > CVN 75 Harry S Truman > CVN 76 Ronald Reagan > CVN 77George H W BushFORD CLASS> CVN 78 Gerald R Ford > CVN 79 John F Kennedy*> CVN 80 Enterprise*> CVN 81Doris Miller*** Under Construction / ** Authorized for ConstructionAMPHIBIOUS WARFARE SHIPS Use of DoD visual information does not imply or constituent DoD endorsement.COMMAND (LCC)BLUE RIDGE CLASS> LCC 19 Blue Ridge> LCC 20 Mount Whitney ASSAULT SHIPS (LHA, LHD)TARAWA CLASS> LHA 6 America> LHA 7 Tripoli> LHA 8 Bougainville* WASP CLASS> LHD 1 Wasp> LHD 2 Essex> LHD 3 Kearsarge> LHD 4 Boxer> LHD 5 Bataan> LHD 6 Bonhomme Richard > LHD 7 Iwo Jima> LHD 8 Makin Island SAN ANTONIO CLASS> LPD 17 San Antonio> LPD 18 New Orleans> LPD 19 Mesa Verde> LPD 20 Green Bay> LPD 21 New York> LPD 22 San Diego> LPD 23 Anchorage> LPD 24 Arlington> LPD 25 Somerset> LPD 26 John P Murtha> LPD 27 Portland> LPD 28 Ft. Lauderdale*> LPD 29 Richard M McCool Jr*> LPD 30 Harrisburg**> LPD 31 (Unnamed)**DOCK LANDING (LSD)WHIDBEY ISLAND CLASS> LSD 41 Whidbey Island> LSD 42 Germantown> LSD 43 Fort McHenry> LSD 44 Gunston Hall> LSD 45 Comstock> LSD 46 Tortuga> LSD 47 Rushmore> LSD 48 AshlandHARPERS FERRY CLASS> LSD 49 Harpers Ferry> LSD 50 Carter Hall> LSD 51 Oak Hall> LSD 52 Pearl HarborMINE COUNTER MEASURES (MCM)AVENGER CLASS> MCM 3 Sentry> MCM 6 Devastator> MCM 7 Patriot> MCM 9 Pioneer> MCM 10 Warrior> MCM 11 Gladiator> MCM 13 Dextrous> MCM 14 ChiefCAPABILITIES> Submarine, Imaging Systems & Consoles, and Radar> Surface Imaging Systems> Fleet Support Services / Marine Services> Dipping Sonar Systems> Towed Array Systems> Bottom Mounted Active & Passive Integrated Hydrophone System> Acoustic Systems> Maritime and Training and > Ocean Observatories> Underwater AcousticCommunications> Undersea Sensor Systems > Unmanned Underwater Vehicles (UUV)> Custom Payloads> Mission Planning Software > C2 Theater ASW Systems > Common Operational Picture Tools> C2 Systems and SystemsSENSORS> Electrical Auxiliary Propulsion> Specialty Submarine Products> Support Services > Power Conversion Modules- Advanced Degaussing- Automatic Bus Transfer- Frequency Converters- AC to DC Rectifiers- Fault Isolation> Circuit Breakers> Switchboards and Load Centers > Power Node Control Centers > Support ServicesSERVICES POWERUse of DoD visual information does not imply or constituent DoD endorsement.NATIONAL SECURITY CUTTERS (WMSL)418-FOOT-LEGEND CLASS > WMSL 750 Bertholf> WMSL 751 Waesche> WMSL 752 Stratton> WMSL 753 Hamilton> WMSL 754 James> WMSL 755 Munro> WMSL 756 Kimball> WMSL 757 Midgett> WMSL 758 Stone*> WMSL 759 Calhoun*> WMSL 760 Friedman* ICEBREAKERS (WAGB) 420-FOOT> WAGB 20 Healy399-FOOT> WAGB 10 Polar Star240-FOOT> WLBB 30 Mackinaw HIGH ENDURANCE CUTTERS (WHEC)378-FOOT-HAMILTON CLASS> WHEC 717 Mellon> WHEC 724 Munro> WHEC 726 Midgett MEDIUM ENDURANCE CUTTERS (WMEC)282-FOOT> WMEC 39 Alex Haley270-FOOT> WMEC 901 Bear> WMEC 902 Tampa> WMEC 903 Harriet Lane> WMEC 904 Northland > WMEC 905 Spencer> WMEC 906 Seneca> WMEC 907 Escanaba> WMEC 908 Tahoma> WMEC 909 Campbell> WMEC 910 Thetis> WMEC 911 Forward> WMEC 912 Legare> WMEC 913 Mohawk210-FOOT> WMEC 615 Reliance> WMEC 616 Diligence> WMEC 617 Vigilant> WMEC 618 Active> WMEC 619 Confidence> WMEC 620 Resolute> WMEC 621 Valiant> WMEC 623 Steadfast> WMEC 624 Dauntless> WMEC 625 Venturous> WMEC 626 Dependable> WMEC 627 Vigorous> WMEC 629 Decisive> WMEC 630 AlertSEAGOING BUOY TENDER(WLB)225-FOOT> WLB 201 Juniper> WLB 202 Willow> WLB 203 Kukui> WLB 204 Elm> WLB 205 Walnut> WLB 206 Spar> WLB 207 Maple> WLB 208 Aspen> WLB 209 Sycamore> WLB 210 Cypress> WLB 211 Oak> WLB 212 Hickory> WLB 213 Fir> WLB 214 Hollyhock> WLB 215 Sequoia> WLB 216 AlderCOASTAL BUOY TENDER(WLM)175-FOOT> WLM 551 Ida Lewis> WLM 552 Katherine Walker> WLM 553 Abbie Burgess> WLM 554 Marcus Hanna> WLM 555 James Rankin> WLM 556 Joshua Applebey> WLM 557 Frank Drew> WLM 558 Anthony Petit> WLM 559 Barbara Mabrity> WLM 560 William Tate> WLM 561 Harry Clairborne> WLM 562 Maria Bray> WLM 563 Henry Blake> WLM 564 George CobbINLAND CONSTRUCTIONTENDERS (WLIC)160-FOOT> WLIC 800 Pamlico> WLIC 801 Hudson> WLIC 802 Kennebec> WLIC 803 Saginaw100-FOOT> WLIC 315 SmilaxPATROL CUTTERS (WPC)154-FOOT-SENTINEL CLASS> WPC 1101 Bernard C Webber> WPC 1102 Richard Etheridge> WPC 1103 William Flores> WPC 1104 Robert Yered> WPC 1105 Margaret Norvell> WPC 1106 Paul Clark> WPC 1107 Charles David Jr> WPC 1108 Charles Sexton> WPC 1109 Kathleen Moore> WPC 1110 Raymond Evans> WPC 1111 William Trump> WPC 1112 Issac Mayo> WPC 1113 Richard Dixon> WPC 1114 Heriberto Hernandez> WPC 1115 Joseph Napier> WPC 1116 Winslow W Griesser> WPC 1117 Donald Horsley> WPC 1118 Joseph Tezanos> WPC 1119 Rollin A Fritch> WPC 1120 Lawrence O Lawson> WPC 1121 John F McCormick> WPC 1122 Bailey T Barco> WPC 1123 Benjamin B Dailey> WPC 1124 Oliver F Berry> WPC 1125 Jacob L.A. Poroo> WPC 1126 Joseph Gercezak> WPC 1127 Richard T Snyder> WPC 1128 Nathan Bruckenthal> WPC 1129 Forrest O Rednour> WPC 1130 Robert G Ward> WPC 1131 Terrell Horne III> WPC 1132 Benjamin A Bottoms> WPC 1133 Joseph O Doyle> WPC 1134 William C Hart> WPC 1135 Angela McShan> WPC 1136 Daniel Tarr> WPC 1137 Edgar Culbertson> WPC 1138 Harold Miller> WPC 1139 Myrtle Hazard> WPC 1140 Oliver Henry> WPC 1141 Charles Moulthrop> WPC 1142 Robert Goldman*> WPC 1143 Frederick Hatch*> WPC 1144 Glenn Harris*> WPC 1145 Emlen Tunnell*> WPC 1146 John Scheuerman*> WPC 1147 Clarence Sutphin*> WPC 1148 Pablo Valent*> WPC 1149 Douglas Denman*> WPC 1150 William Chadwick*> WPC 1151 Warren Deyampert*> WPC 1152 Maurice Jester*> WPC 1153 John Patterson*> WPC 1154 William Sparling*> WPC 1155 Melvin Bell*> WPC 1156 David Duren*> WPC 1157 Florence Finch**> WPC 1158 John Witherspoon**> WPC 1159 Earl Cunningham**> WPC 1160 Frederick Mann**COAST GUARD CUTTERSUse of DoD visual information does not imply or constituent DoD endorsement.ICEBREAKING TUG (WTGB)140-FOOT> WTGB 101 Katmai Bay> WTGB 102 Bristol Bay> WTGB 103 Mobile Bay> WTGB 104 Biscayne Bay> WTGB 105 Neah Bay> WTGB 106 Morro Bay> WTGB 107 Penobscot Bay > WTGB 108 Thunder Bay> WTGB 109 Sturgeon Bay PATROL BOAT (WPB) 110-FOOT> WPB 1304 Maui> WPB 1307 Ocracoke> WPB 1309 Aquidneck> WPB 1310 Mustang> WPB 1311 Naushon> WPB 1312 Sanibel> WPB 1313 Edisto> WPB 1318 Baranof> WPB 1319 Chandeleur> WPB 1322 Cuttyhunk> WPB 1324 Key Largo> WPB 1326 Monomoy> WPB 1327 Orcas> WPB 1329 Sitkinak> WPB 1330 Tybee> WPB 1331 Washington> WPB 1332 Wrangell> WPB 1333 Adak> WPB 1334 Liberty> WPB 1335 Anacapa> WPB 1336 Kiska> WPB 1349 Galveston Island INLAND BUOY TENDERS (WLI)100-FOOT> WLI 313 Bluebell> WLI 642 Buckthorn COASTAL PATROLBOATS (WPB)87-FOOT - MARINEPROTECTOR CLASS> WPB 87301 Barracuda> WPB 87302 Hammerhead> WPB 87303 Mako> WPB 87304 Marlin> WPB 87305 Stingray> WPB 87306 Dorado> WPB 87307 Osprey> WPB 87308 Chinook> WPB 87309 Albacore> WPB 87310 Tarpon> WPB 87311 Cobia> WPB 87312 Hawksbill> WPB 87313 Cormorant> WPB 87314 Finback> WPB 87315 Amberjack> WPB 87316 Kittiwake> WPB 87317 Blackfin> WPB 87318 Bluefin> WPB 87319 Yellowfin> WPB 87320 Manta> WPB 87321 Coho> WPB 87322 Kingfisher> WPB 87323 Seahawk> WPB 87324 Steelhead> WPB 87325 Beluga> WPB 87326 Blacktip> WPB 87327 Pelican> WPB 87328 Ridley> WPB 87329 Cochito> WPB 87330 Manowar> WPB 87331 Moray> WPB 87332 Razorbill> WPB 87333 Adelie> WPB 87334 Gannet> WPB 87335 Narwhal> WPB 87336 Sturgeon> WPB 87337 Sockeye> WPB 87338 Ibis> WPB 87339 Pompano> WPB 87340 Halibut> WPB 87341 Bonito> WPB 87342 Shrike> WPB 87343 Tern> WPB 87344 Heron> WPB 87345 Wahoo> WPB 87346 Flyingfish> WPB 87347 Haddock> WPB 87348 Brant> WPB 87349 Shearwater> WPB 87350 Petrel> WPB 87352 Sea Lion> WPB 87353 Skipjack> WPB 87354 Dolphin> WPB 87355 Hawk> WPB 87356 Sailfish> WPB 87357 Sawfish> WPB 87358 Swordfish> WPB 87359 Tiger Shark> WPB 87360 Blue Shark> WPB 87361 Sea Horse> WPB 87362 Sea Otter> WPB 87363 Manatee> WPB 87364 Ahi> WPB 87365 Pike> WPB 87366 Terrapin> WPB 87367 Sea Dragon> WPB 87368 Sea Devil> WPB 87369 Crocodile> WPB 87370 Diamondback> WPB 87371 Reef Shark> WPB 87372 Alligator> WPB 87373 Sea Dog> WPB 87374 Sea FoxARMY SHIPSLOGISTICS SUPPORT VESSEL– LSV 1 CLASS> LSV 1 GEN Frank S. Besson, Jr.> LSV2 CW3 Harold C. Clinger> LSV 3 GEN Brehon B.Sommervell> LSV 4 LTG William B. Bunker> LSV 5 MG Charles P. Gross> LSV 6 SP/ 4 James A. Loux> LSV 7 SSGT Robert T. Kuroda> LSV 8 MG Robert SmallsLANDING CRAFT UTILITY –LCU 2000 CLASS> LCU 2001 Runnymede> LCU 2002 Kennesaw Mountain> LCU 2003 Macon> LCU 2004 Aldie> LCU 2005 Brandy Station> LCU 2006 Bristoe Station> LCU 2007 Broad Run> LCU 2008 Buena Vista> LCU 2009 Calaboza> LCU 2010 Cedar Run> LCU 2011 Chickahominy> LCU 2012 Chickasaw Bayou> LCU 2013 Churubusco> LCU 2014 Coamo> LCU 2015 Contreras> LCU 2016 Corinth> LCU 2017 El Caney> LCU 2018 Five Forks> LCU 2019 Fort Donelson> LCU 2020 Fort McHenry> LCU 2021 Great Bridge> LCU 2022 Harpers Ferry> LCU 2023 Hobkirk> LCU 2024 Hormigueros> LCU 2025 Malvern Hill> LCU 2026 Matamoros> LCU 2027 Mechanicsville> LCU 2028 Missionary Ridge> LCU 2029 Molino Del Ray> LCU 2030 Monterrey> LCU 2031 New Orleans> LCU 2032 Palo Alto> LCU 2033 Paulus Hook> LCU 2034 Perryville> LCU 2035 Port HudsonMANEUVER SUPPORT VESSEL(LIGHT) – MSV(L) CLASS> MSV(L) 1 SSG Elroy F. Wells*COAST GUARD CUTTERSARMY SHIPSUse of DoD visual information does not imply or constituent DoD endorsement.AUXILIARY SHIPS SPEARHEAD CLASS JHSV > T-EPF1 Spearhead> T-EPF 2 Choctaw County> T-EPF 3 Millinocket> T-EPF 4 Fall River> T-EPF 5 Trenton> T-EPF 6 Brunswick> T-EPF 7 Carson City> T-EPF 8 Yuma> T-EPF 9 City Of Bismarck> T-EPF 10 Burlington> EPF 11 Puerto Rico> EPF 12 Newport> EPF 13 Apalachicola**> EPF 14 Cody**DRY CARGO/ AMMUNITION (T-AKE)> T-AKE 1 Lewis And Clark> T-AKE 2 Sacagawea> T-AKE 3 Alan Shepard> T-AKE 4 Richard E Byrd> T-AKE 5 Robert E Peary> T-AKE 6 Amelia Earhart> T-AKE 7 Carl Brashear> T-AKE 8 Wally Schirra> T-AKE 9 Matthew C Perry> T-AKE 10 Charles Drew> T-AKE 11 WashingtonChambers> T-AKE 12 William McLean> T-AKE 13 Medgar Evers> T-AKE 14 Cesar Chavez FAST COMBAT SUPPORT (T-AOE)> T-AOE 6 Supply> T-AOE 8 ArcticFLEET REPLENISHMENT OILERS (T-AO)> T-AO 187 Henry J Kaiser> T-AO 188 Joshua Humphreys > T-AO 189 John Lenthall > T-AO 193 Walter S Diehl> T-AO 194 John Ericsson> T-AO 195 Leroy Grumman> T-AO 196 Kanawha> T-AO 197 Pecos> T-AO 198 Big Horn> T-AO 199 Tippecanoe> T-AO 200 Guadalupe> T-AO 201 Patuxent> T-AO 202 Yukon> T-AO 203 Laramie> T-AO 204 Rappahannock> T-AO 205 John Lewis*> T-AO 206 Harvey Milk*> T-AO 207 Earl Warren**> T-AO 208 Robert F Kennedy**> T-AO 209 Lucy Stone**> T-AO 210 Sojourner Truth**PREPOSITIONINGSHIPSFLEET OCEAN TUGS (T-ATF)> T-ATF 168 Catawba> T-ATF 171 Sioux> T-ATF 172 ApacheHOSPITAL (T-AH)> T-AH 19 Mercy> T-AH 20 ComfortRESCUE AND SALVAGE(T-ARS)> T-ARS 51 Grasp> T-ARS 52 SalvorSGT MATEJ KOCAK CLASS> T-AK 3005 Sgt Matej Kocak> T-AK 3006 Pfc Eugene A Obregon> T-AK 3007 Maj Stephen W PlessAVIATION LOGISTICSSUPPORT (T-AVB)> T-AVB 3 Wright> T-AVB 4 CurtissMARINE CORPS CONTAINERAND RO/RO (T-AK) 2ND LTJOHN P BOBO CLASS> T-AK 3008 2nd Lt John P Bobo> T-AK 3009 Pfc Dewayne TWilliams> T-AK 3010 1st Lt BaldomeroLopez> T-AK 3011 1st Lt Jack Lummus> T-AK 3012 Sgt William R ButtonLT HARRY L. MARTIN CLASS> T-AK 3015 1st Lt Harry L Martin> T-AK 3016 LCPL Roy M Wheat> T-AK 3017 GySgt Fred WStockhamVEHICLE CARGO SHIP> T-AKR 10 Cape Island> T-AKR 11 Cape Intrepid> T-AKR 112 Cape Texas> T-AKR 113 Cape TaylorLARGE, MEDIUM-SPEED,RO/RO (T-AKR)> T-AKR 310 Watson> T-AKR 311 Sisler> T-AKR 312 Dahl> T-AKR 313 Red Cloud> T-AKR 314 Charlton> T-AKR 315 Watkins> T-AKR 316 Pomeroy> T-AKR 317 SodermanOPDS (T-AG)> T-AG 5001 Vadm K R WheelerAIR FORCE CONTAINER(T-AK)> T-AK 4396 Maj Bernard F FisherARMY CONTAINER (T-AK)> T-AK 4543 Ltc John U D Page> T-AK 4544 SSG Edward A Carter JrMODULAR CARGO (T-AK)> T-AK 5029 Cape Jacob> AK 5070 Cape Flattery> AK 4073 Cape FarewellHIGH SPEED VESSEL (HSV)> HSV 2 Swift> HSV 4676 Westpac ExpressMISSILE RANGEINSTRUMENTATION (T-AGM)> T-AGM 24 Invincible> T-AGM 25 Howard O LorenzenSPECIAL MISSION &SEALIFT SHIPSOCEAN SURVEILLANCE(T-AGOS)> T-AGOS 19 Victorious> T-AGOS 20 Able> T-AGOS 21 Effective> T-AGOS 22 Loyal> T-AGOS 23 ImpeccableSUBMARINE AND SPECIALWARFARE SUPPORT> MV C-Commando> MV C-Champion> MV Malama> MV Dolores Chouest> MV Hos DominatorSUBMARINE ESCORT SHIP> T-AGSE 1 Black Powder> T-AGSE 2 Westwind> T-AGSE 3 Eagleview> T-AGSE 4 ArrowheadMILITARY SEALIFT COMMANDUse of DoD visual information does not imply or constituent DoD endorsement.MILITARY SEALIFT COMMAND* Under Construction / ** Authorized for ConstructionOCEANOGRAPHIC SURVEY (T-AGS)> T-AGS 60 Pathfinder > T-AGS 62 Bowditch > T-AGS 63 Henson> T-AGS 64 Bruce C Heezen > T-AGS 65 Mary Sears > T-AGS 66MauryCABLE LAYING /REPAIR (T-ARC)> T-ARC 7ZeusNAVIGATION TEST SUPPORT (T-AGS)> T-AGS 45WatersSUBMARINE TENDER (AS)> AS 39 Emory S Land > AS 40Frank CableTANKERS (T-AOT)> T-AOT 1125Lawrence H GianellaDRY CARGO (T-AK)> T-AK 4729 American Tern > T-AK 9205VirginianLARGE, MEDIUM-SPEED RO/RO (T-AKR)> T-AKR 295 Shughart > T-AKR 296 Gordon > T-AKR 297 Yano > T-AKR 298 Gilliland > T-AKR 300 Bob Hope > T-AKR 301 Fisher > T-AKR 302 Seay> T-AKR 303 Mendonca > T-AKR 304Pililaau> T-AKR 305 Brittin > T-AKR 306 BenavidezEXPEDITIONARY TRANSFER DOCK (ESD)> T-ESD 1 Montford Point > T-ESD 2John GlennEXPEDITIONARY SEA BASE (ESB)> T-ESB 3 Lewis B Puller> T-ESB 4 Hershel “Woody” Williams > T-ESB 5 Miguel Keith*> T-ESB 6 (Unnamed)*> T-ESB 7(Unnamed)**L3Harris' solutions address customers' critical missions across air, land, sea, space and cyber domains. We empower people who serve from ocean to orbit and everywhere in between.As a full-spectrum systems integrator and network provider, L3Harris is among the world's leading integrators of C5ISR systems for customers around the globe. Our expertise delivers complete turnkey integration of whole-ship electrical, mechanical and electronic systems; powermanagement and distribution; undersea warfare systems; unmanned and autonomous surface and underwater vehicles; and airborne systems for maritime patrol and surveillance that enable secure, agile worldwide interoperability.In a world of ever-accelerating change, threat environments move fast. We move forward faster by delivering systems integrated solutions and。
UNIVERSAL APPLICA TION AND BENEFITS OF AIR CONT AINMENT: A PRACTICAL GUIDEA Dell™ Technical White PaperDavid L. MossDell|Data Center InfrastructureTHIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND.© 2009 Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell.Dell and the DELL logo are trademarks of Dell Inc. Liebert is a trademark of Liebert Corporation. APC is a registered trademark of American Power Conversion.Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.Table of ContentsIntroduction (2)Nomenclature (3)Greenfield vs. Brownfield (4)Supply vs. Return (4)Materials and Flexibility (5)Tightly Coupled vs. Loosely Coupled Containment (5)More on Rack Level Containment (6)Non Hot/Cold Aisle Facilities (8)Summary (8)To operate more efficiently and at higher densities with the ability to predictably deploy IT hardware with less thermal risk, implement containment. Embrace containment aggressively; the approach to containment is a bit like the approach to virtualization. If you experiment with it lightly, you might only see minor benefits like rack density increases. Like virtualization, it takes a strong commitment. You need to contain most, if not all, of the data center in order to tap into large efficiency benefits. Both Liebert™ and APC® have good papers 1,2•An increase in coil capacity accompanying the higher return temperatures associated with containment on containment. Although they do show some bias for their own solutions, they agree on major benefits such as:•Near or absolute 100% sensible operation (no energy lost to condensation and humidification) • The opportunity to raise temperatures and save energy in the chilling processIn addition to these benefits, it should also be mentioned that the elimination of hot spots would result in theimmediate lowering of IT equipment fan power in the affected areas. For a more detailed example of containment-related energy savings, please refer to The Energy Advantages of Containment Systems 3The goal of this paper is not to come to an absolute conclusion as to which solution is the best. What is ideal for one facility will not be ideal for another. However, this paper will point out some of the key considerations to explore in determining the best solution for your facility. The following points are addressed in this paper:Dell whitepaper.•Greenfield vs. Brownfield? •Supply (intake) vs. return (exhaust) containment •Materials and flexibility •Rack level vs. row level containment •Closely coupled vs. loosely coupled1 Focused Cooling Using Cold Aisle Containment, Emerson Network Power, 2009; /common/ViewDocument.aspx?id=12952 Hot Aisle vs. Cold Aisle Containment, John Neimann, 2008; /salestools/DBOY-7EDLE8_R0_EN.pdf3 The Energy Advantages of Containment Systems; David Moss; 2009; /us/en/corp/d/business~solutions~whitepapers~en/Documents~dci-energy-advantages-of-containment-systems.pdf.aspxFor the purposes of this paper, we will attempt to categorize and name different types of containment. StationaryAisle containment like the APC Hot Aisle Containment (HAC) or Liebert Cold Aisle Containment (CAC) is a hard-paneled structure assembled in place that contains integral attachment points to the IT racks. These solutionscontain multiple racks. APC’s solution is designed specifically around their InRow coils,and it contains the hot aisle. Liebert’s solution contains the cold aisle and can bedesigned to contain raised-floor venting and Liebert XD systems. In each solution,hard-paneled construction includes doors and a ceiling structure. This type ofcontainment is typically more stationary and requires more effort to refresh new racksor additional cooling units in comparison to other solutions that are not as integrated. Hanging PartitionsHanging partitions are often referred to as meat locker curtains. Vendorsof these products have both hard and flexible material versions. They aretypically hung from ceiling structures and lightly touch the racks (if theytouch at all). They often are intentionally hung with gaps at the ceiling toallow smoke to pass horizontally and activate fire prevention systems aswell as the fuse links used to hang the partitions themselves. Since thepartitions are not tied to the IT racks, it is generally easier to refreshindividual racks. The containment is looser than with stationary solutions. This picture in one of Dell’s data centers depicts cold aisle containment with both floor and overhead delivery. Hanging partitions can also be used effectively as hot aisle containment.Rack ChimneysRack Chimney solutions add ductwork to each rack. With the rear of the rack closed up, this rack istightly coupled to the IT systems. The chimney is typically extended to a false ceiling which is usedas a return plenum and also ducted to the CRAC units. Unless the chimney contains fans or theCRAC units pull air through the return plenum to aid the flow through the rack, the rack andchimney add pressure to the IT systems. This either slows the flow rate through the systems orcauses them to speed up to maintain proper airflow. There is some debate in the industry as towhether chimneys should be deployed with serial fan units that help the IT fans to evacuate therack.If you have the luxury of a Greenfield opportunity, your options are obviously less limited. Some containment solutions are less invasive in the installation process. Since hanging partitions are not structurally tied to the racks, they tend to be an easier solution to use in a retrofit situation. As a retrofit, a chimney may require serverdowntime, especially for servers located high in the rack. Stationary solutions require attachment to existing racks and possibly drilling holes; this might make some owners uncomfortable. Even if you prefer a more substantial containment system like a stationary HAC or CAC, you might consider the hanging partition products for the retrofit portion of the data center and use your preferred choice for all new racks. The partition products areinexpensive and might be eventually switched out with your preferred choice as IT product is refreshed. Whatever solution you choose, your goal should be to get the entire data center contained so you can reap full efficiency benefits.Supply vs. ReturnHVAC vendors often have strong opinions that favor their own products, and suggest sharp contrasting density limitations specifically for cold aisle containment. However, both Cold Aisle Containment (CAC) and Hot AisleContainment (HAC) can be set up for high density. Hot aisle may offer more flexibility to apportion more density in one area at the detriment of another. In either case, the goal is to provide an adequate compliment to the air consumption rate of the IT equipment. It is the volumetric delivery of the facility that establishes any densitylimitation that might exist for each rack. This is why hot aisle containment may offer a local advantage. With a cold aisle solution there is a finite number of vent tiles. Since the aisle containment captures the vent tiles, the number of vents cannot be increased; it is typically no more than a single vent per rack. In contrast, a hot aisle containment solution does not capture the vents. Venting outside the perimeter of the pod can actually supply the pod with additional airflow.APC makes a similar argument regarding the limitations of cold aisle delivery 4,5Consider this high-density example computed using Dell’s Energy Smart Solutions Advisor(. The APC papers go one step further; they make assumptions about typical raised floor limitations, arguing that a maximum of approximately 600 CFM on average can be delivered through a single vent. APC equates this to a limitation of 6 kW per cabinet which takes their argument past the differences between HACs and CACs, resulting in an argument between raised floor delivery and their InRow products. It can be argued that this as an artificial limitation used to support the claim of superiority of the row cooling product. Higher CRAC-to-vent ratios allow a raised floor to easily achieve higher flow rates. A data center lab at one of the Dell facilities averages twice that value (1200 CFM) per vent. The APC argument of 100 CFM per kW is a good rule of thumb for generic legacy hardware. Today’s Dell servers,however, have much more efficient thermal designs and typically operate closer to 80 CFM per kW. If you combine higher vent flow rates with the fact that newer IT consumes less than 100 CFM per kW, an argument similar in approach to that in the aforementioned APC paper can be made in support of greater than 10 kW per rack. /calc ). A 1U server with high-end processors and 32 GB of memory consumes 324 watts and uses 25.6 CFM, which amounts to just 79 CFM per kW. Assuming 80 CFM per kW and an average of 1200 CFM per vent, the raised floor would support 15 kW per vent if that flow rate is delivered effectively to the rack.Containment is one way to ensure that the 1200 CFM supplied gets consumed effectively to achieve the full 15 kW.4 Hot Aisle vs. Cold Aisle Containment, John Neimann, 2008; /salestools/DBOY-7EDLE8_R0_EN.pdf5 Cooling Strategies for Ultra-High Density Racks and Blade Servers, Neil Rasmussen, 2006; /salestools/SADE-5TNRK6_R5_EN.pdfperceived density advantage. Ultimately, the data center is limited by the total amount of flow available from all the CRAC units. If a hot aisle containment enables an incremental advantage in one area because it can take advantage of adjacent vents outside of the perimeter of the pod, it uses up more of the aggregate CRAC flow rate, and other areas will be slighted. The HAC/CAC decision is more likely based on whether or not the facility already has a return ceiling plenum. It might also just be made on the basis of human comfort, since a HAC renders the personnel space comfortable in terms of temperature, and a CAC essentially uses the entire data center as a return plenum.Materials and FlexibilityAesthetics are important to many data center owners. Some may not have considered hanging partitions for that reason. These systems are gaining in popularity quickly, and their appearance is not as terrible as some people may think. Hard plastic versions are available; they are a bit more expensive than the meat-locker type material, but they are generally perceived as more attractive. Besides their cost advantage over other containment products, some Dell customers find more flexibility with this type of product. The stationary aisle containments typically tie the racks into a pod. Any reconfiguration that entails breaking up the pod will be easier with a hanging partition solution. Hanging partitions are readily available from a variety of vendors, and you can engage Dell Energy Optimization Services for assistance as they can install these types of products for you. Hanging partitions work well as either hot or cold aisle containment. Interestingly, in talking to the vendors of these products, the majority of their deployments have been cold aisle containment. Presumably, this is due to the absence of an existing ceiling return plenum. An additional consideration when contemplating flexible curtains is that, depending upon the criticality of the data center, the data center’s insurance company may have reservations about the flexible material. Even if a fire marshal has signed off on the product, the insurance company may be more conservative and oppose the flexible curtain material.Tightly Coupled vs. Loosely Coupled ContainmentThere are varying degrees of coupling between coil products and IT racks. The minimum goal behind containment is to separate supply and return paths. Above and beyond this minimum goal is an opportunity to more closely match coil flow rates to rack consumption (minimizing waste). The ability to achieve a flow match is proportional to the physical tightness of the coupling between the racks and coils.Hanging Partitions Stationary Rack LevelGreatest Air Over-Provision Least Air Over-ProvisionWith looser coupling, more air overage is required from the coils. Hanging partitions are arguably the loosest since they typically have designed gaps (for example, at the ceiling). The exhaust chimney appears to be the tightest common form of containment. Stationary containment systems range in between the two. Because aisle containment spans many racks, it is quite difficult to make it as “airtight” as a rack chimney. Gaps in the construction, under or between racks, are likely to exist. Any mismatch in flow rate between the coils and the racks will find these leaks. Stationary systems probably require more over-provision of air from the coils than a tightly coupled chimney but not as much as with hanging partitions.of external pressure added to a server, storage, or networking product elicits one of two responses―t he airflow slows and component temperatures climb, or the IT fans respond with additional fan energy to boost the flow rate back to its intended design point. What is meant by external pressure? A small amount of external pressure is added, for instance, when IT is put into a standard front-to-rear cooled rack and the front and rear perforated doors are closed. As a result, some negative pressure is applied to the front of the IT system and some positive pressure to the back of the system. Similarly, contained systems, like rack chimneys or door coils, typically impart two to three times the external pressure as a standard “flow through” rack due to their added airflow resistance. The IT system’s thermal design will determine whether or not its response to pressure is an increase in component temperature, an increase in fan power, or some compromise of the two. Newer systems will likely tend toward a fan speed increase. They have more components enabled with temperature sensors that contribute to the system’s fan response algorithms. If the system design is optimized, it will respond to even small pressure changes that would otherwise have resulted in a component temperature increase. Older IT systems have less discrete component temperature measurement capability and are typically designed more conservatively with higher thermal margins. They typically respond with less of a fan speed increase unless the pressure is large. The IT manufacturer should be able to advise you as to the impact of pressure on his or her system. Dell has historically designed with enough margin to handle the pressure added by a standard rack (two perforated doors) and a full cable management apparatus (translating arm).Therefore, even if the fans do not spin up due to pressure, minor component temperature increases do not exceed specification limits. More details of how Dell systems respond to external pressure can be found in the IT Equipment Response to External Pressure Dell whitepaper6.More on Rack Level ContainmentChimney systems are not the only form of rack containment, although they are probably the most widely used. Enclosed racks with side-car coils also could be considered contained solutions since they separate the hot from the cold. Rear door coils are another product which could technically be considered contained. Any of these systems may have impacts on the IT fan response as mentioned in the paragraphs above.Passive Chimney SystemsCare should be used when deploying passive chimney systems. A good design should impart little to no external pressure on the IT systems within the racks. While in some cases the air handlers may facilitate the flow through the racks and chimneys by creating a significant negative pressure in the ceiling return, a test should always be carried out to determine the presence of negative pressure in the chimneys and rack rears. If the air handlers do not improve the flow through the chimney, an increase of IT fan energy may occur. In addition, you may risk a pressure build-up at the back of the rack because the IT equipment is pushing the air up the chimney, which will cause a larger recirculation between the IT systems. This may not be a concern with larger systems such as blades where there are only a few chassis per rack. However, the 20 to 40 small gaps between 1 and 2U systems can add up. Increased recirculation could raise inlet temperatures and limit the extent to which you raise the overall data center temperature, thus limiting savings at the chiller.New Dell Rack ContainmentDell is currently working on another form of containment―a rack-level containment product that alters the normal front-to-rear flow pattern and converts it to bottom-to-rear. The strategy is scheduled for release late next year. Like other containment solutions, it enables similar energy savings opportunities. It will be a tightly coupled6 IT Equipment Response to External Pressure, Robert Curtis/David Moss, 2009to the floor and not the ceiling, it is more of a plug-and-play solution than most other containment solutions. The rack can be rolled up with no connections other than the vent underneath. Since that coupling surrounds the vent, it has the ability to affect the flow exiting the vent. Up to a certain rack density, the floor tends to dominate and actually aid the IT system’s flow rate; it may lower the IT fan energy as the IT systems try to throttle down flow rates. Above that density, the IT systems in the rack tend to dominate, extracting a greater volume than normal out of the floor. There is no specific density limit with this rack. High densities mean higher airflow which typically translates into increased IT equipment fan energy. This energy increase is in line with the increases cited for other rack solutions in IT Equipment Response to External Pressure7. A slight increase in IT fan energy may be acceptable. in order to achieve facility energy savings like those detailed in The Energy Advantages of Containment Systems8 There are further advantages to this rack level containment strategy. Due to the tight coupling with the floor, the rack has the ability to affect the pressure under the floor. In the case where multiple racks have spun up and increased their air consumption, a constantly supplied raised floor would normally see a decrease in under-floor pressure and a drop in the flow rate through other vents. Air handlers (CRAH units) can be configured to adjust their flow rates based on under-floor pressure. Rather than link airflow control with return or supply temperature (as is more common), variable speed fans in the air handlers speed up or slow down to maintain a specific pressure under the floor. This control strategy typically allows data centers to deploy new hardware with less concern about the adequacy of airflow delivery. As new racks are added, vents are installed as well. The increase in the number of vents would normally drop the pressure and the flow through all vents. The CRAH units, however, compensate to correct the pressure. As long as the CRAH unit flow rates are not at their maximum, the addition of new IT racks is accompanied by an increase in the CRAH unit flow rates.Similarly, as IT equipment dynamically drives rack flow rates up or down, a tightly coupled rack like the Dell containment rack could have a dynamic coupling to the CRAH units. This would be accomplished indirectly through their common pressure connection, the raised floor. Others companies have attempted to achieve similar results by much more complicated means (for example, a competitor introduced a dynamic service with a multitude of sensors feeding into a server to control the floor’s CRAH units).With the Dell solution, a company can have a data center set up such that whenever new racks are added, the CRAH units adjust their flow rates to compensate. Throughout the day, when the IT load changes and the rack airflow fluctuates up and down, the CRAH units also adjust up and down, supplying a near ideal match of air delivery versus rack consumption. The only task the company has is to monitor the Variable Frequency Drive (VFD) settings on the CRAH units to verify how close they are getting to 100%. At some point prior to the unit nearing 100%, another CRAH unit would have been scheduled for bulk airflow infusion into the floor. This situation is comparable to a type of “air buss” where multiple air handlers feed a common buss (the floor plenum) and multiple racks tap into and consume what they need from that buss. In addition to the energy and density advantages obtained with containment solutions, this dynamic coupling with the air handlers specific to the Dell containment rack offers a significant advantage.7 IT Equipment Response to External Pressure, Robert Curtis/David Moss, 20098 The Energy Advantages of Containment Systems; David Moss; 2009;/us/en/corp/d/business~solutions~whitepapers~en/Documents~dci-energy-advantages-of-containment-systems.pdf.aspxNon Hot/Cold Aisle FacilitiesThere are still plenty of facilities that have not converted to hot/cold aisle orientation. Aisle containment strategies rely on the fact that there is already hot/cold aisle orientation. Some of the rack level containment strategies actually do not require hot/cold aisle orientation. Chimneys, self-contained racks, the door coil, and Dell’s new rack containment would all work in a front-to-back oriented facility.SummaryRegardless of the type, containment solutions should be considered in almost any data center setting. The two major areas for reductions in cooling energy are at the chiller and air handler fans. Both of these energy reductions are aided by containment. Containment should be applied to as much of the data center as possible. With the main goal being an increase in overall data center temperature, it may be difficult to achieve without comprehensive containment. Rack densities are also improved with containment. Rack and associated costs are reduced by installing equipment in fewer racks. Finally, some tighter forms of containment, such as the new Dell rack, offer additional benefits in terms of coupling with facility airflow systems to set up a near ideal match of airflow and one that scales with IT load and IT additions..。
Barrier GateUser ManualLegal Information©2022 Hangzhou Hikvision Digital Technology Co., Ltd. All rights reserved.About this ManualThe Manual includes instructions for using and managing the Product. Pictures, charts, images and all other information hereinafter are for description and explanation only. The information contained in the Manual is subject to change, without notice, due to firmware updates or other reasons. Please find the latest version of this Manual at the Hikvision website ( https:/// ).Please use this Manual with the guidance and assistance of professionals trained in supporting the Product.Trademarksand other Hikvision's trademarks and logos are the properties of Hikvision in various jurisdictions.Other trademarks and logos mentioned are the properties of their respective owners. DisclaimerTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THIS MANUAL AND THE PRODUCT DESCRIBED, WITH ITS HARDWARE, SOFTWARE AND FIRMWARE, ARE PROVIDED "AS IS" AND "WITH ALL FAULTS AND ERRORS". HIKVISION MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, MERCHANTABILITY, SATISFACTORY QUALITY, OR FITNESS FOR A PARTICULAR PURPOSE. THE USE OF THE PRODUCT BY YOU IS AT YOUR OWN RISK. IN NO EVENT WILL HIKVISION BE LIABLE TO YOU FOR ANY SPECIAL, CONSEQUENTIAL, INCIDENTAL, OR INDIRECT DAMAGES, INCLUDING, AMONG OTHERS, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF DATA, CORRUPTION OF SYSTEMS, OR LOSS OF DOCUMENTATION, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY, OR OTHERWISE, IN CONNECTION WITH THE USE OF THE PRODUCT, EVEN IF HIKVISION HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR LOSS.YOU ACKNOWLEDGE THAT THE NATURE OF THE INTERNET PROVIDES FOR INHERENT SECURITY RISKS, AND HIKVISION SHALL NOT TAKE ANY RESPONSIBILITIES FOR ABNORMAL OPERATION, PRIVACY LEAKAGE OR OTHER DAMAGES RESULTING FROM CYBER-ATTACK, HACKER ATTACK, VIRUS INFECTION, OR OTHER INTERNET SECURITY RISKS; HOWEVER, HIKVISION WILL PROVIDE TIMELY TECHNICAL SUPPORT IF REQUIRED.YOU AGREE TO USE THIS PRODUCT IN COMPLIANCE WITH ALL APPLICABLE LAWS, AND YOU ARE SOLELY RESPONSIBLE FOR ENSURING THAT YOUR USE CONFORMS TO THE APPLICABLE LAW. ESPECIALLY, YOU ARE RESPONSIBLE, FOR USING THIS PRODUCT IN A MANNER THAT DOES NOT INFRINGE ON THE RIGHTS OF THIRD PARTIES, INCLUDING WITHOUT LIMITATION, RIGHTS OF PUBLICITY, INTELLECTUAL PROPERTY RIGHTS, OR DATA PROTECTION AND OTHER PRIVACY RIGHTS. YOU SHALL NOT USE THIS PRODUCT FOR ANY PROHIBITED END-USES, INCLUDING THEDEVELOPMENT OR PRODUCTION OF WEAPONS OF MASS DESTRUCTION, THE DEVELOPMENT OR PRODUCTION OF CHEMICAL OR BIOLOGICAL WEAPONS, ANY ACTIVITIES IN THE CONTEXT RELATED TO ANY NUCLEAR EXPLOSIVE OR UNSAFE NUCLEAR FUEL-CYCLE, OR IN SUPPORT OF HUMAN RIGHTS ABUSES.IN THE EVENT OF ANY CONFLICTS BETWEEN THIS MANUAL AND THE APPLICABLE LAW, THE LATTER PREVAILS.Symbol Conventions The symbols that may be found in this document are defined as follows.ContentsChapter 1 Introduction (1)1.1 Product Introduction (1)1.2 Key Feature (1)Chapter 2 Installation (2)2.1 Installation Environment (2)2.2 Install Barrier Gate (2)2.2.1 Fix Barrier Gate Host (2)2.2.2 Install Boom Pole (4)2.3 Wiring (5)2.3.1 Connect to Peripheral Devices (5)2.3.2 Connect to Power Supply (7)Chapter 3 Debug (9)3.1 Remote Control (9)3.2 Button Operation (9)Chapter 4 Maintenance (13)4.1 Check Regularly (13)4.2 Check After Collision (13)4.3 Fault Code Description (13)4.4 Troubleshooting for Failed Auto Rising/Falling of Boom Pole After Power Cutoff (15)Appendix A. Peripheral Device Interfaces Introduction (16)Chapter 1 Introduction1.1 Product IntroductionBarrier gate is the entrance and exit management device to limit motor vehicle passing. It can control the boom pole automatically via parking lot management system. Or you can control the boom pole via buttons on remote controller.Barrier gate is widely applicable to toll station, parking lot, the entrance and exit of community and unit, etc. Its working temperature ranges from -30 °C to 70 °C (-22 °F to 158 °F).1.2 Key Feature●Adopts direct current brushless motor which can run steadily, applicable to entrance and exit, ETC system, etc.●The boom pole can rise rapidly and fall slowly. The barrier gate can learn the rising and falling limit positions automatically after it is powered on.●Over-voltage and over-current protection to prevent the motor from being burnt caused by locked rotor during running.●Supports anti-fall function via inductive loop, IR, etc., and protection functions including pressure wave, resistance rebound, etc.●Adjustable boom pole direction from left to right or from right to left.Chapter 2 Installation2.1 Installation EnvironmentThe installation environment of the barrier gate should meet the following requirements.●The installation space should be large enough to guarantee the boom pole can rise or fall normally.●Install the barrier gate on horizontal ground.●Installation surface requirements:○If no base is installed, the installation surface must be firm enough to fix the host to guarantee the barrier gate can run stably.○If base is needed, it is recommended to install the base with quick setting cement. The base should be horizontal. The height should be larger than 300 mm. The length and width of base should be larger than those of the actual barrier gate installation surface. Bury the set bolts prepared by yourself before installation.●If the barrier gate is anti-collision, the boom pole will flick 90° in reverse direction if it is impacted. Make sure there is no obstacle in the range.●Bury the cables before installation. The conduit should be 50 mm higher than the ground to avoid the gathered water on the ground to enter into the cable and cause short circuit.2.2 Install Barrier Gate2.2.1 Fix Barrier Gate HostFollow the steps below to fix the host of barrier gate.Steps1.Mark the positions of holes on the refuge island as shown below. The hole depth is approx. 120 mm.Figure 2-1 Mark Positions of HolesThe suggestions for positions of holes:●The holes in vertical direction should be near to the boom pole.●If the entrance/exit is unidirectional, the holes should be in the horizontal center of the refugeisland. If the entrance/exit is bi-directional, the holes in the horizontal direction should be far away from the entrance/exit.2.Punch the four M12 × 150 expansion screws in the package into the marked positions on refuge island, and fasten the nuts to make the screws expand to grip the ground. Then unfasten thenuts.Figure 2-2 Install Expansion Screws3.Uninstall the top and front covers.1)Use the L-type key to unlock the top cover.2)Lift the top cover gently and push it to take it down.3)Lift the front cover gently to take it down.Figure 2-3 Uninstall Top and Front Covers4.Fix the host.1)Put the layers on the host bottom and parallel them to the rising or falling direction of theboom pole.2)Put the host on the positions of expansion screws on the refuge island to make the screwspass through the layers. Keep the layers parallel to the rising or falling direction of the boom pole.3)Fasten the expansion nuts on the screws to fix the host.Figure 2-4 Fix HostKeep the supporting bracket of the boom pole vertically upward to avoid accident.2.2.2 Install Boom PoleFollow the steps to install boom pole.Steps1.Align the holes on the supporting bracket with those on the boom pole.2.Insert four M8 screws into the holes.3.Install flat washers, spring washers, and nuts on both sides of the screws.4.Fasten the nuts to fix the boom pole.Figure 2-5 Install Boom PoleCautionContact the professional technical personnel to change the boom pole. You may damage the barrier gate if you change it by yourself.2.3 Wiring2.3.1 Connect to Peripheral DevicesThe barrier gate can connect to peripheral devices such as entrance/exit capture unit.Steps1.Open the top cover of the host, and you can see the interfaces to connect peripheral devices.2.Connect peripheral devices to the interfaces as shown below.Refer to "Peripheral Device Interfaces Introduction" for the detailed definition of the peripheraldevices interfaces.Figure 2-7 Connect to Peripheral Devices2.3.2 Connect to Power SupplyConnect the laid power cord (RVV3 × 1.5 mm2 or above) to the power input of barrier gate. Installthe top and front covers. Use the L-type key to lock the top cover.●Cut off the power before wiring.●The power voltage of barrier gate is 220 VAC ± 10%. If the voltage exceeds the range, voltage stabilizer is needed.●Make sure the barrier gate is connected to the ground firmly, or it may cause electric shock.Figure 2-8 Power InputChapter 3 DebugAfter the installation completes, power on the barrier gate, and it will operate self-check of rising to limit position.After the self-check completes, you can control the barrier gate via remote controller or buttons.3.1 Remote ControlAfter the self-check completes, you can control the boom pole to rise, fall, and stop via the remote controller leaving factory with the barrier gate.3.2 Button OperationOpen the top cover of the host, and you can see the buttons and nixie tube. You can control the barrier gate via the buttons and judge the status via the nixie tube.There is respective initial status for the rising limit position, falling limit position, and rising speed of the barrier gate. You can adjust them via buttons if the initial status cannot meet the requirements of the installation site.Figure 3-1 Control ButtonsNote●If you need to hold the buttons to trigger operations, hold for 3 seconds or above.●The nixie tube shows the status (e.g., H0) and fault codes (hexadecimal characters, e.g., 1A). If the fault codes appear on the nixie tube, it means there is operation error. Contact the technical personnel of our company to solve the problems.Table 3-1 Button Operation DescriptionThe controller can learn no more than 481.Press2.Holdadjust the boom pole to H5 status.Displayed fallingunit of thedurationPressnixie tube displays rL.Apply control signal to let the boom pole rise to the limit position.Holdadjust the boom pole to H8 status.HoldPressChapter 4 Maintenance4.1 Check RegularlyThe barrier gate should be maintained every three months. Check according to the following instructions.●Check mechanical drive.●Check if the wiring and GND is firm.●Check if the motor sounds abnormally.4.2 Check After Collision●Check if the slewer is damaged. Change it if it is damaged.●Check if the boom pole is curved. Change it if it is curved.●Check if the barrier gate sounds abnormally during running. Contact the qualified after-sales service agent in time.4.3 Fault Code DescriptionWhen the barrier gate is abnormal, open the top cover, and observe the fault code on the nixie tube to troubleshoot.Table 4-1 Fault Code Description4.4 Troubleshooting for Failed Auto Rising/Falling of Boom Pole After Power CutoffIf the boom pole cannot rise or fall automatically after the power is cut off suddenly, follow the steps to solve the problem.Steps1.Uninstall the top and front covers.2.Insert L-type wrench into the hexagonal hole on the host.Figure 4-1 Rotate Wrench3.Rotate the wrench according to the barrier gate status.-If the barrier gate is in the falling limit status, rotate the wrench anticlockwise to raise the boom pole slowly until it can rise and fall automatically.-If the barrier gate is in the rising limit status, rotate the wrench clockwise to make the boom pole fall slowly until it can rise and fall automatically.Appendix A. Peripheral Device InterfacesIntroductionOpen the top cover of host, and you can see the interfaces as shown below.Figure A-1 Interfaces Table A-1 Interface Description。
云安全管理平台产品白皮书版本信息文档名称密级创建人云安全管理平台产品技术白皮书2.0.3V1.0公开云安全公司修订记录修订日期修订内容修订人2019.7新建，适用于云安全管理平台V2.0.3，文档版本2.0.3V1.0云安全公司版权声明：奇安信集团及其关联公司对其发行的或与合作伙伴共同发行的产品享有版权，本文中出现的任何文字叙述、文档格式、插图、照片、方法、过程描述等内容，除另有特别注明外，所有版权均属奇安信集团及其关联公司所有；受各国版权法及国际版权公约的保护。
对于上述版权内容，任何个人、机构未经奇安信集团或其关联公司的书面授权许可，不得以任何方式复制或引用本文的任何片断；超越合理使用范畴、并未经上述公司书面许可的使用行为，奇安信集团或其关联公司均保留追究法律责任的权利。
免责声明奇安信集团，是专注于为政府、军队、企业，教育、金融等机构和组织提供企业级网络安全技术、产品和服务的网络安全公司，包括但不限于以下主体：北京奇安信科技有限公司、网神信息技术（北京）股份有限公司、北京网康科技有限公司，以及上述主体直接或者间接控制的法律实体。
奇安信集团在此特别声明，对如下事宜不承担任何法律责任：1、本产品经过详细的测试，但不能保证与所有的软硬件系统或产品完全兼容，不能保证本产品完全没有错误。
如果出现不兼容或错误的情况，用户可拨打技术支持电话将情况报告奇安信集团，获得技术支持。
2、在适用法律允许的最大范围内，对因使用或不能使用本产品所产生的损害及风险，包括但不限于直接或间接的个人损害、商业盈利的丧失、贸易中断、商业信息的丢失或任何其它经济损失，奇安信集团不承担任何责任。
3、对于因电信系统或互联网网络故障、计算机故障或病毒、信息损坏或丢失、计算机系统问题或其它任何不可抗力原因而产生的损失，奇安信集团不承担任何责任，但将尽力减少因此而给用户造成的损失和影响。
4、对于用户违反本协议规定，给奇安信集团造成损害的，奇安信集团将有权采取包括但不限于中断使用许可、停止提供服务、限制使用、法律追究等措施。
360网神终端安全响应系统V7.0产品白皮书目录..........................................................................................................................................................................................................................................................................2.1产品概述 (2)2.2产品理念 (2)2.3产品组成与架构 (3)2.3.1终端Agent (4)2.3.2大数据分析平台（硬件） (4)2.3.3威胁情报 (4)2.3.4控制中心 (5).................................................................................................................................3.1终端大数据采集 (5)3.2主动式威胁检测 (6)3.3终端威胁追踪 (6)3.4威胁应急响应 (6)3.5安全状况全面评估 (6).................................................................................................................................4.1威胁情报驱动的积极防御能力 (7)4.2持续不间断的数据采集监测能力 (7)4.3大数据支撑的快速检索定位能力 (7)4.4自动化安全响应能力 (7)4.5一体化终端安全解决方案 (8)4.6多产品安全联动能力 (8).................................................................................................................................5.1提高威胁追踪能力，实现威胁可视化 (8)5.2强化威胁对抗能力，升维打击高级威胁 (8)5.3健全调查机制，提高应急响应效率 (8).................................................................................................................................6.1典型部署 (9)6.2部署清单 (10)1引言随着网络和信息技术的快速发展和普及应用，我国政府和企业的信息基础设施及各种新型业态蓬勃发展，与此同时安全防护系统也经历了一个从无到有、从弱到强的发展过程。
ROVER® 6S ACCESSORY KITSCustomize Your ROVER SystemUse of U.S. DoD visual information does not imply or constitute DoD endorsement. To Meet Your Exacting NeedsL3Harris accessory kits for the ROVER® 6S family of transceiversdeliver powerful, versatile features to ensure mission success.Reliably configure your system with the right power, antenna andcomputing options to enhance your mission-critical applications.Panasonic CF-20(optional)Mission Data Interface CableDOBEPanasonic M-1 (optional)The computer kit also includes flexible and ruggedized power options optimized for use with the ROVER kit.CLS Elevation Gain PatternCLS Omnidirectional Antenna AssemblyKu Omnidirectional Antenna AssemblyKu Elevation Gain PatternKu DirectionalAntenna AssemblyDual Battery BoxThese item(s)/data have been reviewed in accordance with the International Traffic in Arms Regulations (ITAR), 22 CFR part 120.11, and the Export Administration Regulations (EAR), 15 CFR 734(3)(b)(3), and may be released without export restrictions.L3Harris Technologies is an agile global aerospace and defense technology innovator, delivering end-to-end solutions that meet customers’ mission-critical needs. The company provides advanced defense and commercial technologies across air, land, sea, space and cyber domains.Use of U.S. DoD visual information does not imply or constitute DoD endorsement.ROVER 6S Accessory Kits© 2022 L3Harris Technologies, Inc. | 06/2022 | BCS | 20-DSH-240 | Rev-201t 833 537 6837*************************OPTIONAL ANTENNAS1025 W. NASA Boulevard Melbourne, FL 32919Miniature Multiband Directional (MMD) AntennaMedium to long-range, receive-only, quad-band antenna for ground-based operationsThe MMD is a low-SWaP, ruggedized ground antenna combining four frequency bands (L, S, C, and Ku) into a single compact unit. This solution features a low-SWaP, ruggedized design, optimized for harsh tactical environments. The MMD is a single LRU consisting of an antenna controller, power supply, LNAs, necessary filters, and switches. The product comes in a tactical kit including a transit case, tripod, and applicable cables. >Medium to long-range capable>Dual-link acquisition and directional positioning (elevation and azimuth) >High reliability>Quad-band (L, S, C, and Ku)ANTENNA SPECIFICATIONSAperture Gain / 3dB Beamwidth (Minimum / Nominal Midband) >L-Band (Low): 7.0 dBi / 50° >L-Band (High): 8.0 dBi / 48° >S-Band: 11.0 dBi / 44° >C-Band CONUS: 15.7 dBi / 21° >C-Band OCONUS: 17.0 dBi / 18° >Ku-Band:25.0 dBi / 8°PEDESTAL SPECIFICATIONS SWaP>Size (operational mode):13" (w) x 46" (l) x 14" (h) >Weight: < 30 lb>Power Consumption (max): 28VDC, 120W Peak, 70W average >Input Power Range: 22-33 VDC >Operating Temperature: -40°C to 71°CSTINGER MBSimplified long-distance ROVER communicationsL3Harris’ STINGER MB mobile bi-directional ground terminal is extremely rugged and easy to deploy, requiring no additional tools for setup or tear down. Two-man setup can be accomplished in less than 15 minutes. Once assembled, the terminal’s embedded dual GPS/INS automatically aligns the antenna tracker to true north (+/- 0.5˚). This eliminates the need for magnetic calibration or time consuming set-up routines. >Extends CDL range in excess of 100 nm 1 >Supports automatic telemetry tracking >Supports L-, S-, C-, Ku-bands and UHF- option >Includes auto-acquisition feature>Built-in dual-GPS INS with auto-alignment >Universal power 100 to 240 VAC>Rear panel local controller with touch screen ANTENNA PERFORMANCE Gain (mid-band)>UHF (optional): 13.0 dBi >L-Band: 21.0 dBi >S-Band: 24.0 dBi >C-Band: 30.0 dBi >Ku-Band: 36.0 dBiPHYSICAL CHARACTERISTICS Ground Terminal Physical Dimensions >Size: 53" (w) x 42" (h) x 42.5" (d) >Effective swept volume: 94 ft 3 >Weight 2: 265 lb. (120.2 kg)Ground Terminal Transportation >5 wheeled cases>Weight: 54 lb. (24.5 kg) to 104 lb. (47.2 kg) per case 2Prototype unit pictured;production design is improved1. Depending on total system configuration2. Meets USAF guidelines for a two-man lift。
![零度HighOne-Pro用户手册_V1.0[1]](https://uimg.taocdn.com/4ca6e243f7ec4afe04a1df77.webp)
安全技术说明书页: 1/9 巴斯夫安全技术说明书按照GB/T 16483编制日期 / 本次修订: 18.03.2023版本: 6.0日期/上次修订: 06.09.2021上次版本: 5.1日期 / 首次编制: 15.11.2005产品: 交联聚维酮CLProduct: Kollidon® CL(30034964/SDS_GEN_CN/ZH)印刷日期 06.11.20231. 化学品及企业标识交联聚维酮CLKollidon® CL推荐用途和限制用途: 药用辅料公司:巴斯夫(中国)有限公司中国上海浦东江心沙路300号邮政编码 200137电话: +86 21 20391000传真号: +86 21 20394800E-mail地址: **********************紧急联络信息:巴斯夫紧急热线中心（中国）+86 21 5861-1199巴斯夫紧急热线中心（国际）:电话: +49 180 2273-112Company:BASF (China) Co., Ltd.300 Jiang Xin Sha RoadPu Dong Shanghai 200137, CHINA Telephone: +86 21 20391000Telefax number: +86 21 20394800E-mail address: ********************** Emergency information:Emergency Call Center (China):+86 21 5861-1199International emergency number: Telephone: +49 180 2273-1122. 危险性概述纯物质和混合物的分类:根据 GHS 标准，该产品不需要进行分类。
巴斯夫安全技术说明书日期 / 本次修订: 18.03.2023版本: 6.0产品: 交联聚维酮CLProduct: Kollidon® CL(30034964/SDS_GEN_CN/ZH)印刷日期 06.11.2023 标签要素和警示性说明:根据GHS标准，该产品不需要添加危险警示标签其它危害但是不至于归入分类:在一定条件下，产品可形成粉尘爆炸。
The Agile Operations Bridge Micro Focus® Operations Bridge services for better Hybrid IT Operations.Product OverviewDriven by cloud, mobile, big data and DevOps, Hybrid IT delivery promises to bring agility and improved service delivery to business users. But these same trends are also turning already challenging IT Operations into a much more complex world.While business users are now often choosing to obtain services from external vendors, they still expect IT to manage service delivery and ensure that applications are available. So how does IT ensure service delivery when:■Users are bringing their own devices■Applications are becomingmore composite■The infrastructure is virtualand software defined■Workloads run in the cloud■Agile development is increasingthe velocity of change■Security risks are on the riseIT can ensure that it is not overwhelmed by the pace and magnitude of change in the world it is entrusted with, by rethinking, retooling, and evolving its Operations Bridge services to “The agile Operations Bridge.”Y ou Can’t Just ThrowIt over the FenceOver the last two decades, many IT depart-ments have invested heavily in IT Operations.As new technologies were adopted, so werenew tools to monitor these technologies.This has added up to a situation where theaverage IT department now has dozens ofmonitoring tools, yet the ability to prevent thebusiness impact of outages has not markedlyimproved as one would have expected. So theissue is clearly not with insufficient technol-ogy, and more monitoring is not necessarilybetter monitoring.The reality is that most IT organizations(even those that adhere to ITIL) view ServiceOperations in isolation of the service lifecy-cle. In most cases currently, monitoring is anafter-the-fact activity. Applications and ser-vices are built (or bought), released, and thenhanded over to IT Operations for monitoringwith most projects treating monitoring as abox they need to check off before they cango live. This is akin to thinking that winning achampionship game begins when the refereeblows the whistle, while ignoring all of the train-ing and planning that needs to take place priorto the start of the game.Data SheetProfessional ServicesData SheetThe Agile Operations BridgeSo while many IT organizations have plenty of technology and have implemented vari-ous forms of Operations Bridge (typically called a NOC), they are not realizing the full potential because so much of the value of the Operations Bridge depends on what happens before ever going live.“Shift Left” MonitoringTo increase the value from an OperationsBridge, you need to “shift left” and adopt a“monitoring by design” approach. This simplymeans starting to think about how and what tomonitor much earlier than has traditionally beenthe case. It means incorporating monitoringinto the requirements and the design, so thatwhen you deploy to your users, everything isalready instrumented and in place to allow youto collect the data you need. It means definingstandards and working closely with develop-ment teams so you can automate as much aspossible. It means understanding up front whatdata you need so you know how best to collect,process, and report it.Predictive Service OperationsYou also need to recognize that being good atmonitoring (which many IT organizations are)is a prerequisite—not a guarantee—for goodservice delivery. The prevailing view considersmonitoring services as the end rather than themeans, as if simply by monitoring, a root causewill reveal itself when the system has an issue.However, as is the case with most complexsystems, the whole is greater than the sum ofits parts. Monitoring is a tool meant to help ITOperations do their job, not to exist for its ownsake. In short, monitoring services alone arenot enough.T o improve delivery of business service man-agement services, IT needs to expand thescope of the Operations Bridge and turn itinto the core element of Predictive Service Figure 1.The Agile Operations BridgeFigure 2. Services overviewOperations—a holistic, service oriented ap-proach to IT Operations.Key FeaturesY our IT organizations is becoming more agile. Whether it is the adoption of DevOps or the increasing use of cloud and self-service pro-visioning, everything is moving faster, and your Operations Bridge must also become agile to continue to deliver value. There are several ele-ments to the agile Operations Bridge: Governance FrameworkBusiness services have a lifecycle. For a suc-cessful Operations Bridge, the lifecycle must ensure that everything is in place for Service Operations (or as known by The Open Group, the Detect-to-Correct value stream) as soon as the service goes live. This means that there are certain things that need to take place much earlier in the lifecycle. For example:■Understanding what data will flow through the Operations Bridge so itcan be provided to the various roles involved, in the manner most suitable for them to make the right decision basedon accurate and timely information■Definition of standard monitoring templates so that these mightbe offered in a service catalogand to increase the efficiencyof deploying monitors■Definition, discovery, and modelingof the service to drive eventcorrelation and root cause analysisThe role of governance is to ensure that the IT value chains embed these principles so that the Operations Bridge delivers maximum value.SimplifyThe way that application monitoring serviceshave evolved historically has led to a prolifera-tion of tools, many of them with overlappingcapabilities. These tools were primarily de-signed to help experts (such as DBAs) moni-tor the components they are responsible for.New technologies, such as cloud and mobile,require additional monitoring capabilities thatadd to the cost and complexity of managingand integrating an ever-growing fleet of moni-toring tools.On top of that, you also need to account forservice discovery and modeling. While youmay have implemented mechanisms to aggre-gate and reduplicated the events that thesetools generate, this is insufficient for the samereason a doctor would be unable to make adiagnosis simply based on symptoms but withno understanding of anatomy or physiology.The anatomy of business service manage-ment services —also known as the servicemodel—is crucial to providing the contextfor fast and efficient prioritization, root-causeanalysis, and minimization of any business im-pact from outages. Here too, it is likely that youhave multiple discovery tools and methods.Exacerbating this problem is the fact thatyou probably have as many monitoring stan-dards and templates as you have tools. Whatyou therefore need is a simplified applicationmonitoring architecture that allows you to re-duce the costs associated with managing yourOperations Bridge by consolidating your mon-itoring standards into a single set that you con-sistently apply across your entire environment.What you therefore need is a simplified appli-cation monitoring architecture that allows youto reduce the costs associated with manag-ing your Operations Bridge by consolidatingyour monitoring standards into a single setthat you consistently apply across your en-tire environment.Figure 3. Automate, Unify, SimplifyData SheetThe Agile Operations BridgeUnifyUnifying monitoring data and service models into one platform enables you to drive bet-ter decision making. An Operations Bridge receives a large volume of events (research suggests this volume has risen by 300 percent over the last five years) that need to be priori-tized and processed. However, not all events are born equal and you would want to first ad-dress the events with the highest business impact. Service models provide the business context for prioritization. Service models also allow you to tell ‘symptom’ events from ‘cause’ events by correlating them based on the ser-vice model. Y ou can then focus your resources where they are most needed and where they can be most productive: fixing priority root causes, not chasing unimportant symptoms. Having all of this data in one location will help you achieve that. Functions such as service delivery, helpdesk, and capacity manage-ment can now unify their processes as they better collaborate over a unified data set to enhance their own productivity and the value they provide.Simplifying and unifying sets you up with the right foundation for automation.AutomateIncreasing productivity requires automation. Yet the three core activities of an Operations Bridge—monitor deployment, remediation, and reporting—are still, by and large, exe-cuted manually.The benefits of automation are clear when it comes to monitoring deployment. Rather than the current manual or policy-based methods, you can now use configuration item (CI)- based deployment. As soon as your discovery finds a new item (e.g. an app server), it can auto-matically deploy all of the monitors that your standards have defined. The Holy Grail of automated remediation is now within reach. When you can see the whole picture end-to-end, you can begin to automate the incidentlifecycle and become even more efficient atresolving issues. You can focus on the rightevents and create tickets that direct the rightexperts toward the root cause. You can take iteven further and use scripts to automaticallytake corrective action when issues strike,thus eliminating even the need for an expertto be involved.Simplifying and unifying now allow you toalso automate analytics. With all of the per-formance data in one place, you can performpredictive analysis to anticipate capacity con-straints, preempt performance degradation, orjust report on service level agreements.The Simplify, Unify, Automate approach willhelp you increase your productivity and dra-matically enhance the value you get from yourOperations Bridge.Think Big, Start SmallYou may be thinking to yourself “The agileOperations Bridge is a nice concept, but I needto first use all my tools to their fullest capac-ity.” We at Micro Focus Professional Servicesbelieve that to succeed in any endeavor, youneed to set—and keep—your sights on thebig picture, while at the same time take anincremental approach. Start with some quickwins and move on to the bigger items. We be-lieve that your roadmap should allow you toreach your final destination through gradualimplementation, with each step adding morecapabilities while building on the success ofthe previous achievements. And we have de-signed our portfolio to do just that.Operations Bridge Foundation ServiceThis offering from Micro Focus ProfessionalServices puts existing Micro Focus OperationsManager customers on the right path towardan Operations Bridge. Using OperationsManager-i, the market-leading OperationsBridge platform, we onboard a service of yourchoosing by:■Deploying Operations Manager-ias the core of the platform■Migrating agents and policiesfrom Operations Manager■Aggregating events and monitoring data■Discovering your service andcreating the service model■Configuring event processingrules, including Basic as well asT opology and Stream-Based EventCorrelation (TBEC & SBEC)■Automating monitoring deployment■Integrating with a ticketing/notification systemAfter we complete the onboarding process,we provide you with a documented procedureso that you can continue to onboard additionalservices onto the platform.Agile Operations Bridge ServiceThis offering implements a governance frame-work that enables you to consistently and suc-cessfully onboard Operations Bridge services.Ultimately, this means being able to under-stand what information you need to collect,how to collect it, and how to best representand deliver it to the stakeholders, whetherthese are people, processes, or tools.Model and OrganizeOne of the most common mistakes in im-plementing an enterprise-scale OperationsBridge is focusing on the technology as thefirst step. In our view, effective tooling and au-tomation rely on standardization of processes.This is why we begin by modeling and organiz-ing as they are the foundation for standardiza-tion. We do this by working with you to:■Define what a service is■Match discovery and modeling toevent processing and reporting■Define organizational structure and roles■Determine accountability for the provisioning and consumption of information StandardizeOnce we understand the current situation, we can begin to devise methods to standardize your tools, metrics, reports, dashboards, roles, and responsibilities. We achieve this by:■Defining the authoritative sources (tools) of information■Defining standards for information presentation, monitoring, owners,and consumers■Defining responsibility for datacollection■Consolidating toolsAutomateThe last stage of the journey is to leverage your technology to automate and accelerate the process from demand to consumption, thus improving information quality and accu-racy. Here we use Operations Bridge to auto-mate the deployment of:■Role-based reports■Role-based dashboards■CI-based monitorsBenefitsReduce Business Impact of OutagesWith all of your events now in one place and able to be correlated, you can more rapidly di-agnose the situation, quickly identify the cor-rective action needed, and restore service with minimum disruption to the users.Increase ProductivityEvent aggregation and correlation means that your IT Operations don’t have to spend time wading through large numbers of events to find those that require action.T emplate-based, automated monitoring de-ployment allows you to apply monitoring faster and with less manual intervention.Reduce Monitoring TCOThrough standardization and automation, du-plication of effort and tooling is eliminated. The Micro Focus Professional Services DifferenceMicro Focus provides unmatched capabilities with a comprehensive set of consulting and im-plementation services and unique intellectual property that help you drive innovation through streamlined and efficient software delivery.■Proven Micro Focus softwaresolution implementation expertise■More than 20 years of experience helping large, complex, global organizations realize value from their Micro Focus software investments■Rich intellectual property and unparalleled reach into product engineering■T echnology-agnostic implementation approach with no vendorlock-in, no rip-and-replace■Education and support servicesto ensure adoptionLearn more at/itomservices。
Ibot8.0产品白皮书第 1 页共47 页目录1.前言 (6)1.1.目的范围 (6)1.2.产品定位 (6)1.3.名词术语 (6)2.公司简介 (8)2.1.小I简介 (8)2.2.小I发展历程 (8)3.产品概述 (11)3.1.智能机器人 (11)3.2.产品架构 (11)3.1.1.机器人前端平台 (12)3.1.2.智能服务引擎平台 (12)3.1.3.机器人统一管理平台 (14)3.1.4.知识库组织说明 (14)3.3.产品演进路径 (17)3.4.技术特点 (17)3.5.技术指标 (18)3.6.扩展接口 (19)3.7.优势特性 (19)4.产品主要功能 (22)4.1.基础智能问答 (22)4.2.前端用户功能 (23)4.2.1 Web机器人功能 (23)4.2.2微信机器人功能 (28)4.2.3IM机器人功能 (31)4.2.4短信机器人功能 (33)4.3.后台主要管理功能 (35)4.3.1知识管理功能 (35)4.3.2服务管理功能 (36)4.3.3渠道管理功能 (36)4.3.4素材管理功能 (37)4.3.5语音管理功能 (38)4.3.6运维管理功能 (38)4.3.7系统管理功能 (39)5产品实施 (39)5.1.实施流程 (39)5.2.知识建设 (39)5.2.1 语言知识库构建 (40)5.2.2 业务知识库构建 (41)5.3.二次开发 (42)5.4.系统部署 (44)5.4.1 常规部署 (45)5.4.2 扩展部署 (45)5.4.3 集群部署 (47)版权声明版权所有© 2013-2015上海智臻网络科技有限公司。
本文档的内容，所有文本全部或部分均受版权保护，上海智臻网络科技有限公司是本文档所有版权作品的拥有者。
除非预先得到本公司的书面授权，否则严禁对本文档进行复制、改编、翻译、发布等等。
本文信息如有变动，恕不另行通知。
目 次前言 ................................................................................ I II1 范围 (1)2 规范性引用文件 ...................................................................... 1 3 通用术语 . (1)4 导航方式术语 (2)5 转向方式术语 ........................................................................ 3 6 驱动方式术语 ........................................................................ 4 7 驱动结构术语 ........................................................................ 4 8 性能参数 ............................................................................ 5 9 运动方向术语 (6)10 机构与零部件 (6)11 辅助零部件术语 ..................................................................... 7 12 软件功能术语 .. (8)13 充电/供电方式 (9)14 安全术语 .......................................................................... 10 英文索引 .. (12)中文索引 (14)全国团体标准信息平台前 言本标准按照GB/T1.1给出的规则起草。
REACH多媒体录播一体机CL1210技术白皮书V2.52011-03目录一. 概述 (3)二. 特点 (3)三. 接口 (6)四. 技术指标 (7)一. 概述REACH多媒体录播一体机（高清系列：CL1210），是锐取针对中小企业及移动录播的需求自主研发的最新一代可视化信息记录与传播设备。
该设备小巧便携，自身集成了视频、音频、VGA信号输入接口和HDMI高清、VGA、音频输出接口。
支持1路高清视频、1路VGA及1路音频信号的任意组合录制、直播、点播，多流模式存储，支持HDMI高清及VGA信号输出，可以非常方便的实现视频、音频和计算机屏幕信号的同步录制及本地预览、回放，满足用户会议、培训、教学等场景下可视化信息记录与传播的需要。
图：REACH高清多媒体录播一体机二. 特点●多媒体信号（视频、音频、计算机）同步录制、直播多媒体录播一体机（高清）支持视频、音频和计算机屏幕信号的同步组合录制、直播、点播，可以满足会议、教学、培训等场景下主讲人的图像声音以及讲解的内容的记录与传播的需求。
●高清视频视频清晰度最高支持720P，可满足高清视频应用录制需求。
●立体声音频支持双声道立体声音频编码，44.1k音频采样，128Kbps编码带宽，为您提供震撼的高保真立体声效果。
●高清计算机屏幕信号计算机屏幕分辨率最高支持1280×1024，可满足录制计算机屏幕的需要。
● 录制质量支持三级模式可调视频录制质量可根据不同的网络环境调节，调节模式分高、中、低三个等级，满足用户不同网络环境下的录制、直播、点播需求。
录制质量等级码率分辨率视频VGA高4.0MbpsD1、720P640*480、 800*600、 1024*768、 1280*720、 1280*768、 1280*960、 1280*1024中 2.0Mbps 低1.0Mbps● 小巧便携相对于其它常见录播一体机动辄4U ，19英寸的庞大体积，REACH 多媒体录播一体机采用自主研发的硬件平台，稳定可靠，同时体积大大缩小，占用空间更少，易于携带，非常方便在各种移动环境下的会议、报告录播使用。
REACH多媒体会议一体机
CL360
技术白皮书
V1.0
2013-07
目录
一. 概述 (3)
二. 特点 (4)
三. 接口 (6)
四. 技术指标 (7)
一. 概述
REACH多媒体会议一体机CL360，是针对中小企业会议室、培训室及移动录播的需求自主研发的最新一代录播设备。
该设备小巧便携，自身集成高清视频、音频、VGA、USB等输入输出接口，支持高标清信号接入，自动识别信号并自动组合布局模式，可以非常方便的实现视频、音频和计算机屏幕信号的同步录制及本地预览、回放；录制生成通用MP4视频文件；系统可用PC、平板电脑等管理控制;配置简化版媒体中心发布平台，支持Android、IOS等移动终端共享资源，满足用户会议、培训等场景下多媒体信息记录与分享的需要。
图：REACH 会议一体机
图：会议一体机系统连接图
二. 特点
●高清晰多媒体信号同步录制
支持2路高清晰720P/1080P视频或2路D1标清视频信号、1路高分辨率VGA信号、1路高清晰音频信号的同步录制。
●MP4视频文件
系统生成通用MP4视频文件，方便用户对视频随时随地观看需要。
●USB高速直录拷贝
系统自带USB2.0接口，视频文件可直接录制保存移动存储设备，或通过USB接口将录制好的视频文件拷贝至移动存储设备。
●多种控制管理
系统支持PC、iPad平板电脑等设备实现系统管理。
●视频资源移动发布
配置媒体中心发布平台，采用HTML5资源共享技术，支持Android、IOS多种移动终端资源发布。
●支持标准流
系统支持RTP、RTSP等标准数据流推送。
●高低码流
系统支持高低码流文件并存，高码流文件用于高质量文件保存，低码流文件用于移动终端或低带宽的直播点播。
●画面合成
系统自动识别接入信号源类型，根据信号源数量自动合成画中画、画外画布局模式。
●前面板按钮操作
系统前面板设置录制、暂停、停止、下载、回放操作按钮，操作方便、快捷
●录制质量支持三级模式可调
视频录制质量可根据不同的网络环境调节，调节模式三个等级。
●本地预览、回放功能
VGA输出接口，可实现录制视频本地实时预览，录制文件本地回放，并且实现高清输出。
●FTP自动上传
系统内置的FTP自动上传脚本，能实现把录制好的视频文件自动上传至第3方FTP 服务器或锐取公司产品其他系列服务器（注：FTP上传功能与媒体中心连接功能互斥）。
三. 接口
四. 技术指标编码方式
●视频：H.264
●音频：AAC
采集分辨率
●标清：D1
●高清：720P/1080P
●VGA：最高达1920*1200
录制模式
●画面合成录制，单流MP4视频管理方式
●WEB界面
●前面板按钮
●PC管理
●iPad管理
●中控控制
●简化版媒体中心
系统
●嵌入式操作系统
直播点播
●RTP、RTSP标准数据流直播
●iPad直播预览
●PC管理平台直播预览
●本地解码预览回放
●简化版媒体中心直播、点播
录制容量与存储方式
●1T存储硬盘
●标准MP4格式文件
●媒体中心存储
文件下载
●USB下载拷贝
●PC客户端下载
本地解码输出
●1024*768@60Hz、
●1280*720@60Hz 、
●1280*1024@60Hz、
●1366*768@60Hz、
●1280*800@60Hz、
●1440*900@60Hz、
●1400*1050@60Hz
配合软件产品
●简化版媒体中心
●PC管理平台
●iPad控制平台
语言版本
●中文
●英文
电气指标
●工作电压：DC 12V/9.2
●功耗：70
物理特性：
●一体机尺寸（长/宽/高）
430mm×340mm×44.5mm ●重量：约3kg
环境规格：
●存储温度：-40~80℃●相对湿度：5~95% ●工作温度：-20~60。
