joint program executive office - omg program executive office ... !develop proposal for joint ca...
TRANSCRIPT
18 August 2005Vic Popik
Director of Operations, JPEO JTRS(858) 537-0537
JPEO JTRS
Joint Program Executive Office Joint Tactical Radio Systems (JPEO JTRS)
JPEO JTRS Overview to OMG
Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Brian SalisburySCA Manager, JPEO JTRS
(619) [email protected]
2Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Outline
!JPEO JTRS Organization
!JTRS Program Priorities
!Systems Engineering Approach
!JTRS Standards
3Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JPEO JTRS Organization
4Statement A: Approved for public release; distribution is unlimited (18 August 2005)
4 February 05 JTRS ADM!USD (AT&L) retained Milestone Decision Authority for all JTRS
Products
!Established a JPEO for the JTRS program– Reports directly to USD AT&L
!Empowered JPEO with full directive authority for:– All waveform, radio, and common ancillary equipment development– Systems engineering– Performance and standards– R&D funding
!Directed JPEO to immediately:– Assess all Clusters and make recommendations– Develop an organizational structure
5Statement A: Approved for public release; distribution is unlimited (18 August 2005)
USD (AT&L) chairsthe JTRS BoD
JTRS BoD
JCS (J-6)*
Component SAEs*
ChairExecutive Secretary/
NII OIPT Leader
ASD (NII)*
* = IAW DoD Directive 5144.1, dated 2 May 2005, Subject: Assistant Secretary of Defense for Networks and Information Integration/DoD Chief Information Office (ASD (NII)/DoD CIO)
Joint Waveforms Ground and Vehicular
Handheld JEM
Handheld, Manpack, Small Form Fit
AMF
MIDS-JTRS
JPEO JTRS
USD (AT&L)
JPEO JTRS OrganizationReporting Authorities
6Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JPEO JTRS D. Bauman619.524.7358
MIDS JTRSD. Prater, CAPT, USN
Ground and VehicularA. Dwyer, COL, USMC
Director, OperationsV. Popik
Handheld JEMR. Lough
813.281.0560 [email protected]
AMFM. Kercher, CAPT, USN
Director, Business Financial Management
L. Ramsey619.524.7363
Director, AcquisitionR. Fix
Technical DirectorR. North
Executive AssistantJ. Mowery, CAPT, USN
Deputy JPEOH. Pace
Joint Waveforms Dr. R. Knudsen
Handheld, Manpack, Small Form Fit A. Dwyer, COL, USMC
JPEO JTRS Organization
7Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JPEO JTRSTechnical Director Organization
TechnicalDirector
Support(Admin /
Washington Liaison / Process Improvement /
QA / Risk Mgt)
I/A andInfo. Security
SystemsEngineeringCapabilities
Joint SECouncil
ClusterPMOsCluster
PMOsClusterPMOsClusterCHENGs
PM Joint Waveforms
Tech Insertion
Life CycleSupport
JTRS Standards
Test & Evaluation
Deputy Technical Director
8Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTRS Program Priorities
9Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Way AheadProgram Priorities
!Develop and deliver incremental Transformational capabilities to the warfighter– Mobile ad-hoc networking– Cross-banding
! Return programs to executability through proper:– Discipline in requirements, resourcing, and acquisition– Risk management
! Technical! Cost! Schedule
!Establish an open JTRS technology base to promote:– Interoperability– Affordability (e.g., reuse, portability, etc.)– Speed to capability
10Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Actions Taken – First Five Months
!Assessed Clusters 1 and 5, AMF and status of waveforms
!Initiated draft replan of Clusters 1/5/AMF/Waveforms– Reduced high risk programs to moderate risk, incremental development
approach while maintaining current requirements baseline
!Established and strengthened an overall JTRS management structure– Created a centralized JPEO organization with clear R&R, accountability and
reporting– Institutionalizing processes for overall systems engineering across programs
!Engaged key, dependent transformational programs to align to their requirements– FCS - MUOS– BSN - Flight Plan
11Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Way AheadNear-term Strategy
!Execute remaining actions of 4 Feb 05 ADM– Assess remaining Clusters
!Replan Cluster and Waveform developments– Strategize on JTRS JCIDS process to support incremental capability
development and delivery– Assess technology base– Prioritize and construct way ahead for waveforms– Develop an incremental acquisition strategy
!Provide DoD and Congress an executable program plan
12Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Systems Engineering Approach
13Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Systems Engineering
!JPEO JTRS will establish a comprehensive and robust JTRS System Engineering Office – Cluster PMOs, NSA, and industry will work together with the
JPEO JTRS technical staff to solve common technical issues as a team
– Focus Areas!Capabilities!Test and Evaluation! Information Assurance!Life-Cycle Support!JPEO Standards
14Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Systems Engineering Approach
!Planned Approach:– Develop and implement overarching and effective processes in
key technical areas (e.g. requirements, configuration control, risk management)!Create JTRS System Engineering Plan (SEP)
– Collaborate across the JTRS government / industry enterprise team to provide common technical solutions!Establish Systems Engineering Council
– Support JPEO JTRS in the efficient management, oversight, and control of the acquisition programs!Evaluate and control short-term efforts in the interest of the
common good– Dual focus: internal support of program execution and product
delivery and outward role of JTRS within system of systems
15Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Systems Engineering Approach
!Focus on networking waveforms– JAN-TE (Joint Airborne Network-Tactical Edge)
!TTNT, WNW-OFDM, FAST, F-35 FDL
– WNW (Wideband Networking Waveform)– SRW (Soldier Radio Waveform)
!JTRS Network Architecture Strategy development– Propose a network architecture strategy that aligns with
existing efforts (JTRS DoDAF, FCS, BSN, capabilities, etc.)
!Develop acquisition alternatives
16Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Focus Areas
17Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Information Assurance
!Objectives– Facilitate/coordinate NSA certification efforts of clusters
!Help resolve issue of “in-between” SFF requirements!Help resolve throw-away cryptos issue!Help resolve SW/OS encryption requirements issue!Help resolve WF/SW classification issue
– Promote JTRS enterprise-wide initiatives!Develop proposal for Joint CA (Certification Authority)!Assess feasibility of enterprise-wide KMP and key distribution
processes!Assess feasibility of early waveform/CEA testing
– Facilitate a regular IA issues discussion forum
18Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Capabilities
!Capabilities Priorities– JTRS Wireless CONOPS– Top Level System of Systems Architecture– Waveform Migration Roadmap– JTF WARNET Lead
19Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Test & Evaluation
!Test and Evaluation Objectives– Develop and maintain T&E related policy & guidance– Liaison to Operational Test and Test Oversight Agencies
!Approach– T&E Policy
!Recommends policy changes and initiatives. !Articulates JPEO JTRS’ position on recommended changes
– Develop and coordinate Joint/Capstone TEMP for the JPEO JTRS.
– Coordination of Modeling & Simulation– SCA Compliance T&E
20Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Life – Cycle Support
!Objectives– Develop and execute a software management process (i.e.
business model) for JTRS
!Critical JPEO Risks Addressed– Waveform availability– Expectation for delivery of defect free waveform software
21Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Proposed JTRS SW Development Model
JTRSRepository
(web-based)
JTRS PCRDatabase
(web-based)
Rqmts Design Code Test FQT
Software Development
Verification
JTRSStandards
Testing
AdditionalTests(TBD)
JTRS Test Lab
SSA
CDT GDT JITC OT
JTRS Development / Testing / Maintenance Environment
DD-250 signed aftersuccessful JITC
Post-JITCPCRs
Pre-JITC PCRs
EvaluatePCRs
(Programmatic)
EvaluatePCRs
(Technical)
Contract /SourceSelect
Software Support Activity
Incremental Code Drops Problem / Change Reports
Government CommercialLegend:
Test Signature OperationalSignature
22Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTRS Standards
23Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTRS StandardsOverview
!Mission– To establish baseline specifications and standards for the
JTRS Enterprise– To maintain and manage JTRS standards and specifications
and to guide their future evolution.
!Current Responsibilities– Software Communications Architecture (SCA)– JTRS Common Application Program Interfaces (APIs)
!JTR Service APIs!JTR Device APIs!Hardware Abstraction Interface Standards (HAL)
24Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTRS Standards
!Approach – near term– JTRS Common Application Program Interfaces (APIs):
!Establish process for standardizing JTR APIs- Evaluation of Cluster 1 APIs
!Maintain Configuration Management over all standardized JTR APIs
!Chair Interface Control Working Groups
– SCA:!Create Standards Board to address interpretation issues related to
v2.2 (no Change Proposals (CPs))!Work with NSA on Security Supplement Issues/Ownership.!Collect and review issues from Cluster developments
25Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTRS Standards
!Approach – long term– APIs:
!Evolutionary improvement of APIs!Hardware Abstraction Layer (HAL) standard
– SCA:!Redefine SCA TAG/CCB Process!Evaluate SCA concerns and issues with Industry and International
organizations!Work at aligning SHS with API Standardization efforts and
propose a way forward!Provide an update to the SCA to serve as the development
baseline
26Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTRS Infrastructure Baseline
Cluster 1 MHAL
Tailored
JTRS HWAbstraction Layer
(HAL)
Cluster 1 RadioServices
Tailored
StandardizedJTRS ServiceDefinitions and
APIs
Cluster 1Devices
Tailored
StandardizedJTRS Device
Definitions andAPIs
JTRS Infrastructure Baseline
Step 1: Published C1Standards (Platform
Specific)- ITAR -
Step 3: Published,Platform Independent
JTRS Standards- No ITAR (goal) -
Step 2: Tailoringwhere required
!Preserves compatibility with current Cluster 1 developments without limiting other developments
27Statement A: Approved for public release; distribution is unlimited (18 August 2005)
JTR API SpecificationStrategy
!JPEO Role– Maintain Configuration Management over all standardized JTR
APIs!Grant final approval for API changes based on established criteria
(TBD) with regard to appropriateness for the JTRS enterprise anddegree of compatibility with existing APIs.
!Determine timeline for incorporation of API changes in the overall JTRS development schedule
!Review and maintain API documentation (after initial submission
– Chair Interface Control Working Groups (ICWGs)!Mitigate decisions on conflicting requirements
28Statement A: Approved for public release; distribution is unlimited (18 August 2005)
SCA
SCA 2.2
SCA 2.2Main Document
SCA 2.2Appendix A
Glossary
SCA 2.2Appendix B
AEP
SCA 2.2Appendix C
IDL
SCA 2.2Appendix D
Domain Profile
SCA 2.2Security
Supplement
SCA 2.2API Supplement
- Address known issues and approved CPs- Refine Requirements Language (including SRD)- Solicit and Address other concerns
JTR
S A
PIs
NS
A
!The JPEO is evaluating the current status of the SCA with respect to near-term goals and obligations.– Path-forward must support current developments but offer path for
needed improvements.
29Statement A: Approved for public release; distribution is unlimited (18 August 2005)
SCAStrategy
!Support current SCA (JTRS) development efforts– Create Standards Board to address interpretation issues related to
v2.2– Open SCA web portal
! Remove anonymity to encourage contributions (socialization)! Improve service mechanisms! Begin disposition of 200+ outstanding CPs
!Support future SCA efforts– Redefine SCA TAG/CCB Process– Provide an update to the SCA to serve as the development baseline– Encourage commercial and international support of CP process
! Adopt a documented plan for architectural evolution of the SCA with commercial and industry support
30Statement A: Approved for public release; distribution is unlimited (18 August 2005)
Questions