system of systems architecture and tspr contractor model · tspr roles for client • develops,...
TRANSCRIPT
Conf on the ACQ of SW-IntensiveSystems
1UpStartSystems
System of SystemsArchitecture and
TSPR Contractor Model
Conference on the Acquisitionof Software-Intensive Systems
January 29, 2003
Jonathan D. Addelston(mailto:[email protected])
Conf on the ACQ of SW-IntensiveSystems
2UpStartSystems
Presentation Goal
• Base discussion a recent 10-month study for akey intelligence agency (without attribution)
• Identify acquisition issues driving the agencyPMOs for mission critical IT systems
• Show relationship between System-of-SystemsArchitecture and TSPR Acquisition Model
• How well does the TSPR approach respond tothe software-intensive acquisition issues?
Conf on the ACQ of SW-IntensiveSystems
3UpStartSystems
Agenda
• Acquisition Organization Pressures• Very Quick View of System-of-Systems
and its Architecture(s)• TSPR – Total System Performance
Responsibility Contracting– Overarching Systems Integrator
• Acquisition Process Changes
Conf on the ACQ of SW-IntensiveSystems
4UpStartSystems
Acquisition Issues “Nightmare”
ArchitectureAs a Goal or Standard?
(S)COTS Products
System Safety and Security
Technology Adoption
System of Systems
Roadmap
Trusted Agents
Industrial Base
Checks and Balances
Client Core Competencies
Governance and IPTs
Client R&D Investments
Client eBusiness Transition
Client Mission and Strategy
IV&V Contractor
Client Organization
System Delivery
System Operations and Maintenance
Life Cycle
Project Definition
Process Improvement(Maturity, Capability)
Of Client
Of Contractors
CMM-SWCMMISA-CMMFAA-iCMMOther Models
Transition
Incentives
Other
Conf on the ACQ of SW-IntensiveSystems
5UpStartSystems
Acquisition PMO Issues
• Limited trained, skilled acquisition managementteam struggling with multiple systems contracts
• Attempting process improvement without keycore competencies
• Hoping to gain control while outsourcing criticalfunctions and decisions
• Unanticipated impacts on acquisition processesand controls
• Massive management and technical controlchanges
Conf on the ACQ of SW-IntensiveSystems
6UpStartSystems
TraditionalAcquisition Documents
• Statement ofObjectives (SOO)
• OperationalRequirementsDocument (ORD)
• Statement ofRequirements (SOR)
• Systems OperationsConcept (SOC)
• Statement of Work(SOW)
• Concept ofOperations(CONCOPS)
• System RequirementsDocument (SRD)
• System Architecture(“as is” and “to be”)
Conf on the ACQ of SW-IntensiveSystems
7UpStartSystems
Acquisition Overview
RFI RFP
TeamingAgreements
BAFO Contract
Subcontracts
Proposal
RFQ Quote
Conf on the ACQ of SW-IntensiveSystems
8UpStartSystems
Agency Program Management
Pre-Acquisition
Systems-Level Program Managemnt
SystemsIntegration
(across contractlines)
SystemsEngineering
(SystemAcquisition)
SystemsMaintenance
Business Ops
Systems andNetwork(IS / IT)
Operations
Acquisition:System
ContractorSelection
System of SystemsProgram
Management
ArchitectureManagement
QualityAssurance
ProcessManagement
CCB
Conf on the ACQ of SW-IntensiveSystems
9UpStartSystems
System of Systems Architecture
After Behind the Wizard's Curtain, Figure 2-1
System
System SystemSubsetOf SOS
System of Systems(SOS)
Conf on the ACQ of SW-IntensiveSystems
10UpStartSystems
Client Organization
Client
R&D (S)COTS Delivery IV&V
Trusted Agents
Prime Contractor X Prime Contractor Y Prime Contractor Z
Subcontractor A
Subcontractor B
Conf on the ACQ of SW-IntensiveSystems
11UpStartSystems
TSPR and Requirements
SystemElement y
ORD, CONOPS, SOO & SORClientResponsibility
SystemArchitecture
TSPRResponsibility
Element Reqts.Documents
(ERDs)
SystemElement x
SystemElement z...
SOC
Data ArchSys Arch
Tech ArchOps Arch
andStandards
RequirementsDecomposition
CONOPSSOOSOR
CONOPSSOWSRD
Client reviews andapproves only theSystem Architecture
TSPR produces, reviews,and approvesthe top-level reqts docs.
TSPR conducts all technical reviews below the Architecture level and has approval authority.
DeliveryContractorResponsibility
SLC Work Packages SLC Work Packages SLC Work Packages
Conf on the ACQ of SW-IntensiveSystems
12UpStartSystems
TSPR and ArchitectureORD, SOO, SOC, and SOR
System Architecture
Element RequirementsDocuments (ERDs)
Element y Element zElement x
SLC WorkPackages
SLC WorkPackages
SLC WorkPackages
ClientResponsibility
Reviews and Approves onlythe System Architecture
Operational View(CONOPS)
TSPR produces,reviews, andapproves the top-level requirementsdocuments
TSPRResponsibility
SystemDeliveryContractorResponsibility
TSPR conducts all technical reviews below the Architecture leveland has approval authority
Conf on the ACQ of SW-IntensiveSystems
13UpStartSystems
TSPR Integrated Master PlanORD, SOO, SOC, and SOR
SystemIntegrated Master Plan
Element Plan x Element Plan y Element Plan z
ClientResponsibility
TSPR Contract withPerformance Targets andGoals
Lower-level Plan integration andinter-project commitments
TSPRResponsibility
SystemDeliveryContractorResponsibility
Element Delivery Project Plans roll up into the Integrated Master Plan.TSPR monitors costs, schedules, requirements, deliverables, services, and risks.
TSPR reviews andapproves plans for elementand component delivery;monitors and reviewsdetailed status
Reviews TSPR against performance targets,incentive plans, and critical milestones, in theIntegrated Master Plan
ArchitectureMigration Plan
Conf on the ACQ of SW-IntensiveSystems
14UpStartSystems
TSPR SubcontractsTSPR Prime Contract
TSPR Contract CLIN andTask Allocation
Contract B Contract CContract A
Ax CLINsand SubKs
ClientResponsibility
Single system deliverycontract supported byTrusted Agents
TSPRResponsibility
SystemDeliveryContractorResponsibility
TSPR may allow any or all of its subcontractors to use one or moresubcontractors of its own to meet its contractual obligations to the TSPR.
Whether or not subcontractors are competitively awarded depends uponthe flexibility provided to the TSPR and its subcontractors by the client.
TSPR chooses anysubcontract type forproducts and services;may have multiplecontracts with someproviders
TSPR uses its ownresources or subcontracts
By CLINsand SubKs
Bz CLINsand SubKs
Bx CLINsand SubKs
Ay CLINsand SubKs
Cy CLINsand SubKs
Cz CLINsand SubKs
Conf on the ACQ of SW-IntensiveSystems
15UpStartSystems
TSPR “End-to-End”
• End-to-end responsibility means:– Control of all of the system components from
the beginning to the end of any systeminteraction or transaction
– Control of the system engineering life cycle• From the elicitation of detailed requirements
through the operation of the deployed systemthrough system retirement
• With certain key exceptions, especially at keycontrol points during the integration phase thatare not even under client’s control
Conf on the ACQ of SW-IntensiveSystems
16UpStartSystems
Acquisition Changes
• Long term partnership with dominant prime• Less of technology control• Less of contractor community control• Fewer contract deliverables reviews and
approvals (open loop implementation?)• Dependency on TSPR incentives for influence in
lieu of control• Complex commitment process for integration
with external systems• Non-traditional acquisition, program, and
technical management skills still required
Conf on the ACQ of SW-IntensiveSystems
17UpStartSystems
Backup Slides
Conf on the ACQ of SW-IntensiveSystems
18UpStartSystems
Acronyms (reference)• ASCON Associate Contractor• CLIN Contract Line Item Number (item itself)• CMM Capability Maturity Model• CMMI Capability Maturity Model Integrated• CMM-SW Capability Maturity Model for Software• CONOPS Concept of Operations• COTS Commercial Off-the-Shelf (product)• FAA Federal Aviation Administration• iCMM Integrated CMM from FAA (see CMMI)• IEC International Electrotechnical Commission• IPPD Integrated Product and Process Development• IPT Integrated Product Teams• ISO International Standards Organization• IV&V Independent Verification and Validation• O&M Operations and Maintenance• ORD Operational Requirement Document• OSSP Organizational Standard Software Process• R&D Research and Development• RFI Request for Information• RFP Request for Proposal• RFQ Request for Quote
• S&S Safety and Security• (S)COTS Standard Commercial Off-the-Shelf (product)• SA Software / System Acquisition• SE System Engineering• SI System Integration• SOO Statement of Objectives• SOC System Operating Capability• SOR Statement of Requirements• SOW Statement of Work• SRD System Requirement Document• SubK Subcontract• SW Software• TSIR Total System Integration Responsibility• TSPR Total System Performance Responsibility
Conf on the ACQ of SW-IntensiveSystems
19UpStartSystems
Systems Life Cycle Eye Test
Pre-Acquisition
AcquisitionSystems
EngineeringSystems
IntegrationOperations Maintenance
Systems-LevelProgram Managemnt
Unplanned iterations slow the pipeline
deployment
Conf on the ACQ of SW-IntensiveSystems
20UpStartSystems
Four Acquisition Models
• The “Four Horsemen”– System Engineering (SE)– System Integration (SI)– Total System Integration Responsibility (TSIR)– Total System Performance Responsibility
(TSPR)
• To transition smoothly from SystemsEngineering to TSPR, use the other two
Conf on the ACQ of SW-IntensiveSystems
21UpStartSystems
TSPR, TSIR, and SI Intent(Theory)
• Total System Performance Responsibility (TSPR)– A contract team is responsible for performance of end-to-end system
capabilities, from the development of detailed requirements, throughdeployment and operations
• Total System Integration Responsibility (TSIR)– A contract team is responsible for delivery of an end-to-end system that
has pieces already developed and available (constraining the approach)from Associate Contractors (ASCONS), (S)COTS vendors, or theGovernment, from the end of system test (beginning of systemintegration) through deployment
• System Integration (SI) including System Engineering (SE)– A contract team is responsible to prepare for system integration through
deployment and to recommend to the government effective and efficientstandards, plans, decisions, and actions to ensure successful systemintegration
Note: TSPR and TSIR introductory phrases are based heavily on TSPR presentation by Al Hoheb, Systems Planningand Engineering, The Aerospace Corporation, 20 March 1998.
Conf on the ACQ of SW-IntensiveSystems
22UpStartSystems
Control Spectrum
At the left end, more control is retained by client.At the right end, more control is allocated to the Prime Contractor.
SES SI TSIR TSPR
System EngineeringServices
SystemIntegrator
Total SystemIntegration
Responsibility
Total SystemPerformance
Responsibility
In each case, the Prime develops the Architecture, maintains acomprehensive Integrated Master Plan, and manages IT Infrastructure, inresponse to the Problem Statements. The Client retains an appropriatelevel of SA, SE, and SI support from independent trusted agents.
Conf on the ACQ of SW-IntensiveSystems
23UpStartSystems
TSPR Definition• A systematic and tailored management strategy that is
implemented by a contractor team which is responsible for theperformance of end-to-end system capabilities.
• A strategic partnership between a government agency or majorprogram and its exclusive (total) systems development primecontractor:– Exploiting the core competencies of each organization– Including System Acquisition (through subcontractors), System
Engineering (including System Architecture), and System Integration(including final testing, exercises, deployment, operations, andmaintenance)
– Based on (1) operation concepts, general objectives, and top-levelrequirements including system performance and (2) allocation ofauthority and substantial control to the TSPR Prime Contractor fordetailed requirements and implementation within broad schedule andcost constraints and detailed quality objectives
Conf on the ACQ of SW-IntensiveSystems
24UpStartSystems
TSPR Roles• Develops, uses, improves, and enforces the architecture, as
approved by client, as the systems blueprint for all contractors,including relationship of requirements to (S)COTS products (withSCOTS-specific roles) and to approved technologies
• Delivers (S)COTS-based and mission-specific solutions in systemlife cycle from requirements allocation through O&M
• Develops and manages to the integrated master plan across thesystem life cycle from after research investment through retirement
• Manages system acquisition, engineering, and integration, includingprocess improvement, through itself and subcontractors, including ITinfrastructure provisioning and management, except for functionsallocated to research, SCOTS-specific, (I)V&V S&S, and “trustedagent” (advisors) contracts which it monitors
• Manages from top-level requirements and prioritization provided byclient (ORD-level) and runs the requirements elicitation,requirements management, and prioritization processes (SRD-level)for individual systems projects
Conf on the ACQ of SW-IntensiveSystems
25UpStartSystems
TSPR Roles for Client• Develops, uses, improves, and enforces the architecture, as
approved by Client, as the systems blueprint for all contractors,including relationship of requirements to (S)COTS products (withSCOTS-specific roles)
• Delivers (S)COTS-based and mission-specific solutions in systemlife cycle from requirements allocation through O&M
• Develops and manages to the integrated master plan across theSystem life cycle from after research investment through retirement
• Manages system acquisition, engineering, and integration throughitself and subcontractors, including IT infrastructure provisioning andmanagement, except for functions allocated to research, SCOTS-specific, (I)V&V S&S, and “trusted agents” (advisory contractors)
• Manages from top-level requirements and prioritization provided byClient (ORD-level) and runs the requirements elicitation,requirements management, and prioritization processes (SRD-level)for individual systems projects
Conf on the ACQ of SW-IntensiveSystems
26UpStartSystems
TSPR Transition• TSPR cannot be introduced immediately with full TSPR
responsibility and accountability because its risks with respect to thecurrent system implementation and ongoing projects would be toogreat.
• In the simple model, TSPR shadows the SE contractor and takesover the responsibilities as a SES (System Engineering Support)Contractor.
• Then it transitions to take over SI responsibilities for incrementalparts of the system, overlapping with some SES functions.
• Then it transitions to take over TSIR responsibilities for incrementalparts of the system, overlapping with some SES and SI functions.
• Then it transitions to take over TSPR responsibilities for incrementalparts of the system, overlapping with some SES, SI, and TSIRfunctions.
Conf on the ACQ of SW-IntensiveSystems
27UpStartSystems
Architectural Transition• A more realistic model for the TSPR transition takes advantage of
prioritization within the System Architecture, as in the ArchitectureMigration Strategy, starting at the time the TSPR contract starts:
– New parts that have to be delivered with or without (S)COTS components– High priority parts due to high priority requirements to be met or existing high risk
conditions with impact on high priority parts– Medium priority parts due to priority and risk, including heritage systems that will
continue in the Architecture– Low priority parts due to priority and risk, including legacy systems that will
continue in the Architecture– Parts in maintenance or “unattended” mode that need little attention, based on
failure and maintenance records; this includes (S)COTS products andinfrastructure components
– Parts (typically legacy or heritage) that are scheduled for rapid replacement andlow-level maintenance (rapid retirement) that may never become the TSPR’sresponsibility
Conf on the ACQ of SW-IntensiveSystems
28UpStartSystems
Architectural Migration• New, funded systems have highest priority, otherwise
resources and funding would address enhancement ormaintenance of other systems
• Enhancement of existing systems meets new andemerging customer requirements with new andimproved technologies, (S)COTS products, and specialdevelopment
• Maintenance of existing systems addresses repairsand achieving existing commitments for requirementsimplementation and deployment
• Near-retirement systems can be addressed throughexisting contractors without System Prime involvement
• IT Infrastructure Operations support configuration andoperation of existing and improving SystemInfrastructure Elements for prototyping, testing, andoperations
Legend
Newsubsystem
HighPriority
MediumPriority
LowPriority
Mainten-ance Only
EarlyRetirement