AIR-3.1E, WARRANTY GUIDE - LOGISTICS POLICY AND PROCESSES

AIR-3.1E, WARRANTY GUIDE - LOGISTICS POLICY AND PROCESSES. It is NAVAIR policy to pursue cost effective warranties on all procurements. The NAVAIR Program Managers (PMs) are responsible for the development and inclusion of appropriate warranty provisions in solicitations. The program manager should include the expertise of the integrated product team when determining warranty requirements. Additionally, warranty periods must be clearly stated in the solicitation. Warranty clauses should explain what benefit would be derived by the Government; for example, explain how the warranty would improve fleet readiness and mission effectiveness. Because most business considerations are metric driven, a cost/benefit analysis is required to support the specific business case for use of a warranty. If a warranty can not be supported by a cost/benefit analysis, then the program manager should not invoke warranty clauses. This means the warranty clause should only be invoked to support a smart business decision. The warranty is the exception rather than a legal requirement.

DC-PMC-01 V1.0, PROJECT HEALTH AND TROUBLESHOOTING HANDBOOK (17 MAY 2005)

DC-PMC-01 V1.0, PROJECT HEALTH AND TROUBLESHOOTING HANDBOOK (17 MAY 2005)., This Handbook has been developed to assist project and line management in the care and conduct of Space and Naval Warfare (SPAWAR) Systems Center (SSC) San Diego projects, and should be considered a companion document to the most current version of the SSC San Diego Project Management Guide (PMG) . The objective is to guide managers in the proper management practices that will result in the delivery of quality products and services within the desired schedule and budget. With these goals in mind, this Handbook includes the items listed below: • Questions a manager should ask to determine the status and health of their project. • References to applicable sections of the PMG. • Characteristics of common project problems and how to troubleshoot or (preferably) avoid them. • Listing of essential project management and engineering processes (available on the SSC San Diego Process Asset Library (PAL)).

DEPARTMENT OF THE NAVY FOREIGN DISCLOSURE MANUAL (SEP 2007)

DEPARTMENT OF THE NAVY FOREIGN DISCLOSURE MANUAL (SEP 2007)., This manual implements references (a), (b), (c), and (d). It provides Department of the Navy (DoN) foreign disclosure policy and procedures, delegates disclosure authority, and assigns responsibilities. It applies to DoN commands, agencies, staff elements, and other DoN organizations that are involved in activities that will result in contacts with, or the disclosure of, Classified Military Information (CMI) to foreign governments and international organizations, their representatives, and other foreign persons and entities pursuant to references (a), (b), (c), (d), and (e). In addition, this manual provides policy and assigns responsibilities for the foreign disclosure of Controlled Unclassified Information (CUI) that is determined, in accordance with reference (f), to require export controls as well as other unclassified information with a military or space application that is determined to be exempt from public disclosure pursuant to reference (g).

MANUAL OF STYLE FOR NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION TECHNICAL PUBLICATIONS (JAN 2000)

MANUAL OF STYLE FOR NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION TECHNICAL PUBLICATIONS (JAN 2000). This manual establishes the format and style requirements for technical reports and special reports prepared by or for the NAVAIRWARCENTRASYSDIV. It establishes preferred usage to ensure that reports are consistent and that requirements of military standards are met. This manual is to be used by NAVAIRWARCENTRASYSDIV personnel and by contractors who prepare reports for NAVAIRWARCENTRASYSDIV.

NAVAL "SYSTEMS OF SYSTEMS" SYSTEMS ENGINEERING GUIDEBOOK (VOLUME 1) (VER. 2.0) (6 NOV 2006)

NAVAL "SYSTEMS OF SYSTEMS" SYSTEMS ENGINEERING GUIDEBOOK (VOLUME 1) (VER. 2.0) (6 NOV 2006)., The Naval "Systems of Systems" Systems Engineering Guidebook, Volume 1, Version 2.0 has been developed by the ASN (RDA) Office of the Chief Systems Engineer to support the Naval acquisition community in implementing capability-based acquisition and systems engineering for systems of systems in accordance with SECNAVINST 5000.2C. The Guidebook focus is on a systems engineering process that enables the realization of successful "systems of systems" that provide needed capabilities and functionality within a Net Centric Operating and Warfare environment. Volume I of the Guidebook describes the recommended capability-based systems engineering process activities and products for systems of systems acquisitions.

NAVAL "SYSTEMS OF SYSTEMS" SYSTEMS ENGINEERING GUIDEBOOK (VOLUME 2) (VER. 2.0) (6 NOV 2006)

