LCPM_Pre_Solicitation_Conference_Final.pdf

PDF 3 MB Posted

Attached to
Life Cycle Product-line Management (LCPM) Draft Request for Proposal
Solicitation number
W900KK-17-R-0023
Issued by

About this file

Jan 10th, 2017 Pre-Solicitation Conference Slides

View the file

Other files

File Type Posted
LCPM_Draft_RFP_Questions_and_Answers_9Jun2017.pdf PDF
Attachment_7.0_Draft_IMTS_DO_0002.pdf PDF
Attachment_10_Industry_Question-Comment_Form.pdf PDF
Attachment_6.0_Draft_HPL_DO_0001.pdf PDF
Attachment_7.2_Draft_IMTS_Performance_Spec_01Feb17.pdf PDF
Attachment_6.1_LCPM_DO_0001_HPL_SOW_14Mar2017.pdf PDF
Attachment_6.3_LCPM_HPL_DO_0001_CostPrice_Workbook_8Feb17.xlsx XLSX spreadsheet
LCPM_Draft_RFP_Amendment_1_SF33_Sections_A-M__14Mar17.pdf PDF
Attachment_5_Work_Request_Procedures.pdf PDF
Attachment_1_LCPM_BASE_SOW_09Feb2017.pdf PDF
LCPM_Presolicitation_Conference_Attendees.pdf PDF
Attachment_7.4_LCPM_IMTS_DO_0002_CostPrice_Workbook.xlsx XLSX spreadsheet
Draft_RFP-W900KK-17-R-0023_LCPM_(Sections_A-M).pdf PDF
Attachment_6.1_LCPM_DO_0001_HPL_SOW_02Nov16.pdf PDF
Attachment_15_Work_Requests.pdf PDF
Attachment_16_Delivery_Order_Procedures_DRAFT.pdf PDF
Attachment_11_SF1408-14.pdf PDF
Attachment_1_LCPM_BASE_SOW_02Nov16.pdf PDF
Attachment_7.2_Draft_IMTS_Performance_Specification.pdf PDF
Attachment_8_LCPM_Reference_Matrix-Needs_Updating_after_IMTS_SPEC_is_complete.xlsx XLSX spreadsheet
Attachment_10_Solicitation_Clarification_Form.pdf PDF
Attachment_2_LCPM_Solicitation_DD254.pdf PDF
Attachment_6.0_Draft_HPL_DO_0001.pdf PDF
Attachment_4_Data_Item_Transmittal.pdf PDF
Attachment_3_SB_Participation_Form.pdf PDF
Attachment_7.1_LCPM_DO_0002_SOW_02Nov_16.pdf PDF
Attachment_5_Work_Request_Form.pdf PDF
Attachment_12_Inst_for_the_LT2_Portal.pdf PDF
Attachment_6.2_LCPM_DO_0001_HPL_CDRLS.pdf PDF
Attachment_6.3_LCPM_HPL_DO_0001_CostPrice_Workbook.xlsx XLSX spreadsheet
Attachment_7.3_LCPM_DO_0002_IMTS_CDRLS.pdf PDF
Attachment_13_LT2_Portal_Documents.pdf PDF
Attachment_7.0_Draft_IMTS_DO_0002.pdf PDF
Attachment_9_LCPM_PPQ_for_Solicitation_W900KK-17-R-0023.pdf PDF
Attachment_7.1_LCPM_DO_0002_SOW_02Nov_16.pdf PDF
LCPM_Presolicitation_and_Site_Visit_Registration_Form.xlsx XLSX spreadsheet
Attachment_12_Inst_for_the_LT2_Portal.pdf PDF
Attachment_6.1_LCPM_DO_0001_HPL_SOW_02Nov16.pdf PDF
Attachment_1_LCPM_BASE_SOW_02Nov16.pdf PDF
Show all 39

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

UNCLASSIFIED

Agile – Proficient – Trusted UNCLASSIFIED As of 25-Oct-12

ACC Orlando

January 10, 2017

W900KK-17-R-0023

Life Cycle Product-line

Management (LCPM)

Pre-Solicitation

Conference

Agile – Proficient – Trusted

UNCLASSIFIED

Introduction

Ms. KeYanna Boone

Contracting Officer

UNCLASSIFIED

Introduction

• Ms. KeYanna Boone – Contracting Officer

• Mr. Jason Holden – Contract Specialist

• Mr. Jim Griffith – Program Lead LCPM

• Mr. Michael Craven – Engineer Lead LCPM

UNCLASSIFIED

Agenda

1:00 – 1:10PM Ground Rules/Purpose

1:10 – 1:40PM LCPM Requirements Overview

1:40 – 2:10PM Draft RFP Overview (Sections A-J)

2:10 – 2:20PM Break

2:20 – 2:50PM Draft RFP Overview (Sections L & M) and Source Selection Process Overview

2:50 – 3:00PM Questions

UNCLASSIFIED

Ground Rules

• All attendees must sign in

• Attendees are not authorized to enter any areas requiring badge access

• Please silence your cell phones

• No recording is allowed

