Primary Functional Area : Life Cycle Logistics
Post Production Software Support (PPSS) is a key software support concept that includes the activities necessary to ensure that Systems Engineering and sustainment principles, processes and practices are applied to software. While the title indicates a focus on deployed software, the nature of software support is that critical activities occur throughout the acquisition process, in terms of planning, development of a support capability, and the effective deployment and maintenance of software resources.
Software Support begins early in the Life Cycle with the identification of Software Support Requirements within the Life Cycle Sustainment Plan (LCSP). Rights in Technical Data and Software Data Rights are significant components of the Intellectual Property Strategy as required by DoDI 5000.02, Enclosure 1, and the Better Buying Power Initiative. The Systems Engineering (SE) process addresses the development of software as a configured item equal to hardware in all programs, therefore addressed in program reviews, systems requirements reviews, testing, sustainment planning, and maintained as part of Operations and Support (O&S) phase activities.
Defense Acquisition Guidebook Chapter 4.1.3.1, Software, discusses Post Deployment Software Support (PDSS) as follows:
“The management of the software development process and the implementation of a process that ensures software supportability are among two of the most difficult challenges facing the Program Manager in management of software-intensive systems. The Program Manager should effectively address the issues of software supportability, the software test environment, and other equipment, material, and documentation, including data rights that are required to provide PDSS for those end users identified in the SDP or in other documents similar to the Computer Resources Life Cycle Management Plan. Successful PDSS planning should assist the Program Manager in controlling software life-cycle costs.”
As discussed in the NAVAIR Software Logistics Primer Version 1.0 DTD August 2008, software support considerations are uniquely different that those of hardware support. Hardware support activities are typically dominated by preventive and corrective maintenance, which involves replacement or repair of a failed part. The failed part is replaced with an identical, functioning part. When software fails, the software engineer does not replace the offending code with an identical piece of code, but rather must modify the code to provide the needed functionality. Software modification is undertaken to defect corrections, address policy or doctrine, ensure safety, enable interoperability, reflect hardware changes, accommodate technology insertion, and incorporate functional changes.
Typically, Software Support costs include the labor, material, and overhead costs incurred after deployment in supporting the update, maintenance and modification, integration, and configuration management of software. These costs include operational, maintenance, support and diagnostic software programs for the primary system, support equipment, and training equipment. The respective costs of operating and maintaining Software Support Environment (the associated computer/peripheral equipment and associated software dedicated to performing software maintenance) and the cost to conduct all testing of the software should also be included. Other costs may include licensing fees for commercial software and accreditation of processes and facilities.
The identification and establishment of Software Support Activity (SSA) is the first step in the preparation of a Post-Production Software Support Contract. The Software Support Activity assumes the role of providing post-deployment life cycle support for modifications or upgrades made to a system's software following the system's initial fielding. System modifications and upgrades include multi-system changes, block changes, preplanned product improvements, repair of deficiencies reported by the user, and other types of system change packages. The SSA organization typically compiles these needed updates into formal software releases to avoid disrupting the fielded system. Software development activities performed by a SSA in providing life cycle support are the same as those carried out during the development effort that led to the first fielding. They are tailored, as appropriate, to reflect the effort required to implement each change package, update pertinent documentation, verify the changes, and distribute the changes to users.
Non-organic software support may be achieved through either traditional contacting methods or through a Performance-Based Logistics (PBL) program. If commercial software support is required, the steps in obtaining software support contracts parallel those of the original procurement, to include preparation of requirements, development of a procurement package, to include a statement of work/objectives, Contract Data Requirements, deliverables, contract pricing and evaluation and award criteria. Under the Performance-Based Logistics (PBL) construct, Performance-Based Agreements may be structured to provide software support. In either case, a clear statement of outcomes to be achieved and the metrics needed to evaluate success are required.
Defense Acquisition Guidebook, Policies, Directives, Regulations,
Laws
[Suggest Change]
DoD Directive 5000.01, The Defense Acquisition System, defines the management process by which the Department of Defense provides effective, affordable, and supportable systems to the users in a timely manner. Its policy includes implementation of a Total Systems Approach as discussed in E1.1.29. Total Systems Approach for accomplishing program objectives for total life-cycle systems management, including sustainment, and implementing performance-based strategies throughout the product life cycle, as discussed in E1.1.17, Performance-Based Logistics.
Defense Acquisition Guidebook Chapter 7 – Acquiring Information Technology and National Security Systemsaddresses refers to The Government Performance and Results Act (GPRA) that requires Federal Agencies acquiring Information Technology and National Security Systems to compare actual program results with established performance objectives, and the Clinger-Cohen Act (CCA) requires that Federal Agencies ensure that performance measurements are prescribed for the information technology (IT) to be acquired, that these performance measurements measure how well the IT supports the programs of the Agency. As a result, a Post Deployment Performance Review (PDPR) is required for MAIS and MDAP acquisition programs at the Full-Rate Production Decision Review. An appropriately conducted PDPR can satisfy both GPRA and CCA requirements for a post deployment evaluation.
USD (AT&L) Memorandum Implementing a Life Cycle Management Framework [ACC], DTD 31 Jul 08, identified Implementing a Life Cycle Management Framework as a top priority for the Department of Defense. To achieve that objective, DoD must seamlessly integrate its acquisition and life cycle sustainment policies. To that end, this memo establishes a strategy and provides direction to achieve the following: (1) reinforce the implementation of mandatory life cycle sustainment metrics; (2) align resources to achieve readiness levels; (3) track performance throughout the life cycle; and (4) implement performance-based life cycle product support strategies.
DUSD (L&MR) Policy Memo "Life Cycle Sustainment Outcome Metrics", DTD 10 Mar 07 establishes four sustainment outcome metrics for all ACAT (Acquisition Category) I Acquisition Programs, as well as all major legacy programs currently included in the Defense Readiness Reporting System (DRRS). The four metrics are Materiel Availability, Materiel Readiness, Ownership Cost, and Mean Down Time. In addition, Materiel Availability is also a JROC-established Key Performance Parameter (KPP) requirement; Materiel Readiness and Ownership Cost are JROC-established Key System Attribute (KSA) requirements for new acquisitions. Specific definitions of each of these four metrics are contained in the memorandum, as well as fourteen "Life Cycle Sustainment Enablers”.
The Life Cycle Sustainment Plan is required by Section 3 of Enclosure 6, Life Cycle Sustainment, of DoD 5000.02 and is developed to document sustainment requirements throughout the Life Cycle and to ensure their consideration “up-front” in the acquisition process. The LCSP is required at Milestones A, B and C, and the Full-Rate Production Design Review.
The Replaced System Sustainment Plan is a DoDI 5000.02 requirement and supports Milestone B. The RSSP addresses the support required by an existing system once a decision has been made that a system will replace it. The RSSP includes the budget estimates required to sustain the existing system until the new system assumes the majority of mission responsibility; the milestone schedule for developing and fielding the new system; the anticipated funding levels necessary to ensure acceptable reliability and availability rates and maintain mission capability against the relevant threats; and the extent to which it is necessary and appropriate to transfer mature technologies from the new system or other systems to enhance the mission capability against relevant threats and provide interoperability with the new system during the period from initial fielding until the new system assumes the majority of responsibility for the existing system mission.
Best Practices, Lessons Learned, Stories, Guides,
Handbooks, Templates, Examples, Tools
[Suggest Change]
The Naval Air Systems Command (NAVAIR) Software Logistics Primer Version 1.0 DTD August 2008 provides an excellent Life Cycle overview of software development and maintenance. The Primer includes definitions of software related terms, references to public law related to software acquisition, software processes and best practices and the contract related activities to be conducted to obtain software support services.
Defense Acquisition Guidebook Chapter 4, Systems Engineering, provides an overview of the Systems Engineering process, its activities and outputs in the context of the Defense Acquisition Management Framework. The Chapter provides program managers with a method to effectively implement a total systems approach to meeting program requirements. Software is discussed throughout the Chapter, with detailed discussion of software related activities in each phase of the life cycle.
Defense Acquisition Guidebook Chapter 5, Life Cycle Logistics, provides an overview of key Life Cycle Logistics (LCL activities) and outputs in the context of the Defense Acquisition Management Framework, to help program managers effectively implement LCL, Total Life Cycle Systems Management (TLCSM), and Performance-Based Logistics (PBL). Software planning and maintenance is an integral part of Sustainment as formulated in the Product Support Strategy, detailed in the Product Support Plan, and implemented through Performance-Based Logistics product support agreements.
The Life Cycle Logistics Community of Practice (LOG CoP) contains a comprehensive discussion of Software Sustainment as a part of the Sustainment process. Other excellent references include Understanding and Leveraging Data Rights in DoD Acquisition and the LOG CoP Resources & Tools site's Post Production Support page.
Better Buying Power
Defense Acquisition University (DAU) Catalog of Courses (iCatalog)
DAU Resident Courses
- LOG 201 Intermediate Acquisition Logistics, Part B
- LOG 211 Supportability Analysis
- LOG 340 Life Cycle Product Support
- LOG 350 Enterprise Life Cycle Logistics Management
- LOG 465 Senior Seminar for Product Support Managers
DAU Distance Learning Courses
- LOG 101 Acquisition Logistics Fundamentals
- LOG 102 Fundamentals of System Sustainment Management
- LOG 103 Reliability, Availability and Maintainability (RAM)
- LOG 200 Intermediate Acquisition Logistics, Part A
- LOG 204 Configuration Management
- LOG 206 Intermediate Systems Sustainment Management
- LOG 215 Technical Data Management
- LOG 235 Performance-Based Logistics
DAU Continuous Learning Modules
- CLL 015 Business Case Analysis
- CLL 025 Depot Maintenance Interservice Support Agreement
- CLL 008 Designing for Supportability in DoD Systems
- CLL 020 Independent Logistics Assessments
- CLL 016 Joint Logistics
- CLL 014 Joint Systems Integrated Support Strategies (JSISS)
- CLL 011 Performance Based Logistics (PBL)
- CLL 012 Supportability Analysis
- CLL 022 Title 10 Depot Maintenance Statute Overview (Statutory Framework)
- CLL 024 Title 10 Limitations on the Performance of Depot-level Maintenance (50/50)
- CLL 056 Sustainment of Software Intensive Systems
|
|
Page Information
|
Page Views
|
32,259
|
|
Created on
|
4/19/2005
|
|
Modified on
|
8/5/2016
|
|
Last Reviewed
|
8/2/2016
|
|