NAVAL "SYSTEMS OF SYSTEMS" SYSTEMS ENGINEERING GUIDEBOOK (VOLUME 2) (VER. 2.0) (6 NOV 2006)., The Naval "Systems of Systems" Systems Engineering Guidebook, Volume 2, Version 2.0 has been developed by the ASN (RDA) Office of the Chief Systems Engineer to support the Naval acquisition community in implementing capability-based acquisition and systems engineering for systems of systems in accordance with SECNAVINST 5000.2C. The Guidebook focus is on a systems engineering process that enables the realization of successful "systems of systems" that provide needed capabilities and functionality within a Net Centric Operating and Warfare environment. Volume I of the Guidebook describes the recommended capability-based systems engineering process activities and products for systems of systems acquisitions.

NAVAL SYSTEMS ENGINEERING GUIDE (NSEG) - OCTOBER 2004

NAVAL SYSTEMS ENGINEERING GUIDE (NSEG) - OCTOBER 2004. The Naval Systems Engineering Guide is provided to help ensure the systems we develop for the fleet are affordable, operationally effective and suitable, and can be a timely solution to satisfy user needs at an acceptable level of risk. This Guide defines the systems engineering (SE) requirements and tasks; their implementation and products; and explains the tools and techniques used throughout a product life cycle. This Guide satisfies the DoD requirement for having a documented SE process, and emphasizes the relationship between the technical management process and the SE process. It documents a common Naval Systems Engineering Process that has been accepted by the Naval Virtual Systems Command. The purpose of this Guide is to characterize the contents of the SE discipline, to promote a consistent and common view of SE across the Navy, to clarify the boundary of SE with respect to other disciplines, and to provide a foundation for curriculum development and SE certification. This Guide consists of information and 33 required or normative processes. This Guide describes a rigorous process to assist the systems engineer in defining, performing, managing, and evaluating SE efforts in Naval acquisition and technology development programs. The intended audience is the new systems engineer, an engineer in another discipline that needs to perform some SE functions, or a more-experienced systems engineer who needs a convenient reference. The hyper-linking to the imbedded reference material makes it very convenient using the electronic version of this Guide. The intent is to provide enough information for the user to determine whether a given process activity is appropriate in supporting the objective(s) of the program or project they support, and how to go about implementing the process activity. The framework for this Guide is an industry standard, ANSI/EIA-632, Processes for Engineering a System. The standard was developed to replace the SE military standard, MIL-STD-499 as part of the 1994 DoD Acquisition Reform initiative prescribing the use of “performance-based” acquisition specifications and the substitution of the standards and practices used in the commercial marketplace for military specifications and standards. The Naval Systems Engineering Steering Group (SESG), comprised of members from NAVAIR, NAVSEA, MARCOR, and SPAWAR, provided the common and unique SE requirements and implementation approach for the various Naval development and acquisition programs. Periodic updates are planned to implement continuous process improvement, based upon feedback from programs / contractors, by the Naval SESG which maintains this Guide.

NAVFAC P-307, MANAGEMENT OF WEIGHT HANDLING EQUIPMENT (JUNE 2006)

NAVFAC P-307, MANAGEMENT OF WEIGHT HANDLING EQUIPMENT (JUNE 2006)., This publication provides requirements for the maintenance, inspection, test, certification, repair, alteration, operation, and/or use of weight handling equipment (WHE) under the technical cognizance of the Naval Facilities Engineering Command (NAVFAC). Activities covered include Navy shore activities, the Naval Construction Force (NCF), Naval Special Operating Units (SOU), and the Naval Construction Training Center (NCTC). These criteria are the minimum requirements for all applicable equipment. This publication meets or exceeds all applicable OSHA requirements for maintenance, inspection, testing, certification, repair, alteration, and operation of equipment covered herein.

NAVFAC P-405, SEABEE PLANNER'S AND ESTIMATOR'S HANDBOOK (OCT 1996)

NAVFAC P-405, SEABEE PLANNER'S AND ESTIMATOR'S HANDBOOK (OCT 1996)., The Seabee Planner's and Estimator's Handbook is a technical GUIDE for planning and estimating construction projects undertaken by the Naval Construction Force (NCF). The handbook provides information on estimating construction work elements and material quantities, including equipment and manpower requirements. Prepared by Seabees for Seabees, the handbook is specifically for use in typical Seabee construction projects, and is designed for flexible application to projects of varying size, scope, and conditions. Tables for estimating labor have been provided to show the number of man-hours required for each work function. Diagrams illustrate the functions of planning and estimating. Both tables and illustrations have been made as useful, accurate, and comprehensive as possible.