• Slide presentation information can be found in the “draft” solicitation (W900KK-17-R-

0023), and is based on the best information available (slides will be posted via the

FedBizOpps website (www.fbo.gov)

• The information provided is notional and is not to be considered binding. All discussions, including the solicitation and Q&A is subject to modification or cancellation

• The draft solicitation is not a formal request for proposal and does not commit the

Government to procure any goods or services

UNCLASSIFIED

Ground Rules (continued)

• Questions are welcomed during or after each briefing

– Write your question(s) on the note cards provided and turn them in prior to leaving

– Provide a POC in case follow-up is necessary

• Official answers to all industry questions will be published on the FedBizOpps website

(www.fbo.gov)

• Questions to the “draft” solicitation are due January 23, 2017

• Contracting Officer and Contract Specialist are the only POCs for communication between the Government and industry regarding the LCPM procurement

UNCLASSIFIED

Purpose of Pre-Solicitation Conference

• The goal of this event is to provide industry with the most up-to-date information about the Life Cycle Product-line Management (LCPM) effort and to solicit comments on the current draft solicitation

• To ensure industry’s understanding of the Acquisition Strategy

• Discuss RFP structure, technical requirements and Source Selection methodology

• Provide overview of sections L&M to assist industry in proposal preparation

UNCLASSIFIED

Points of Contact

KeYanna Boone

Contracting Officer

Army Contracting Command – Orlando

12211 Science Drive

Orlando, FL 32826-3224

Telephone number: 407-380-8078

E-mail: Keyanna.r.boone.civ@mail.mil

Jason Holden

Contract Specialist

Army Contracting Command - Orlando

12211 Science Drive

Orlando, FL 32826-3224

Telephone number: 407-208-3312

E-mail: jason.n.holden.civ@mail.mil mailto:Keyanna.r.boone.civ@mail.mil mailto:jason.n.holden.civ@mail.mil

UNCLASSIFIED

LCPM Overview

Mr. Michael Craven

Engineer Lead LCPM

UNCLASSIFIED

Overview

• The evolution of the LT2 P/L programs and life cycle management for Product Managers operating within the training domains from stove piped approaches to a product line implementation.

• Ensure system relevancy via a consolidated, streamlined approach that protects, leverages and matures the Army’s LT2 investment.

• Reduce the life cycle sustainment and maintenance costs by providing a strategic approach to identifying and standardizing common hardware components that can be used across PM TRADE programs.

UNCLASSIFIED

Objective One

• A contract vehicle for live training systems to perform life cycle sustainment in support of the LT2 Family of

Training Systems (LT2 FTS) and other DoD customers adopting the LT2 Product-line.

– Technology refreshment

– Obsolescence management

– Concurrency

– Technology insertion

– Upgrades

– Disposal for LT2 systems

– Support LT2 programs

– Other DoD customers

LCPM

JPMRC-IS

DRTS

Target Mod

I-MTS

CMUR

Other LT2 Users

CTC

MOUT-IS

HITS

UNCLASSIFIED

Objective Two

• The LCPM contract will establish a deliberate approach to Life Cycle Management (LCM)

– Leverage the successful contract strategy demonstrated by CPM with a hardware centric focus.

– Implement a Hardware Product Line (HPL) to find opportunities for cost avoidances

LT2 core process, procedures and tools

Eliminate stove piped contract execution

Use common COTS devices across programs

Improve system maintenance while reducing total ownership costs

Reduce life cycle footprint (HW, tech data, spares, etc.)

Improve realism and relevancy

UNCLASSIFIED

LCPM Goals

• Proactively address all life cycle phases

• Maintain or improve system performance/relevancy and operational readiness

• Improve system maintenance while reducing total ownership costs

• Ensure standardization, commonality, synchronization, maximum reuse, core asset reuse, and interoperability

• Align with the business goals of PM TRADE:

– Reducing Operational Cost & Complexity

– Aligning & Supporting Product Development (common standards, interfaces)

– Enhancing Soldier Training Effectiveness

– Reducing Sustainment & Development Costs

– Increasing Technology Agility

– Leveraging Other Army Systems

– Increasing training realism, relevancy, and usability for the Warfighter

UNCLASSIFIED

Stove Pipe Example

REQUIREMENTS

- Large Engine

- Large Transmission

- Large Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Large Engine

- Large Transmission

- Large Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Medium Engine

- Large Transmission

- Medium Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Medium Engine

- Medium Transmission

- Medium Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Small Engine

- Medium Transmission

- Small Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Small Engine

- Small Transmission

- Small Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

1 2 3 4 5 6

UNCLASSIFIED

Product-line Example

REQUIREMENTS

- Large Engine

- Large Transmission

- Large Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Large Engine

- Large Transmission

- Large Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Medium Engine

- Large Transmission

- Medium Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Medium Engine

- Medium Transmission

- Medium Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Small Engine

- Medium Transmission

- Small Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

REQUIREMENTS

- Small Engine

- Small Transmission

- Small Wheels

- GPS Navigation

- Vehicle Computer

- Location Tracking

Large Engine Large Transmission Medium Transmission Small TransmissionMedium Engine Small Engine

LT2 Core Assets

HPL

SPL

- Owners/Operator manual

- Maintenance procedures

- Service procedures

- Testing/troubleshooting

- Diagrams/drawings

- Reduced Spares

- Common Training

Common components/reuse

UNCLASSIFIED

Key Roles

- Software Product Line

- PDSS

- PPSS

- LT2 core assets

- Construct

Government

WFF/ATMP

- On Site Operations

- Maintenance & Repairs

- Spares

- Supply & Depot

- Training support

Operations and Maintenance

LCPMCPM NEXT

Original Fielding

Lifecycle Sustainment

- New locations

- New programs

- OEM system

- NET/ICS

- Original Documentation

- Hardware Product Line

- Continuous Technology

Refresh (CTR)

- Technology insertion

- Concurrency

- Upgrade

- Disposal

- Obsolescence

OEM Fielding

Contractor

LT2 Ops Guide / ICDs

- Tools

- Standards

- Processes

- Governance

Software centric efforts Hardware centric efforts

UNCLASSIFIED

Timeline Example (Stewart CACTF) Initial

Fielding

SW

Upgrade

HW

Upgrade Full

CTR Disposal

Operations and Maintenance

SW

Architecture

Technology

Insertion

End of Life

SW

Upgrade

HW

Concurrency

CPM Next LCPM WFF/ATMPProgram of record contractor

Full

CTR

Program XYZ

Life-Cycle Contract Roles

8 Years 8 Years End of Life

End of Life

Year 3 Year 6 Year 13 Year 16 Year 23

10 Years

Year 27

Year 1

PDSS / PPSS

Year 30

You are here

Fielded

UNCLASSIFIED

Delivery Order Changes

Requirements

Design

Procure

Install

Integrate

Test

Training

Documentation

Configuration

Data

Delivery Order 0001 Delivery Order 0003 - n

Manage HW P/L

Standards

Process

Procedures

Tools

Portal

Integration

WFF Data

Data

Feedback

Delivery Order 0002

P/L Analysis

Multiple programs

To establish P/L

Requirements

Design

Procure

Install

Integrate

Test

Training

Documentation

Configuration

Data

Delivery Order 0001

Delivery Order 3

Manage HPL

Standards

Process

Procedures

Tools

Portal Integration

WFF Data

Data

Feedback

Delivery Order 0002

I-MTS CTR

P/L Analysis

Multiple programs

To establish P/L

Delivery Order 4…

Previous Current

UNCLASSIFIED

Base SOW

• The Base SOW for LCPM defines the scope and breadth of tasks that can be performed under the various envisioned DOs

– Program Management

– Engineering

– Logistics

– Information Assurance

– Hardware Product Line

– LT2 Governance

– CPM Next / WFF / ATMP Synchronization

UNCLASSIFIED

DO 0001 SOW (HPL)

• Establish

– Analyze current systems and future objectives

– Develop an HPL that will satisfy PM TRADE’s performance requirements

• Manage

– Tools, process, and governance

– Synchronizing with established LT2 processes and standards as defined on the

LT2 Portal

– Metrics and Return on Investment (ROI)

– Use of RAM and data analytics

• Evolve

– Providing a methodology and oversight to be used across future delivery orders as a guide to making HPL decisions

– Technology awareness and roadmap

– Introduction of new requirements/stakeholders

– Obsolescence and diminishing sources

UNCLASSIFIED

DO 0002 SOW (I-MTS)

• I-MTS Continuous Technology Refreshment (CTR)

– Combined Arms Collective Training Facilities (CACTF)

Ft. Stewart, GA

Ft Indiantown Gap, PA

Ft Drum, NY

Ft Polk, LA

– Automated Shoothouse (ASH)

Ft Stewart, GA

Gowen Field, ID

FT Bragg, NC

Cp Shelby, MS

Cp Bullis, TX

• DO 0002 also contains a Performance Specification for the I-MTS program

UNCLASSIFIED

DO 0003 - n

• Subsequent Delivery Orders will be utilized by the programs to award contract actions for individual efforts

• Each DO will have a unique SOW (and Spec)

• The DOs will utilize the DO 0001 functions/tools to provide an analysis for impact and application to the

HPL as well as providing feedback via the LT2 portal

• The DOs will encompass the phased implementation of the developed Hardware Component Agreements

(HCAs)

UNCLASSIFIED

LT2 Documentation

• Draft RFP Documentation

– This folder contains documents (SOWs) associated with the draft release.

• Final RFP Documentation

– This folder is currently empty and will be updated when the final RFP is released.

• I-MTS Site Survey Data

– This folder contains a significant amount of data that has been gathered by the

Government teams for the I-MTS locations identified in DO 0002. It includes pictures, drawings, inventories, and a site survey report for each location.

• LT2 Background Info

– This folder provides a consolidated location for reference material on LT2. For example, the Interface Control Documents and Operations Guide.

• PM TRADE System Requirements

– This folder contains the requirements (i.e. Performance Specifications) for the major programs in PM TRADE. These documents are intended to be used by the offerors in their evaluation of the TRADE portfolio as part of the analysis for the creation of the HPL in DO 0001.

https://www.lt2portal.mil/

UNCLASSIFIED

Draft RFP Overview (Sections A-J)

Mr. Jason Holden

Contracts Specialist

UNCLASSIFIED

Draft RFP Overview (Section A)

• Single-Award, Indefinite-Delivery/Indefinite-Quantity (SA ID/IQ) contract with a five year ordering period

• Offerors shall complete blocks 14 thru 18 of the SF 33 as part of the final RFP

• Proposals shall be valid for 365 calendar days after submission

• Each individual Delivery Order will have its own Contract Type, Contract Line Item Number (CLIN) Structure, and individual requirement

• Delivery Orders 0001 and 0002 will be awarded concurrently with the SA ID/IQ contract

• Contract Ceiling is $465,000,000.00

• The minimum guarantee amount is $3,000.00

• The North American Industry Classification System (NAICS) code for this acquisition is 333318

UNCLASSIFIED

Section B – Supplies or Services and Prices

• B.1 CLINs 0001 through 1000 are established in Section B of the solicitation/contract for administrative purposes

• Pricing for CLINs will be at the individual Delivery Orders

• Offerors shall utilize the cost/pricing workbooks (Attachments 6.3 and 7.4) to price Delivery Orders 0001 and 0002

• B.2 Offerors shall complete the fee and/or profit rates in Section B.2 which will be applicable to all delivery orders awarded from the basic

ID/IQ contract

UNCLASSIFIED

Section C – Descriptions and Specifications

• Statement of Work (SOW) reference (PEO-STRI-14-W095, Version

1.0)

• Personnel Qualifications

– Contractor responsible for employing qualified management, technical and support personnel to perform the basic contract and any subsequent orders

– Contractor personnel shall possesses the required security level clearance

– Government reserves the right to review resumes of key personnel and any substitutes, as applicable at the Delivery Order level

• Technical Data

– A representative list of the types of Contract Data Requirements Lists (CDRLs) are listed in the SOW

• Contractor Manpower Reporting Application

UNCLASSIFIED

Section E – Inspection and Acceptance

• Inspection and Acceptance will be performed by the Government which will be specified at the individual Delivery Order level and generally be at Destination.

UNCLASSIFIED

Section F – Deliveries or Performance

• The LCPM contract will commence on the date of contract award and continue for a period of 60 months.

• Technical Data and Information shall be delivered in accordance with the requirements of the Contract Data Requirements List, DD

Form 1423, as specified in individual Delivery Orders.

• Each Delivery Order will specify the applicable delivery date(s).

UNCLASSIFIED

Section G – Contract Administration Data

• Contractor’s Authorized Contract Coordinator and Technical Liaison

• All funding for the resultant contract will be provided on the individual Delivery Orders

• Designation of Contracting Officer’s Representative (COR) will be identified at time of award

• Clause to note: 252.232-7006 Wide Area Workflow Payment

Instructions – to be completed at the Delivery Order level

UNCLASSIFIED

Section H – Special Contract Requirements

• H.1 Delivery Order Types

• H.2 Security Classification

• H.3 Small Business Participation

• H.4 Availability of Data Item Descriptions (DIDs)

• H.5 Government Installation Work Schedule

• H.6 Disclosure, Use and Protection of Proprietary Information

• H.7 Liability Insurance

• H.8 Reimbursement of Travel, Per Diem, and Special Material Costs

• H.9 Allotment of Funds

• H.10 Authorized Changes Only by the Contracting Officer

• H.11 Technical Direction Letter Instructions

• H.12 Organizational Conflicts of Interest

UNCLASSIFIED

Section I – Contract Clauses

Clauses to note:

• 52.216-19 Order Limitations

• 52.216-22 Indefinite Quantity

• 252.216-7006 Ordering

UNCLASSIFIED

Section J - Attachments

• Attachment 1 Basic SOW, PEO-STRI-14-W095, Version 1.0

• Attachment 2 DD254

• Attachment 3 Small Business Participation Form

• Attachment 4 Data Item Transmittal / Acceptance / Rejection Form

• Attachment 5 Work Request Form

• Attachment 6.0 HPL Delivery Order 0001

• Attachment 6.1 SOW HPL, PEO-STRI-15-W096, Version 1.0

• Attachment 6.2 HPL CDRLs

• Attachment 6.3 HPL Cost/Price Workbook

• Attachment 7.0 IMTS Delivery Order 0002

• Attachment 7.1 SOW IMTS, PEO-STRI-15-W094, Version 1.0

• Attachment 7.2 SPEC IMTS, PRF-PT-668, Version 1.0

• Attachment 7.3 IMTS CDRLs

• Attachment 7.4 IMTS Cost/Price Workbook

UNCLASSIFIED

Section J - Attachments

• Attachment 8 Requirements Matrix

• Attachment 9 Past Performance Questionnaire

• Attachment 10 Clarification Form

• Attachment 11 SF1408

• Attachment 12 Instructions for the LT2 Portal

• Attachment 13 LT2 Portal Documents

• Attachment 14 Reserved

• Attachment 15 Work Request Procedures

• Attachment 16 Delivery Order Procedures DRAFT

UNCLASSIFIED

BREAK

10 Minutes

UNCLASSIFIED

Draft RFP Overview (Sections L&M)

Mr. Jason Holden

Contract Specialist

Mr. Jim Griffith

Program Lead LCPM

UNCLASSIFIED

Section L – Instructions, Conditions and Notice to Bidders

• The LCPM source selection will encompass two distinct portions: 1) A pre-recorded video presentation and 2) A written proposal.

