LPD-17

   
    
    LPD-17C⁴I WORKSHOP REPORTJune 1996

    编制：Dahlgren, Virginia 22448-5000

I.执行摘要

从1996年4月30日至1月1日，指挥官，两栖小组（Compribgru三）（加利福尼亚州圣地亚哥）举办了第一个关于指挥，控制，通讯，计算机，计算机，信息的LPD 17研讨会（C⁴我）。该研讨会是LPD 17计划办公室PMS 317的系列中的一个研讨会，它是其“所有权设计”理念的一部分：一种并发的工程方法，它将Warrior（操作员，维护者和培训师）投入到设计开发中过程。结果，除了在弗吉尼亚州水晶城的17号设计站点外，还在弗吉尼亚州的海军地面战争中心达尔格伦分部（NSWCDD），弗吉尼亚州达尔格伦和远征战训练小组（大西洋（大西洋）（NSWCDD）建立了17个战室。Ewtglant），海军两栖基地（NAB）小溪，弗吉尼亚州。Dahlgren（工程入口）和Little Creek的Warrior Inlet的系统工程环境将结合起来，生成有效的并发工程过程，从而实现LPD 17设计，努力满足操作员，维护人员和培训人员的需求。除了每年进行OPTEV的早期运营评估外，这些研讨会还提供了一种与战士参与此并发工程过程的重要，协作的手段。来自加利福尼亚州蒙特雷海军研究生院的早期讲习班（9月95日）和Ewtglant（1月96日），C⁴I was identified as an important area requiring additional Warrior and engineering input.

This workshop gathered together experts in the field of Littoral Battlefield execution and C⁴I systems. The intent was to discuss LPD 17 C⁴I operational requirements, systems plans, and their relationship to both current and future Amphibious Ready Group (ARG)/Marine Expeditionary Unit (MEU) and integrated Battle Group (BG) operations. The workshop validated many aspects of the LPD 17 design, identified areas for future workshops, and suggested some near term space/room layout recommendations. Since the field of C⁴我是如此广泛，两天没有足够的时间来详细介绍该主题的各个方面。因此，谈判了界限以集中讨论。

Due to limitations of space not all acronyms have been defined in the mainbody of the text. However, a comprehensive list ot acronyms and abbreviations is given in Appendix C.

Specific workshop recommendations that can be applied to the LPD 17 are as follows:

LPD 17必须能够充当替代指挥船，并准备好在被要求时支持此类任务的系统。
LPD 17智能和SSE/设备需要连接到LHA/LHD上可以找到的相同设备。LPD 17或LHA/LHD将用作卫星通信（SATCOM）输入点回美国大陆（CONUS）。
LPD 17 acting as an Advance Force ship will need to support some limited SACC functionality with accompanied surface combatants and forces ashore (SEALs, Recon Teams, Raiders, etc.)
LPD 17需要支持参数数字宽带Transmission System (DWTS) implementation of a "GATOR" Hub/Node concept.

(Return to Table of Contents)

ii。介绍

LPD 17 C⁴I Conference/Workshop attendees received program and operational briefs from the following:

RADM Robinson, Program Executive Office (PEO) Carrier, Littoral, and Auxiliaries (CLA)
MAJ J.D. Wilson, Headquarters Marine Corps (HQMC) - USMC C⁴I Requirements Conference Out Brief
RADM Saffell, COMPHIBGRU THREE (CPG 3) - C⁴ISR for the Pacific Littoral Warriors
CAPT Marshall, Commander Aphibious Squadron Five (COMPHIBRON FIVE) (CPR 5) - Commander, Amphibious Task Force Missions/Concept of Operations (CONOPS)/Information Requirements
LtCOL Blankenhorn, CG I Marine Expeditionary Force (MEF) (G3)
指挥官，登陆部队任务/CONOPS/信息要求
LCDR Binney，PMS 317-当前LPD -17 ROC/POE（PMS 317）和
LT Gensure/Mr. Doug Jackson, SPAWAR PD05 - LPD-17 current C⁴我的建筑

The symposium was conducted in three phases:

第一阶段：这包括Pacific Fleet两栖小组之间在ARG/MEU的特定任务和Conops团队中进行的信息交流，以实现当前和未来的运营。第一阶段的产物是一种名义操作架构，包括一组海军两栖任务，各自的conops和战术信息需求，这些需求反映了车队指挥官的战斗要求。

PHASE TWO: This provided insight into current LPD 17 C⁴i计划的体系结构，需要操作能力。第二阶段的乘积是提供当前LPD-17 C的概述⁴我操作性要求和系统计划，包括通信，传感器，智能和加密以及指挥与控制（C²) systems.

PHASE THREE: This provided some analysis and relative ranking of planned C⁴I系统基于Pacific Fleet两栖动物的观点的操作假设。作为第三阶段的一部分，相关的C⁴审查了LPD 17 ROC/POE的部分，并提供了对系统命令和OPNAV赞助商的评论。第三阶段的乘积将阶段第一和第二的结果占据了概念作战体系结构和LPD 17 C的结果。⁴I baseline, and conducted a gap analysis of capabilities versus assumed CONOPS/information requirements.

(Return to Table of Contents)

III. CONFERENCE BRIEFS

