SEC P3 One-on-One Additional Information.pdf

SEC P3 TEAMING AGREEMENTS

Purpose:

The Teaming Agreement establishes a collaborative framework between an industry vendor and the Communications-Electronics Command (CECOM) Software Engineering Center (SEC). This agreement defines the management and technical approach for jointly addressing government contracting opportunity.

Objectives

• Sustain the Domestic Industrial Base - Support the core competencies and technical expertise of both CECOM SEC and the industry vendor.

• Enhance Operational Efficiencies – Optimize resource utilization and leverage the combined capabilities of both parties.

• Foster Public-Private Collaboration – Strengthen the partnership to deliver innovative solutions, adopt new technologies, and improve readiness and modernization efforts for government customers.

Approach

• Proposal Development – In response to a federal government Request for Proposal (RFP), the industry vendor may seek SEC as a partner. The two entities collaborate on pre-award proposal development.

• Proposal Submission – The industry vendor is solely responsible for submitting the final proposal to the government procuring activity.

• Contract Award & Execution – If awarded the contract, the industry vendor becomes the Prime Contractor.

• The Prime Contractor will submit an RFP to SEC, SEC will submit proposal to the P3 government procuring activity Contracting

Officer (KO), then KO will submit proposal to Prime Contractor.

• Negotiations, such as advance payment terms, etc., are part of the final process.

• The P3 Direct Sales Agreement serves as the executed subcontract that will be signed by the KO and Prime Contractor.

• Receipt of advance payment(s) must be received prior to work execution.

SEC P3 PARTNERING PROCESS

CUI

1) Evaluate Potential Partnership

• P3 POC coordinates follow-on meeting(s) with technical team

• P3 POC & technical team meet w/vendor to determine way-ahead

• SEC Brief Leadership: Go/No-Go decision will be determined

2) Protect the Partnership

• SEC establish evaluation team (SMEs/Legal/Budget/Contracting/others)

• SEC POCs sign Non-Disclosure Agreement Conflict of Interest document

• Teaming Agreement (TA) created

• TA signed by SEC Directorate, Vendor and SEC Senior Executive

• Firewalls created for competitive requirements

3) Pre-award/Prepare for Potential Partnership

• Create Business Case Analysis (BCA)/for final internal approval

• Technical SMEs and Vendor collaborate on pre-award submission

• SEC provide Rough order of Magnitude (ROM) estimate to vendor

4) Post-award/Develop Subcontract Proposal

• Prime Contractor provide SEC RFP (SOW/PWS) documents

• SEC develop technical and cost proposal

• SEC send proposal to P3 contracting officer for submittal to Contractor

• Contractor evaluate documents

5) Develop P3 Direct Sales Agreement

• SEC, Contractor, and Contracting negotiate advance payment terms, etc.

• Negotiated advance payments will be included in final agreement

• SEC will coordinate final subcontract with SEC Director

• Contracting Officer and Prime Contractor signs P3 Direct Sales Agreement

• Receipt of advance payment(s) must be received prior to work execution

6) Execute P3 Direct Sales AgreementFinalized P3 Contract

Steps to Partnering

Non-Disclosure Agreement

Statement of Work

Evaluation

Cost Estimate

Negotiation

Teaming Agreement

SEC CORE CAPABILITIES

Software Deployment & Field Support System Automated Deployment Patch Management Deployment Delivery Pipelines Field Support Software Readiness

Software Acquisition Support Acquisition Management and Process Support Foreign Military Sales (FMS) Development and

Support Software License Management Contract Management Support

Cybersecurity Risk Management Framework (RMF)/Authorization to

Operate (ATO) Patch Management Hardening Software Assurance (SwA) Assessments

Software Testing Test Automation Interoperability Independent Verification and Validation Modeling and Simulation

Software Development Development (across multiple domains) Continuous Integration/Continuous Delivery (CI/CD) and

Agile Development Process CI/CD Automated Developmental – Build Pipelining Cloud Native Software Development Applications Support Web Services Support Micro-Services Artificial Intelligence (AI)/Machine Learning (ML) Lead System Integrator

CI/CD Infrastructure Developmental Infrastructure Tactical Infrastructure Facilities and Lab Infrastructure Lab Virtualization Containerization

Enterprise Resource Planning Enterprise Help Desk Business Process Re-engineering Data Strategies Application Integration

Electromagnetic Warfare Reprogramming Collaborate requirements and solutions with the Joint

Electronic Warfare Community Improve responsiveness, quality, and speed for performing the reprogramming mission and delivery to the Warfighter Develop and maintain platform and/or mission specific software reprogramming mission data and tools Develop and maintain threat-based models and simulations that support development, testing, and verification

SD CI/CD

ST ERP

CS SD/FS

EWR SAS

Building Army-wide Software Capabilities with Agile CI/CD Best Practices