• The video presentation and written proposal will be evaluated together, as a single submission, using the same evaluation factors/subfactors.

• Offerors are advised to register for an account in the LT2 portal to access necessary information for proposal preparation. An LCPM collaboration area has been established on the LT2 portal for supporting documentation. The

LT2 portal is accessible at www.lt2portal.mil.

UNCLASSIFIED

Section L – Instructions, Conditions and Notice to Bidders

• Video Presentation Summary/Guidelines

– Pre-recorded video presentations shall be submitted by each offeror to augment their written proposals.

– Each offeror shall video tape various speakers presenting for no longer than a total of 2.5 hours.

– The presenters should use slides during their presentation; however, no more than 75 total slides are to be utilized during the total video presentation.

– The video presentation will be considered in conjunction with the written proposal.

– The speakers during the video presentation shall be team members (i.e. program management, technical personnel) who will work or perform a key role on the

LCPM effort.

– If information presented in the video presentation differs from the written proposal, a weakness or deficiency may be generated, which may result in an unfavorable adjectival rating.

UNCLASSIFIED

Section L – Instructions, Conditions and Notice to Bidders

• Written Proposal

– Written proposal will be comprised of the (1) PowerPoint Presentation to the video; (2) Technical Papers covering each subfactor in Factor, 1

Technical, and each subfactor in Factor 2, Management; (3) Written information for Factor 3, Small Business Participation Plan, Factor 4, Past Performance, and Factor 5, Cost/Price; and (4) Administrative

