2012 dod maintenance symposium - sae international€¦ · electronic warfare, avionics, sensors...

U.S. Army Materiel Command | Communications-Electronics Command

2012 DOD Maintenance Symposium

Nelson H. Keeler

Director, AMC CECOM

Software Engineering Center (SEC)

13 November 2012


AMC CECOM SEC Overview

Mission: Provide life cycle software solutions and services that enable Warfighting

superiority and information dominance across the enterprise.

LIFE CYCLE

A B C

Pre-Systems Acquisition Systems Acquisition Sustainment

Materiel

Solution

Analysis

Technology

Development

Engineering and

Manufacturing

Development

Production and

Deployment Operations

and Support

Domains:

Tactical Communications Satellite Communications Joint Networks Mission Command Intelligence Electronic Warfare, Avionics, Sensors Fires Logistics Systems Business Systems Enterprise Solutions Field Software Engineering Acronyms:

• AMC: Army Materiel Command

• CECOM: Communications-Electronics Command

2

U.S. Army Materiel Command | Communications-Electronics Command 3

0

100000

200000

300000

400000

500000

600000

700000

800000

900000

1000000

0

100

200

300

400

500

600

700

800

900

1000

FY05 FY07 FY09 FY11 FY13 FY15 FY17

Man

po

we

r

Fiscal Year

Manpower Actual

Manpower Required (per OPS 29)

Manpower Authorized TDAs

Total PPSS $ Funded

Total PPSS $ Required (OPS 29)Fu

nd

ed

/Re

q. ($

in K

)

FY12 Manpower includes section 852 funded

FY 07 normalized to FY 08

"Buy down" of $77M

FY08 normalized to above and "Buy down" of $33M

Manpower

AMC CECOM Depot

Maintenance PPSS

Acronyms:

• PPSS: Post Production Software Support


OMA 72.5%

$1,022.5M

OPA 23.9%

$336.7M

RDTE

2.8% $39.2M

WCF 0.8%

$10.7M FMS 0.1%

$1.7M

Customer 58% Customer Program

$841.5M 59.6%

Direct Program

$569.5M 40.4% Customer 58% Business Systems $306.3M (21.7%)

Battlespace Systems

$1,104.7M (78.3%)

Acquisition Support

$375.9M (26.6%) PDSS/PPSS

$1,035.1M (73.4%)

Other Army

16% CECOM

11.5% PEO EIS 11.5%

PEO IEWS 37% PEO C3T 19%

Other DoD 5%

PEO EIS

$162.3M 11.5%

PEO IEW&S

$522.0M 37%

PEO C3T

$268.1M 19%

CECOM

$162.3M 11.5%

Other Army

$225.8M 16%

Other

$70.5M 5%

SEC Funding Composition FY11

Material Solution

Analysis

Engineering &

Manufacturing

Development

Technology

Development

Production &


& Support

System LCSE Support

$375.9M (26.6%) $1,035.1M (73.4%) A B C

Acronyms:

• OMA: Operations & Maintenance, Army

• RDTE: Research, Development, Test, & Evaluation

• OPA: Operations, Army

• WCF: Working Capital Fund

• FMS: Foreign Military Sales

• PDSS: Post Deployment Software Support

• PEO: Program Executive Office

• C3T: Command, Control and Communications - Tactical

• EIS: Enterprise Information Systems

• IEW&S: Intelligence, Electronic Warfare & Sensors

4


Depot Maintenance Laws

L03V2

Title 10 section - §2460 provides legal guidance on terminology. “…In this chapter, the term “depot-level maintenance and repair” …The term includes all aspects of software maintenance…” In addition, Frank Kendall, Acting Under Secretary of Defense, Acquisition, Technology and Logistics, signed a memo (5 April 2012) to further clarify: “…his revision also further defines software depot-level maintenance as the repair, adaptive modifications or upgrades, change events made to operational software, integration and testing.” Title 10 §2464. Core depot-level maintenance and repair capabilities ‘‘…It is essential for national security that the Department of Defense maintain a core depot-level maintenance and repair capability…. This core depot-level maintenance and repair capability shall be Government-owned and Government-operated, including the use of Government personnel and Government owned and Government-operated equipment and facilities, throughout the lifecycle of the weapon system….” Section 2472 of Title 10. Prohibition on management of depot employees by end strength. Title 10 §2464. “The civilian employees of the Department of Defense…who perform, or are involved in the performance of, depot-level maintenance and repair workloads may not be managed on the basis of any constraint or limitation in terms of man years, end strength, full-time equivalent positions, or maximum number of employees. Such employees shall be managed solely on the basis of the available workload and the funds made available for such depot-level maintenance and repair.”

CECOM SEC Depot Maintenance personnel are to be based solely on funding and workload.

CECOM SEC is performing a depot maintenance function per title 10 section 2460.