RADM Robinson, PEO CLA:
海军探险战IPT终于成为现实。IPT将九个主要利益相关者聚集在一起，以应对战斗机对学说和工程的要求。LPD 17的RFP在街上，评论即将出现。两（2）个主要区域意外事件（MRC）可能会重新谈判至一（1）或一半。这只会增加对灵活，适应性战士友好的LPD 17的需求。
MAJ J.D. Wilson, HQMC CSBT - USMC C⁴I CONFERENCE:
The USMC C⁴I Conference/Workshop was held at MCCDC, Quantico, VA in March with over 160 attending. The conference identified the top level naval C⁴I issues and amphibious missions. There was a reduction in duplication of many requirements by this conference. A document is in the final stages of production and will be forthcoming soon. The LPD 17 requirements were detailed in the following list:
- Act as Alternative Command Ship/Split ARG operations.
- JIC space layouts are not adequate for both USMC and Navy personnel/systems (too small).
- Need enhanced imagery support.
- 需要实时的国家资产能力。
- 需要位置信息（PLI）；拉进去融合。
- LPD 17的无人机（UAV）操作极为有可能。
- LPD 17的MCM操作极为有可能。
- 需要详细的天气数据。
- Need targeting data.
海军陆战队（CMC）的指挥官和海军行动负责人（CNO）并未在哥白尼前锋上齐心协力。CMC不同意OPNAV N6概念。一支工作团队已组装以谈判问题。乐动冠军OPNAV内部正在进行一些两栖总体规划，而草稿版本将很快访问多个命令进行评论/审查。
radm saffell，compribgru三-C⁴ISR FOR THE PACIFIC LITTORAL WARRIOR:
The challenge for C⁴I in the Pacific Littoral Warrior is 97% forward projection and contingency and only 2% actual warfare (1% undefined). The amphibious forces are seen as the "911" responders. With expanding threats, the Integrated Battle Organization (IBO) will require increased "morphing" into a joint working force. Force levels are extremely dynamic, where revenues are down 41% and deployments (expenses) are up 31%. Operating days at sea are coming down again (from 27 days to 25 days on average per quarter per ship - impacts readiness). Based on this financial reality, joint efforts will be needed to renegotiate the two MRC scenarios. KSQ-1 needs to be integrated within JMCIS, but there is no fleet requirement to do this. CNSP has agreed to fix this hole in the system requirements definition (error came out of last weeks JRWG). The Fleet wants to delete requirements for big ships to go through the Panama Canal. (MGEN Jones, OPNAV N85 has just signed this out.) ARG underway planning within the Fleet today requires at a minimum two helicopters per day just to move information/personnel between ships. LPD class ships are used extensively as advance force ships today (30nm off beach). The Special Boat companies are on the LPDs and move mostly at night. The USS BOXER ARG will deploy next year with a DDG (USS CHANDLER) in company. Very Shallow Water (VSW) (40 ft water mark to the beach) ) MIW stood up recently at NAB, Coronado, CA. A new unit will consist of SEALs, EDOs, and a Marine Reconnaissance Team.
COMMODORE(CAPT) Marshall, COMPHIBRON FIVE - ARG REQUIREMENTS:
The ARG assumptions are as follows:
- 总会有一个伴随的战斗人员/射击者分配给ARG/MEU进行应急操作。
- 国旗将永远留在大甲板上（LHA/LHD）。
- 从收到消息到执行分裂ARG操作的六（6）小时的时间限制与独立操作不同。西海岸几乎没有分裂的ARG行动。东海岸进行了许多分裂的ARG行动。在过去的几年中，ARG从五档ARD变成了三身ARG。因此，支持拆分ARG越来越困难，因为拆除一艘船会大大降低了ARG的能力。
- The Navy cannot accomplish advance force operations without UAV coverage. The Fleet uses UAVs to spot mines. The Fleet does not like the current Joint Tactical UAV (JTUAV) PIONEER; it is too unreliable and hard to operate, but at present, it is all that is available. There are several customers out there who want to use ARG UAV-capable ships when they are deployed. When the USS DENVER last deployed, she was pulled into the Persian Gulf to support land forces watching Iraq.
- LPD 17 does not need to be Flag configured but maybe Flag capable for short periods of time. This may, however, require supporting a Flag staff.
- The R2P2 process involves between 200-300 people afloat.
- LPD 17同时需要JIC和SSES。战斗DF也是这艘船的舰队要求。至少需要两个船舶配置。这艘船也可能需要在敌人的视线（LOS）中进行拦截，以拦截蜂窝电话对话。LPD 17还需要与SSES进行通信，并将被要求在SSES功能上拥有几位语言专家。BGPHE还需要几位熟练的语言专家。Tacintel需要SI通信。SSES人员将需要与CO和TAO的直接连接/通信管道。根据LPD 17任务，可能有必要将SSES处于睡眠模式，但具有迅速提高的能力。SSE将有独特的曼宁要求。
- Planning and operations will need to be conducted in the future with a virtual staff (i.e., off-board ship/ARG). The ability to conduct planning on several ships simultaneously without required helicopter hopping personnel from ship-to-ship (interactive planning) is also a necessity. The LPD 17 will be required to seamlessly access Flagship databases for the latest information. VTC between ship and shore will be a standard requirement by FY 2002-04. LPD 17 will need a GBS downlink capability.
LtCOL Blankenhorn, I MEF G3 - USMC REQUIREMENTS:
从MEF级别的角度来看，需要做出更大的努力，以使所有海军陆战队都参与这一符合设计的所有权过程。西海岸倾向于发展信息。
- When the next Desert Shield/Desert Storm (DS/DS)-like event occurs, the Marines will immediately load up the Amphibious ships and move out while working out details on the way over. In 1989/1990, the East Coast immediately loaded up and sailed, whereas the West Coast waited until more details became available and a plan was hammered out (left months later than the East Coast Marines - hence late to the party). The next DS/DS will have seven big decks in theater. I MEF is building a Command/Combat Operations Center (COC) at Camp Pendleton, CA. This COC will have access to SIPRNET and NIPRNET via the DII/GCCS. The East Coast will also be building a COC soon. GCCS should be able to eliminate 90% of the stupid questions coming from the NMCC, ACOM, CINC, etc. If you want to see where GCCS is going, take a look at the USS MOUNT WHITNEY today. What once were Green Spaces are now Purple/Joint Spaces. When you stand up a CJTF and go joint, a MARFOR will stand up and partly run out of a CONUS-based COC. The MARFOR works for the Naval Component Commander when in theater. Collaborative planning will be driven by technology.
- LPD 17必须执行LFOC/TACLOG/TACC/SACC样函数，而不管有执行这些功能的专用空间的可用性如何。
- LPD 17将是21世纪的船；为什么它不具有现代的精密方法系统，以便我们可以执行夜间和低知识性方法（IFR功能）？目前，该船仅具有1950年的飞行甲板控制技术。LPD 17应具有SPN型雷达。
- The LPD 17 will need a remote CTAPS/ATO capability. Fleet will require a CNN (TVRO ?) capability for intelligence, events, I&W, etc.
- The LPD 17 will have to be able to handle a Mine/MIW Detachment and associated equipment. (What must be taken off to make room for this capability?)
LCDR Binney，PMS 317-当前LPD -17 ROC/POE（PMS 317）
C⁴我发乐动冠军表：
- Common Tactical Picture
- plifusion (SIP, SABER, KSQ-1, PLRS, etc.)
- Functional allocation (on ship/off ship)
- Need overall architecture defined
- Communications
- OPNAV N61/SPAWAR/NRaD is working on some cheaper ACDS functionality.
- TROOP OPS and LOGISTICS have been split up into two spaces based on fleet inputs. The spaces will be located next to each other.
- 现在，BGSITS授权软件升级截止（部署前3-6个月没有新的升级）。这在近期部署者的ARG集成中产生了问题（例如，11th Meu具有JMCIS UB 2.2软件，USS Essex USS Essex具有JMCIS UB 2.1软件 - 因此，另一个也没有与其他软件互操作。）
- PMS 317已要求CPG 3/I MEF对LPD 17 ROC/POE草案进行质量检查。
LT Gensure & Mr. Doug Jackson, SPAWAR PD05 - LPD-17 CURRENT C⁴I ARCHITECTURE
A new Amphibious Master Plan is being worked by OPNAV N6/SPAWAR/HQMC. SPAWAR is taking a turnkey approach to the C⁴我在LPD 17上套房，以获取最新/最现代的设备。他们将于1998年开始购买系统。Spawar有许多问题和问题，他们希望战士的意见。提出了以下问题：乐动冠军
JMCOMS和单个通道收音机。他们不确定要购买/安装多少个Sincgars。海军和海军陆战队的通信要求（专用网络与虚拟网络）是什么？他们需要容纳几个不同的支队 - 旗手，无人机，MIW，Specops等 - 以及他们独特的沟通要求是什么？
当他们在井甲板或储藏区倒下时，他们是否需要与海军陆战队进行培训？海军陆战队提到需要在EMCOM期间进行无线电检查，EMCOM通常在上岸移动之前执行（可能需要单个无线电的虚拟负载）。
海军陆战队将需要与旧系统（即可能不在天鹅上）进行交互。他们可能必须在无线电中心或其他C的Radio Centra或其他C中的架子中容纳非navy设备⁴我的空间（盟军的设备或联盟部队 - 我们在波斯尼亚经历）。目前，Navsea拥有Spawar的所有设备在非重要的功率上，而战斗系统都具有重要的力量。重要的力量连接全部基于任务关键系统。也许我们需要返回并重新检查这些名称并确定哪些系统真正至关重要？收音机/电路和英特尔系统不是至关重要的吗？空的设备架空间需要内置，以便未来的增长（海军，海洋，其他系统）。
SPAWAR难以来关闭the Marines on required communication circuits. How many do the Marines need and how many need to be operating simultaneously? (impacts the number of antennas on the ship, LPD 17 already has 129 antennas). Right now they cannot put up all of the circuits required, so which ones need to be taken down to bring up others. What are the priorities/requirements? SPAWAR sent over to OPNAV a draft list of required radios for the LPD 17. Is this the right number; they need a Marine Corps final scrub. The Marines will start placing orders for equipment in 1998, so a correct figure is needed soon.
Which SINCGARS circuits will be frequency hoppers and which ones will be single frequency? Each SINCGARS that frequency hops requires its own antenna. (The Navy tends to link two or three SINCGARS to a common antenna to save space.) The Fleet today cannot frequency hop, so how will that impact the land battle operations?
在有关传播方面，Spawar针对海军陆战队有一个分为两部分的问题：
- 通过每个电路/使用的是什么？
- How many circuits are needed to do various functions?
海军陆战队在海滩上使用便携式SATCOM系统。这些系统需要纳入Spawar通信体系结构。便携式SATCOM系统会成为“ Gator Hub”的一部分？
The operators need to get together and determine what information is needed and what equipment needs to go to whom? The N/G-6s will not make the determination but the N/G 2s,3s, and 4s will. Once they come to a consensus, the N/G 6s will figure out the communication paths/how data gets from one spot to another. (RADM Saffell statement)
车队必须确定指挥的梯队以及谁在什么船上。（radm saffell语句）