Information.

– In preparing the written proposal, each offeror is encouraged to focus on its unique ideas and solutions to satisfying the Government requirements.

UNCLASSIFIED

Section L – Instructions, Conditions and Notice to Bidders

VOLUME TITLE

I Video Presentation Slides

Technical and Management Papers

Factor 1 Technical

Subfactor 1.1: Hardware Product Line Implementation

Subfactor 1.2: Hardware Product Line Engineering

Subfactor 1.3: Cybersecurity and Logistics

Factor 2 Management

Subfactor 2.1: Overall Management Approach

Subfactor 2.2: Delivery Order Implementation

II Factor 3 Small Business Participation Plan

III Factor 4 Past Performance

IV Factor 5 Cost/Price

V Administrative Information

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I)

L.6.1. Subfactor 1.1: Hardware Product Line Implementation [20 page limit, Paper 1]

The offeror shall describe their understanding and experience with the Live Training Transformation (LT2) Product-Line philosophy and the LT2 Product-Line Domain. The offeror shall describe their approach for using the LT2 philosophy and domain for the development of the LT2 Hardware Product-Line (HPL). The offeror shall describe their strategy for managing the interactions between the LT2 HPL and existing LT2 Software Product Line to ensure compatibility of products, ease of component reuse, and reduction in life cycle costs.

The offeror shall describe their process, approach and tools for establishing and evolving the LT2 HPL and identifying the hardware components for inclusion into the LT2 HPL. The offeror shall describe their processes for leveraging the

LT2 core assets to include components, services, tools, and governance framework for the LT2 HPL while managing lifecycle costs, schedule and performance through the life of the program. The offeror shall describe their strategy for forecasting and implementing hardware changes, due to obsolescence, high failure rate, and more cost effective components, across the LT2 HPL. The offeror shall describe their strategy for implementing innovative solutions across multiple DOs/LT2-Domain.

