1 / 24

IPR #2 NATO Sea-Strike 21, Team 2 Paid Proposal - Phase 0

IPR #2 NATO Sea-Strike 21, Team 2 Paid Proposal - Phase 0. Trigui Lead Systems Engineer for Operations / Subcontractor Precision Company , Inc. Topics. Mission Needs Statement NSS-21 Operational Concept Architecture Definition Options & Choice Software Subcontractor Summary.

willa
Download Presentation

IPR #2 NATO Sea-Strike 21, Team 2 Paid Proposal - Phase 0

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. IPR #2NATO Sea-Strike 21, Team 2Paid Proposal - Phase 0 Trigui Lead Systems Engineer for Operations / Subcontractor Precision Company, Inc.

  2. Topics • Mission Needs Statement • NSS-21 Operational Concept • Architecture Definition Options & Choice • Software Subcontractor • Summary

  3. Mission Need Statement • A mobile precision strike cell is required in order to command and control US, Allied and NATO strike forces against the TBM launcher threat • Mission – Plan, task, execute and assess precision strike against TBM launchers in-theatre in support of NATO requirements

  4. MNS Needs • NATO needs a 24-hour, reliable and integrated command and control cell which is not vulnerable to TBMs, local unrest, or terrorist violence • Reduce precision strike timelines compared to the current capability by improving target location, identification, weapons effectiveness and combat assessment. • Advance precision strike concepts of employment including real-time weapon sensor cueing, near real-time data dissemination, seamless sensor-to-shooter node communications and dynamic retargeting. • A mobile (ship-based) C&C cell is needed to perform this mission • NATO Sea- Strike 21

  5. MNS Needs Fundamental Priniciples of TMD • Centralized Planning and Control with Decentralized Execution • Will allow integrated defense concepts to be developed and implemented • Decide, Detect and Deliver • Allows use of preapproved rules of engagement and battleplans that permit flexible decentralization schemes • Maintains continuity of operations and integrated tactical missile defense.

  6. MNS Threat • SS-1B/C ‘SCUD’ - Short-Range TBM • Mobile Launchers • Fast Setup (<30 min) and Removal • False Targets New TBM Threats continue to be developed Existing threats are being upgraded

  7. MNS Threat • Turkish/Cypriot Instability • Ship-based Command Cell avoids civilian riots and potential terrorist cells compared to a shore-based C&C cell Design architecture will be suitable to land and mobile based applications

  8. MNS Threat • Land-based Cell Vulnerability • Syria/Iraq/Iran sole/combined forces in pre-emptive attacks • Diyarbakir vulnerable from each threat nation SCUDs targeting strategic forces and capabilities • SCUD range includes Ankara, other NATO bases inside Turkey • NATO Sea-Strike 21 counters this threat

  9. MNS Requirements • Prototype cell must be operational • System must be supportable in the long-term • Hardware and software • Maintainable by NATO detachment & ships force • Interfaces with… • Ship’s systems for navigation, communications & data links, SIPRNET, ship’s internal voice net circuits, & power • NATO personnel – User interfaces must meet NATO tactical symbol standards & language requirements

  10. NSS-21 Proposed Schedule Schedule MAR APR MAY JUN JUL AUG SEP • Deploy • Deploy System • Leave Behind Support • Training/TTP Package • ARCHITECTURE TRADE OFFS AND DECISION • All Users Considered • PMO Review • PMO Approve • Demonstrate and Refine • Assessment Analysis • System Refinement • System Integration • TTP Refinement Initial Planning & Analysis DEMONSTRATION LAN & CLIENT/ SERVER USER SOFTWARE SHIP INTEGRATIONC SHIP TEST SHORE-BASED BUILD Operations Warfighter Assessments (US, NATO, CAOC, PSC)

  11. MNS Requirements • Interoperable with: • Microwave link to shore command CAOC • Integrated Air Defense Commander (IADC) • AOCC • MASSTIC • BICES • RPC net / RAP • US & Allied air and ground forces via TADIL-J and HF/UHF communications

  12. MNS Constraints • Command ship cannot accommodate large contingent –footprint must be small • Schedule – war imminent - 6 Months • Costs - $5M budgeted for prototype cell • PMO directed software subcontractor in order to meet 6 month goal • Drives the requirement to re-use previously developed architecture and software • Contract specifies all hardware will be new

  13. MNS Alternatives • Shore-based cells – vulnerable to TBM • Air-Based cells - >1 year development • There are no viable alternatives to NSS-21 that: • Are not vulnerable to the TBM threat • Allow direct, in-theatre C & C of forces • Will be deliverable in 6 months

  14. NSS-21 Cell Concept • Manning requirements: • O-6 NATO Commander – Senior Operations Officer • Leadership corps - 4 officers/NCOs • Twelve cell operators • Four 3-person teams • Guidance & support by leaders • Ships space – 5m x 9m, 3m high • Subdivided into command, operations and plan/task/assess compartments

  15. Cell Conceptual Spaces Actors Strike Ops Task Operations Area Server Area Plan Plan/Task/Assess Area Assess SOO Area & Access Control Assess

  16. Real-time Operations Area • Direct links to weapons • Visible from command area • Isolated from Planning area • Separate Server (Redundant) from Planning / Tasking /Assessing area

  17. Architecture Definition • Object-oriented architecture • Hardware, software and people included • User-Case examination determines players and functions • Abbreviated user-case definition period (2 weeks) due to time constraint • Object-oriented design for future upgrades and flexibility • Ensure requirements are well understood prior to system design/integration

  18. Architecture Definition • O-O architecture provides inheritance, encapsulation, minimizes mistakes in developing requirements • Allows for future upgrades with reasonable efforts • Will work with software sub to implement the O-O methodology

  19. Actors • CAOC Coordinator • Cell Commander – Senior Ops Officer • TAO • Strike Force Coordinator (SFC) • Weapons Controller (2) (WCs) • Weapons Planner • Weapons Tasker • Battle Damage Assessor

  20. User Processes • Add current available weapon • Assign available weapon • Designate target/weapon pairing • Designate weapons loitering area • Assign loitering weapon • Assemble ATO • Submit ATO

  21. Software Subcontractor • Directed by PMO to subcontract S/W • OPAINC has developed CAOC software • Excellent teamwork in developing requirements • Certification -- SEMM Level 5 (Optimizing) by CMI 3/1/00

  22. Subcontractor Roles • OPAINC will be the end-to-end software developer • Improved system integrity and interoperability • Leverage the company’s experience in this area • PCI will integrate the software, hardware, people • OPAINC has submitted software architecture and Budget • OPA budget will fit within overall PCI budget for NSS-21 cell • Current SW architecture provides inputs for developing NSS-21 architecture

  23. Software Layer Hierarchy Sensor Processing Weapon Planning Weapon Execution Database Control Comm Control ATO Prep Maps Executive Communications Windows NT 2000 O.S.

  24. Summary • NATO Sea Strike will be field-ready in time for currently unfolding conflicts • Initial field prototype ready in 6 months • User-Case examples used to ensure system design complete and flexible • Software Sub developing end-to-end software solution per requirements

More Related