1 / 10

NDIA / USMC War Game 2007 Command & Control Integration

NDIA / USMC War Game 2007 Command & Control Integration. Cell 3 Out Brief. C2 Integration Issue 1.

manchu
Download Presentation

NDIA / USMC War Game 2007 Command & Control Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NDIA / USMC War Game 2007 Command & Control Integration Cell 3 Out Brief

  2. C2 Integration Issue 1 • Issue: MAGTF C2 Commander-Centric capabilities require shared understanding of commander’s intent and guidance, coordination of executable tasks, collaborative planning, execution, assessment and decision-making support requirements. This inherently requires the integration of displays, processes, data feeds, net-centric services, and necessitates an open, service oriented architecture (SOA) development. This represents the decision-makers interface (command) with the supporting infrastructure (control). This capability must extend across all MAGTF C2 Capability Sets (CAPSETS I – V) from MEF Command to the individual Marine. • Examine this issue in the context of Joint, Naval, Coalition, Inter-Agency C2 viewpoints and provide suggestions, solutions or recommendations. • When examining this issue attempt to: • Identify current and projected technologies supporting this capability • Discuss SOA development to date including lessons learned • Identify unique DOTMLPF needs associated with this capability development, e.g. tactics, techniques, procedure (TTP) modifications; significant bandwidth needs, compression capability, etc.

  3. C2 Integration • Assumptions • Funding is not an issue

  4. C2 Integration Issue 1 • Identify current and projected technologies supporting this capability • Data Strategy Policy to support SOA doesn’t exist • Same issue raised @ MCEITS Industry Day • Multi-level Security – topic for industry white paper • Cross-domain solutions • Information Assurance in a Coalition Environment • IPV4 vs IPV6 • 5 W’s – roll-out….DOTMLPF • Server Virtualization - intermediate step to SOA • Content Mining, Search and Exploitation – how will gov’t articulate this reqt to industry? • Model Driven Architecture – define CAPSET 0 – V architecture configuration • Commercial development environment readily support SOA implementations • BEA WebLogic • IBM WebSphere • Microsoft .NET • Bandwidth management/prioritization across CAPSETS (CCIRs)

  5. C2 Integration Issue 1 • Identify unique DOTMLPF needs associated with this capability development, e.g. tactics, techniques, procedure (TTP) modifications; significant bandwidth needs, compression capability, etc. • Organization • MAGTFC2 Marines or Aviation C2 Marines or Ground Marines • IMO – who’s the advocate? Owns? Trains? • Training: • Intuitive Training – build systems that are intuitive: cut down on training time/cost • Training should be focused on the audience being trained…is it really happening?

  6. C2 Integration Issue 2 • Issue: MAGTF C2 capabilities require “common, modular, scalable” solutions that are fully integrated with in an adaptive, distributed network of commanders, staffs, operating units, supporting organizations, sensors, weapons, and other C2 nodes interacting with one another over an underlying information infrastructure and service oriented architecture (SOA). This capability attribute envisions multi-functional roles for operational facilities (OPFACS), e.g. Direct Air Support Center (DASC) today, and Tactical Air Command Center (TACC) tomorrow, with only minimal adjustment... • When examining this issue attempt to: • Identify current and projected technologies supporting this capability • Identify unique DOTMPLF needs associated with this capabilities development, e.g. occupational skills (MOS) requirements, etc. • Discuss SOA as an enabler in supporting “common, modular, scalable” solutions. • Examine this issue in the context of Joint, Naval, C2 viewpoints and provide suggestions, solutions or recommendations

  7. C2 Integration Issue 2 • Identify current and projected technologies supporting this capability • Our interpretation of multi-functional nodes… • Need an agreed-to definition of multi-functionality • See answers to Issue 1 • We need Industry to identify what is needed from the Marine Corps Systems Command to move us forward…Net-centricity, Industry Standards, Technology Insertion, Industry Design and Development, Engineering, Streamlining of System of Systems • BTW: • Sea-based version of MAGTFC2 – Navy MOC • Distributed Operations • UAS integration/robotics • Is MARSOC a CAPSET player? • Relationship of C2 UUNS to MAGTFC2 PORs • Industry visibility into UUNS • MAGTFC2 in support of homeland defense/DHS • Is MAGTFC2 a weapons system?

  8. C2 Integration • Provide recommendations for NDIA Study Groups • Multi-level security • Bandwidth management/prioritization • ROI for Industry?

  9. C2 Integration • ID Opportunities for increased Collaboration between Industry and USMC • MARCORSYSCOM PG representation • MAGTFC2 POR “belly button” • PEO LS…CAC2S/GATOR, etc • Establish routine dialogue among HQMC, MCCDC, MCSC and Industry • MAGTFC2 TTF

  10. The End

More Related