The offeror shall describe their approach to requirements' management as each new DO is implemented and how requirements management will impact the LT2 HPL. The offeror shall describe their approach and processes for ensuring that all future systems/capabilities/DOs utilize the LT2 HPL while ensuring the LT2 HPL remains relevant to existing LT2 programs and stakeholders. The offeror shall describe their vision and plan to maintain the LT2 HPL, as more programs utilize the LT2 HPL, resulting in cost and complexity avoidance, increased performance, and higher quality products. The offeror shall identify the impacts the on-going LT2 HPL evolution will have on existing programs already utilizing the LT2 HPL and a mitigation strategy to address those impacts.

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I)

L.6.1. Subfactor 1.1: Hardware Product Line Implementation [20 page limit, Paper 1] (continued)

In preparing its written response to this subfactor, the offeror should consider the information below.

The Project Manager Training Devices (PM TRADE) live training domain includes the Live Training Transformation (LT2) product line. This product line consists of open architectures, common components, standards, processes, policies, governance, documentation, and other core assets that make up the common approach and frameworks for developing live training systems. Examples of the many types of training systems in the LT2 product line domain include: Military

Operations on Urban Terrain (MOUT), Home Station, Combat Training Centers (CTCs), instrumented live-fire range training, and other LT2 users’ systems to include the Marine Corps.

The LT2 vision has been and continues to be to create a family of live training systems using common methodologies

(e.g.; common architecture and common data, standards, processes, components and services). This commonality facilitates the rapid development of new products but also ensures that products across the LT2 product line can communicate and interoperate with each other. This is important because large training exercises need to employ different kinds of training systems working together. The LT2 product line makes use of plug and play components, services and applications that are common between products, and permits changes, upgrades and fixes developed for one product to be applied to others. This concept provides the inherent logistics support benefits that derive from commonality, standardization and interoperability including the reduction of total life cycle costs.

The LT2 focus is to support the LT2 vision to evolve common live training solutions and to improve cost efficiencies in a resource-limited environment, thereby to:

• Protect the significant live training investment.

• Provide for the continued development, production, and sustainment of LT2 products and ease the insertion of new and disruptive technology.

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I)

L.6.1. Subfactor 1.1: Hardware Product Line Implementation [20 page limit, Paper 1] (continued)

• Realize objectives for return on investment and sustainment cost avoidance.

• Enable managers to maintain visibility and provide enhanced configuration control of their systems, to avoid duplicating efforts.

It is the objective of the LCPM contract to develop a HPL by ensuring standardization, commonality, synchronization, maximum reuse, core asset reuse, and interoperability within the PM TRADE’s live training systems to include the LT2

P/L. The HPL should allow the Government to save significant resources (time and funding) in the future by utilizing this approach. This paper will inform the Government as to how the contractor will achieve these objectives.

Hypothetical scenario: PM TRADE currently has multiple programs of record with fielded systems in various locations requiring both CTR and hardware obsolescence resolution. These programs of record have not completed their CTR and obsolescence management requirements in anticipation of LCPM addressing their comprehensive life-cycle management tasks. The paper shall cover the technical aspects of the hypothetical scenario where the Government issues five delivery orders(DO)s all within 120 days after the basic contract award and the award of DO 0001 and DO

0002. The scenario will include additional DOs for the following programs of record:

a. Digital Range Training System (DRTS) at three locations

b. Target Modernization at 20 locations

c. Joint Pacific Multinational Readiness Capability Instrumentation System (JPMRC-IS) at one location

d. Homestation Instrumentation Training System (HITS) at two locations

e. An additional 10 Integrated MOUT Training System( I-MTS) locations

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I) L.6.2 Subfactor 1.2: Hardware Product-Line Engineering [15 page limit, Paper 2]

The offeror shall describe their technical understanding and experience with a hardware centric product line regarding a product's or product-line's configuration throughout the entire lifecycle from concept development to disposal. The offeror shall describe their experience with continuously managing complex interdependent changes of a hardware centric product line initiated by various technical factors (changes, enhancements, innovations) and business stakeholders. The offeror shall identify and address the significant challenges/risks and accompanying mitigations associated with the implementation and management of a hardware centric product line.

The offeror shall describe their strategy for maintaining awareness of existing and emerging technologies that align with the LT2 Product-Line Domain. The offeror shall describe their strategy for forecasting and implementing new capabilities in the LT2 HPL due to technology improvements. The offeror shall describe their plan for incorporating existing, evolving and disruptive capabilities, new technologies, and/or new system implementations into the LT2 HPL in order to reduce the logistics footprint and total ownership costs across the LT2 Product-Line domain as well as increase the relevancy/realism of the training. The offeror shall describe their near and long term implementation goals of LCPM and how they support innovation, lifecycle impacts, benefits, cyber security tradeoffs via a technology roadmap.

The offeror shall describe their approach to identify, collect, analyze, present data in support of the HPL implementation and describing the Government's Return on Investment (ROI). The offeror shall describe how they will use metrics and analytics to measure and quantify the ROI that their HPL has achieved in support of the PM TRADE business goals.

The offeror shall detail their plan to utilize metrics and analytics to facilitate decision making of the implementation, integration, deployment, evolution, support and sustainment of the HPL.

The offeror shall describe and provide evidence of how their proposed technical approach to lifecycle management will benefit (i.e. reduced costs and footprint, increased capability) the Government for the LT2 programs while increasing training realism and relevancy.

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I)

L.6.2 Subfactor 1.2: Hardware Product-Line Engineering [15 page limit, Paper 2] (continued)

In preparing its written response to this subfactor, the offeror should consider the information below.

The below paragraphs provide context specifically for the Tech Roadmap:

One of the main methodologies for the Army to maintain system relevance and to achieve life-cycle cost savings is through the development and insertion of new technologies into its training systems and the management of the training systems. All of the training systems, the HPL, and the processes/tools used to manage the product lines need to evolve over time in order to remain relevant and to provide realistic training to the ever changing threats the Army faces. The

Tech Roadmap will provide insight into how the contractor will help the Government achieve these objectives.