CECOM SEC must have a core capability – government personnel/facilities to maintain systems.

5


• When a system enters PPSS – many requirements are “locked” - use of COTS

vs. an organic capability is basically decided at Milestone B – Executed at

Milestone C (Production).

• Use of COTS products drives many sustainment requirements to include:

license costs, Information Assurance Vulnerability Alerts, Certification &

Accreditation, etc.

• License – Legal financial obligation to use COTS product. Generally

required throughout life.

• IAVAs – Vulnerabilities associated with commercial product that must be

analyzed/incorporated to software code – potential secondary impacts

(IAVA impact other coding).

• C&A – must be performed (regardless of COTS/GOTS); however, COTS

drives many “findings”.

• COTS drives secondary requirements – managerial/project lead time to

manage/purchase COTS, adjust code to accommodate changes from other

systems using COTS, additional releases, etc.

L03V2

Example of Today Challenges:

PPSS in relation to COTS

Acronyms:

• COTS: Commercial Off-The-Shelf

• IAVA: Information Assurance & Vulnerability Assessment

• GOTS: Government Off-The-Shelf

• C&A: Certification and Accreditation

6


Emerging Challenge:

Cyber Attacks

￭ One of Secretary of the Army John

McHugh’s top 10 priorities

￭ Significant area of vulnerability

￭ Only recently being addressed

￭ Applications are current weakest point

￭ DoD “cloud” and data center

consolidation concepts put even more

emphasis on the criticality of

applications security

￭ The Cyber threat will have a lasting

impact on software maintenance

￭ Systems currently in sustainment

￭ Systems entering maintenance phase

￭ Systems under Development

￭ Maintainers have to develop mitigation

strategies

￭ By anticipating future threats we can

develop applications with ‘baked-in’

security measures.

￭ Remember Stuxnet?

Early involvement can assist in developing new applications that are “Born Secure”

7


At the End of the Day…

8

It’s all about the Warfighter!


BACKUP INFORMATION

L03V2

Following slides provide additional

details/Information

9


Depot Maintenance Definition

L03V2

Title 10 section - §2460 provides legal guidance on terminology – Definition of depot-level maintenance and repair: In General.—In this chapter, the term “depot-level maintenance and repair” means (except as provided in subsection (b)) material maintenance or repair requiring the overhaul, upgrading, or rebuilding of parts, assemblies, or subassemblies, and the testing and reclamation of equipment as necessary, regardless of the source of funds for the maintenance or repair or the location at which the maintenance or repair is performed. The term includes (1) all aspects of software maintenance classified by the Department of Defense as of July 1, 1995, as depot-level maintenance and repair, and (2) interim contractor support or contractor logistics support (or any similar contractor support), to the extent that such support is for the performance of services described in the preceding sentence. In addition, Frank Kendall, Acting Under Secretary of Defense, Acquisition, Technology and Logistics, signed a memo (5 April 2012) to further clarify: 10 U.S.C. § 2460 - Definition of depot-level maintenance and repair: Language: Removes the exception for modifications and adds that the definition of depot-level maintenance and repair includes, In the case of either hardware or software modifications or upgrades, the labor associated with the application of the modification. his revision also further defines software depot-level maintenance as the repair, adaptive modifications or upgrades, change events made to operational software, integration and testing.

10


Software Depot Maintenance – “Laymen's Term”

Software maintenance includes all activities following initial hardware operating capability (IOC) and/or the fielding of the system required to maintain the operational capability of the weapon system. DA systems apply Post Deployment/Post Production Software Support.

Activities include:

1. Maintain Organic Infrastructure (labs and associated equipment)

2. Operational: Purchase Licenses, Incorporate Information Assurance Vulnerability Alerts and Perform Certification and Accreditation.

3. Provide Field Support Engineers.

4. Maintain Software:

• Correct faults/errors (driven from field).

• Doctrinal changes (i.e. system from Division asset to Brigade asset).

• Modifications driven by external systems/external influences (i.e. new systems, new data

interfaces, changes to COTS software)

• Modifications driven by user/TRADOC requirement changes

• Change driven by hardware/software obsolescence

• Modification driven by C&A Acronyms:

• DA: Department of the Army

• TRADOC: Training & Doctrine Command

11


Software Depot Maintenance

LIFE CYCLE

A B C

Pre-Systems Acquisition Systems Acquisition Sustainment

Materiel

Solution

Analysis

Technology

Development

Engineering and

Manufacturing

Development

Production and


and Support

Title 10 section 2464: ” Core depot-level maintenance and repair capabilities and capacity, including the facilities, equipment, associated logistics capabilities, technical data, and trained personnel, shall be established not later than four years after a weapon system or item of military equipment achieves initial operational capability or is fielded in support of operations.”

