Download presentation
Presentation is loading. Please wait.
Published byClaire Barker Modified over 6 years ago
1
MODULE 7 Creating the Facility Software Surveillance Plan (SSP)
Lesson 1: The Facility Software Surveillance Plan
2
Purpose Given the course materials presented, the students should be able to recognize the process for creating a Facility Software Surveillance Plan. 2
3
CMQ101 - Course Introduction
6/1/2018 Module Lesson Lesson 1: The Facility Software Surveillance Plan
4
What Will You Learn in This Module?
CMQ101 - Course Introduction 6/1/2018 What Will You Learn in This Module? This module: Introduces you to the Facility Software Surveillance Plan purpose and creation process Allows the Software Professional to consolidate surveillance efforts on multiple contracts/programs from a single supplier
5
Lesson 1: Facility Software Surveillance Plan (FSSP)
Objective: Recognize the purpose and process for creating a Facility Software Surveillance Plan.
6
CMQ101 - Course Introduction
6/1/2018 Lesson Objective Lesson 1: The Facility Software Surveillance Plan (FSSP) Objective: Recognize the purpose and process for creating a Facility Software Surveillance Plan.
7
Applicable SAMI Paragraphs
Creating a Facility Software Surveillance Plan (FSSP) is described in DCMA-INST 203, Paragraph 3.17, Creating a Facility Software Surveillance Plan (Facility SSP). The FSSP uses the Facility SSP template in addition to existing multiple SSPs DCMA-INST 203
8
What Is a Facility SSP? The Facility SSP is a Contract Management Office (CMO) elective (optional) plan that can only be implemented if: More than one SSP is in place at the CMO for a supplier The supplier has institutionalized common processes across the programs contained in the existing SSPs Facility SSP template contains the following sections: Core technical, cost, schedule, and CMO Unique Elements Surveillance schedules for four quarters of planning Contract List tab not found in the other SSP templates
9
Facility SSP Exclusion
If a process is NOT executed the same way from one program to another, it is NOT an institutionalized common process. Therefore, it cannot be included in the Facility SSP, and it will remain in the Contract, Program, or Lite SSP.
10
Why Use a Facility SSP? A Facility SSP can consolidate surveillance efforts on a single supplier by covering multiple customers and/or contracts. Facility SSP process accomplishes this by: Including only the tasks/activities from each SSP that are “common processes” institutionalized by the supplier across multiple programs Ensuring each SSP is updated to reflect the common institutionalized processes that are moved into the Facility SSP
11
Facility SSP Content The SSP Worksheet tab in the Facility SSP template only includes the: Core Elements – Technical, Cost, and Schedule CMO Unique Elements Program Measures and Customer Unique Elements are always unique to the applicable program/contract. 11
12
Creating the Facility FSSP: Step 1
Step 1 – Determine which tasks and/or activities within the SSPs the supplier has institutionalized as common processes. 12
13
Creating the Facility FSSP: Step 2
Step 2 – Transfer all qualified SSP Tasks/Activities into the Facility SSP: For each Task/Activity transferred, mark the “Task/Activity Surveillance Status” cell with “Task covered in Facility SSP” in the SSP and “Active, being engaged” in the Facility SSP. For any Task/Activity not transferred to the Facility SSP, mark the Facility SSP “Task/Activity Surveillance Status” cell with “Task covered in Contract, Program, or Lite SSP.” For the Core Technical, Cost, and Schedule Element, use the highest “Risk Rating” among the SSPs in the Facility SSP. Contract SSP Facility SSP 13
14
Creating the Facility FSSP: Steps 3–6
Step 3 – In the Facility SSP, enter the aggregate from the SSPs for the Surveillance Frequency Needed for each Task/Activity. Step 4 – In the Facility SSP, the entry for Hours Per Task/Activity shall be determined. Step 5 – In the Facility SSP, determine the Surveillance Frequency Allocated using the Resource Estimation process. Step 6 – In the Facility SSP, document the Quarterly Surveillance Schedule(s). Contract SSP Facility SSP 14
15
Creating the Facility FSSP: Steps 7–10
Step 7 – In the Contract List, document which SSPs are included in the Facility SSP. Step 8 – Document the rest of the Facility SSP as you would the SSP. Step 9 – In the SSPs, update all Revision History tables to reflect that identified Tasks/Activities have been incorporated (transferred) into the Facility SSP. Step 10 – Submit both the Facility SSP and the associated SSPs for CMO approval. Contract SSP Facility SSP 15
16
Facility SSP Data Transfer
SSP n… Facility SSP Use the highest “RISK Rating” from the SSPs Work is moved from SSPs to ONE Facility SSP SSP 1 Cells left blank Facility SSP 16
17
Facility SSP Calculations
Aggregate of SSPs = ADJUST DOWNWARD for Efficiency Gained Resource Estimation 17
18
Facility SSP High Points
To determine whether a Facility SSP can be implemented the Software Professional must ask: Is there more than one SSP for the supplier? Has the supplier institutionalized common processes for the programs/contracts documented in the SSPs? If implemented, the Facility SSPs must be submitted for CMO approval using the same process as required for SSPs. 18
19
Questions 19 19 of 21
20
Knowledge Review Question 1
Why would a CMO elect to implement a Facility SSP? It can consolidate SP surveillance efforts on a supplier by covering multiple customers and contracts. It consolidates SP surveillance efforts on a customer by covering multiple suppliers and contracts. It can consolidate contracts for a supplier by covering multiple customers and surveillance efforts. 20
21
Knowledge Review Question 2
When transferring over “common” core elements, you should ensure that you include core elements from which types of SSPs? Cost, Schedule, Technical Contract, Lite, Program Schedule, Program, Lite Contract, Lite, Cost 21
22
Knowledge Review Question 3
Who is the approval authority for a Facility SSP? Supplier Customer SQA POC SW POC 22
23
CMQ101 - Course Introduction
6/1/2018 Lesson Summary Recognized the purpose and process for creating a Facility Software Surveillance Plan. Lesson 4: Safety Stock
24
CMQ101 - Course Introduction
6/1/2018 Module Summary This module: Described the purpose and process for creating a Facility Software Surveillance Plan Lesson 4: Safety Stock
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.