The below paragraph provides context for the metrics:

The offerors proposed metrics shall be divided into two different segments for LCPM. There shall be metrics which allow the Government insight to the benefit LCPM has provided and metrics applied to the data from the HPL and fielded systems.

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I) L.6.3 Subfactor 1.3: Cybersecurity and Logistics [15 page limit, Paper 3]

The offeror shall describe their processes and methodology for meeting DoD and Army Cybersecurity requirements for all components, infrastructure, and systems fielded while ensuring initial Risk Management Framework (RMF) compliance, ease of transition to Post Deployment Software Support / Post Production Software Support (PDSS/PPSS) for sustainment, and leveraging LT2 cybersecurity processes including Security Technical Implementation Guide (STIG) and

Information Assurance Vulnerability Alert (IAVA) implementation. The offeror shall describe their approach to security engineering given a migration to a distributed network infrastructure to address secure configuration management, RMF compliance, and continuous monitoring of assets.

The offeror shall describe the tools and processes it will use to obtain, analyze and share life cycle sustainment data in accordance with the LT2 Data Interface Control Document (ICD). The offeror shall describe their processes and the data analysis tools that will be used to ensure supportability goals are an integral part of their Total Life Cycle System

Management (TLCSM) strategy. The offeror shall describe their tools and processes to identify Diminishing Manufacturing

Sources/Material Shortages (DMS/MS), obsolete components and failure rate trends to establish a proactive system configuration management program to optimize the LT2 HPL.

The offeror shall describe their overall approach for meeting DO 0001, DO 0002, and future DOs logistics support requirements that will ensure efficient life cycle system operation and maintenance is maximized for current and future upgrades. The offeror shall describe their TLCSM strategy, to include how the offeror will minimize the use of new or unique system parts, support equipment, personnel or maintenance skills. The offeror shall describe their TLCSM approach for system level hardware and software components, to include how the offeror will minimize future upgrade costs, support the LT2 HPL evolution while meeting system upgrade requirements across current and future DOs.

Inclusive to this description is the offeror's ability to minimize long-term costs associated with future upgrades for the system components. The Offeror shall describe their strategy and procedures for developing and/or managing the

Logistics Product Data / Logistics Product Data Summaries (LPD/LPDS), training materials, and technical documentation for DO 0002 and future delivery orders.

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I)

L.6.3 Subfactor 1.3: Cybersecurity and Logistics [15 page limit, Paper 3] (continued)

In preparing its written response to this subfactor, the offeror should consider the information below.

The concept for the LCMP contractor will be to ensure cybersecurity compliance during implementation of technical refreshes and hardware updates to LT2 Product-line systems with sustainment then being performed by a Post

Deployment Software Support (PDSS) contractor. The LCPM contractor should ensure the system is optimized and configured to provide cybersecurity sustainment in a cost effective and efficient methodology requiring the least amount of labor hours during sustainment as resources are reduced and cybersecurity requirements increase. The

Government will expect the LCPM contractor to develop innovative concepts, procedures, and technology insertion recommendations to reduce the cybersecurity burden once the system is transitioned to the PDSS contractor.

Cybersecurity compliance may require either a full certification event with a third party validation team or an internal cybersecurity assessment, depending on the scope of the technical refresh or hardware replacement. The determination of cybersecurity compliance will be specific to each DO. The LCPM contractor will be responsible for security engineering, IAVA implementation, and cybersecurity documentation updates required by the DO.

One of the biggest challenges the Government has is to create an efficient and cost effective transition for a technical refresh as sustainment is transferred to the PDSS contractor. In many cases the PDSS contractor must reengineer the system to create efficiencies in sustainment to reduce the amount of travel to the site. The end goal is to manage the system’s cybersecurity requirements when cybersecurity personnel are not resourced to be on site, leveraging the operator/maintainer when necessary for simple, documented procedures.

UNCLASSIFIED

Section L – Factor 1-Technical (Vol I)

L.6.3 Subfactor 1.3: Cybersecurity and Logistics [15 page limit, Paper 3] (continued)

The onsite travel and reengineering by the PDSS contractor could be eliminated if the LCPM contractor creates a transparent, efficient, and documented process. Remote management of the system’s cybersecurity compliance does not always mean a highly innovative approach is the only solution. PM TRADE is attempting to leverage innovation to make cybersecurity compliance more cost effective and secure, however basic industry best practices that could serve as near term solutions and immediately achievable given our use case are requested as well.

Hypothetical Scenario:: The XYZ Program currently has twenty one systems fielded in various CONUS and OCONUS locations. The LCPM contractor will perform an upgrade that will become the new baseline for the type accreditation of

XYZ program.

The below paragraph to provide context for Logistics Management:

One of the biggest challenges that TRADE faces in its life-cycle management of its programs is the on-going requirements to keep their systems operational after the Original Equipment Manufacturer has completed fielding of the system and it has transitioned to STRI’s life-cycle sustainment contractor. The Government is looking for ways to improve the logistics processes as they pertain to life-cycle management, for example performing failure rate analysis, planning for rather than reacting to obsolescence, reducing sustainment costs, reducing the cost/time required to develop logistical documentation, etc. This paper will provide insight into how the contractor will help the Government achieve these objectives.

UNCLASSIFIED

Section L – Factor 2-Management (Vol I)

L.7.1 Subfactor 2.1: Overall Management Approach [20 page limit, Paper 4]

The offeror shall describe their overall management plan for executing the LCPM program management, contract and administrative management requirements of the contract and subsequent DOs. The offeror shall describe their proposed organizational team structure to manage the LCPM program over the life of the contract. The offeror shall describe the roles of critical positions, internal project team and supporting corporate organizations (i.e. teaming partners and subcontractors). The offeror shall also explain their vision for the management lines of authority and responsibilities to accomplish the LCPM DOs with external teams (i.e., PEO STRI sustainment contractors, the

Government, and the Consolidated Product-line Management (CPM) Next team). The offeror shall identify any challenges associated with managing the scope of the LCPM contract and describe their mitigation strategies to address the challenges identified.

