1 / 42

Projects Land 75 and Land 125 Battle Management System Industry Brief Bandiana , VIC 22 May 07

Projects Land 75 and Land 125 Battle Management System Industry Brief Bandiana , VIC 22 May 07. Project Director Land 75 . Lieutenant Colonel Michael Toohey Russell Offices (Canberra) (02) 6266 7432. Project Director Land 125. Lieutenant Colonel Craig Oakley Victoria Barracks (Melbourne)

Olivia
Download Presentation

Projects Land 75 and Land 125 Battle Management System Industry Brief Bandiana , VIC 22 May 07

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. Projects Land 75 and Land 125Battle Management SystemIndustry BriefBandiana, VIC22 May 07

  2. Project Director Land 75 Lieutenant Colonel Michael Toohey Russell Offices (Canberra) (02) 6266 7432 Project Director Land 125 Lieutenant Colonel Craig Oakley Victoria Barracks (Melbourne) (03) 9282 6486

  3. Limit of Briefing • This Industry briefing is conducted for the purpose of providing background information only and will not be used to provide potential tenderers with information additional to that contained in the request documentation • Potential tenderers cannot rely on a statement made at this industry briefing as amending or adding to the request documentation unless the amendment or addition is confirmed by Defence in writing Defence Procurement Policy Manual, Chap 5.4, para 48

  4. Agenda • Introduction • Request for Tender/Conditions of Tender • Conditions of Contract • FPS/OSC • Conclusion

  5. Aim • To discuss Request for Tender 06/050 (EWS) • To outline to potential Prime System Integrators (PSI) and sub-contractors key elements of the combined solicitation strategy for the Battle Group and Below Command, Control and Communications (BGC3) capability

  6. Follow-on Activities • For those who are bidding as a Prime System Integrator (and their consortium team members) the following activities will also be conducted: • One-on-one discussions to discuss any areas of clarification conducted IAW COT • Vehicle viewing of the M113 family AS4 variants • Photographs of vehicles will be taken by Commonwealth officers and provided to the potential PSI on request.

  7. BGC3 System • BGC3 Mission System • Battle Management System (BMS) (L75/L125) • BMS-Dismounted • BMS-Mounted • BMS-Command Post • Combat Radio System (CRS) (L125/JP2072) • BMS data • Local & Higher Command voice • Network Management System (NMS) (L125/JP2072) • BGC3 Support System for all the above

  8. Indicative Capability Schedule • Initial Operational Capability – Mid 2009 • A Sub-Unit / Combat Team equipped & trained • Support System operational • Operational Battle Group – End 2009 • Or sooner

  9. Request for Tender • RFT 06/050 released 10 May 2007 • Based on ASDEFCON Strategic Materiel • RFT closes 6 Aug 2007 • Release of Information to Tenderers • UNCLASSIFIED • RESTRICTED • ICT Clearance required for E-copy • Technical Data is Commercial-in-Confidence (not RESTRICTED as previously advised) • OSC, SCGD and Military Pamphlets RESTRICTED

  10. Matters Concerning Response • The Commonwealth seeks responses using the embedded Microsoft XL Spreadsheets within clause 4 of Annex A to Attachment A of the Conditions of Tender • Certain response volumes seek only limited responses at RFT close, with a full response required only by those invited to participate in the Parallel Offer Definition Activity (PODA) • eg. Response to Annex I to Attachment A - Integrated Logistic Support • The Commonwealth will not consider partial responses

  11. Technical Data • Commonwealth has provided Technical Data to enable Tenderers to respond • Requests for additional Technical Data should be directed to the Commonwealth (cf. cl. 5.5.2 in the COT)

  12. Conditions of Tender • Note that Annex J to Attachment A is the PODA Deed • Enclosure 1 to the PODA Deed is the PODA Statement of Work • Note that Attachment B is the BGC3 System Demonstration Instruction • Note the Tender Data Item Deliverables (TDIDs) • Combat Radio System Description (CRSD) • Network Management System Description (NMSD) • System Integration Description (SID) – Vehicle Integration • System Software Description (SSD) • Support System Constituent Capability Description (SSCCD) • Proposed Support System Solution (PSSS)

  13. Tender Evaluation Demonstrations • Four weeks prior to tender closure the Commonwealth will seek confirmation that potential tenderers areinterested inparticipating in the system demonstrations • IAW the BGC3 System Demonstration Instruction (Attachment B to COT) • The Commonwealth will advise of the timings • Tenderers are to provide software, hardware and communications solutions • Type 1 vs Type 2 radios

  14. Tender Evaluation Demonstrations • All demonstrations will be conducted in Canberra, ACT • Demonstrations will be in two parts: • 1. VTT-VMF Compliance test • 2. Bench Top and Range Testing System Demonstration • Initial Screening activity • Failure to pass VTT-VMF Compliance test may lead to Tender being set aside from further evaluation

  15. VTT-VMF Compliance • Desktop compliance demonstration utilising a VMF Test Tool • Conducted during the period 14-21 Aug 2007 (immediately following tender closure) • Individual demonstration will take one day

  16. System Demonstration • Successful completion of VMF Compliance test is a prerequisite • Bench top and Field (Majura) testing demonstration conducted during the period 6 Sep – 4 Oct 2007 • Individual demonstration will take 5 days • Hardware and personnel requirements are detailed in Attachment B of COT

  17. Parallel Offer Definition Activity • At the completion of Tender Evaluation, the Commonwealth intends to enter into a Deed (Annex J to Attachment A to the COT) with one, two or more tenderers to conduct a PODA • The aim of conducting a PODA is to allow selected tenderers to further demonstrate their technical solution to the BMS requirement and refine their offer to the Commonwealth • The Commonwealth will make a “contribution” to costs

  18. Parallel Offer Definition Activity • The schedule is the key driver for the PODA • The final activities, including integration and installation of prototypes into vehicles, will depend on Tenderers responses. • The PODA is expected to be of approximately six months duration • PODA is expected to commence NLT 1st quarter of 2008

  19. Draft Conditions of Contract • ASDEFCON Strategic Materiel Format with tailoring

  20. Parallel Offer Definition Activity • Specific activities and milestones during the PODA include: • Achieving Prototype Design Acceptance (PDA) on vehicle interface solutions • Limited GUI modifications to meet ADF requirements • Achieving Design Acceptance on dismounted soldier interface solutions • Successful completion of System Requirements Review (SRR) • Submission of a refined offer based on work conducted during the PODA

  21. Function and Performance Specification

  22. FPS Clause Reference

  23. Elements of the BGC3 System

  24. Elements of the BGC3 System: S – System D – Dismounted CP-MP – Command Post Man Packable CP-VM – Command Post Vehicle Mounted M - Mounted

  25. Verification Methods: T – Test D – Demonstration A – Analysis I - Inspection

  26. Example: CP Node FPS Requirement 4.1.1.4.a BMS Manoeuvre System: Essential Requirement for the BMS-CP MP Essential Requirement for the BMS-CP VM Will be verified by Demonstration during PODA Will be verified by Inspection during Tender Evaluation (or Both)

  27. BGC3 System • BGC3 Mission System • Battle Management System (BMS) (L75/L125) • BMS-Dismounted • BMS-Mounted • BMS-Command Post • Combat Radio System (CRS) (L125/JP2072) • BMS data • Local & Higher Command voice • Network Management System (NMS) (L125/JP2072) • BGC3 Support System

  28. Battle Management Systems • BMS-Dismounted • Designed for the dismounted Commander from Fire team to and including Battalion Commander • BMS-Mounted • Designed for the mounted Vehicle Commander • Integrated into turreted and non-turreted vehicles, including sub-systems such as Laser Range Finders • BMS-Command Post • Designed for the mounted and dismounted tactical command post. • Sub-unit commander and HQ staff • Unit commander and HQ staff • Other BCSS users up to Div HQ

  29. Battlespace Communications System –Land (BCS-L)System of Systems Environment

  30. BCS(L) – SYSTEM OF SYSTEMS ENVIRONMENT

  31. BCS(L) – SYSTEM OF SYSTEMS ENVIRONMENT BGC3

  32. BCS(L) – SYSTEM OF SYSTEMS ENVIRONMENT JP2008 JP2072 A87 JP129 BGC3 JP2089 A9000 JP2089 L17 L121 & L75 Ph 4 L19

  33. BGC3 Interoperability

  34. (SES)

  35. Essential/Very Important • BMS Manoeuvre System (E) • MIL-STD-2525B - Symbology set. • IPv4; • MIL-STD-6017A with MIL-STD-2045-47001C • Combat Radio System (VI) • Secure and non-secure voice with in-service Combat Net Radio (CNR) equipment specified in Annex B • MIL-STD-188-220B with MIL-STD-188-242 and SINCGARS ESIP waveform. • MIL-STD-188-220B with MIL-STD-188-243 and with HAVEQUICK I/II ECCM waveforms compliant with JIEO 9120A “UHF HAVEQUICK/SATURN Waveform Technical Interface Specification”

  36. Important/ Desirable • BMS Manoeuvre System • Dual Stack IPv4 and IPv6. • Combat Radio System • MIL-STD-188-220C with MIL-STD-188-242 and SINCGARS ESIP waveform. • MIL-STD-188-220C with MIL-STD-188-243 and with HAVEQUICK I/II ECCM waveforms compliant with JIEO 9120A “UHF HAVEQUICK/SATURN Waveform Technical Interface Specification”

  37. Network Latency • Prime Function – Common Operating Picture (including Blue Force Tracks) • Latency requirements • are specified to meet operational need • are not specified to support any particular network topology/design • recognise that at any instant the COP will have information of varying ‘age’ at different organisational levels within the AO.

  38. Network Management • Open Systems • Scalable • Ability for a NMS Manager to plan, deploy, operate and reconfigure the System from any mounted Node or CP • Automate generation of Army SOIs and CEOIs • Ability to test system plans based on expected Operator requirements, terrain analysis and concept of operations • Shall plan, configure, monitor, and manage interfaces to external systems. • The NMS shall assign and de-conflict frequency assignments for current and future system architectures while monitoring current operation

  39. Conclusion • Tender process designed to select a mature BGC3 system • Tender packs for cleared Companies are available in the Foyer after the question time • A L75 WWW Website will be created over the next three weeks • This presentation will be posted on that website • New Land 75 PM BMS – Major Roger Grose (WEF 14 Jun) • Questions may be answered or taken on notice • E-Correspondence bgc3.tender@defence.gov.au

  40. QUESTIONS?

More Related