MSC Industry Day 1-08-10.ppt

PPT presentation 4 MB Posted

Attached to
RECOVERY Mobile Surveillance Capability (MSC) Federal contract opportunity
Solicitation number
HSBP1010R2914
Issued by
Department of Homeland Security Customs and Border Protection

About this file

MSC INDUSTRY DAY POWERPOINT PRESENTATION

View the file

Other files for this federal contract opportunity

Other files attached to RECOVERY Mobile Surveillance Capability (MSC), newest first.
File Type Posted
MSC UCF SOLICITATION3.3.10.pdf PDF
MSC SF 30 3.3.10.pdf PDF
MSC SF 30 A00006 2.24.10.pdf PDF
MSC UCF SOLICITATION2.24.10.pdf PDF
MSC Past Performance Questionnaire2.19.10.doc DOC document
MSC SF 30 A00005 2.19.10.pdf PDF
MSC Q A 2.19.10.pdf PDF
MSC UCF SOLICITATION2.19.10.pdf PDF
MSC Past Performance Table2.19.10.doc DOC document
CBP_Training_Development_Standards_Oct_2008_107pgs.pdf PDF
MSC A00004 2.5.10.pdf PDF
REVISED MSC RFP HSBP1010R2914.pdf PDF
Mobile Surveillance Capabilities Matrix —
MSC Q A 2.5.10.pdf PDF
MSC Environment Objectives —
Attendees01.08.10.doc DOC document
HSBP1010R2914 A00002.pdf PDF
Mobile Surveillance Capabilities Matrix —
MSC Past Performance Questionnaire.pdf PDF
MSC Operational Description —
MSC RFP HSBP1010R2914.pdf PDF
No Chg Log_MSC Environment Objectives —
MSC RFP HSBP1010R2914 Cover page.pdf PDF
Mobile Surveillance Capabilities Matrix —
Show all 24

On GovTribe

Work with this file on GovTribe

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

Text version

Welcome to MSC Industry Day

January 8, 2010

U.S. Customs and Border Protection Secure Border Initiative (SBI)

Last Updated: 2/25/2009

Briefing Agenda, Purpose, Introductions, and Ground Rules, Mr. James Riordan, SBInet Executive Director (SBInet XD)

Briefing Agenda

1. Greeting, Government Team Introductions, and SBI Overview 1000 – 1010hrs: Agenda, Purpose, Introductions, and Ground Rules 1010 – 1025hrs: SBI Overview

James Riordan, SBInet XD

Mark Borkowski, SBI XD

2. Core Presentations 1025 – 1040hrs: MSC Project Overview 1040 – 1055hrs: MSC Operational Overview 1055 – 1110hrs: MSC Capabilities Matrix Walk-through 1110 – 1130hrs: MSC Contract Overview Mike Forest, MSC PM Steve Potter, SBPA Clay Hudgins, MSC Engr Janice Washington, MSC CO

3. Vendor Question and Answer Session: 1130 – 1230hrs Government Team (facilitated by the MSC PM and CO)

Purpose To facilitate discussion and clarify any issues or concerns communicated by Offerors

Provide Offerors with a better understanding of OBP’s needs and the operational environment likely to be encountered by MSC

Encourage open communications, allowable by law, during the proposal development process to ensure Offerors prepare high quality proposals for delivery to the Government

MSC Team Introductions Mark Borkowski, SBI Executive Director

James Riordan, SBInet Executive Director

Mike Forest, MSC Project Manager

Janice Washington, MSC Contracting Officer

Clay Hudgins, MSC Lead Engineer

David Belles, MSC Chief Logistician

Steve Potter, Supervisory Border Patrol Agent

Ground Rules No audio or video recording of the Industry Day Conference is permitted

Please hold questions until the end of all presentations

Please silence or turn off any cellular phones or other electronic devices

Written comments can be submitted via e-mail to MSC@dhs.gov

Today’s briefing slides will be posted to the Federal Business Opportunities website no later than four (4) days after this conference

Questions may be rendered verbally or on 3 X 5 cards

Written responses supersede oral responses

SBI Overview, Mr. Mark Borkowski, SBI Executive Director