NAVOPNAV INSTRUCTION 5442.2G, AIRCRAFT INVENTORY REPORTING SYSTEM (AIRS)

OPNAV INSTRUCTION 5442.2G, AIRCRAFT INVENTORY REPORTING SYSTEM (AIRS). The Aircraft Inventory Reporting System (AIRS) has been revised, incorporating aircraft controlling custodian, Naval Aviation Depot Operations Center, Naval Aviation Maintenance Office and Naval Sea Logistics Center requirements/inputs. This edition provides aircraft reporting custodians with a single aircraft accounting directive responsive to information requirements at all echelons.

NAVSO P-3690, ACQUISITION LOGISTICS FOR THE REST OF US (SEP 2001)

NAVSO P-3690, ACQUISITION LOGISTICS FOR THE REST OF US (SEP 2001)., The purpose of this guide is to provide acquisition logistics practioners with an assessment tool to aid in measuring logistics progress from program start through initial operational capability. Logistics program success is primarily driven by various design test and production practices conducted during the acquistion phase. The relationships between these practices and their impact on logistics are addressed in this guide. This guide should be used as a tool to measure logistics risk.

NAVSO P-5239-01, INTRODUCTION TO INFORMATION SYSTEMS SECURITY (INFOSEC) GUIDEBOOK

NAVSO P-5239-01, INTRODUCTION TO INFORMATION SYSTEMS SECURITY(INFOSEC)GUIDEBOOK. Navy Staff Office Publication (NAVSO Pub) 5239, "Information Systems Security (INFOSEC) Program Guidelines" is issued by the Naval Information Systems Management Center. It consists of a series of modules providing procedural, technical, administrative and/or supplemental guidance for all information systems, whether business or tactical, used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission or receipt of data. Each module will focus on a distinct program element and describe a standard methodology for planning, implementing and executing that element of the INFOSEC program within the Department of the Navy (DON). This module, "Introduction to Information Systems Security (INFOSEC) Guidebook", provides a basic introduction to INFOSEC and summarizes the DoN INFOSEC Program. The guidance contained herein applies to all DON AIS's and is effective upon receipt. Electronic versions of this document may be download via anonymous ftp from infosec.nosc.mil or //http://infosec.nosc.mil/inf.html.

NAVSO P-5239-22, PROTECTED DISTRIBUTION SYSTEM (PDS) GUIDEBOOK, MODULE 22 INFORMATION SYSTEMS SECURITY

NAVSO P-5239-22, PROTECTED DISTRIBUTION SYSTEM (PDS) GUIDEBOOK, MODULE 22 INFORMATION SYSTEMS SECURITY (INFOSEC) PROGRAM GUIDELINES (OCT 1997)., This guidebook applies to Department of the Navy activities which use, or are contemplating the use of a PDS to protect the transmission of unencrypted classified National Security Information (NSI). This guidebook describes the requirements for a PDS installed within the U.S. (including its territories and possessions) and within LOW and MEDIUM threat locations outside the United States as described by reference (b). The threat within the U.S. is LOW. The use of a PDS within a HIGH or CRITICAL threat location (per reference (b)) is not recommended. If a PDS is used in these location, protection techniques are determined on a case-by-case basis by the cognizant Approval Authority.

NAWCWPNS TP 8347, ELECTRONIC WARFARE AND RADAR SYSTEMS ENGINEERING HANDBOOK (1 APRIL 1997 W/ REV 2 OF 1 APRIL 1999 AND LATER CHANGES)

NAWCWPNS TP 8347, ELECTRONIC WARFARE AND RADAR SYSTEMS ENGINEERING HANDBOOK (1 APRIL 1997 W/ REV 2 OF 1 APRIL 1999 AND LATER CHANGES).

NRaD TD-108, PROJECT MANAGEMENT AND SYSTEMS ENGINEERING GUIDE (3RD EDITION) (MAR 1994)

NRAD TD-108, PROJECT MANAGEMENT AND SYSTEMS ENGINEERING GUIDE (3RD EDITION) (MAR 1994). This guide is intended to help the manager to scope, plan, and set up the management system for projects requiring research and development within the Department of Defense, especially the Navy. It is assumed the manager has a background that is primarily technical and not necessarily managerial. THe guide treats the acquisition cycle in chronological order and supports this perspective with specialized information on the various disciplines employed. The emphasis is on the implementation of practical methods of acquiring the best possible product for the resources available. This report was sponsored by Naval Command, Control, and Ocean Survelliance Center (NCCOSC), RDT&E Division., San Diego, CA.

