1. Contract Acquisition Life-cycle Management (CALM) Status Update A webinar – 8/6/2019

2. Objectives
Socialize the potential change in Acquisition Strategy for the Contract Acquisition Lifecycle Management (CALM) system
Discuss high level industry feedback on CALM requirement documents and notional changes
Discuss next steps

3. The Acquisition Strategy
Leverage CIO Modernization and Enterprise Transformation efforts
Align acquisition with GSA FAS strategic vision and expectation to use existing GSA sources of supply
Address industry concerns
Considering changing acquisition strategy from Schedule 70 BPA purchase to buying a part or all of CALM through COMET. COMET is GSA’s IT Modernization contract vehicle that aligns all modernization and transformation efforts across the enterprise.
Using COMET would reduce industry OCI concerns; enable the purchase of a total solution (product + service); give CALM team more time to refine requirements and re-engage with industry on a revised draft CALM; and gives CALM a permanent home.

4. CALM Impact Requirements BPA Order
Order to reflect agile implementation
Schedule
October COMET is awarded
Fall CALM order competed on COMET
Winter CALM order notional award and work begins
Spring Value delivered to non-MAS ITC pilot group. There is great rejoicing!
Late Spring 2020 & Beyond - Sprint to success!
Acquisition team
Impact to CALM
Must restructure BPA to be agile task order
Schedule will be pushed out months
Acquisition team changes - POCS on next page

5. CALM/COMET POCs
CALM Project Leads: Becky Koses - Keonia Cobbins -
COMET BPA:
Brian Bogucki -
COMET Task Order:
Kimberly Hampel -

6. Questions on the new acquisition strategy before we discuss RFQ feedback?

7. Tremendous Feedback and Suggestions
Themes we heard from industry:
FedRAMP - We received several industry concerns regarding FedRAMP - from industry wanting us to identify the cloud preference we have to defining what exactly has to be FedRAMP authorized to conflicting language in the RFQ regarding FedRAMP requirements. There were also concerns that the FedRAMP approach changed considerably between our discussion back in April where we talked about various cloud deployment models to the draft requirements, which required one deployment model.
RTM: Discrepancies between/among requirement, user story, acceptance criteria - which one takes precedence? Also, source selection tab is lacking key activities.
Reporting/Dashboards: More clarity around data, purpose, and whether we can leverage in house existing tools
Evaluation Approach:
Timing! Industry wanted a better understanding of the timeline for each phase and between each phase. They wanted to understand how offerors would move through each of the phases. We had several recommendations on the movement through phases - anything from moving through the phases in succession to combining Phase 2 (Phase 1 validation) and Phase 3 (knotty scenarios) together - and specific to Phase 4 which was the submittal of the PWS/PIP, QC and QASP, to only requiring Phase 4 proposals if the offeror successfully passed Phase 3 to help mitigate supplier costs to participate.
Point schematic! Consider more granularity; relaxing 100% pass rate for validation; weight requirements appropriately; clear definition of terms; keep number of test scenarios manageable
5. First task order: Be more clear; provide usage numbers; define scope
6. Contract line items: Be more clear; define CLINs, eliminate current CLIN structure and move to outcome / sprint based pricing
7. Period of performance: Truncate it and reconsider award terms
8. Miscellaneous: Clarity on help desk and training expectations; provide transactional volumes; clarity on interface with USSM efforts on govt-wide procurement data standards; and provide clearer offeror instructions

8. Next Steps for CALM
Reconcile industry feedback on draft CALM RFQ (there’s still time! Send feedback to
Work with CALM operational steering committee team, contracting and IT to determine final requirements and evaluation approach
Develop and distribute second draft RFQ for industry/workforce feedback
Finalize acquisition strategy once COMET is awarded
Establish acquisition milestones
Issue RFQ (see slide 4 for notional timelines)