MSC Project Overview, Mr. Mike Forest, MSC Project Manager

MSC Project Overview The Mobile Surveillance Capabilities (MSC) Project is:

Firm Fixed Price (FFP)
NOT a developmental contract
Best Value Procurement
Potential for Multiple Awards
Wide Area Surveillance
Land-based Solution
The Government is procuring a commercial item as a Turn-key System
The Offeror is responsible for the performance of the system
Read the entire solicitation and not just the Statement of Objectives
The FY2010 funding source is the American Recovery and Reinvestment Act (ARRA)

Government Furnished Equipment (GFE):

Land Mobile Radio
Installation
Considerations
Interference (RFI)
Operation of radio in transport mode and operational mode
Vehicle
Vehicle may be part of solution, particularly if it is a non-standard vehicle
If solution is skid-based, and requires a standard vehicle (i.e. Ford/GM/Dodge truck), the vehicle will be GFE

System Testing Overview:

In-factory Testing
Focuses on quality of the manufacturing process
Considerations
Built as advertised
Finding and fixing problems before the system is delivered to the customer
First Article Testing (FAT)
In-field testing
Intent is to ensure the system performs as advertised and meets requirements as stated in the MSCM
Focuses on system performance in the operational environment of intended use
Vendor supports by:
Preparing FAT Plan and Procedures
Training of operators in advance of the test
In-field support and maintenance throughout the test period
As needed support for preparation of the FAT Report
Transition of the system from test to operational use

System Testing Overview (Continued):

Unit Acceptance Testing (UAT)
In-field testing of production-run articles
Random testing of at least 20% of production-run articles
Intent is to ensure the system performs as advertised and meets requirements as stated in the MSCM
Focuses on system performance in the operational environment of intended use
Vendor supports by:
Preparing UAT Plan and Procedures
Training of operators in advance of the test
In-field support and maintenance throughout the test period
As needed support for preparation of the UAT Report
Transition of the system from test to operational use

MSC Operational Overview, Supervisory Border Patrol Agent (SBPA) Steve Potter

Office of Border Patrol’s Mission As the primary federal law enforcement agency between the ports-of-entry, the Border Patrol’s mission is to:

Prevent the entry of terrorists and their weapons of terrorism; and

Enforce the laws that protect America’s homeland by the detection, interdiction, and apprehension of those who attempt to illegally enter or smuggle any person or contraband across our Nation’s sovereign borders.

Office of Border Patrol’s National Strategy Gain, maintain, and expand operational control of the border using the right combination of personnel, tactical infrastructure, and technology. The Border Patrol’s Strategy consists of six core elements:

(1) Secure the right combination of personnel, technology and infrastructure
(2) Improve mobility and rapid deployment to quickly counter and interdict based on shifts in smuggling routes and tactical intelligence
(3) Deploy defense-in-depth that makes full use of interior checkpoints and enforcement operations calculated to deny successful migration
(4) Coordinate and partner with other law enforcement agencies to achieve our goals
(5) Improve border awareness and intelligence
(6) Strengthen the Headquarters command structure.

MSC Operations To further success of this mission, the Office of Border Patrol has identified a need for technology that provides OBP with:

Automated wide area surveillance
Detection
Identification
Tracking

The MSC shall provide OBP with:

Force multiplication through automation and wide area surveillance providing real time information to agents on the ground. This allows fewer agents to cover a larger area. It also can improve the quality of the law enforcement resolution and enhance officer safety by providing the agents on the ground with more information about the IoI (item of interest) that they are investigating.

An additional layer of situational awareness to enhance existing tactical infrastructure and provide surveillance where no real time surveillance capability existed before.

This technology shall provide OBP with:

Rugged design to provide a persistent surveillance in a 24/7, 365 capacity

Mobility, must be able to reach the deployment sites across the varying terrain of the southwest border and able to be redeployed to adapt to a shifting threat.

The mission that needs to be addressed presents a threat that is dynamic, persistent and fluid. Thus the system must be able to maintain a persistent deployment strategy.
A operator workspace that supports the demands of the 24 hour 365 days a year deployment strategy.

The environments of the southwest border are harsh and measures must be taken to protect the operator from exposure.

Ergonomic workspace