The offeror shall provide their Integrated Master Schedules (IMS) covering all the work performed under DO 0001 and

DO 0002. The IMS shall identify key milestones, timelines, critical paths, and the linkages between the DOs including all options.

The offeror shall describe their risk and opportunity management (good idea) process relative to LCPM. The offeror shall identify all anticipated key risks with the LCPM requirements, goals and objectives (for example; the creation and implementation of the LT2 HPL, management challenges, contractor relations). The offeror shall provide a mitigation plan for each identified risk. The offeror shall describe potential opportunities relative to LCPM and the LT2 Product-Line domain, including potential future benefit and their process for pursuing opportunities in partnership with the

Government.

UNCLASSIFIED

Section L – Factor 2-Management (Vol I)

L.7.1 Subfactor 2.1: Overall Management Approach [20 page limit, Paper 4] (continued)

In preparing its written response to this subfactor, the offeror should consider the information below.

The below paragraph provides context for life-cycle management: Currently, PM TRADE conducts fielding and total system life-cycle management for a diverse array of live training systems through an equally diverse mix of contracts.

The LCPM contract’s objective is to consolidate the contractual execution of life-cycle management toward unity of effort and to also implement a HPL to achieve cost savings and standardization of hardware components to the greatest practicable extent. The challenge for the Government is to effectively and efficiently manage the roadmap toward an HPL with an emphasis on knowledge of legacy systems and integration of new and emerging technologies back into the HPL. Governance of these methodologies will be implemented by the LT2 Core Asset Working Group

(CAWG), industry partners, the LCPM contractor, CPM Next contractor, Warfighter Focus and Army TADSS

Maintenance Program (ATMP) contractors, PM TRADE Assistant Product Managers for their individual programs, and

PM TRADE leadership. The LCPM contractor must be able to seamlessly integrate into the governance framework and provide responsive support to the diverse mix of PLs affecting PM TRADE objectives.

The below paragraphs provide context for IMS: The contractor shall provide an IMS as reference document as a

Microsoft Project file. The IMS shall only identify items at the task level (no additional details) and will not be included in the page count. The paper shall cover the offerors Integrated Master Schedule (IMS) to include dependencies and linkages between DO 0001 and DO 0002. Plan for teaming, subcontract management plan, small business goals, ability to adjust staffing and resource allocation methodology in support of LCPM shall be addressed. It shall also cover the management concept and planning that is common amongst the DOs (existing and future).

UNCLASSIFIED

Section L – Factor 2-Management (Vol I)

L.7.1 Subfactor 2.1: Overall Management Approach [20 page limit, Paper 4] (continued)

The paper shall cover the offeror’s plan to execute DO 0001.

The effort to stand up the Hardware Product-Line forms the initial basis for achieving a workable HPL. As such, the background work on the HPL must be conducted in a logical and timely manner in order to expeditiously establish the

HPL and realize cost-benefits of stream-lined operations. The standing up of the HPL will entail the analysis of multiple systems/programs at multiple sites to establish baseline criterion and then synthesize the base data back into the HPL.

This paper shall cover the offerors plan on how they will execute the establishment of the HPL as part of the DO 0001 effort.

The DO 0002 effort is indicative of the typical Continuous Technology Refreshment (CTR) scope of a LCPM contract

DO. The Government is seeking a level of innovation and strategy to employ the initial HPL and to make this effort more efficient and cost effective as the initial HPL continues to evolve and mature. This paper shall cover the offeror’s plan to execute DO 0002. It shall cover the identification, mitigation, and implementation of management and technical risks/challenges for this DO. It shall cover the analysis to meet the LCPM goals while contributing to the HPL objectives as they pertain to this DO. It shall cover the offerors management approach to perform CTR for the multiple Integrated

MOUT Training System (I-MTS) sites.

UNCLASSIFIED

Section L – Factor 2-Management (Vol I)

L.7.2 Subfactor 2.2: Delivery Order Implementation [20 page limit, Paper 5]

The offeror shall describe their approach for managing multiple DOs concurrently, each with their own set of requirements, schedules and Government teams, while maintaining the integrity and objectives of the LT2 HPL. The offeror shall describe their personnel scalability strategy for assembling teams to meet expanding requirements, when additional DOs are awarded in parallel with existing DOs. The offeror shall describe their task organization of project teams to ensure that the requisite skills and experience base associated with the supported system are sufficiently represented to complete the each distinct DO. The offeror shall describe their approach regarding implementation of programmatic processes supporting multiple Government Project Leads The offeror shall describe their methodology for selecting subcontractors and ensuring maximum competition at the subcontract level, managing subcontractor performance and problem resolution for the individual DOs.

The offeror shall describe their approach for ensuring their project teams, including subcontractors and/or team members, fully participate and comply with the LT2 governance process to accomplish DO requirements. The offeror shall describe how they will enforce the overarching goals and objectives of the LT2 Product-Line and the reuse methodology established in DO 0001 while managing the future DO requirements.

The offeror shall describe their approach to managing overall cost, schedule and performance and how those elements will be balanced to ensure the Government's requirement are met. The offeror shall also include its Configuration

Management plan for managing the evolution of the LT2 HPL assets over time as well as managing variation within the

LT2 Product-Line domain.

UNCLASSIFIED

Section L – Factor 2-Management (Vol I)

L.7.2 Subfactor 2.2: Delivery Order Implementation [20 page limit, Paper 5] (continued)

In preparing its written response to this subfactor, the offeror should consider the information below.

The offeror shall address the following potential scenario in its description of the management of multiple DOs: PM

TRADE currently has multiple programs of record with fielded systems in various locations requiring both CTR and hardware obsolescence resolution. These programs of record have not competed their CTR and obsolescence management requirements in anticipation of LCPM addressing their comprehensive life-cycle management tasks. This paper shall cover the management aspects of the hypothetical scenario where the Government issues five delivery orders all within 120 days after basic contract award and the award of DO 0001 and DO 0002. The scenario will include additional DOs for the following programs of record:

a. Digital Range Training System (DRTS) at three locations