“Wise men memo” (G8, G 3/4/7, Director Army Budget): Software Programs with no (major) programmed development efforts will transition to Post Production Software Sustainment (PPSS) under the following conditions: (1) Software Block General Officer (GO) User Panel has approved software for release, (2) At least 10 percent of the force has been fielded with approved software, and (3) One full fiscal year has elapsed from GO User Panel approval.

AR 750-1/AR70-1 Post Production Software Sustainment (PPSS) initiates first full year after production completion.

12

U.S. Army Materiel Command | Communications-Electronics Command L03V2

Background – Laws/Guidance associated with Depot Maintenance PPSS

In the fiscal year 2012 National Defense Authorization Act. SEC. 327. CORE DEPOT-LEVEL MAINTENANCE AND REPAIR CAPABILITIES. In General.—Section 2464 of Title 10, United States Code, is amended to read as follows: § 2464. Core depot-level maintenance and repair capabilities ‘‘(a) NECESSITY FOR CORE DEPOT-LEVEL MAINTENANCE AND REPAIR CAPABILITIES.— (1) It is essential for national security that the Department of Defense maintain a core depot-level maintenance and

repair capability, as defined by this title, in support of mission-essential weapon systems or items of military equipment needed to directly support combatant command operational requirements and enable the armed forces to execute the strategic, contingency, and emergency plans prepared by the Department of Defense, as required under section 153(a) of this title.

(2) This core depot-level maintenance and repair capability shall be Government-owned and Government-operated, including the use of Government personnel and Government owned and Government-operated equipment and facilities, throughout the lifecycle of the weapon system or item of military equipment involved to ensure a ready and controlled source of technical competence and resources necessary to ensure effective and timely response to a mobilization, national defense contingency situations, and other emergency requirements.

Therefore: DA Software sustainment organizations must have GOVERNMENT workforce and facilities able to maintain the operational capability of ANY system in depot maintenance; however, due to HQ AMC mandated personnel limits, cannot meet the legal requirement.

13



Section 2461 of Title 10, United States Code notes the Department is prohibited from converting work currently performed (or designated for performance) by civilian personnel to private sector (contract) performance without first conducting a public-private competition. The National Defense Authorization Act for fiscal year 2010 (public Law 111-84) included a significant modification to this statute, extending the requirement for a public-private competition prior to the conversion of work by any number of civilian employees. The Department is currently precluded, under a moratorium, from conducting public-private competitions. This prohibits the conversion of any work currently performed (or designated for performance) by civilian personnel to contract performance. This prohibition applies to functions and work assigned to civilians, regardless of whether or not the position is encumbered. When new requirements arise, such as those that may occur as military end-strength levels are reduced, special consideration must first be provided, consistent with section 2463 of title 10, U.S.C., and applicable Department policies, to using Department of Defense civilian employees..

Therefore: DA sustainment organizations are prohibited from converting work from Government to Contractor Personnel; however, with NO reduction of mission – MUST DO to meet mission.

14



Section 2466 of Title 10. Limitations on the performance of depot-level maintenance of materiel. (a) Percentage Limitation. - Not more than 50 percent of the funds made available in a fiscal year to a military department or a Defense Agency for depot-level maintenance and repair workload may be used to contract for the performance by non-Federal Government personnel of such workload for the military department or the Defense Agency.

In relation to CECOM SEC, due to Manpower restrictions imposed by HQ AMC/CECOM on personnel performing the depot maintenance function, about 85% of the workforce supporting CECOM SEC depot maintenance PPSS is a contractor workforce. Although the 50/50 rule is at the department level, by SEC having such a high ratio of contractor support, other DA organizations are required to have a much larger government workforce to counter the heavy contractor workforce used by SEC. As more systems enter PPSS in the POM with no increases to government manpower, this will impact the 50/50 percentage to a greater extent.

15



Section 2472 of Title 10. Prohibition on management of depot employees by end strength. The civilian employees of the Department of Defense, including the civilian employees of the military departments and the Defense Agencies, who perform, or are involved in the performance of, depot-level maintenance and repair workloads may not be managed on the basis of any constraint or limitation in terms of man years, end strength, full-time equivalent positions, or maximum number of employees. Such employees shall be managed solely on the basis of the available workload and the funds made available for such depot-level maintenance and repair.

Therefore: per Title 10 Section 2464 as amended in FY12 Defense Authorization act and April 5th 2012 clarifying memo from USD(ALT), DA software sustainment personnel maintaining systems are performing a Depot Maintenance function. Therefore, prohibited to limit personnel to manpower targets. However, HQ AMC has imposed manpower limits to LCMCs.

16


Backup - Depot Maintenance “Software

Maintenance” Definition per 50/50

L03V2

