files: 91

This data as json

rowid	image	timestamp	memento	first_capture	last_capture	current_status	text	mime	status	url	urlkey	digest	length	file_path
91		20060314015624	https://web.archive.org/web/20060314015624/http://www.defence.gov.au:80/dmo/esd/jp2072/wr_industry_brief_16_feb_v1.pps	2006-03-14	2006-03-14	500	JOINT PROJECT 2072 Battlespace Communications System (Land) Joint Project 2072 Battlespace Communications System (Land) David Marshall Director General Communications Joint Project 2072 Battlespace Communications System (Land) LTCOL Andrew Shegog Project Director JP 2072 Joint Project 2072 Battlespace Communications System (Land) Aim • Overview of the Project and capability requirement • Highlight key aspects of the RFT • Highlight key selection criteria and tender deliverables • Describe full Prime Systems Integrator role • Describe the requirements of the SOW Joint Project 2072 Battlespace Communications System (Land) Industry Brief Scope • Scope of Project • Acquisition Strategy • User Requirements • Statement of Work • Conditions of Tender • Conditions of Contract • Tender Deliverable Requirements • Open Forum Joint Project 2072 Battlespace Communications System (Land) Industry Brief Scope • Scope of Project • Acquisition Strategy • User Requirements • The OCD • ASDEFCON Template • Draft Statement of Work Joint Project 2072 Battlespace Communications System (Land) Industry Brief Scope • Conditions of Tender • Conditions of Contract • Technical Regulation in the Land Environment • Security Joint Project 2072 Battlespace Communications System (Land) Joint Project 2072 Project Scope Joint Project 2072 Battlespace Communications System (Land) Project Overview • Multi-phase project – Phase 1 approved Nov 2001 to Dec 07 – Phase 2 YOD 05/06 • Iterative approach to capability development • Minimum development in Phase 1 Phase 1 Approach • Prime Systems Integrator – Define architectural path – Complete Requirements definition and system level design • Prime Equipment Procurement – Provisioning to Bde Sized JTF – Selective solutions to fill current deficiencies • Phase 2 Definition Study • Capability Solution Demonstrators (CSD) AIRFIELD POE TACTICAL UNITS DJFHQ BDE HQ JP 2072 JP 2072 STRATEGIC INTERFACES STRATEGIC INTERFACES L o c k h e e d P - 3 O r i o n AIR & MARITIME INTERFACES COALITION INTERFACES LSF JP 2072 - Battlespace Communications System (Land) JP 2072 - Battlespace Communications System (Land) Joint Project 2072 Battlespace Communications System (Land) Battlespace Communication Systems (Land) Model Current Current Local Sub-System Tactical Data Distribution System Tactical Airborne System Overlaid Comms Systems (Inmarsat, IRIDIUM) Tactical Trunk System Tactical CNR System Supported Subsystems (BCSS, ACSS, NINOX, SDSS) Strategic Comms System Future Future Allied/ Coalition Systems Joint Project 2072 Battlespace Communications System (Land) Current Systems Combat Radio Local Area Tactical Trunk Joint Project 2072 Battlespace Communications System (Land) Phase 1 Capability Gaps • System wide – Not Integrated - Systems are stovepiped and lack interoperability – Ineffective/non-existent Network Management – Joint and coalition interoperability: • Pri 1 - Joint • Pri 2 - US forces • Pri 3 - Other coalition nations – Interfaces to legacy systems as BCS(L) develops Joint Project 2072 Battlespace Communications System (Land) Phase 1 Capability Gaps • Combat Radio Sub-System – Improved Capacity and Efficiency of Tactical Data Nets – Improved voice and data contention – Increased networking capability (not necessarily hierarchical architecture) – Enhanced confidence in HF through reliability of link and capacity (eg. ALE, ALM) – Embedded geo-location system (Automatic Position Location and Reporting) – Provisioning / Supportability of Current Fleet – Coalition interoperability (JTRS as a potential growth path) Joint Project 2072 Battlespace Communications System (Land) Phase 1 Capability Gaps • Tactical Trunk Sub-System – Enhanced bearer capacity, range and networking – Improved data switching – Improved Network Efficiency and Bandwidth utilisation – Integration into greater variety of platforms (LR 110 4x4, M113 ACV) Joint Project 2072 Battlespace Communications System (Land) Phase 1 Capability Gaps • Local Network(s) – Improved deployability and mobility – Rationalised Network Infrastructure – Converged Voice and Data Services • Integrated Network Management – Dynamic bandwidth management – One management system for all sub-systems Joint Project 2072 Battlespace Communications System (Land) Phase 1 endorsed scope • Digitised Bde-sized JTF • JTF based upon: – HQ 3 Bde and JTF manoeuvre units – Includes LSF HQ, RAAF Elms (APOD) and links to DJFHQ • Trunk, Combat Radio and local sub-systems • Priority is data throughput and management • PDS and CSDs to assist development of future phases (TDDS and TAS) Joint Project 2072 Battlespace Communications System (Land) Phase 2 • PCOD Nov/Dec 03, COD Mar 05 • Funding and user need dependant (increased data demand from other projects) • Based largely on Ph 1 solution • Technology ‘refresher’ on Ph 1 solution Joint Project 2072 Battlespace Communications System (Land) Phase 3 • TDDS • TAS and other range extension solutions for TDDS • Continue rollout of BCS(L) in higher readiness units/formations • Technology refresh on earlier phases Joint Project 2072 Battlespace Communications System (Land) Statement of Work Joint Project 2072 Battlespace Communications System (Land) SOW - Document Structure Attachment A - Draft Statement of Work (Part 3) Annex A - Operational Concept Document Annex B- Specifications (TBI) Annex C - Contract Data Requirements List Annex D - List of DMO Checklists Section 2 - General Requirements Section 3 - Project Management Section 4 - Systems Engineering Section 5 - Integrated Logistic Support Section 6 - Configuration Management Section 7 - Verification and Validation Section 8 - Quality Management Program Section 1 - Scope DIDs CHECKLISTS Annex E – Core Work & Orders Annex F – Approved Substances Annex G – PRB TOR Annex H –Trade Studies SOW Annex I – Future Orders Joint Project 2072 Battlespace Communications System (Land) Statement of Work • Based on ASDEFCON (SM) template • Focuses on Core Work only • Orders specific tasks removed from JP 2072 SOW – Will be included at commencement of first Order Joint Project 2072 Battlespace Communications System (Land) Prime System Integrator - Core Work • Establishment of Contractor’s Project Management Organisation – operate through the life of the Contract • Management of the project including all reviews • Requirements analysis leading to development of the FPS, SS and SSSPEC • Conduct of the BCS(L) Trade Study • Development of the Orders Implementation Plan Joint Project 2072 Battlespace Communications System (Land) Prime System Integrator - Orders • IAW Approved Orders Implementation Plan • Issued under the head Contract • PSI SOW amended to include generic clauses • Order specific clauses included as an Annex (I) to the PSI SOW. • Must address shortfalls in the current domains of: – Combat Radio, – Tactical Trunk, – Local Area and – Network Management System Joint Project 2072 Battlespace Communications System (Land) BCS(L) Trade Study • Commenced post, or just before, SDR – Separate SOW at Annex H to PSI SOW • Trade Study Plan is a tender deliverable • Develop Trade Study Plan and Trade Study Report DID during Offer Definition Joint Project 2072 Battlespace Communications System (Land) BCS(L) Trade Study Outcomes • Provide alternative system solutions with a recommended solution • Provide detailed equipment solution to support the recommended system solution • Provide full costs for implementation of recommended solution • Include life cycle costs trade offs for all solutions studied Joint Project 2072 Battlespace Communications System (Land) Orders Implementation Plan • Final deliverable prior to issuing Orders • Based upon outcomes of the Trade Study • Gives a proposed plan for the implementation of the entire system solution – detailed proposal for Phase 1 Orders – less detail for Orders proposed for future phases Joint Project 2072 Battlespace Communications System (Land) DETAILED SYSTEM (SUBSYSTEMS) DESIGN AND IMPLEMENTATION ACQUISITION V&V ILS CORE WORK ORDERS SYSTEM DEFINITION TRADE STUDIES OIP OCD FPS DRAFT SS SS FUNCTIONAL ANALYSIS ANALYSIS REVIEWS VERIFICATION SDR ENGINEERING BASELINES FBL PBL ABL SRR2 SRR1 SYSTEM FUNCTIONAL DESIGN OPERATIONAL ANALYSIS DDR PDR V&V JP 2072 PSI CORE WORK AND ORDERS RELATIONSHIP PROJECT MANAGEMENT TIME QUALITY MANAGEMENT INTEGRATED LOGISTICS SUPPORT MANAGEMENT SYSTEMS ENGINEERING MANAGEMENT Version 2.0 Joint Project 2072 Battlespace Communications System (Land) Prime System Integrator Project Review Board • PSI Company /Project Authority higher management participation • Provide Commonwealth visibility • Provide PSI ongoing policy guidance from Commonwealth • Conduct of Contract Performance Reviews • Issue resolution outside the Project Authority/ Contractor Project Manager relationship Joint Project 2072 Battlespace Communications System (Land) Contract Data Requirements List (CDRL) • DID Maintenance Actions – only required when necessary • DID Format – guide only – content is important Joint Project 2072 Battlespace Communications System (Land) JP2072 Operational Concept Document MAJ Travis Faure’ JP2072 Phase 2 Project Manager “Providing the future NCW communications architecture for the ADF Land Environment” Joint Project 2072 Battlespace Communications System (Land) Topics • JP2072 Final Operational Concept Document (OCD) Overview • OCD Changes – Section One: Scope – Section Two: Definitions and References – Section Three: Capability Needs – Section Four: Existing System – Section Five: System Solution – Annex A: Operational Scenario • Summary Joint Project 2072 Battlespace Communications System (Land) JP2072 Operational Concept Document Overview • The OCD is classified RESTRICTED • CoA sole document for expressing ‘capability requirements’ for JP2072 Describes • Characteristics of required capability • Facilitates understanding ‘Engineering Speak’ • Detail missions • Fitness for purpose Joint Project 2072 Battlespace Communications System (Land) Section One: Scope • Scope • Capability shortfalls • Acquisition boundaries • Context for the project • Network Centric Warfare (NCW) • Multi Dimensional Manoeuvre Joint Project 2072 Battlespace Communications System (Land) Section One • 1.3.1.13 greater explanation of Obj Force • 1.4.1 Rewritten System acquisition boundaries general • 1.4.3.1.1 – rewritten Mission System Outline general – Inclusion of endorsed scope ‘Digitised JTF’ – Inclusion of Endorsed Scope diagram • 1.4.4.4.2 Rewritten Repair and Maintenance • 1.4.5.1 Rewritten Contract Boundary • 1.4.7.1 Rewritten acquisition Strategy Boundaries Joint Project 2072 Battlespace Communications System (Land) Section 2 -References • All references noted have been included on the RESTRICTED CD Joint Project 2072 Battlespace Communications System (Land) Section 3 • New capability requirements • Tactical information network • Medium Intensity Conflict (MIC) • Military Operations in the Littoral Environment(MOLE) Joint Project 2072 Battlespace Communications System (Land) Section 3 • 3.2.8.3 new para levels of Information systems Interoperability (LISI) and table • Figure 3.2 User Organising Principals modified • 3.3 Changed to personnel interfaces to system • Inserted Figure 3.3 Personnel Interfaces • Inserted 3.3.3 user groups (expanded and developed) • 3.3.6.1.4 reworded Under JTF • 3.3.6.7 other FMA units modified Joint Project 2072 Battlespace Communications System (Land) Section 3 • 3.15 Inserted Figure Brigade Main CP • 3.16 Brigade Main HQ Layout • 3.3.8 Manoeuvre Unit inserted • 3.19 Inserted Figure Unit Command Post (CP) • 3.5.2.1 Inserted Table 3-4 : Top Level Operational Needs • 3.5.3.1 Table :3-7 amended to include additional Operational issue Joint Project 2072 Battlespace Communications System (Land) Section 4 -Existing system Overview • 4.1 Rewritten to include all current in service comms systems: – Single channel Radio • RAVEN • WAGTAIL • MBITR • 4.1.6 Expanded detail of Battlespace Telecommunications Network (BTN) • 4.1.11Rewritten Existing Support system Joint Project 2072 Battlespace Communications System (Land) Section 5 -System Solution Description • To be developed by architectural studies as Part Systems Integration contract. Joint Project 2072 Battlespace Communications System (Land) Annex A • Contains – Operational Scenarios – Describe operational business processes – Functional Flow Block Diagrams (FFBD) – Developed using the logical modelling tool CORE Joint Project 2072 Battlespace Communications System (Land) Annex A • Operational activities and needs amended • Modification/revamping to scenario layouts in Table 1-2 • Identification of Operational needs from activity description. Some examples of the operational needs: – interoperability – collabortive planning – management tools – multi level security – spt voice, data and video – automated position and locating data Joint Project 2072 Battlespace Communications System (Land) Annex A – Seemless information transfer b/t nodes – Dynamic allocation of bandwidth – Interface ground to air – Real time information transfer – Precedence management – Transmission of large volumes of data – planning of concurrent operations – Deployable by C130 – Modular and scale in terms of function and performance Joint Project 2072 Battlespace Communications System (Land) Conditions of Tender Joint Project 2072 Battlespace Communications System (Land) General Conditions • No partial tenders • No joint tenders Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • Demonstrated understanding of the end user needs – Summary of Operational Requirement – Overview of architectural direction Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • Mature Systems Engineering Processes – Quality of draft documents – Evidence of mature and documented processes – Evidence of a strong link between corporate R&D programs and project staff – Use of modelling and synthetic environments in developing architectures and proposed solutions Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • Suitability of Project Management Proposal – Proposed PM structure – Suitability of draft PMP – Past PM Performance – Identified Key Staff Positions and skill sets identified for Orders – Evidence of mature and documented PM processes Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • Suitability of Project Management Proposal – Proposed plan to meet the EVM of the SOW – Demonstrated ability to manage risk – Adequacy of risk assessment – Evidence of good subcontract management record – Sound Product Evaluation Procedure Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • Australian Industry Involvement – level of AII likely to be achieved with each proposal – key areas in which AII likely to be achieved Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • System Support – demonstrated ability to implement and manage complex system support mechanisms – the maturity and scope of the organisation’s ILS management and processes – evidence of organisational skills in Life Cycle Cost (LCC) analysis • draft LCC Management Plan Joint Project 2072 Battlespace Communications System (Land) Key Selection Criteria • Contractual issues – past performance – compliance with JP 2072 contract conditions • Cost issues – cost of core work components in SOW – rates for personnel for future work – level of overhead applied to future work Joint Project 2072 Battlespace Communications System (Land) PSI CONTRACT • Contract Structure • Risk share and performance requirements • Ownership of IP • PSI interaction with third parties • Warranty Joint Project 2072 Battlespace Communications System (Land) Tender Deliverable Requirements Major Steven Welsh JP 2072 Phase 1 Manager Joint Project 2072 Battlespace Communications System (Land) Tender Deliverables • A single DOORS 5.2 Project Archive .dpa file ( on CD ) – with supporting external files in softcopy • 6 Paper copies of all modules, OLEs and external files Joint Project 2072 Battlespace Communications System (Land) 6 Paper copies each in vol 1-8 in accordance with TDRL • Vol 1 – Overview • Vol 2 – Commercial • Vol 3 – Financial ( no financial information elsewhere in paper copies, it will appear in the DOORS archive with appropriate CoT Annexes ) • Vol 4 – Project Management • Vol 5 – Technical • Vol 6 - AII • Vol 7 – ILS • Vol 8 – Offer Definition Joint Project 2072 Battlespace Communications System (Land) DOORS 5.2 References • JP 2072 Tender Response Guidelines v2.0 • JP 2072 Tender Response Diagram v3.0 – Minor change from issued in RFT Package • Available in hardcopy or on 2072 website Joint Project 2072 Battlespace Communications System (Land) Summary Respond? Response Note to tenderer etc False Tenderers are to specify ……….. True An executive summary and relevance of supporting documents goes in here… Next point …. True Next summary … Next point2 …. True Next summary2 … Next point3 …. True If referring to an External Supporting File, a description of the appropriate section is required ie. Para 1.2.3. All RFT modules that require a response in RESPONSE view RFT JP2072/Conditions of Tender/Supporting Information Folder in DOORS 1. Supporting Information Index 1.1 Doors Modules 1.1.1. Supporting Module Title A brief description of nature and relevance of supporting module. 1.1.2. Next Supporting DOORS Module Title A brief description of nature and relevance of supporting module, in this case a large document. 1.1.2.1. Details of subset1 of large document 1.1.2.2. Details of subset2 of large document 1.2 External Files 1.2.1. Supporting External File Title A brief description of nature and relevance of supporting information, highlighting specific paragraphs that are applicable. RFT JP2072/Conditions of Tender/Supporting Information/Supporting Information Index Supporting Information Folder(s) ( sub-folders if reqd ) 1.1.1. Supporting Information Module (with OLE if reqd) - Module Title (first object in module) - key supporting object (description of OLE relevance ) 1.1.2. Next Supporting Information Module - Module Title (first object in module) - key supporting object(s) The DOORS Links module is to contain all linkset information for all 1st, 2nd level and Indexing links. Formal Module properties should be set to create link module pairings, enabling drag and drop linking. RFT JP2072/Conditions of Tender/Supporting Information/ DOORS Links Next Supporting Information Module ( subset 1) - Subset Module Title (first object in module) - key subset supporting objects Next Supporting Information Module ( subset 2) - Subset Module Title (first object in module) - key subset supporting objects 2nd Level Links From subset supporting objects to main supporting objects. Linkset information to DOORS Links module. 1st Level Links From supporting document objects to RFT objects. Linkset information to DOORS Links module. Indexing Links From subset and main supporting objects, to the applicable object in the Supporting Information Index. Linkset information to DOORS Links module. >5 MB External File <5 MB OLE Embedded Version 3.0 Joint Project 2072 Battlespace Communications System (Land) Further DOORS Guidance • Switch to DOORS Joint Project 2072 Battlespace Communications System (Land) Key Tenets • Develop long term relationship • Systems Engineering focus at the outset • Integration skills essential • System design to implementation and support • Broad range of technologies required • Phase 1 focused on available technologies • Management of technology insertion and refresh • Value for money through life Joint Project 2072 Battlespace Communications System (Land) PSI Qualities • Architectural design capability and experience • System engineering capability • System integration capability • Objectivity and vendor neutrality • Subcontract management • Introduction into service experience • System support capacity Joint Project 2072 Battlespace Communications System (Land) Delivery Details • Postal Defence Mail Services Department of Defence CANBERRA ACT 2600 Tender number 03/018ES BCS(L) 12 PM 29 April 2004 • Personal Delivery Defence Mail Services Queanbeyan Annex 6 14-22 Wycombe St QUEANBEYAN NSW 2620 Tender number 03/018ES BCS(L) 12 PM 29 April 2004 Joint Project 2072 Battlespace Communications System (Land) Communication • www.defence.gov.au/dmo/esd/jp2072 – Unclassified package in DOORS 5.2 and Microsoft Word • RFT questions – Faxed to 02 62652618 – Attn: PD JP 2072 • One on One Question Sessions – Be at R3 Security Desk 10 minutes prior to allocated time JOINT PROJECT 2072 Battlespace Communications System (Land)	application/vnd.ms-powerpoint	200	http://www.defence.gov.au:80/dmo/esd/jp2072/wr_industry_brief_16_feb_v1.pps	au,gov,defence)/dmo/esd/jp2072/wr_industry_brief_16_feb_v1.pps	3YQN3BMNGD32QWJFC5XORWCVFX2OEKXM	697538	domains/defence-gov-au/powerpoints/original/au-gov-defence-dmo-esd-jp2072-wr-industry-brief-16-feb-v1-pps-20060314015624.pps