EXECUTIVE SUMMARY
TABLE OF CONTENTS
LIST OF FIGURES
LIST OF TABLES
1.0 INTRODUCTION
1.1 Purpose of the NATO CALS Handbook
1.2 Background
1.2.1 Continuous Acquisition and Life-cycle Support
1.2.2 The Challenge to Decision Makers
1.2.3 Industry Perspective
1.2.4 Military Perspective
1.2.5 The Multi-National Program Perspective
1.2.6 NATO Perspective
1.2.7 NATO CALS
1.2.7.1 Going Digital Now
1.2.7.1.1 Through Life Management
1.2.7.1.2 Through Life Information Management
1.2.7.1.3 Shared Data Environment
1.3 Managing the Life-cycle Process
1.3.1 NATO CALS Environment
1.3.2 Program Management Issues
1.3.2.1 Relationship Management
1.3.2.2 Continuous Review and Approval
1.3.2.3 Contract Management
1.3.2.4 Financial Management
1.3.3 Technical Information Management Issues
1.3.3.1 Requirement Management
1.3.3.2 Configuration Management
1.3.3.3 Quality Assurance
1.3.3.4 Information Management
1.3.4 The Staged Process for Through Life Information Management
2.0 STAGE 1: DEVELOPING A THROUGH LIFE INFORMATION MANAGEMENT STRATEGY
2.1 Develop Improvement Targets
2.2 Analyze Environment and Options
2.2.1 Business Environment and Options
2.2.1.1 External Environment
2.2.1.2 DS Program Process Improvement Tool
2.2.1.3 DS Program Process Improvement Tool Tailoring
2.2.1.4 DS Program Forecasting
2.2.1.5 Content of Program Strategy for TLIM
2.3 Analyze Cost and Benefits
2.4 Decide Through Life Information Management Strategy
3.0 STAGE 2: DEVELOP A THROUGH LIFE INFORMATION MANAGEMENT PLAN
3.1 Analyze User Requirements
3.2 Define Information Requirements
3.3 Define Infrastructure Requirements
3.4 Develop Information Management Plan
3.5 Develop a Business Case for Through Life Information Management
3.5.1 Business Case Need
3.5.2 Why Do We Need It Now?
3.5.3 Benefit Determination
3.5.3.1 Benefit Indication
3.5.3.2 Benefit Classification
3.5.4 Cost Determination
3.5.4.1 Unit Costs
3.5.4.2 When Costs Are Accrued
3.5.5 The Analysis
3.5.5.1 Rollout Model
3.5.6 The Financial Model
3.5.7 Sensitivity Analysis
3.5.8 Project Specific Aspects
4.0 STAGE 3: IMPLEMENTING A SHARED DATA ENVIRONMENT
5.0 STAGE 4: MANAGING INFORMATION THROUGH LIFE
5.1.1 Information Manager
5.1.2 Contractor Involvement
5.1.3 Data Management Scheme
5.2 Input Information
5.3 Update Information
5.4 Access/Distribute Information
5.5 Store Information
6.0 MODELS
6.1 The Through Life Business Model
6.1.1 Purpose of a Through Life Business Model
6.1.2 Developing a TLBM
6.1.2.1 TLBM Definition
6.1.2.2 TLBM Scope
6.1.2.3 Purpose
6.1.2.4 TLBM Viewpoint
6.1.2.5 Manage a Defense System Through Life
6.1.2.5.1 Defense System
6.1.2.5.2 TLBM Principles
6.1.2.5.3 Information as an Asset
6.1.2.5.4 Organizational Interfaces
6.1.2.6 Manage a Defense System Through Life - First Level Breakdown
6.1.2.6.1 Establish and Control Defense System Program Through Life
6.1.2.6.2 Obtain Defense System
6.1.2.6.3 Support the Use of the Defense System
6.1.2.6.4 TLBM Activity Definitions
6.2 NATO CALS DATA MODEL (NCDM)
6.2.1 Introduction
6.2.1.1 General
6.2.1.2 Technical view
6.2.1.3 A Brief History
6.2.1.4 What is new in Version 4.00
6.2.1.5 Motivation
6.2.1.6 Information Modeling
6.2.2 How to Use the NCDM
6.2.2.1 Specifying Information Requirements.
6.2.2.2 Defining a Common Vocabulary
6.2.2.3 Implementing an Integrated Product Database
6.2.2.3.1 In the Industry
6.2.2.3.2 In a Project
6.2.2.3.3 In the NATO Armed Forces
6.2.2.4 How to Implement the NCDM
6.2.2.5 To Create a Physical Model
6.2.2.5.1 The Requirement
6.2.2.5.2 The Method
6.2.3 Model Overview
6.2.3.1 The High Level Model
6.2.3.2 Model Organization
6.2.4 The Core Model (CoreModel)
6.2.4.1 Overview
6.2.4.2 Description
6.2.4.2.1 Product Design
6.2.4.2.2 Product Instance
6.2.4.2.3 Crossing between Breakdowns and Product Design Structure
6.2.5 Configuration
6.2.5.1 Overview
6.2.5.2 Description
6.2.5.2.1 Configuration Items
6.2.5.2.2 Configuration Change
6.2.5.2.3 Product Concept
6.2.6 Failure Analysis (Anomaly)
6.2.6.1 Overview
6.2.6.2 Description
6.2.6.2.1 Effects
6.2.6.2.2 Causal Relationships
6.2.7 Task Descriptions (Task)
6.2.7.1 Overview
6.2.7.2 Description
6.2.7.2.1 What to do
6.2.7.2.2 What Is Used To Do The Job
6.2.8 Technical Documentation (InfoObj)
6.2.8.1 Overview
6.2.8.2 Description
6.2.9 Logistic Support Analysis (LSA)
6.2.9.1 Overview
6.2.9.2 Description
6.2.9.2.1 Scenario and Role
6.2.9.2.2 Characteristics
6.2.10 Supporting Schemas
6.2.10.1 Approval
6.2.10.2 Person and Organization
6.2.10.3 Date and Time
6.2.10.4 Support Resources
6.2.10.5 Referenced STEP Integrated Resources (IR)
6.3 Developing a Life-cycle Cost Model
6.3.1 Life-cycle Cost Models
6.3.1.1 Background
6.3.1.2 A Summary of "Design-to-LCC" and Life-cycle Cost Models
6.3.1.3 Life-cycle Cost Model Characteristics
7.0 TOOLS
7.1 Tools
7.1.1 Desktop User Applications
7.1.2 Tool Sets
7.1.3 Areas for Tool Consideration
7.1.4 Configuration Management
7.1.5 Interchange Specifications
7.1.5.1 Introduction
7.1.5.2 Background
7.1.5.3 NATO CALS Data Architecture
7.1.5.4 Through Life Business Model Analysis
7.1.5.5 Architectural Core
7.1.5.6 Product ID
7.1.5.7 Organization
7.1.5.8 Configuration
7.1.5.9 State
7.1.5.10 Effectivity
7.1.5.11 Linking and Referencing
7.1.5.12 Product Life-cycle Support (Logistics)
7.1.5.13 Within the NATO Context
7.1.5.14 Information Sharing and Exchange
7.1.5.14.1 Bulk Data Transfer
7.1.5.14.2 Data Lists
7.1.5.14.3 Tables
7.1.5.14.4 Reports
7.1.5.14.5 Direct Access
7.1.5.14.6 Dynamic Link
7.1.5.14.7 Through Life Interchange/Interface Specifications
7.1.5.15 Methodology
7.1.5.15.1 Define Scenario
7.1.5.15.2 Apply the Scenario to the TLBM
7.1.5.15.3 Define Government/Industry Interface
7.1.5.15.4 Determine TLIS Purpose
7.1.5.15.5 Select Type/Style of Exchange
7.1.5.15.6 Determine Nature of the TLIS
7.1.5.15.7 Define Content of TLIS
7.1.5.15.8 Develop STEP Part 21 Definition
7.1.5.16 Use of EXPRESS
7.1.5.17 EXPRESS Import Facilities
7.1.5.17.1 EXPRESS Rules
7.1.5.17.2 Use of ISO 10303-21
7.1.5.18 Common Conventions for all Interchange Specifications
7.1.5.18.1 Example of Conventions
7.1.5.19 An Example Interchange Specification
7.1.5.19.1 Objective
7.1.5.19.2 Activity Overview
7.1.5.19.3 Activity Description
7.1.5.19.4 Activity Methodology
7.1.5.19.5 Mapping of Required Data into the NCDM
7.1.5.19.6 The Use Study Interface Specification Schema
7.1.6 Product Data Management
7.1.7 Enterprise Resource Management
8.0 TECHNIQUES
8.1 Through Life Business Case Analysis
8.1.1 Background
8.1.2 Introduction
8.1.3 Purpose of this Section
8.1.4 Business Case Modeling Fundamentals
8.1.4.1 What is a Business Case?
8.1.4.2 What is the Role of Business Case Modeling in Logistics Reengineering?
8.1.4.3 When Should I Prepare a Business Case?
8.1.4.4 How Do I Get Started?
8.1.4.5 What Should My Model Include?
8.1.4.6 Who Should Prepare a Business Case and What Should They Know?
8.1.4.7 What Should the Decision-Maker Know?
8.1.4.8 What Else Should I Know?
8.1.5 Business Case Model Minimum Report Requirements: A Simple Structure
8.1.5.1 Executive Summary
8.1.5.2 Boundaries of the Business Case - Goals and Vision
8.1.5.3 Boundaries of the Business Case - Context and Perspective
8.1.5.4 Boundaries of the Business Case - Functional Performance and Metrics
8.1.5.5 Boundaries of the Business Case - Initiatives Considered
8.1.5.6 Boundaries of the Business Case - Alternatives Considered
8.1.5.7 Boundaries of the Business Case - Key Assumptions
8.1.5.8 Boundaries of the Business Case - AS-IS Activity Model
8.1.5.9 Discussion of Alternatives - Functional Process Description
8.1.5.10 Discussion of Alternatives - Performance Impact and Metrics
8.1.5.11 Discussion of Alternatives - Technical Architecture (Optional)
8.1.5.12 Discussion of Alternatives - Cost Projections (Economic Analysis)
8.1.5.13 Discussion of Alternatives - Cost Projections - Investments
8.1.5.14 Discussion of Alternatives - Cost Projections - Operational
8.1.5.15 Discussion of Alternatives - Risk Assessment
8.1.5.16 Comparison of Alternatives - Functional
8.1.5.17 Comparison of Alternatives - Performance
8.1.5.18 Comparison of Alternatives - Costs
8.1.5.19 Comparison of Alternatives - Investment Costs
8.1.5.20 Comparison of Alternatives - Operational Cost Savings
8.1.5.21 Conclusions, Recommendations, and Issues
8.2 CALS Techniques
8.2.1 Approach to Implementation - Change Management
8.2.1.1 General
8.2.1.1.1 CALS
8.2.1.1.2 PMview
8.2.1.1.3 Techniques
8.2.1.2 Step 1 - Motivate to Change
8.2.1.2.1 Top Level Management
8.2.1.2.2 Why Change
8.2.1.3 Step 2 - Develop Change Plan
8.2.1.3.1 Develop an Organizational Structure
8.2.1.3.2 Identify Customer Needs
8.2.1.4 Step 3 - Conduct Training
8.2.1.5 Step 4 - Identify Goals and Performance Measures
8.2.1.5.1 Business Case Analysis
8.2.1.5.2 Performance Measures
8.2.1.5.3 Goal Prioritization
8.2.1.6 Step 5 - Document, Plan, and Sell
8.2.1.7 Step 6 - Create Tiger Teams
8.2.1.8 Step 7 - Implement
8.2.1.8.1 People
8.2.1.8.2 Business
8.2.1.8.3 Processes
8.2.1.8.4 Information
8.2.1.8.5 Technology
8.2.1.9 Step 8 - Monitor
8.2.1.9.1 Evaluate Results
8.2.1.9.2 Recognize Success
8.2.1.9.3 Adjust
8.2.1.10 Change Tools
8.2.1.10.1 Success Stories
8.2.1.10.2 Compendium - Business Technologies
8.2.1.10.3 Total Cost of Ownership-Models
8.2.1.10.4 Business Process Modeling Tools
8.2.2 Guide for Developing a NATO/Government CALS Concept of Operation
8.2.2.1 Section Summary
8.2.2.1.1 Purpose/Scope
8.2.2.1.2 How to Use This Section
8.2.2.2 CALS Implementation Strategy
8.2.2.3 Relationship of the NCoO to Contracting Process
8.2.2.3.1 Pre-Request For Proposal/Request For Quotation Activities and RFP/RFQ Release
8.2.2.3.2 Contractor Proposal
8.2.2.3.3 Proposal Evaluation
8.2.2.3.4 Negotiation
8.2.2.3.5 Contract Award
8.2.2.4 Background Information for NCOO Development
8.2.2.4.1 Identify Data Type Deliverables
8.2.2.4.2 Data Users
8.2.2.4.3 Identify Data Use/Processing
8.2.2.4.4 Identify Data User Infrastructure
8.2.2.4.5 Identify Type of Data Deliverable
8.2.2.4.6 Determine Data Format
8.2.2.4.7 Determine Data Interchange Standards
8.2.2.4.8 Determine Data Delivery and Access Media
8.2.2.5 Data Acquisition Requirements Method
8.2.2.5.1 Identify Data Type Requirements
8.2.2.5.2 Identify Data Users
8.2.2.5.3 Identify Data Use/Processing
8.2.2.5.4 Identify Data User Infrastructure
8.2.2.5.5 Identify Type of Data Deliverable
8.2.2.5.6 Identify Data Format Required
8.2.2.5.7 Identify Data Interchange Standards
8.2.2.5.8 Identify Data Delivery and Access Media
8.2.3 Concurrent Engineering
8.2.3.1 The Key to Concurrent Engineering-Shared Data
8.2.3.2 Example Use of an Integrated Database
8.2.3.2.1 Design Process
8.2.3.2.2 Maintenance Analysis
8.2.3.2.3 Design for Manufacturing Analysis
8.2.3.2.4 Detailed Design
8.2.3.2.5 Assembly Analysis
8.2.3.2.6 Re-design
8.2.3.2.7 Release
8.2.4 CITIS - Implementation of Contractor Integrated Technical Information Service
8.2.4.1 Introduction
8.2.4.1.1 The Primary Advantages of Using CITIS
8.2.4.2 The Decision to Acquire CITIS
8.2.4.2.1 Preliminary Data Collection
8.2.4.2.2 Number of Data Reviewers and Users
8.2.4.2.3 Recommended CITIS Deliverables
8.2.4.2.4 Infrastructure Upgrades and Contractor Compatibility
8.2.4.2.5 Reviewer Locations
8.2.4.2.6 Data Currency
8.2.4.2.7 Existing Electronic Communication Capabilities
8.2.4.2.8 Data Revision Frequency
8.2.4.2.9 Program Considerations
8.2.4.2.10 CITIS Functional Requirements Determination
8.2.4.3 CITIS Functionality
8.2.4.3.1 CITIS Services and Functions
8.2.4.3.2 Printing Capabilities
8.2.4.4 Contracting for CITIS
8.2.4.4.1 NATO/NATO Nations Concept of Operations
8.2.4.4.2 Solicitation
8.2.4.4.3 CITIS Contract Line Item Number
8.2.4.4.4 Sample CITIS Statement of Work
8.2.4.4.5 Deliverables
8.2.4.5 CITIS Development
8.2.4.5.1 CITIS Strategy
8.2.4.5.2 Hardware, Software, and Networks
8.2.4.6 CITIS Issues
8.2.4.6.1 Legal Issues
8.2.4.6.2 Warranties and Liabilities
8.2.4.6.3 International Data Exchange
8.2.5 Applying CALS to the Acquisition Logistics and Operational Logistics Processes
8.2.5.1 Acquisition Logistics and Operational Logistics
8.2.5.2 ILS, LSA, and LSAR Introduction
8.2.5.2.1 The Integrated Logistics Support
8.2.5.2.2 Logistics Support Analysis
8.2.5.2.3 Logistics Support Analysis Record
8.2.5.2.4 ILS Summary
8.2.5.2.5 LSA Summary
8.2.5.2.6 LSAR Summary
8.2.5.2.7 MIL-STD-1388-2B Summary
8.2.5.2.8 AECMA SPEC 2000M Summary
8.2.5.2.9 AECMA SPEC 1000D Summary
8.2.5.3 LSA DATA Activities
8.2.5.3.1 LSA Data Creation Activities
8.2.5.3.2 Follow-on LSA Data Modification
8.2.5.3.3 LSA Data Management
8.2.5.3.4 LSA Data Uses During the Acquisition Process
8.2.5.3.5 LSA Data Uses During the Operational Phase
8.2.5.3.6 CALS-Related Questions
8.2.5.4 LSA Process in a CALS Environment
8.2.5.4.1 Potential Sources of LSA Data
8.2.5.4.2 Managing/Maintaining LSA Data
8.2.5.4.3 Using LSA Data in the CALS Environment
8.2.5.4.4 CALS Effects on LSAR Report Requirements
8.2.5.4.5 Interaction of LSA Data with Concurrent Engineering/Integrated Design
8.2.5.4.6 Specific CALS Considerations Affecting Data Acquisition
8.2.5.4.7 Migration of LSA Data into ILS Element Products
8.2.5.5 Sample CALS and LSA Tasks Statement of Work
8.2.5.5.1 MIL-STD-1388-1A 100 Series Tasks
8.2.5.5.2 MIL-STD-1388-1A 200 Series Tasks
8.2.5.5.3 MIL-STD-1388-1A 300 Series Tasks
8.2.5.5.4 MIL-STD-1388-1A 400 Series Tasks
8.2.5.5.5 MIL-STD-1388-1A 500 Series Tasks
8.2.5.6 Future Considerations for the LSA Process in a CALS Environment
8.2.5.6.1 Integrated Weapon Systems Database
8.2.5.6.2 Contractor Integrated Technical Information Service
8.2.5.6.3 NATO CALS Efforts
8.2.5.7 Summary and Conclusions
8.2.6 Applying CALS to the Creation, Management, and Use of Technical Data Packages
8.2.6.1 Introduction
8.2.6.2 General Considerations
8.2.6.2.1 TDP Data
8.2.6.2.2 TDPs in the CALS Environment
8.2.6.2.3 Digital Data Deliverables
8.2.6.2.4 Life-cycle Considerations
8.2.6.2.5 Infrastructure Development
8.2.6.2.6 Data Uses
8.2.6.3 Specific Considerations
8.2.6.3.1 TDP Delivery
8.2.6.3.2 Potential TDP Delivery Options
8.2.6.3.3 Raster
8.2.6.3.4 Processable Data Files
8.2.6.4 Decision Guidelines
8.2.6.4.1 Maintenance and Control of the TDP
8.2.6.4.2 Competitive Reprocurement
8.2.6.4.3 TDP Modification/Revision Determination
8.2.6.4.4 Digital System/Environment
8.2.6.4.5 System/Environment Compatibility
8.2.6.5 Sample CDRL's
8.2.6.5.1 Raster Delivery Option
8.2.6.5.2 Product Data File Delivery Option
8.2.6.5.3 Native CAD/CAE Data File Delivery Option
8.2.6.5.4 Product Data File Delivery Option (IGES Format)
8.2.6.6 Advantages and Disadvantages of Delivery Options
8.2.6.7 Contract Validation
8.2.6.7.1 Contractor Validation
8.2.6.7.2 Government Verification
8.2.7 Applying CALS to the Creation, Management, and Use of Technical Manuals (TM)
8.2.7.1 General Consideration
8.2.7.1.1 Identify/Establish the Requirements for the TM
8.2.7.1.2 Identifying the TM User's Requirements
8.2.7.1.3 TMs in the CALS Environment
8.2.7.1.4 Non Digital Data Deliverables
8.2.7.2 Specific Considerations
8.2.7.2.1 TM Delivery Format Selection
8.2.7.2.2 Interactive Electronic Technical Manual
8.2.7.2.3 IETM Viability
8.2.7.2.4 IETM Development
8.2.7.3 TM Development
8.2.7.3.1 TM Availability
8.2.7.3.2 New Technical Manual or Complete Revision
8.2.7.4 Decision Guidelines
8.2.7.4.1 Decision #1: Deliverable Options
8.2.7.4.2 Decision #2: Forms Options
8.2.7.4.3 Decision #3: Specification and Standard Options
8.2.7.4.4 Decision #4: Digital delivery mode options
8.2.7.4.5 Digital Deliverable Summary
8.2.7.5 Validation and Verification
8.2.7.5.1 Contractor Validation
8.2.7.5.2 NATO/NATO Nations Verification
9.0 SECURITY
9.1 What is Information Security
9.1.1 The Environment
9.1.2 Types of Security
9.1.2.1 Regulatory Requirements
9.1.2.2 Information Assurance
9.2 What Needs to be Considered?
9.2.1 System Security Methodology
9.2.2 Technical Security Countermeasures
9.2.2.1 Fundamental Security Services
9.2.2.2 Security Technologies
9.2.2.3 Robustness Strategy
9.2.2.4 Interoperability Framework
9.2.2.5 Security Management Infrastructure Considerations
9.2.3 Security Solutions Framework
9.2.3.1 Requirement Category Guidance
9.2.3.2 Security Management Infrastructure Considerations
9.2.3.3 Aggregated Solution
10.0 CONTRACTING
10.1 Introduction
10.2 How to contract for CALS - Sample Statement of Work Language and Source Selection Criteria
10.3 Statement of Work Language
10.3.1 Scope
10.3.2 Specific Requirements
10.3.3 CALS Implementation Plan
10.3.4 CALS Approach
10.3.5 Database Architecture/System Tradeoffs
10.3.6 CALS Standards Conformance Test
10.3.7 Security
10.3.8 Program Assessment and Control
10.3.9 Post Award CALS Program Orientation Conference
10.3.10 Government Furnished Information
10.3.11 Contractor Integrated Technical Information Services)
10.3.12 Data Element Dictionary [If CITIS is required.]
10.3.13 Engineering Data (Graphic and Text Files)
10.3.14 Automation and Functional Integration
10.3.15 Reliability and Maintainability Automation
10.3.16 R&M-Logistic Support Analysis Record Integration
10.3.17 LSAR Data Automation
10.3.18 Reliability Centered Maintenance and Age Exploration Automation
10.3.19 Level of Repair Analysis
10.3.20 Diagnostics
10.3.21 Management Information Tools
10.3.22 Technical Manuals
10.3.23 Supply Support
10.3.24 Facilities Data
10.3.25 Training
10.4 Source Selection Criteria
10.4.1 Source Selection for CALS
10.5 Guidelines and Sample Clauses for Electronic Data Interchange
10.5.1 Introduction
10.5.2 Agreement First Page
10.5.3 Object and Scope
10.5.4 Definitions
10.5.5 Authenticity of Messages
10.5.6 Validity and Formation of Contract
10.5.6.1 Validity of the Contract
10.5.6.2 Formation of the Contract
10.5.7 Admissibility in Evidence of EDI Messages
10.5.7.1 Processing and Acknowledgement of Receipt
10.5.7.2 Processing of Electronic Data Interchange Messages
10.5.7.3 Acknowledgement of EDI Messages
10.5.7.4 Time Limit and Acknowledgement of Receipt Transmission
10.5.7.5 Failure of Receipt of an Acknowledgement
10.5.7.6 Inability to Send Messages
10.5.8 Security and Protection of EDI Messages
10.5.8.1 Obligations of Parties
10.5.8.2 NATO Classified Information
10.5.8.3 Security Procedures and Measures
10.5.8.4 Failure and Security Procedures
10.5.8.5 Encryption
10.5.9 Confidentiality
10.5.10 Data-Log: Recording, Storage, and Reconciliation of EDI Messages
10.5.10.1 Storage Procedures and Time Limits
10.5.10.2 Format of Storage
10.5.11 Operational Requirements for EDI
10.5.11.1 Operational Environment
10.5.11.2 Operational Equipment
10.5.11.3 Means of Communications
10.5.11.4 EDI Message Standards
10.5.11.5 Codes
10.5.12 Technical Specifications and Requirements
10.5.12.1 User Manual
10.5.12.2 Test and Trial Procedures
10.5.13 Liability
10.5.13.1 Exclusion of Liability
10.5.13.2 Force Majeure
10.5.13.3 Intermediaries Liability
10.5.13.4 Supplier Contracts
10.5.14 Dispute Resolution
10.5.14.1 Options
10.5.14.2 Arbitration Clause
10.5.14.3 Court of Law
10.5.14.4 0ption C
10.5.15 Applicable Law
10.5.16 Effect, Modification, Term, and Severability
10.5.16.1 Effect
10.5.16.2 Modification
10.5.16.3 Termination
10.5.16.4 Severability
10.5.17 Signature Page
11.1 NATO CALS Standards Policy
11.1.1 ISO Standards
11.1.2 Multi-national or National Standards
11.1.3 Standardization Agreements/Military Profiles
11.1.4 Limitations of Standards
11.1.5 NATO User Groups
11.2 NATO CALS Standards
11.2.1 Temporary Standard [ T ]
11.2.2 Emerging Standard [ E ]
11.2.3 Recommended Standard [ R ]
11.2.4 Not Recommended Standard [ N ]
11.2.5 Undetermined Status [ ]
12.0 EXAMPLES AND LESSONS LEARNED
12.1 The Viking Submarine
12.2 The Crusader (US Howits)
12.2.1 Statement of the Situation
12.2.2 CALS Technologies, Philosophies, and Standards Implemented
12.2.3 Team Members
12.2.4 Results Achieved
12.3 U.S. ARMY PMCMS