Code U - Software Maintenance. Used to report software maintenance that includes all activities following initial hardware operating capability (IOC) and/or the fielding of the system. Software maintenance must be reported regardless of location or funding source. Activities include all events to maintain operational capability, correct faults, improve performance, and adapt the software to environmental changes or new requirements. These activities include (1) change events made to operational software resident in military materiel (including weapon systems and their components and space control systems and their components) as well as the associated software technical data, automated test equipment (ATE), including interface test adapters (ITA) and test program sets (TPS), and laboratory support (simulation or stimulation software, data acquisition or reduction software); and (2) software infrastructure maintenance which includes the purchasing of license agreements, maintaining standards that ensure the software is certified and accredited to operate safely, conducting information assurance vulnerability assessments (IAVAs), etc. Change events include the corrective maintenance or fixes which successfully repair faults discovered in the software, preventive maintenance or fixes which detect and correct latent faults in the software, adaptive modifications or upgrades which incorporate enhancements made necessary by modifications in the software or hardware (operational) environment of the program, or perfective modifications or upgrades which incorporate enhancements demanded by the users. Unless otherwise specified, software maintenance and software sustainment are considered synonymous.

17


Secretary of Army Software Initiative

L03V2

Secretary of Army memo (Oct 1, 2012): A. Review equipment in Inventory for Possible Divestiture. B. Establish Procedures/Processes to ensure sustainment costs addressed pre-

milestone B. C. Improve Life Cycle Models for software maintenance estimating. D. Optimize software support in the field. E. Ensure license purchases/use are optimal. F. Develop recommendations on ownership of data rights. G. Develop Guidance on purchase and use of COTS. H. Ensure software acquisition, sustainment and Integration to COE are factored

into costs. Eliminate redundancies within and between RDECOM and LCMCs. I. Create ability to track expenditures of PPSS. ID potential changes to

policies/regulations/laws that restrict ability for efficiencies. J. Examine improved management of software.

Acronyms:

• COE: Common Operation Environment • RDECOM: Research Development and Engineering Command • LCMC: Life Cycle Management Command

18


C4ISR is a Growth Business 1800’s 1900 – 1950 1950 – 2000 2000+

19


STARTING DATA POINT ENDING DATA POINT WORKLOAD

YR # YR #

Number of

Systems/Programs 1983 37 2011 400 +1081% over 28 years

Software Releases 1997 64 2011 378 +591% over 14 years

Software Licenses 2004 34,205 2011 131,037 +383% over 7 years

System Size/Complexity 1970 Small 2011 Med-Large 500+%

PPSS Requirements 2003 $126M 2011 $569.5M +452% over 8 years

Customer Requirements 2001 $179M 2011 $841.5M +470% over 11 years

SEC’s Software Workload Trends

• Software is a large and growing part of DoD systems • Software delivers much of today’s systems’ functionality • Most items the Soldier uses are driven by or managed with SW

As a result, SEC and software costs have grown Continued management and efficiency required to remain affordable

20


POM CECOM SEC Post Production Software Support Requirements:

L03V2

FY13 FY14 FY15 FY16 FY17 FY18

Must Fund-Infrastructure (14) 110.8 117.9 119.8 125.0 127.3 133.8

Must Fund - Operational (17) 194.7 210.4 212.6 217.9 236.7 255.7

Licenses 132.7 139.6 142.6 146.7 164.4 180.3

IAVAs 49.9 54.9 55.1 55.9 57.1 59.3

C&As 12.1 15.9 14.9 15.3 15.2 16.1

FSEs (24+38+50) 138.4 150.5 151.7 155.0 154.3 179.3

Capability Sets (25+32+39+51) 85.4 87.2 81.5 101.0 94.5 105.4

Sys Msn Cap (26+40+52) 168.2 199.9 211.8 213.4 220.1 218.4

TOTAL 697.5 765.9 777.4 812.3 832.9 892.6

Challenges with PPSS in relation to COTS:

Significant driver is use of COTS Products Acronyms:

• FSE: Field Software Engineer • POM: Program Objective Memorandum

21


1. Disjoint between manpower ceilings/targets (limiting manpower to TDA vs. mission) for Depot Maintenance PPSS mission will increase reliance on contractor workforce. Estimated FY13 ratio of contractor to government workforce is 90% contractor, 10% government for depot maintenance PPSS mission.

2. TDAs do not account for new systems entering PPSS. FY13, eight systems enter PPSS requiring fourteen additional manpower authorizations or overhire authority. FY14 Thirteen systems entering PPSS, requiring 34 additional manpower authorizations or overhire authority.

3. Non mission supporting administrative requirements/calls for data/audits/etc. from HQ continue to increase, requiring personnel to perform/answer/etc.

Manpower Challenges to Support Depot

Maintenance PPSS

22

Acronyms:

• TDA: Table of Distribution and Allowances

2012 dod maintenance symposium - sae international€¦ · electronic warfare, avionics, sensors...

Documents