Temperature Extremes of both hot and cold are present in the southwest border.

10o to 124o F is a realistic range for ambient temperatures found on the SWB. However solar loading can create surface temperatures on the equipment that well exceed the upper ambient range

Examples of SWB Geography

Mountainous Terrain

Line of sight obstructions created by other mountains
Absence of improved roads
Climbing ability of the unit (capability to access deployment sites)
Stability in wind
Colder conditions and problems such as snow and ice.
Reduced oxygen (reduced generator output)

Plains Terrain -Line of sight -Importance of increasing sensor height -Absence of high points -Soft ground, no maintained roads

River line Terrain

Increased Vegetation near water line
Line of sight obstructions
Over water detection (unique Items of Interest) as well as over ground detection
Soft ground
High winds
Fog

Shoreline Terrain

Over water detection
Unique IoIs (Items of Interest) such as people in water and boats
Soft ground
High winds
Fog

MSC Capabilities Matrix Walk-through, Mr. Clay Hudgins

Outline Purpose Of this presentation and the associated technical documents

Government’s Technical Documents

Mobile Surveillance Capabilities Matrix (MSCM)
MSC Environmental Objectives (MSCEO)

Offeror’s Technical Documents Emphasis on cross references to the Government’s MSCM and MSCEO

Structure of Capabilities Matrix (MSCM) document Structure of Environmental Objectives (MSCEO) document Concluding Highlights

Purpose of Presentation Purpose: provide an overview of MSC technical documents Mobile Surveillance Capabilities Matrix (MSCM) MSC Environmental Objectives (MSCEO)

Goals of the Government Technical Team in preparing these documents:

Clearly document capabilities needed by the Border Patrol Deliberately allow Offerors flexibility in crafting a best-value solution Provide a uniform format for Offerors to cross-reference their proposed solutions to the capabilities needed by the Border Patrol

Alert:

The items published by the Contracting Officer (CO) take precedence over this presentation.
Offerors’ questions will be handled in writing per methods established by the CO

Government’s Technical Documents Capabilities Matrix document

Full Name:
Mobile Surveillance Capabilities Matrix (MSCM)
Documents Capabilities needed by Border Patrol
Documents Parameters needed by Government’s Technical Team to understand Offeror’s proposed solution
Documents a carefully considered set of “Threshold Acceptable Values”
Any proposal failing to meet any single Threshold Acceptable Value will be rejected
Only for those “Threshold Acceptable Value(s)” for which a value is provided
An Example is provided on an upcoming slide

Environmental Objectives document

Full Name:
Mobile Surveillance Capabilities – Environmental Objectives (MSCEO)
Is incorporated by reference into the Capabilities Matrix document (MSCM)
Supports and supplements the MSCM regarding environmental objectives

Offeror’s Technical Documents Volume I: Offeror’s Technical Proposal Prepared per outline and format instructions released by Contracting Officer

Volume II: Offeror’s Cross Reference to the Government’s Mobile Surveillance Capabilities Matrix (MSCM)

An Offeror-prepared copy of the MSCM with the right-most column filled-in
Providing a cross reference to the corresponding section(s) and page(s) in the Offeror’s technical proposal Volume I, and
Optionally a very brief response consistent with the space available in the table-cell.

Volume III: Offeror’s Cross Reference to the Government’s Mobile Surveillance Capabilities – Environmental Objectives (MSCEO)

An Offeror-prepared copy of the MSCEO document’s Tables with
The right-most column filled-in with a cross reference to the corresponding section(s) and page(s) in the Offeror’s technical proposal Volume I, and
Optionally a very brief response consistent with the space available in the table-cell.

Structure of Capabilities Matrix (MSCM)

*Any Offeror’s offered solution (proposal) failing to meet any single Threshold Acceptable Value will not be considered, which means that proposal will be rejected.

This statement only applies to those parameters for which the Government has specified a value for “Threshold Acceptable Value.” See upcoming slide.

FactorMSC Capability
(Subfactor)ParameterNominal Desired Value
(Objective)Threshold Acceptable Value*Offeror Cross-Reference
DetectionC1. The MSC provides …Parameter #1Objective ValueThreshold Value*
Parameter #2Objective ValueOfferor to propose
C2. …………
C5. …Parameter #X1Offeror to propose …
Parameter #X2Objective ValueDesired but Not Required
2. IdentificationC6. …Parameter #Y1……
……………
7. MobilityC26. The MSC is capable of ….Parameter #Z1……

*Any Offeror’s offered solution (proposal) failing to meet any single Threshold Acceptable Value will not be considered, which means that proposal will be rejected.

“Factor” describes the capability category (grouping of similar capabilities).

“MSC Capability (Subfactor)” describes a capability that the acceptable system will provide or possess.

“Parameter” describes the specific standards and conditions the capability (subfactor) will be evaluated against.

“Nominal Desired Value (Objective)” describes the desired (at a minimum) level of the capability’s parameters for enhanced system deployment and operations.

“Threshold Acceptable Value” describes the minimum level of the capability’s parameters acceptable for system deployment and operations.

FactorMSC Capability
(Subfactor)ParameterNominal Desired Value
(Objective)Threshold Acceptable Value*Offeror Cross-Reference
DetectionC1. The MSC provides …Parameter #1Objective ValueThreshold Value*
Parameter #2Objective ValueOfferor to propose
C2. …………
C5. …Parameter #X1Offeror to propose …
Parameter #X2Objective ValueDesired but Not Required
2. IdentificationC6. …Parameter #Y1……
……………
7. MobilityC26. The MSC is capable of ….Parameter #Z1……

*Any Offeror’s offered solution (proposal) failing to meet any single Threshold Acceptable Value will not be considered, which means that proposal will be rejected.

In the example of Parameter #1, the Gov’t specifies both a Threshold and an Objective value.

In the example of Parameter #2, the Gov’t specifies an Objective value, but chooses not to specify a Threshold Value.

In the example of Parameter #X1, the Gov’t chooses not to specify any value, but does request the Offeror to propose a value consistent with stated Capability (Subfactor) objectives.

In the example of Parameter #X2, the Gov’t specifies an Objective value, but chooses not to specify a Threshold Value.

FactorMSC Capability
(Subfactor)ParameterNominal Desired Value
(Objective)Threshold Acceptable Value*Offeror Cross-Reference
DetectionC1. The MSC provides …Parameter #1Objective ValueThreshold Value*
Parameter #2Objective ValueOfferor to propose
C2. …………
C5. …Parameter #X1Offeror to propose …
Parameter #X2Objective ValueDesired but Not Required
2. IdentificationC6. …Parameter #Y1……
……………
7. MobilityC26. The MSC is capable of ….Parameter #Z1……

*Any Offeror’s offered solution (proposal) failing to meet any single Threshold Acceptable Value will not be considered, which means that proposal will be rejected.

“Offeror Cross Reference” column is reserved for Offerors to fill-in and provide as Volume II of Technical Response.

FactorMSC Capability
(Subfactor)ParameterNominal Desired Value
(Objective)Threshold Acceptable Value*Offeror Cross-Reference
DetectionC1. The MSC provides …Parameter #1Objective ValueThreshold Value*
Parameter #2Objective ValueOfferor to propose
C2. …………
C5. …Parameter #X1Offeror to propose …
Parameter #X2Objective ValueDesired but Not Required
2. IdentificationC6. …Parameter #Y1……
……………
7. MobilityC26. The MSC is capable of ….Parameter #Z1……

Uses tables with a similar format to the Capabilities Matrix Is incorporated by reference into the Capabilities Matrix (MSCM) Ruggedization and Mobility Factors link the two documents MSC Environmental Objectives (MSCEO) Outline

1.0 Introduction
2.0 Environmental Capability Needs
Table 2-1. Naturally Occurring Operating Environment
Table 2-2. Stressing Naturally Occurring Operating Environment
Inclement weather
Table 2-3. Natural Survival Environment
Severe weather
Table 2-4. Operationally Generated Environment
Transportation on-road and off-road, shipping, EMI/EMC, etc.
3.0 Southern Sector Environment Overview
Provided to familiarize Offerors with the regions of deployment

Structure of the MSC Environmental Objectives (MSCEO) Document

The rightmost columns of these Tables are reserved for Offerors to fill-in and provide as a cross-reference in Volume III of Offerors’ Technical Response.

Concluding Highlights In preparing Technical Documents, the Government Team’s goals were

Clearly document capabilities needed by the Border Patrol
Deliberately allow Offerors flexibility in crafting a best-value solution
Provide a uniform format for Offerors to cross-reference their proposed solutions with the capabilities needed by the Border Patrol

This presentation’s purpose is to further clarify existing documents

The documents published by the Contracting Officer (CO) take precedence
Offerors’ questions will be addressed in writing through the CO

Contract Overview, Ms. Janice Washington, MSC Contracting Officer

MSC Proposal Timeline

Request For Proposal (RFP) posted FEDBIZOPPS on 12/28/09

Proposals due 1200hrs, Eastern Standard Time (EST) 1/29/2010

Questions & Answers deadline 1/15/2010

SOLICITATION DISCREPANCIES

Proposal due date listed in FEDBIZOPPS as 5:00 pm EST, 1/29/10. Should be 1200 EST, 1/29/10.

In Section I, clause I.6 should be deleted.

Improve alignment of the SOO to the CDRLs and CLINs; add list of CDRLs to Section J (attachments) of the RFP.

Although it is already requested in Section M (Evaluation Factors) of the RFP, the requirement to substantiate/provide evidence of system performance capabilities will be amplified in Section L (Instructions to Offerors)

Corrections to discrepancies will be posted within four (4) days.

Contract Overview Contract Type:

a. Firm Fixed Price
b. Period of Performance – 5 years
c. Multiple awards possible

First Year (CLINS 0001- 0009):

a. American Recovery and Reinvestment Act of 2009 (ARRA) Funds

3. ARRA Reporting Requirements:

a. Amount received
b. List of projects recovery funds expended
c. Requirements found at www.FederalReporting.gov

CONTRACT LINE ITEM NUMBER (CLIN STRUCTURE)

1. Step pricing: range pricing of units which shows an economic purchase quantity at which a significant price break occurs.

2. First Year:

a. Two (2) test units
b. Additional units based on step pricing
c. Training
d. Component manuals
e. ILS plan
f. Maintenance
g. Unit spares
h. Schematic drawings
i. Over & above (incidentals)

CONTRACT LINE ITEM NUMBER (CLIN STRUCTURE) CON’T

Options:

Based on need Quantity depends on need within 12 month period Recurring CLINS Step pricing units Maintenance Unit spares

Financing payments allowed IAW 52.232-29 (Financing of Commercial Items)

SECTION L (Instructions to Offerors)

Volume I – Technical Proposal:

a. Three (3) documents – transmittal letter, executive summary, and performance work statement

b. Three (3) parts:
i.Technical proposal
ii. Cross reference to the Mobile Surveillance Capabilities Matrix (MSCM)
iii. Cross reference to the Mobile Surveillance Capabilities Environmental Objectives (MSCEO)

Volume II – Price Proposal

a. Pricing table 1 – summary of total price
b. Pricing table 2 – summary of prices per price break (step pricing)
c. Pricing table 3 – summary of option prices

SECTION M (Evaluation Factors)

Evaluation factors (in order of importance):

a. Technical
b. Price
c. Past Performance

Failure to meet a discrete threshold in the capabilities matrix constitutes an offereror’s proposal as being non-compliant

Technical Factors (in order of importance): Detection; identification; tracking; ruggedization; reliability & maintainability; ease of use; and mobility.

Technical subfactors 2-7 are individually weighted less important than technical subfactor 1.

SECTION M (Evaluation Factors) (Continued)

Past Performance:

a. Substantiation of system performance against the capabilities matrix (MSCM)
b. Customer satisfaction (completion of Past Performance Questionnaires)

Basis of Award:

a. Best value (trade-off analysis)
b. Overall value: Technical performance more important than price; price more important than past performance. When combined, the nonprice factors are approximately equal to price.

Questions & Answers Session

Summary

THANK YOU

For more information on SBI, please visit us on the Web: WWW.CBP.GOV/SBI Additional questions regarding the MSC Procurement should be sent to MSC@dhs.gov before the closing date (1.15.2010)

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