(Return to Table of Contents)

iv。乐动冠军问题

The following issues were brought up and discussed during the workshop.

无人机操作。到达2002-04财政部进入舰队时，无人机将在LPD 17中运行。将有某种无人机支队与船一起部署。LPD 17将需要上行链路和下行链路对无人机（有机或无机的ARG）。LPD 17将需要使用ARG和基于岸的单元进行无人机视频/数据传播。无人机操作将是进行提前部队操作的必要条件。无人机将用于矿山检测/避免矿山。（由马歇尔上尉提交，CPR 5）
JIC和SSES空间/有机功能。SSES/SI data does not need to pass outside of the GATOR Hub. There may be a requirement to pass raw SSES data back to NCI/CONUS. (submitted by CAPT Marshall, CPR 5)
战斗DF功能。LPD 17将被要求在船上具有战斗DF能力。ARG需要多艘船才能具有三角剖分的DF战斗能力。（由马歇尔上尉提交，CPR 5）
AN/KSQ-1集成到JMCIS。这需要使用JMCIS软件（V）2.2或更高版本。特殊船只组使用KSQ-1，以使其可见度低，夜间操作进行位置/跟踪。（由Radm Saffell提交，CpG 3）
独立操作。LPD 17必须能够进行独立的操作。未来的运营将需要扩展的通信和C²比今天的LPD船只所拥有的。LPD 17必须能够在廉价的枪击中生存，因此能够为自己辩护。也可能需要使用SPMAGTF进行分裂ARG操作。（由马歇尔上尉提交，CPR 5）
Advance Force Operations。The LPD 17 maybe the closest ship to the beach because of its ability to survive (vice the other ARG ships), hence would be used as the Advance Force ship. The LPD 17 will need to handle Special Forces and associated equipment; what must come off to take these forces aboard? (submitted by CAPT Williams, Commander Third Fleet, N6)
配置标志- Flag Configured vs. Flag Capable. Any Flag can come aboard for short periods of time. This creates C², communications, and space issues. (submitted by RADM Saffell, CPG 3)
替代国旗船。LPD 17可能必须在ARG中充当替代旗舰。对C的影响是什么²and communication spaces/equipment? (submitted by RADM Saffell, CPG 3)
Precision approach for Aircraft。The LPD 17 will need a precision approach system for aircraft. The ship will enter the Fleet with 1950's technology with regards to aircraft landing/approach systems. This ship should be equipped with low visibility and nightime operation systems (SPN- control/approach radar). (submitted by LtCOL Blankenhorn, I MEF G-7)
LPD 17 C²Space Functional Analysis。Need to conduct a TROOP OPS/LFOC, TACLOG, TACC, SACC space functionality analysis. Who needs what data when and where? What format should the data be in? Who sits where and what is in front of him/her to look at or use? (submitted by LCDR Matters, CPG 3)
LPD 17部队OPS和物流中心。部队操作和物流中心空间需要分为两个独立的空间，因为它们的功能/操作不同。（由LTCOL BLANKENHORN提交，I MEF G-7）
SPS-48E Consoles。The SPS-48E is directly tied to the Advanced Combat Direction System (ACDS) but has old antiquated consoles (1970's technology). Can't the System Commands come up with something better, more useful, and maintenance supported? (submitted by RADM Saffell, CPG 3)
pli。plidata needs to be fused and correlated. PLI data needs to be integrated into the Combat System to help build a Common Tactical Picture. KSQ-1/PLRS is only the first of these new systems coming down the pike, and we need to get our hands around them instead of finding out about them during their installation. (submitted by RADM Saffell, CPG 3)
SI Data。SI数据将留在Gator Hub内。LHA/LHD将充当带有其他两栖船的鳄鱼枢纽，作为集线器（DWTS）的一部分。最终将需要在海滩上建立一个枢纽，以支持岸上扩大的海洋业务。（由Radm Saffell提交，CpG 3）
Common Tactical Picture。ARG needs the ground picture and may need the Allied Picture/Combined Forces picture. KSQ-1 is a start into the ground picture. Will need to bring in Army and Air Force data and fuse/correlate for integrated common tactical picture across the board or at least within the ARG. (submitted by RADM Saffell, CPG 3)

(Return to Table of Contents)

V.其他研讨会评论

一旦您将ARG/MEU拆分，从USMC的角度来看，它不再是MEU。也许它也不再是ARG。
Split ARG = two simultaneous limited missions for a limited period of time.
How independent do we want the ships to be?
XPLOT - where real-time and non-real-time data come together for Tactical SA. (SACC - L, LFOC -L, JIC/SSES - L, Communications Redundancy - F)
Future ships will require functionality already be installed but in a sleep mode/suspended animation until needed.
航空维护-Nalcomis（USMC航空备件订购）。LPD 17有吗？[包装套件（PUK）]
SOF将使用EHF。也向CVBG通信路径进行辩护。
INMARSAT is used with SALTS. Commercial communication systems cannot be used for tactical purpose. (OOTW and Sailor Phone - OK).
Joint Computer Program Management System (JCPMS)- SYSCOM will be used in the future for management and planning?
Combat System needs PLI data as fast as it can get it. (Primary Function, SA - Secondary Function). Joint problem with PLI. Bigger issue in correlation of different PLI data.
地雷战 - 非常浅的矿山检测能力（VSW）现在是一项要求。
Need Mine Environment Decision Analysis Library (MEDAL) function within JMCIS.
Need a common Naval Architecture. Open architecture/flexible.
Where is a Navy SEA DRAGON? The Marine Corps have one now!

(Return to Table of Contents)

附录A：LPD 17 ROC/POE问题乐动冠军

a. Overall comments on the ROC/POE for inclusion are from CPG THREE and THIRD FLEET Representatives:

Link 14 - out
链接16-在
Link 11 SATCOM - in (USQ-125 requirement from CENTCOM)
东海岸将要求LPD由于分裂ARG OPS而具有SHF
自卫：仅反性 - AAW，ASW，等等。
SSES - in
舰队Optas条款已更改：应该反映在
ROC/POE
AAW to AW (Air Warfare)
ASW to UW (Undersea Warfare)
ASUW到SW（表面战）
CRRC - in (Combat Rigid Raider Craft)
RIB - Rigid Inflatable Boat
LPDs have AICs (Air-to-Air) and ASAS (Air-to-Ground) controllers. TACRON DET bring the AICs

b。ROC/POE具体：

AMW 5.5 - include CRRC, RIBS, small boats
CCC 2.11 - AICs aboard - yes
CCC 6.2 - Automated Records - visual
CCC 7.2 - MIL Deception gear required
C²W5 needs a better definition
Need to add micro z/m repair
MIW（海洋哺乳动物）中使用的哺乳动物
Bottom Crawlers for MIW

c. Additional Comments:

Well Deck/Flight Deck - simultaneous operations.
Amphibious Ships are very manpower intensive:
Conditions 1A most stressful
Ship needs lots of line handlers (Deck Dept.)
飞行甲板需要很多处理程序。
Big difference between CRUDES and Amphibs
条件1和1A必须能够处理24小时的连续操作。Flex甲板操作。
MV-22需要解决 - 也需要CH-46。
Ammo Stowage/Handling - HELLFIRE, PENGUIN, etc. plus cross decking ammo.
KSQ-1/PLR应该由海军全面管理
GATOR HUB will need a manager
i-syscon（陆军术语） - 管理/监视 - 如何。
Techcon (Army term)- equipment repair - the who/EMO, will require an information manager (new organization)
Medical - Triage: big space that will only be used 1% of the time; should look into Tele-Medicine
Fleet going commercial - Sailor phone standard on ships now.
USMC going to put TRI-Band in MEF, how will this impact the ship/ARG?(POTS/STEL/Commercial Links)
海军在SHF方面是弱势用户。
TACLOG on LPD 17 has limited functions. Ship will be required to accomplish full missions; may require a full TACLOG.
ROC/POE - INTEL = F AMW = L - wrong priorities
OPNAV ROC/POE instruction is out-dated and needs a revision.

(Return to Table of Contents)

APPENDIX B: WORKSHOP "QUICK LOOK" MESSAGE

rttuzyuw ruwdsgg5828 1231634-uuuuu-rulsacw。
znr uuuuu
RHODAAA T USS ANCHORAGE
罗达巴t uss丹佛
Rhpadxw t uss Rushmore
RHPALHA T COMPHIBRON THREE/USS TARAWA
rhpavju t uss duluth
RHWZMDD T USS FORT FISHER
RUHPEXU T USS CORONADO
RUHPPEL T COMPHIBRON ONE/USS PELELIU
R 021634Z 5月96日Zyb
FM ComphibGru三// 00/N4/N44/N441 //
TO RUENAAA/CNO WASHINGTON DC//N6/N61/N62/N63/N85/N86//
INFO RUEACMC/CMC WASHINGTON DC//C4I/CSBT//
RUWICBE/CG I MEF//01/G2/G3/G6/G7//
RUCKMEA/CG II MEF//01/G2/G3/G6/G7//
ruhbaba/cg iii mef // 01/g2/g3/g6/g7 //
Rhhmhah/Cincpacflt珍珠港HI // N6 //
rulsmca/cg mccdc quantico va // reqr/doct/cwl //
rucbtfa/comnavsurflant Norfolk VA // N2/N3/N4/N4/N432/N6/N621 //
RUWDEAA COMNAVSURFPAC圣地亚哥CA / / N2和N3 /陶瓷/ N432 /N6/N621//
ruhbvma/compribgru
rulyvka/rulyjpx/compribgru两个
RULSSPA/COMSPAWARSYSCOM WASHINGTON DC//05F2/PMW176/PD70//
ruhpqua/comthirdflt // 00m/n6 //
RUCBFAG/EWTGLANT NORFOLK VA//00//
RUWFAFI/EWTGPAC SAN DIEGO CA//00//
rueacmc/marcorsyscom华盛顿特区// c4i/c4idpr //
RUWICCI/MCTSSA CAMP PENDLETON CA//00/FMFSD//
RULSACW/NAVSURFWARCENDIV DAHLGREN VA//F30/F31/F10//
RUWICBA/ELEVENTH MEU
RHPALHA/THIRTEENTH MEU
RUHPPEL/FIFTEENTH MEU
RULSSBI/PEO CLA WASHINGTON DC//00/PMS317/PMS400B//
PHIBGRU THREE AFLOAT
RUWFOAA/NCCOSC RDTE DIV SAN DIEGO CA//00/611/60F//
RUCBCLF/CINCLANTFLT NORFOLK VA//N6//
BT
UNCLAS //N03120//
MSGID/GENADMIN/CPG-3 //
SUBJ/LPD-17 C4I研讨会结果//
REF/A/MSG/CPG-3/112000ZAPR96//
AMPN/MSG ANNOUNCING CPG-3 HOSTED LPD-17 C4I SYMPOSIUM//
POC/B.H. MATHERS/LCDR/CPG-3 N44/TEL: (619) 556-3585/TEL:DSN:526-3585.//
RMKS/1. THIS IS A CG I MEF/COMPHIBGRU THREE COORDINATED MESSAGE.

2. COMPHIBGRU THREE HOSTED AN LPD-17 C4I SYMPOSIUM 30 APRIL-01 MAY 1996. THE INTENT OF THE SYMPOSIUM WAS TO GATHER EXPERTS IN THE FIELDS OF LITTORAL BATTLEFIELD EXECUTION AND C4I SYSTEMS IN ORDER TO DISCUSS LPD-17 C4I OPERATIONAL REQUIREMENTS, SYSTEMS PLANS, AND THEIR RELATIONSHIP TO BOTH CURRENT AND FUTURE ARG/MEU AND INTEGRATED BG OPERATIONS. SYMPOSIUM ATTENDEES RECEIVED OPERATIONAL BRIEFS FROM CPG-3, CPR-5, CG I MEF (G3), WHICH FOCUSED ON ARG/MEU MISSIONS AND CONOPS FROM WHICH C4I REQUIREMENTS WERE DERIVED. ADDITIONAL BRIEFS WERE PROVIDED ON THE CURRENT LPD-17 ROC/POE(PMS 317) AND LPD-17 CURRENT C4I ARCHITECTURE (SPAWAR). THE SYMPOSIUM WAS CONDUCTED IN THREE PHASES: PHASE ONE CONSISTED OF THE INFORMATION EXCHANGE AMONG THE PACIFIC FLEET AMPHIBIOUS TEAM ON THE SPECIFIC MISSIONS AND CONOPS OF THE ARG/MEU FOR BOTH CURRENT AND FUTURE OPERATIONS. PHASE TWO PROVIDED INSIGHTS INTO CURRENT LPD-17 C4I PLANNED ARCHITECTURE AND REQUIRED OPERATIONAL CAPABILITY. PHASE THREE THEN PROVIDED SOME ANALYSIS AND RELATIVE RANKING OF PLANNED C4I SYSTEMS BASED ON OPERATIONAL ASSUMPTIONS FROM THE PACIFIC AMPHIBIOUS FLEET POINT OF VIEW. AS PART OF PHASE III, THE RELEVANT C4I SECTIONS OF THE LPD-17 ROC/POE WERE REVIEWED WITH COMMENTS PROVIDED TO THE SYSTEMS COMMANDS AND PROGRAM SPONSORS. A DETAILED REVIEW WILL BE PROVIDED SEPCOR.

3. THE FOLLOWING ARE KEY PACIFIC AMPHIBIOUS TEAM OPERATIONAL ASSUMPTIONS UPON WHICH A FUNCTIONAL/SYSTEMS ASSESSMENT WAS CONDUCTED. THIS REPRESENTS A QUICK LOOK AT THE RESULTS OF PHASE ONE:
- ARG/MEU（SOC）团队的主要行动集中在三个领域：和平时期前进，应急响应和更大的力量推动者。
-ARG/MEU（SOC）团队应在危机应急操作/回应中获得CRUDES支持。
-LHA/ LHD应作为“鳄鱼”通信/信息中心。定义“鳄鱼”枢纽至关重要。LHA/LHD应该是信息流的渠道，并应拥有与外界的大部分ARG/MEU连接性/触及到背景。它通常应处理ARG的完整SHF汇总，当适用的保险丝时，然后通过适当的系统将信息引导到ARG订户。如果需要在独立操作期间，则应在LHA/LHD和LPD-17之间适当分配SHF聚合物，以便在不超过ARG的分配带宽的情况下向“ Gator”中心提供脐带通信连接。
- ARG COMPONENTS SHOULD ALWAYS REMAIN ON STATION IN DIRECT SUPPORT OF THE MEU(SOC).
- LPD-17 SHOULD BE CAPABLE OF CONDUCTING INDEPENDENT OPERATIONS, INCLUDING SPECIAL PURPOSE MARINE AIR GROUND TASK FORCE (SPMAGTF) CONDUCTING UP TO TWO SIMULTANEOUS, LIMITED MISSIONS; ADVANCE FORCE OPERATIONS; MARITIME PEACETIME OPERATIONS TO INCLUDE OPERATIONS OTHER THAN WAR (OOTW) AND AS ALTERNATIVE COMMAND PLATFORM FROM WHICH THE MEU COMMANDER COULD FIGHT FOR A LIMITED TIME SHOULD THE SITUATION REQUIRE SUCH TRANSFER OF FUNCTION.
-LPD-17必须支持同时飞行和井甲板操作。
-LPD-17必须维持LHD/LHA C4I功能功能的子集，以进行冗余和有限的独立操作。该假设意味着在独立操作或由CATF酌情决定的情况下，包括一个小的“ Gator”轮毂功能并激活。在激活时，应通过ARG的增强来提供MANNING。
-LPD-17任务能力必须等于或大于LPD 7级船只的任务能力。
-LPD-17必须具有有限的SCI能力。
- LPD-17 MUST POSSESS A DEDICATED INTEL SPACE THAT IS PRIMARILY MANNED DURING INDEPENDENT/CONTINGENCY OPERATIONS.
-LPD-17必须在有限的威胁环境中独立生存，并具有自动船的自卫系统。
-LPD-17必须具有C4I设计，该设计有助于登上部队的“插头”。

4. BASED ON THE OPERATIONAL ASSUMPTIONS PRESENTED PARA 3, THE WORKING GROUP THEN ANALYZED THE COMMUNICATIONS, C2 DECISION AIDS AND SENSORS PLANNED FOR LPD-17. A CONSENSUS PROCESS WAS DERIVED IN ORDER TO ACHIEVE NAVY/MARINE CORPS INPUTS INTO THE SYSTEMS. THE FOLLOWING REPRESENT THE WORKING GROUP RECOMMENDATIONS AS FAR AS LPD-17 C4I SYSTEMS.

4A. COMMUNICATIONS:
--HF CAPABILITY IS REQUIRED.
-VHF和UHF视线（LOS）功能安全，需要敏感。
-UHF和SHF卫星通信功能应在很大程度上包括在内，以支持独立操作和ARG操作的冗余。SHF体系结构应支持船上JMCONS架构。EHF被作为海军的要求。不确定未来的海军陆战队EHF要求。
--COMMERCIAL SATCOM SHOULD BE INCLUDED FOR SIMPLEX (GBS) CIRCUITS. FULL DUPLEX (COMMERCIAL WIDE BAND SATCOM) NOT REQUIRED.
- 高带宽，视线数据/语音/视频/视频功能（数字宽带传输系统（DWTS））才能运送和运送到数据和岸上连接，以获取数据和电路交换网络以及虚拟命令和控制。电路交换网络应是互操作的TRI TAC，或必须与TRI TAC系统接口。
--LINK 11 AND LINK 16 FUNCTIONALITY IS REQUIRED.
--SI COMMUNICATIONS (TACINTEL) FUNCTIONALITY IS REQUIRED.
--A FULLY INTEGRATED WIDE AREA NETWORK IS REQUIRED. THE SHIP WIDE AREA NETWORK (SWAN) REQUIREMENT MUST INCLUDE A NETWORK MANAGEMENT CAPABILITY THAT ENABLES NETWORK MANAGERS VISIBILITY INTO THE SWAN OPERATIONS WHILE EMBARKED OR REMOTELY FROM THE "GATOR" HUB. FURTHERMORE, A SYSTEMS CONTROL CAPABILITY ALLOWING THE MANAGEMENT OF THE COMMUNICATION SYSTEM EMBARKED OR REMOTELY FROM THE "GATOR" HUB IS REQUIRED.

4B. COMMAND AND CONTROL/ DECISION AIDS:
--THE PRIMARY MISSION OF LPD-17 IS LANDING MARINE FORCES AS PART OF AN ARG/MEU(SOC) TEAM. THEREFORE, FUNCTIONALITY FOR SUPPORTING ARMS COORDINATION CENTER (SACC), TACTICAL AIRCRAFT CONTROL CENTER (TACC), TACTICAL LOGISTICS AND SUPPORT CENTER (TACLOG), LANDING FORCE OPERATIONS CENTER (LFOC), HELICOPTER DIRECTION CENTER (HDC) IS DEEMED CRITICAL AND ESSENTIAL. LEVEL OF FUNCTIONALITY REQUIRES ADDITIONAL DISCUSSION/REVIEW.
-C2系统应能够将战术，操作，戏剧和相关图片融合到一个系统中。需要JMCIS/GCC功能，并且必须提出一个常见的战术图片，以包括空气，表面和地面轨道以获取位置信息（PLI）。实时和近实时数据的集成应提供情境意识（近/非实时）
--DEDICATED SSES SPACE REQUIRED WHICH IS CAPABLE PROVIDING BOTH ARG SCI PROCESSING REDUNDANCY AND STANDALONE CAPABILITY FOR LIMITED INDEPENDENT OPERATIONS.
-LPD-17应该能够托管/集成随身携带的战斗方向查找设备。
--LPD-17 SHOULD POSSESS THE CAPABILITY FOR COOPERATIVE ENGAGEMENT AND LIMITED SELF DEFENSE (CEC AND SSDS).

4C. SENSORS:
--REQUIREMENTS INCLUDE THE NEED FOR THE STANDARD SHIPBOARD RADARS FOR NAVIGATION, COMMAND/CONTROL, AND SHIP'S SELF DEFENSE. THIS INCLUDES AIR, SURFACE, NAVIGATION, AND FIRE CONTROL.
--THE LPD-17 SHOULD INCLUDE A UNMANNED AERIAL VEHICLE (UAV) CAPABILITY TO CONTROL/TASK, RECEIVE, INTEROPERATE AND DISSEMINATE INFORMATION WITH TRI-SERVICE UAVS.
- 用于航空恢复的“精度方法”系统，并被视为对ACFT至关重要的ACFT，例如V-22和AV-8。
--POSITION LOCATION INFORMATION (PLI) SENSORS REQUIRED. THE ISSUE OF PLI IS PROBLEMATIC FOR AMPHIBIOUS FORCES AND REQUIRES RESOLUTION. IT IS CRUCIAL TO RESOLVE EARLY IN LPD-17 DESIGN PROCESS. RECOMMEND THAT A DEDICATED PLI WORKING GROUP BE CONVENED TO ADDRES THE FULL INTEGRATION OF PLI SENSORS INTO ONE SYSTEM TO AID IN PRODUCTION OF THE COMMON TACTICAL PICTURE. THIS NEEDS TO BE ACCOMPLISHED IN CONJUNCTION WITH AND AS PART OF THE COMBAT SYSTEMS FUNCTIONAL ALLOCATION BOARD (CSFAB) TASKING AS DESCRIBED IN ASSISTANT SECRETARY OF THE NAVY FOR RESEARCH, DEVELOPMENT AND ACQUISITION (ASN (RDA)) LETTER DATED 15 MAR 96 ON COHERENT TACTICAL PICTURE.
- 需要进行预先力量操作和SPMAGTF操作的有机矿山检测能力。这对于武力交付的决策过程至关重要，需要对船只有机。

5.两天的工作非常成功WILL HOPEFULLY ENERGIZE FURTHER DIALOGUE AS LPD-17 DEVELOPMENT EFFORTS EVOLVE. COMPREHENSIVE MINUTES WILL BE AVAILABLE WITHIN 30 DAYS. LCDR BRUCE MATHERS, CPG3 COMBAT SYSTEMS OFFICER, HAS BEEN TASKED WITH COORDINATION OF THE PACIFIC AMPHIBIOUS TEAM LPD-17 ISSUES FOR CONTINUITY, (619)556-3585, E-MAIL MATHERS@NOSC.MIL.//
BT #5828

nnn

(Return to Table of Contents)

APPENDIX C. ACRONYMS

ACDS高级战斗方向系统ACOM大西洋司令部ARG ARPIOUIS READY GROUP ATO ATO ATO ATO TAMENGING bg BAT BAT BLGPHES BGPHES BAT BAT BATERVE GROUT GRATE GROUTE HORIDENS EXTENSION SYSSEM²命令和控制C⁴我命令，控制，通信，计算机，信息c⁴ISR指挥,控制,通信,计算机,我nformation, Surveillance and Reconnaissance CINC Commander In Chief CJTF Commander, Joint Task Force CLA Carrier, Littoral, and Auxiliaries CMC Commandant of the Marine Corps CNN Cable News Network CNO Chief of Naval Operations CNSL COMNAVSURFLANT CNSP COMNAVSURFPAC CO Commanding Officer COC Command (or Combat) Operations Center COMNAVSURFLANT Commander, Naval Surface Force Atlantic COMNAVSURFPAC Commander, Naval Surface Force Pacific COMPHIBGRU Commander, Amphibious Group COMPHIBRON Commander, Amphibious Squadron CONOPS Concept of Operations CONUS Continental United States CTAPS Contingency TACs Automated Planning System CVBG Carrier Battle Group DF Direction Finding DII Defense Information Infrastructure DS/DS Desert Shield/Desert Storm DWTS Digital Wideband Transmission System EDO Engineering Duty Officer EHF Extremely High Frequency EWTGLANT Expeditionary Warfare Training Group, Atlantic GBS Global Broadcast Service (or System) GCCS Global Command and Control System HQMC Headquarters, Marine Corps I&W Indications and Warning IBO Integrated Battle Organization IFR Instrument Flight Rules INMARSAT International Maritime Satellite IPT Integrated Product Team JCPMS Joint Computer Program Management System JIC Joint Intelligence Center JMCIS Joint Maritime Command Information System JMCOMS Joint Maritime Communications Strategy JTUAV Joint Tactical Unmanned Aerial Vehicle LFOC Landing Force Operations Center LOS Line of Sight MARFOR Marine Force MCCDC Marine Corps Combat Development Command MCM Mine Countermeasure MEDAL Mine Environment Decision Analysis Library MEF Marine Expeditionary Force MEU Marine Expeditionary Unit MIW Mine Warfare MRC Major Regional Contingency NAB Naval Amphibious Base NALCOMIS Naval Aviation Logistics Command Management Information System NIPRNET Non-secure Internet Protocol Router Network NMCC National Military Command Center NRaD Navy Research and Development NSWCDD Naval Surface Warfare Center, Dahlgren Division OOTW Operations Other Than War OPNAV Operational Navy (CNO staff) OPTEVFOR Operational Test and Evaluation Force PD Program Director PEO Program Executive Officer PLI Position Location Information PLRS Position Location Reporting System PMS Program Manager-Sea POE Projected Operational Environment PUK Pack Up Kits RFP Request For Proposal ROC Required Operational Capability SABER Situational Awareness Beacon with Reply SACC Supporting Arms Coordination Center SALTS Strategic Arms Limitations Talks SATCOM Satellite Communications SI Special Intelligence SINCGARS Single Channel Ground and Airborne Radio System SIPRNET Secret (or Secure) Internet Protocol Router Network SOF Safety of Flight SPAWAR Naval Space and Warfare Systems Command SPECOPS Special Operations SPN Joint electronics type designation sytem (AN/xxx): Water/Surface-craft Navigation Radar SSES Ship's Signal Exploitation Space SWAN Ship-Wide Area Network SYSCOM System Command TACC Tactical Air Control Center TACINTEL Tactical Intelligence TACLOG Tactical Logistics TAO Tactical Action Officer UAV Unmanned Aerial Vehicle UB Unified Build VSW Very Shallow Water VTC Video Teleconference

(Return to Table of Contents)