b. Target Modernization at 20 locations

c. Joint Pacific Multinational Readiness Capability Instrumentation System (JPMRC-IS) at one location

d. Homestation Instrumentation Training System (HITS) at two locations

e. An additional 10 Integrated MOUT Training System( I-MTS) locations

UNCLASSIFIED

Section L – Factor 3 - Small Business

Participation Plan (Vol II) L.8.1 Small Business Participation Plan

The Small Business Participation Plan shall stand on its own merit without reference to a separate Small Business

Subcontracting Plan that is required for large businesses. The information provided should assume that no cross-reference will be checked, and that all claims, approaches, and statements must be clearly articulated in their entirety within the proposal volume being submitted. The Small Business Participation Plan will be incorporated into any resulting contract award.

All offerors, both small and large businesses, are required to submit a Small Business Participation Plan that shall clearly demonstrate a viable plan for meeting or exceeding the Small Business Participation goal of no less than

[20-30%] (The Government anticipates the goal will be within this range, and will specify the exact goal in the

Final Solicitation) of the ID/IQ $465M total contract value (cumulative of all DOs) in the five year ordering period with representation from small business (SB), small disadvantaged business (SDB), service disabled veteran owned small business (SDVOSB), woman owned small business (WOSB) and Historically Underutilized Business Zone small business (HUBZones). For example, a delivery order award funded in the amount of $1,000,000 would have a small business participation goal of at least [$200,000-300,000] (The exact amount will be specified when the goal is established in the Final Solicitation). Small business offerors can meet the small business participation goal through performance as a prime small business, or a combination of performance and small business subcontracting.

UNCLASSIFIED

Section L – Factor 3 - Small Business

Participation Plan (Vol II) L.8.1.1 All offerors, both small and large businesses, are required to submit Small Business Participation Plan information in accordance with DFARS 215.304 that shall include the following:

a) Type of Business of Prime Contractor

Check all applicable boxes and fill out all applicable fields:

[ ] Large

[ ] Small (also check type of Small Business below)

[ ] Small Disadvantaged Business

[ ] Woman-Owned Small Business

[ ] HUB Zone Small Business

[ ] Veteran Owned Small Business

[ ] Service Disabled Veteran Owned Small Business

b) Total Contract Value: $465,000,000

c) Dollar Value performed by offeror as a Prime Contractor: $__________

UNCLASSIFIED

Section L – Factor 3 - Small Business

Participation Plan (Vol II)

d) Identify the proposed Dollar Value and Percentage of Total Contract Value awards to both large and small business.

All percentages should use TOTAL CONTRACT VALUE as a baseline. Include only first tier U.S. subcontractors.

Note 1: Small includes: Small Business (SB), Small Disadvantaged Business (SDB) (including HBCU/MI), Women-

Owned Small Business (WOSB), HUBZone small business (HUBZone), Veteran-Owned Small Business (VOSB), and

Service-Disabled Veteran-Owned Small Business (SDVOSB). Only include once regardless if represented in multiple groups.

Note 2: Include the prime offeror’s dollars and percentage.

e) The Offeror shall populate the following table to identify all anticipated Prime and subcontracted supplies/services.

When combined, Prime and anticipated subcontracted totals must equal 100% of the Estimated Contract Ceiling Value of $465M. The sum of the Estimated Total Dollars for Each Service/Supply for the stated SB subcontractors should ultimately lead to achieving the Small Business Participation goal of no less than 20-30% (participation goal to be finalized in the Final solicitation). The Offeror shall create as many rows in the table as necessary to adequately identify all subcontractors.

Dollar Value Percentage of Total

Contract Value

Large: $ %

Small: $ %

Total: $ 100%

UNCLASSIFIED

Section L – Factor 3 - Small Business

Participation Plan (Vol II) Pursuant to Sections 8(d) of the Small Business Act, a concern is small for subcontracts which relate to Government procurements if it does not exceed the size standard for the NAICS code that the prime contractor believes best describes the product or services being acquired by the subcontract. In other words, the size of your subcontractors and suppliers is determined by the NAICS code of their subcontract, which may or may not be the same NAICS code as the one for your prime contract with the Government.

The Offeror shall provide a short description of the specific services to be provided and the nature of complexity by each SB, the rationale supporting SB selection(s), and the estimated total dollar value for each service. Complexity is defined as the level of involvement for performance of functions provided by the SB concerns. The Offeror shall provide an explanation pertaining to the process the Offeror uses for identifying and selecting SBs for subcontracted work and how the process will be used on this contract to meet the Offeror’s SB Participation goal.

f) Extent of Commitment

The Offeror shall provide documentation regarding individual and enforceable commitments to utilize any Small

Business, as defined in FAR Part 19, as subcontractors. Copies of such commitments should be provided as part of your small business participation plan.

Name of Company

(Include CAGE Code)

Anticipated NAICS Code for Each Subcontractor

Type of

Service/Supply

Estimated Total Dollars for Each Service/Supply

Prime Offeror: N/A

Large:

Small:

UNCLASSIFIED

Section L – Factor 3 - Small Business

Participation Plan (Vol II)

g) Prior Performance Information

All Offerors shall substantiate past utilization of SBs. This evidence shall consist of three past relevant contracts to include evidence of attainment of Small Business Participation goals as a percentage of Total Contract Value/Price over the past three calendar years to include goal identification and achievement. A SB Offeror shall include its own performance in the documentation. Any information concerning long-term relationships with SB subcontractors, such as mentor-protégé relationships, supporting the Offeror's past utilization of SBs on relevant contracts, should be reported.

In addition, all Offerors are to provide a description of performance, over the past three calendar years, in complying with the requirements of FAR 52.219-8, Utilization of Small Business Concerns to include a description and available documentation of the methods employed to promote SB utilization, the internal methods used to monitor such utilization, and any other information substantiating that the Offeror will satisfy the requirements of FAR 52.219-8.

Large Business Offerors shall provide proof of compliance with the requirements of FAR 52.219-9, Small Business

Subcontracting Plan,…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .