Industry Day 2 - BIM.pdf

ROEs for Questions

1. Vendors display name must include full name and company represented– unrecognized names will be removed. Do not post this in the chat window. The chat window is for questions only.

2. All questions must be posted into the chat, including verbal questions. Any verbal questions must raise their hand to be unmuted.

3. Concluding the Industry Day presentation there will be a Q&A session focused solely on BIM. Questions about Wave 1 or other programs will not be addressed.

4. The chat window will be open to receive questions throughout the briefing – It is recommended that Vendors wait until the Q&A session to avoid redundant questions.

5. Once a question is submitted, it will be reviewed internally to determine whether it is immediately answerable (e.g. is it relevant, is the information requested releasable, etc.), answerable later (requires further analysis), or is non-answerable.

6. As time and resources allow, the Government will do its best to answer verbally in real time. This may not be achievable. However, the Government will provide a response to any missed questions in the formalized Q&A submitted on Sam.gov.

7. SAM.gov will include all the answerable questions and will be sanitized of any identifiable information.

Industry Day is being recorded for Internal Use ONLY

Government Attendees: Questions must be sent through Teams/Email

AFLCMC/HNIB

14 December 2022 v2

Base Infrastructure Modernization Industry Day #2

Controlled by: AFLCMC/HNIB Controlled by: AFLCMC/HNIB Program Office Category: General Procurement and Acquisition Distribution/Limited Dissemination Control: FEDCON POC: Major Nicholas Hollerbach, AFLCMC/HNIBIndustry Day will be Recorded for Internal Use Only

Agenda

• Opening Remarks – Lt Colonel Joseph Dolce

• Organizational Conflict of Interest – Hanscom JA

• BIM Acquisition Updates – Major Nicholas Hollerbach

• Questions and Answer Session – All

Opening Remarks Lt Colonel Joseph Dolce

Organizational Conflict of Interest

(OCI)

Office of the Staff Judge Advocate Hanscom AFB, MA

Organizational Conflict of Interest Definitions

FAR 2.101 - Because of other activities or relationships with other persons,

• a person is unable or potentially unable to render impartial assistance or advice to the Government, or

• the person’s objectivity in performing the contract work is or might be otherwise impaired, or

• a person has an unfair competitive advantage

FAR 9.504, Contracting Officer Responsibilities

• Identify and evaluate potential OCIs as early as possible

• Avoid, neutralize, or mitigate potential conflicts before contract award

• Should obtain the advice of legal counsel and technical experts in evaluating potential conflict

FAR 9.505, General Rules

• Each individual situation should be examined on the basis of its particular facts and the nature of the proposed contract

• Evaluation requires the exercise of common sense, good judgment, and sound discretion

Types of OCI

Biased Ground Rules

• Systems Engineering and Technical Direction (FAR 9.505-1)

• Preparation of Statement of Work; Requirements (FAR 9.505-2)

Impaired Objectivity

• Providing Evaluation Services (FAR 9.505-3)

Unequal Access to Information

• Access to Proprietary Information (FAR 9.505-4)

Identification of an OCI

• An OCI may be identified by a contractor, Contracting Officer (CO), or industry

• An OCI may be actual or potential conflicts

• Types of conflicts involved

• Description of contracts and business relationships that form the basis of the conflict

• Explanation of means by which conflict may be eliminated or mitigated

Governing FAR Provisions

FAR 9.504, Contracting Officer Responsibilities

• Identify and evaluate potential OCIs as early as possible

• Avoid, neutralize, or mitigate potential conflicts before contract award

• Obtain the advice of legal counsel and technical experts in evaluating potential conflicts

FAR 9.505, General Rules

• Each individual situation should be examined on the basis of its particular facts and the nature of the proposed contract

• Evaluation requires the exercise of common sense, good judgment, and sound discretion

Identification of an OCI

OCI Mitigation Plan Contents

• General Considerations

• Definitions

• Description of OCI situation

• Management of plan

• Management of personnel

• Review of plan

OCI Conclusion

• Definition of an Organizational Conflict of Interest

• Governing FAR provisions

• OCI Review Process

Base Infrastructure Modernization (BIM) Updates

Major Nicholas Hollerbach

D e s c r i p t i o n P r o g r a m D i a g r a m Connect Solutions

• Connectivity via Black Core Architecture at Layer 1 as-a-service

• Optimal combination of wired and wireless infrastructure to connect users to on- and off-premise enterprise services

BAN Operations (NIPR/SIPR)

• Network Distribution through a modernized architecture and network stack

Network Administration (NIPR/SIPR)

Support for SD-WAN and Future Zero Trust Initiatives

P r o p o s e d S c h e d u l e C o n t r a c t O v e r v i e w

• Proposed Draft RFP: Q1 FY23

• Proposed Final RFP: Q2 FY23

• IDIQ Award: Q2 FY23

• First TO Award: Q3 FY23

• Multiple Award IDIQ, PoP: Q2 FY23 – Q2 FY33

• IDIQ Total Length: 10 years (5-year base; 5-year option)

• Task Order Pool for Base Modernization/Operations (Large/Small business)

• 8(a) Set-Aside Pool for Material Purchases

Effort Overview

What can our Airmen and Guardians expect?

Increased availability and resiliency of networks, through more pervasive wireless connectivity, and modern network architecture

Interoperability with Joint networks and systems

Network performance that can support mission unique applications, tools, and systems

Reliable connectivity throughout installations, facilities, flight lines, and geographically separated units (“network anywhere”)

Ability to process unclassified and classified communications5

BIM Service Catalog

• Network Distribution (BAN) through a modernized architecture and network stack

• Optimal combination of wired and wireless infrastructure to connect users to on- and off-premise enterprise services

• Connectivity ensuring continuous availability and performance optimization

• Adherence to the most recent TEMPEST / Emission Security (EMSEC) regulations

• Maintenance of continuous authorization of IAW NIST global connectivity guidance

• WITO operations conducted by Vendor for Network Management and Support (at Base Comm Squadron)

B a s e C o n n e c t i v i t y

Provides a Modern and Robust Local Network Airmen and Guardians can execute their mission anywhere, anytime, with greater mission effectiveness and speed.

W h a t t h i s m e a n s

Enables the Future Fight Modern Network architecture enables seamless JADC2 and AI-Human teaming, speeds up our OODA loop and maintains consistent agility to adapt to an ever-changing battle space.

Increases Program Efficiency Vendor managed services free up Air Force/Space Force personnel for more mission critical work.

ACC/Cyberspace Capabilities Center

• Lead Command for Cyber

• Manage/Prioritize Requirements

BIM Stakeholder Roles/Responsibilities

C3I&N

• Acquisition Management

• Contract Management

16 AF

• Air Force Network Operators

• Enforce Security Requirements

SAF/CN

• Policy Ownership

• IT Strategy

BIM BAN Services

Out-of-Scope for BAN Modernization

Base Gateway & Security -- Enhances security through application of industry best practices to ensure mission security efforts to protect sensitive data

• Software-defined Perimeters, Continuous Monitoring, and Threat Detection

• Cloud Based Internet Isolation (CBII) Integration and Identified Aware Proxies

• Software Defined Networking Orchestration and Policy Enforcement

Government Provided Systems & Service Requiring Interoperability, Connectivity, and/or Transport

• On-premise Services, Clouds and Applications

• POTS, VoIP, and Cloud-hosted Telephony Systems

• Tactical Systems and Simulators for Training or Mission Planning Purposes

• ICS/SCADA Systems, Smart Buildings, Electronic Tools (E-tools), Wearables, Air Traffic Control and Landing Systems, Radio Transmission Systems, and Communities of Interest (COI)

Base Perimeter -- Prioritizes transport for maximum data throughput and optimizes user bandwidth consumption

• Software-defined WAN to Streamline Management Functions

• Dual Path Redundancy at Bases’ Network Points of Presence

• Geographically Separated Units (GSUs) Connectivity to Main Operating Bases (MOBs)

• Network Addressing, Translation, and DNS Caching

Global Connectivity -- The DISN Multi-protocol Label Switching (MPLS) represents the line of demarcation for Government operated WAN

• WWW (commercial)

• DISN

• AFIN

BAN Modernization VENDOR Network Distribution Provides optimal combination of wired and/or wireless infrastructure to connect users to on- and off-premise enterprise services

• Inside and Outside Plant (ISP/OSP) Infrastructure and Micro Segmentation

• Holistic Wired & Wireless Across Installations

• Bandwidth-On-Demand (BoD)

• Data Capture and Cyber Ops Integration

• On-site Service Restoration

• Network Health and Performance Monitoring

BIM will provide a Ubiquitous Black Transport Core providing a unified medium for transmission of NIPR, SIPR and Mission Systems data within the Base Boundary.

Engineering Solution

PCD SLAs Category Description Service Level*

Availability Availability of services 24 hours per day, 7 days per week 99.999% for C2 facilities and Assured Voice

99.99% for non-C2

Customer Satisfaction

Customers satisfied or very satisfied with services, as measured by survey data captured periodically

80%, 4.0 rating on a scale of 5.0

Resilience

Time to restore connectivity Routine: 4 hours; 99.99% of the time Critical: 2 hours, 99.999% of the time No non-repairable network component shall exceed 150% of its documented Mean Time to Failure

Security Data protected IAW DoD and industry best practices;

including time to report incidents of data leakage over base network connections

Routine: Within 24 hours, 99% of the time* Critical: Within 6 hours, 99% of the time**

Responsiveness Network response time, defined by time required for a packet to go between an end-user demarcation point and the host site FEP or similar device

Average < 500 milliseconds**

*Service Levels are prescribed from the requirements document **Service Level should update to reflect current industry-leading standards

SLAs executed at the Task Order Level

Leverage Existing 1067s / Other Req's

• Flightline of the Future (FLOF)

• Base Prioritization

• Bandwidth / Wireless / SIPR

Program Updates and Clarifications

Length of the IDIQ and TO's necessitate dynamic requirements and contractors

• Stagnation of the DAFs network infrastructure will be a thing of the past

IDIQ PWS language is broad and all encompassing

• IDIQ can't include base specific language to cover all 187 bases

• TOs will be tailored to the Base/GSUs - TO PWS will be based on the IDIQ PWS

• TO proposals will be made on the TO PWS; Evaluation criteria for TOs is not releasable at this stage

• Future solutions (SD-WAN, ZT etc.) will be either a part of the TO contract or contract modification.

IPv4 to IPv6 transition

• The government will determine the required IPv level at the TO level.

• Solution Requirement will evolve over time from dual stack solution to IPv6 only

Wireless Solution – Base specific transition is focused on a predominately wireless NIPR solution

NIL and ITF – Required for Vendor provided network, not legacy AFNET NIPR

IDIQ

Task Order

PWS Detail

Program Updates and Clarifications

SLAs Monitoring and TOs

• Industry Question: For customer satisfaction ratings, what other considerations are included such as customer experience, application(s) being used, edge devices being used, etc.?

• There will be more detailed SLAs at the TO level

• Monitoring will be done at a base level

• Network will be bounded for performance evaluation

Authority-to-Operate (ATO) process

• The TO vendor will be responsible for providing artifacts and information – Vendors responsibility to give information to appropriate officials at the Base(s)

• A separate ATO would apply to a NOC should a vendor propose one as part of their solution

• Government will work with vendor for appropriate POCs

W1 and BIM vendor interactions

• CMDB/ITSM from Wave 1 vendor will be required usage

• Instructions will be developed for issues between vendors/Government provided solutions

Program Updates and Clarifications – Hardware/Software

TO Vendors will have the flexibility to perform Ad Hoc equipment buys

• Significant purchases will be required to go through the Hardware pool

• All vendors on the IDIQ require a SCRM plan for any material purchase

• The service vendor will need be responsible for acquiring and loading any required software onto GFE hardware.

Will the Government standardize procedures (CONOP) for how full and open vendors will interact with Small Business Hardware Contractors that have responsibility for ordering equipment and supply chain management?

• The Government will provide instructions and facilitate yearly equipment buys

• Service vendor will not directly interact with 8(a) vendor pool

Hardware and Software Licenses

• The service vendor will need to go through the Government channels to procure licenses

• Any required exemptions must be approved by the Government

Proposed IDIQ Structure and Operational Dynamic

TO 1

Government

TO 2 TO 3 TO # Equip.

BOM 1

Equip.

BOM 2

Equip.

BOM 3

Equip.

BOM #

IDIQ Level

Task Order Vendor 8(a) Hardware Acq Pool

Delivery of

Hardware

Government PMO <Delivery of

GFE/GFP

Network Hardware Procurement ProcessTO Contract Start

8(a) Equipment PoolTask Order Vendor Pool

Gates 1 & 2 Gate 3

Sample Base Prompt Clarification

• Intention is to gauge the offerors' ability to perform the overarching PWS requirements based on the Sample Base details

• The response shouldn't be detailed to the TO level, but shall provide an adequate high-level response to base modernization requirements

• The base details provided are a baseline for an average DAF location

• The prompt is designed around assessing the vendors ability to understand and address various DoD/DAF concerns

• A few suggested clarifications were made; however, much of the prompt remains unchanged

• Flightline of the Future Requirements will be included/added

Reminder: Section L - "If there is missing information, the offeror should include an approach to identify and/or collect the missing information to provide their solution."

Prior Experience vs Past Performance

Prior Experience / Gate 1

• Only looks at the relevance and similarity of the work in relation to BIM that the Offeror has done themselves. How well the Offeror performed on the work is not considered.

• Ensures only Offerors with relevant and recent networking experience pass through Gate 1

Past Performance / Gate 2 & 3

• Ensures the Offeror has performed well for their customers

• Utilized to demonstrate that the Offeror has accomplished similar work and performed well. (poor performances in this area will affect the evaluation)

TO Evaluation Criteria

• Basis for each TO evaluation will be at the TO level

The FAR provides the Government with broad discretion in deciding how they will consider Offerors' Prior Experience, which refers to whether the Offerors have done similar work before, and Past

Performance, which describes how well they have performed that work

Prior

Projected Acquisition Timeline – Industry Timeframe

BIM

2022 2023

Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

IDIQ

Award

Task Order Award

12/14: Second Industry Day Session

Release Draft RFP as RFC

Release RFP

RFP Released to Industry

RFP Response Period

Eval/Source Selection Source Selection

TO Award Announcement

Eval/Source Selection Source SelectionRelease Task Orders

RFP

RFP Response Period

Tentative

IDIQ Award Announcement

Q&A Session and Closing

Verbal answers will be unofficial until formalized in writing posted on Sam.gov

The Government will post answered questions received during Industry Day on Sam.gov