PR-OPD-29 V1.2, PROJECT MANAGEMENT GUIDE (PMG), SSC SAN DIEGO (4 JAN 2005)

PR-OPD-29 V1.2, PROJECT MANAGEMENT GUIDE (PMG), SSC SAN DIEGO (4 JAN 2005)., This Project Management Guide provides project managers at SSC San Diego with the vision, information, resources, and activities to successfully plan, execute, and control projects. Adopting a standard set of technical, engineering, and management work processes, best practices, and a common approach to project management, will help accomplish this. This requires commitment from all management levels, as well as the implementation and use of standard processes and tools by project management. This Guide assists the project managers in: • Establishing the project and empowering the project manager • Planning and scheduling project activities • Applying engineering and management best practices • Monitoring and controlling progress and managing risks • Supporting the successful transition of the product or service.

TD-108, TECHNICAL DOCUMENT 108 (3RD ED), PROJECT MANAGEMENT AND SYSTEMS ENGINEERING GUIDE (30 MAR 1994)

TD-108, TECHNICAL DOCUMENT 108 (3RD ED), PROJECT MANAGEMENT AND SYSTEMS ENGINEERING GUIDE (30 MAR 1994). This guide is intended to help the manager to scope, plan, and setup the management system for projects requiring research and development within the Department of Defense, especially the Navy. It is assume the manager has a background which is primarily technical and not necessarily managerial. The guide treats the acquisition cycle in chronological order and supports this perspective with specialized information on the various disciplines employed. The emphasis is on the implementation of practical methods of acquiring the best possible product for the resources available.

TD-3132, TECHNICAL DOCUMENT 3152 - ACQUISITION AND DEVELOPMENT OF SYSTEM COMMAND (SYSCOM) TECHNICAL MANUALS - A GUIDE FOR SSC SAN DIEGO EMPLOYEES (DEC 2003)

TD-3132, TECHNICAL DOCUMENT 3152 - ACQUISITION AND DEVELOPMENT OF SYSTEM COMMAND (SYSCOM) TECHNICAL MANUALS - A GUIDE FOR SSC SAN DIEGO EMPLOYEES (DEC 2003)., This manual describes how to acquire, develop, and maintain System Command (SYSCOM) Technical Manuals (TMs) for SYSCOM sponsors such as Naval Sea Systems Command (NAVSEA) and Space and Naval Warfare Systems Command (SPAWAR). TMs are the primary information source for technical training, installation, operation, testing, maintenance, and repair associated with NAVSEA/SPAWAR systems or equipment. Unless adequate and suitably written TMs already exist, new manuals must be developed and procured as part of all NAVSEA/SPAWAR systems, equipment, or major component acquisitions. No other forms of technical information will be purchased without specific justification.

TR04-0600, PLASTIC ENCAPSULATED MICROCIRCUIT (PEM) DERATING, STORAGE AND QUALIFICATION REPORT

TR04-0600, PLASTIC ENCAPSULATED MICROCIRCUIT (PEM), DERATING, STORAGE AND QUALIFICATION REPORT. Plastic Encapsulated Microcircuits (PEMs) have been a consideration for military/space use for about thirty years. Early in the development of PEMs, silicon and the epoxy molding compounds (EMCs) had several shortcomings and left a lot to be desired from reliability point of view. Moisture, which is present in most military/space applications, had a devastating impact on the early PEMs due to the impurities in the EMCs. These failures did not originate from an electrical standpoint (die level) but were chemical or mechanical in nature. The typical failure mechanism seemed to revolve around Kirkendall voiding (see Fig. 1). Kirkendall voiding, or purple plague, is the formation of voids in wire bonds caused by the intermetallic formation between the gold bond wires and the aluminum bond pads. This intermetallic formation between gold and aluminum is significantly accelerated in the presence of an encapsulant contaminant, such as certain halides (chlorine, bromine, fluorine), moisture and elevated temperatures. This voiding is normally considered an end of life failure mechanism. Other random failure mechanisms occur and are usually lot or manufacturer dependent. These failures are detailed later in this report. In PEMs process improvements, EMCs have evolved over time. This evolution has made PEMs more reliable; however, reliability is still a concern, when considering usage of PEMs in military/space systems. This report will review general derating storage and qualification guidelines for PEM devices. Also included in this report is some test data (from 1996-1999) that Naval Surface Weapons Center (NSWC) Crane, Indiana, has completed on some PEM lots.