Preliminary Design Review (PDR)

40.1 General.
The PDR shall be a formal technical review of the basic design approach for a configuration item or for a functionally related group of configuration items. It shall be held after the hardware Development Specification(s), the Software Top Level Design Document (STLDD), the Software Test Plan (STP), the HWCI Test Plan, and preliminary versions of the Computer System Operator's Manual (CSOM), Software User's Manual (SUM), Computer System Diagnostic Manual (CSDM), and Computer Resources Integrated Support Document (CRISD) are available, but prior to the start of detailed design. For each configuration item the actions described below may be accomplished as a single event, or they may be spread over several events, depending on the nature and the extent of the development of the configuration item, and on provisions specified in the contract Statement of Work. A collective PDR for a group of configuration items, treating each configuration item individually, may be held when such an approach is advantageous to the contracting agency; such a collective PDR may also be spread over several events, as for a single configuration item. The overall technical program risks associated with each configuration item shall also be reviewed on a technical, cost, and schedule basis. For software, a technical understanding shall be reached on the validity and the degree of completeness of the STLDD, STP, and the preliminary versions of the CSOM, SUM, CSDM, and CRISD.

40.2 Items to be Reviewed.
The contractor shall present the following for review by the contracting agency:

40.2.1 HWCIs:

? a. Preliminary design synthesis of the hardware Development Specification for the item being reviewed.

? b. Trade-studies and design studies results (see paragraph 20.3.2 of SDR for a representative listing).

? c. Functional flow, requirements allocation data, and schematic diagrams.

? d. Equipment layout drawings and preliminary drawings, including any proprietary or restricted design/process/ components and information.

? e. Environment control and thermal design aspects

? f. Electromagnetic compatibility of the preliminary design

? g. Power distribution and grounding design aspects

? h. Preliminary mechanical and packaging design of consoles, racks, drawers, printed circuit boards, connectors, etc.

? i. Safety engineering considerations

? j. Security engineering considerations

? k. Survivability/Vulnerability (including nuclear) considerations

? l. Preliminary lists of materials, parts, and processes

? m. Pertinent reliability/maintainability/availability data

? n. Preliminary weight data

? o. Development test data

? p. Interface requirements contained in configuration item Development Specifications and interface control data (e.g., interface control drawings) derived from these requirements.

? q. Configuration item development schedule

? r. Mock-ups, models, breadboards, or prototype hardware when appropriate

? s. Producibility and Manufacturing Considerations (e.g., materials, tooling, test equipment, processes, facilities, skills, and inspection techniques). Identify single source, sole source, diminishing source.

? t. Value Engineering Considerations, Preliminary VECPs and VECPs (if applicable).

? u. Transportability, packaging, and handling considerations

? v. Human Engineering and Biomedical considerations (including life support and Crew Station Requirements).

? w. Standardization considerations

? x. Description and characteristics of commercially available equipment, including any optional capabilities such as special features, interface units, special instructions, controls, formats, etc., (include limitations of commercially available equipment such as failure to meet human engineering, safety, and maintainability requirements of the specification and identify deficiencies).

? y. Existing documentation (technical orders, commercial manuals, etc.,) for commercially available equipment and copies of contractor specifications used to procure equipment shall be made available for review by the contracting agency.

? z. Firmware to be provided with the system: microprogram logic diagrams and reprogramming/instruction translation algorithm descriptions, fabrication, packaging (integration technology (e.g., LSI, MSI), device types (e.g., CMOS, PMOS)), and special equipment and support software needed for developing, testing, and supporting the firmware.

? aa. Life Cycle Cost Analysis

? ab. Armament compatibility

? ac. Corrosion prevention/control considerations

? ad. Findings/Status of Quality Assurance Program

? ae. Support equipment requirements.

40.2.2 CSCIs:

? a. Functional flow. The computer software functional flow embodying all of the requirements allocated from the Software Requirements Specification and Interface Requirements Specification(s) to the individual Top-Level Software Units (TLSU) of the CSCI.

? b. Storage allocation data. This information shall be presented for each CSCI as a whole, describing the manner in which available storage is allocated to individual TL SW Units. Timing, sequencing requirements, and relevant equipment constraints used in determining the allocation are to be included.

? c. Control functions description. A description of the executive control and start/recovery features for the CSCI shall be available, including method of initiating system operation and features enabling recovery from system malfunction.

? d. CSCI structure. The contractor shall describe the top-level structure of the CSCI, the reasons for choosing the components described, the development methodology which will be used within the constraints of the available computer resources, and any support programs which will be required in order to develop/maintain the CSCI structure and allocation of data storage.

? e. Security. An identification of unique security requirements and a description of the techniques to be used for implementing and maintaining security within the CSCI shall be provided.

? f. Re-entrancy. An identification of any re-entrancy requirements and a description of the techniques for implementing re-entry routines shall be available.

? g. Computer software development facilities. The availability, adequacy, and planned utilization of the computer software development facilities shall be addressed.

? h. Computer software development facility versus the operational system. The contractor shall provide information relative to unique design features which may exist in a TLCSC in order to allow use within the computer software development facility, but which will not exist in the TLCSC installed in the operational system. The contractor shall provide information on the design of support programs not explicitly required for the operational system but which will be generated to assist in the development of the CSCI(s). The contractor shall also provide details of the Software Development Library controls.

? i. Development tools. The contractor shall describe any special simulation, data reduction, or utility tools that are not delivered under the terms of the contract, but which are planned for use during software development.

? j. Test tools. The contractor shall describe any special test systems, test data, data reduction tools, test computer software, or calibration and diagnostic software that are not deliverable under terms of the contract, but which are planned for use during product development.

? k. Description and characteristics of commercially available computer resources, including any optional capabilities such as special features, interface units, special instructions, controls, formats, etc. Include limitations of commercially available equipment such as failure to meet human engineering, safety and maintainability requirements of the specification and identify deficiencies.

? l. Existing documentation (technical orders, commercial manuals, etc.) for commercially available computer resources and copies of contractor specifications used to procure computer resources shall be made available for review by the contracting agency.

? m. Support resources. The contractor shall describe those resources necessary to support the software and firmware during operational deployment of the system, such as operational and support hardware and software, personnel, special skills, human factors, configuration management, test, and facilities/space.

? n. Operation and support documents. The preliminary versions of the CSOM, SUM, CSDM, and CRISD shall be reviewed for technical content and compatibility with the top-level design documentation.

? o. Updated since the last review to all previously delivered software related CDRL items.

? p. Review considerations applicable to 40.2.1 as appropriate.

40.2.3 Support Equipment (SE):

? a. Review considerations applicable to paragraph 40.2.1 and 40.2.2 as appropriate.

? b. Verify testability analysis results. For example, on repairable integrated circuit boards are test points available so that failure can be isolated to the lowest level of repair (See Section 3 Definitions, for "Level of repair").

? c. Verify that the Government furnished SE is planned to be used to the maximum extent possible.

? d. Review progress of long-lead time SE items, identified through interim release and SE Requirements Document (SERD) procedures.

? e. Review progress toward determining total SE requirements for installation, checkout, and test support requirements.

? f. Review the reliability/maintainability/availability of support equipment items.

? g. Identify logistic support requirements for support equipment items and rationale for their selection.

? h. Review calibration requirements.

? i. Describe technical manuals and data availability for support equipment.

? j. Verify compatibility of proposed support equipment with the system maintenance concept.

? k. If a Logistic Support Analysis (LSA) is not done, then review the results of SE trade-off studies for each alternative support concept. For existing SE and printed circuit boards testers, review Maintainability data resulting from the field use of these equipments. Review the cost difference between systems using single or multipurpose SE vs. proposed new SE. Examine technical feasibility in using existing, developmental, and proposed new SE. For mobile systems, review the mobility requirements of support equipment.

? l. Review the relationship of the computer resources in the system/subsystem with those in Automatic Test Equipment (ATE). Relate this to the development of Built In Test Equipment (BITE) and try to reduce the need for complex supporting SE.

? m. Verify on-equipment versus off-equipment maintenance task trade study results, including support equipment impacts.

? n. Review updated list of required support equipment.

40.2.4 Engineering Data.
Review Level 1 engineering drawings for ease of conversion to higher levels and, if available, review Level 2 and 3 drawings for compliance with requirements. The review of engineering data, as defined in paragraph 3.15, should consider the checklist items discussed in para 100.6, as properly tailored.

40.3 Evaluation of Electrical, Mechanical, and Logical Designs.

40.3.1 HWCIs.
The material of paragraph 40.2.1 above shall be evaluated to:

? a. Determine that the preliminary detail design provides the capability of satisfying the performance characteristics paragraph of the HWCI Development specifications.

? b. Establish compatibility of the HWCI operating characteristics in each mode with overall system design requirements if the HWCI is involved in multi-mode functions.

? c. Establish the existence and nature of physical and functional interfaces between the HWCI and other items of equipment, computer software, and facilities.

40.3.2 CSCIs.
The material of paragraph 40.2.2 above shall be evaluated to:

? a. Determine whether all interfaces between the CSCI and all other configuration items both internal and external to the system meet the requirements of the Software Requirements Specification and Interface Requirements Specification(s).

? b. Determine whether the top-level design embodies all the requirements of the Software Requirements Specification and Interface Requirements Specification(s).

? c. Determine whether the approved design methodology has been used for the top-level design.

? d. Determine whether the appropriate Human Factors Engineering (HFE) principals have been incorporated in the design.

? e. Determine whether timing and sizing constraints have been met throughout the top-level design.

? f. Determine whether logic affecting system and nuclear safety has been incorporated in the design.

40.4 Electromagnetic Compatibility.
Review HWCI design for compliance with electromagnetic compatibility/electromagnetic interference (EMC/EMI) requirements. Use Electromagnetic Compatibility Plan as the basis for this review. Check application of MIL-STDs and MIL-Specs cited by the system/ equipment specification(s) to the HWCI/Subsystem design. Review preliminary EMI test plans to assess adequacy to confirm that EMC requirements have been met.

40.5 Design Reliability.

40.5.1 Identify the quantitative reliability requirements specified in the hardware Development and Software Requirements Specification(s), including design allocations, and the complexity of the CSCIs.

40.5.2 Review failure rate sources, derating policies, and prediction methods. Review the reliability mathematical models and block diagrams as appropriate.

40.5.3 Describe planned actions when predictions are less than specified requirements.

40.5.4 Identify and review parts or components which have a critical life or require special consideration, and general plan for handling. Agencies so affected shall present planned actions to deal with these components or parts.

40.5.5 Identify applications of redundant HWCI elements. Evaluate the basis for their use and provisions for "on-line" switching of the redundant element.

40.5.6 Review critical signal paths to determine that a fail- safe/fail-soft design has been provided.

40.5.7 Review margins of safety for HWCIs between functional requirements and design provisions for elements, such as: power supplies, transmitter modules, motors, and hydraulic pumps. Similarly, review structural elements; i.e., antenna pedestals, dishes, and radomes to determine that adequate margins of safety shall be provided between operational stresses and design strengths.

40.5.8 Review Reliability Design Guidelines for HWCIs to insure that design reliability concepts shall be available and used by equipment designers. Reliability Design Guidelines shall include, as a minimum, part application guidelines (electrical derating, thermal derating, part parameter tolerances), part selection order of preference, prohibited parts/materials, reliability apportionments/predictions, and management procedures to ensure compliance with the guidelines.

40.5.9 Review for HWCIs preliminary reliability demonstration plan: failure counting ground rules, accept-reject criteria, number of test articles, test location and environment, planned starting date, and test duration.

40.5.10 Review elements of reliability program plan to determine that each task has been initiated toward achieving specified requirements.

40.5.11 Review subcontractor/supplier reliability controls.

40.6 Design Maintainability.

40.6.1 Identify the quantitative maintainability requirements specified in the hardware Development and Software Requirements Specifications; if applicable, compare preliminary predictions with specified requirements.

40.6.2 Review HWCI preventive maintenance schedules in terms of frequencies, durations, and compatibility with system schedules.

40.6.3 Review repair rate sources and prediction methods.

40.6.4 Review planned actions when predictions indicate that specified requirements will not be attained.

40.6.5 Review planned designs for accessibility, testability, and ease of maintenance characteristics (including provisions for automatic or operator-controlled recovery from failure/ malfunctions) to determine consistency with specified requirements.

40.6.6 Determine if planned HWCI design indicates that parts, assemblies, and components will be so placed that there is sufficient space to use test probes, soldering irons, and other tools without difficulty and that they are placed so that structural members of units do not prevent access to them or their ease of removal.

40.6.7 Review provisions for diagnosing cause(s) of failure; means for localizing source to lowest replaceable element; adequacy and locations of planned test points; and planned system diagnostics that provide a means for isolating faults to and within the configuration item. This review shall encompass on-line diagnostics, off-line diagnostics, and proposed technical orders and/or commercial manuals.

40.6.8 Review for HWCIs the Design for Maintainability Checklist to insure that listed design principles shall lead to a mature maintainability design. Determine that contractor design engineers are using the checklist.

40.6.9 Evaluate for HWCIs the preliminary maintainability demonstration plan, including number of maintenance tasks that shall be accomplished; accept-reject criteria; general plans for introducing faults into the HWCI and personnel involved in the demonstration.

40.6.10 Review elements of maintainability program plan to determine that each task has been initiated towards achieving specified requirements.

40.6.11 Insure that consideration has been given to optimizing the system/item from a maintainability and maintenance viewpoint and that it is supportable within the maintenance concept as developed. Also, for HWCIs insure that a Repair Level Analysis (RLA) has been considered.

40.7 Human Factors.

40.7.1 The contractor shall present evidence that substantiates the functional allocation decisions. The Review shall cover all operational and maintenance functions of the configuration item. In particular, ensure that the approach to be followed emphasizes the functional integrity of the man with the machine to accomplish a system operation.

40.7.2 Review design data, design descriptions and drawings on system operations, equipments, and facilities to insure that human performance requirements of the hardware Development and Software Requirements Specifications are met. Examples of the types of design information to be reviewed are:

? a. Operating modes for each display station, and for each mode, the functions performed, the displays and control used, etc.

? b. The exact format and content of each display, including data locations, spaces, abbreviations, the number of digits, all special symbols (Pictographic), alert mechanisms (e.g., flashing rates), etc.

? c. The control and data entry devices and formats including keyboards, special function keys, cursor control, etc.

? d. The format of all operator inputs, together with provisions for error detection and correction.

? e. All status, error, and data printouts - including formats, headings, data units, abbreviations, spacings, columns, etc.

These should be presented in sufficient detail to allow contracting agency personnel to judge adequacy from a human usability standpoint, and design personnel to know what is required, and test personnel to prepare tests.

40.7.3 Make recommendations to update the System/Subsystem, or Software Requirements Specification and Interface Requirements Specification(s) in cases where requirements for human performance need to be more detailed.

40.7.4 Review man/machine functions to insure that man's capabilities are utilized and that his limitations are not exceeded.

40.8 System Safety.

40.8.1 Review results of configuration item safety analyses, and quantitative hazard analyses (if applicable).

40.8.2 Review results of system and intra-system safety interfaces and trade-off studies affecting the configuration item.

40.8.3 Review safety requirements levied on subcontractors.

40.8.4 Review known special areas of safety, peculiar to the nature of the system (e.g., fuel handling, fire protection, high levels of radiated energy, high voltage protection, safety interlocks, etc.).

40.8.5 Review results of preliminary safety tests (if appropriate).

40.8.6 Generally review adequacy and completeness of configuration item from design safety viewpoint.

40.8.7 Review compliance of commercially available configuration items or configuration item components with system safety requirements and identify modifications to such equipment, if required.

40.9 Natural Environment.

40.9.1 Review contractor's planned design approach toward meeting climatic conditions (operating and non-operating ranges for temperature, humidity, etc.) that are specified in the HWCI Development Specification.

40.9.2 Insure that the contractor clearly understands the effect of, and the interactions between, the natural aerospace environment and HWCI design. In cases where the effect and interactions are not known or are ambiguous, insure that studies are in progress or planned to make these determinations.

40.9.3 Current and forecast natural aerospace environment parameters may be needed for certain configuration items; e.g., display of airbase conditions in a command and control system, calculation of impact point for a missile, etc. Insure compatibility between the configuration item design and appropriate meteorological communications by comparing characteristics of the source (teletype, facsimile, or data link) with that of the configuration item. Insure that arrangements or plans to obtain needed information have been made and that adequate display of natural environmental information shall be provided.

40.10 Equipment and Part Standardization.

40.10.1 Equipment and Components:

? a. Review current and planned contractor actions to determine that equipment or components for which standards or specifications exist shall be used whenever practical. (Standard item with NSN should have first preference).

? b. Review specific trade-offs or modifications that maybe required of existing designs if existing items are, or will be, incorporated in the HWCI.

? c. Existing designs will be reviewed for use or non-use based on the potential impact on the overall program in the following areas:

1. (1) Performance

2. (2) Cost

3. (3) Time

4. (4) Weight

5. (5) Size

6. (6) Reliability

7. (7) Maintainability

8. (8) Supportability

9. (9) Producibility

? d. Review HWCI design to identify areas where a practical design change would materially increase the number of standard items that could be incorporated.

? e. Insure that Critical Item Specifications shall be prepared for hardware items identified as engineering or logistics critical.

40.10.2 Parts Standardization and Interchangeability:

? a. Review procedures to determine if maximum practical use will be made of parts built to approved standards or specifications. The potential impact on the overall program is to be evaluated when a part built to approved standards and specifications cannot be used for any of the following reasons:

1. (1) Performance

2. (2) Weight

3. (3) Size

4. (4) Reliability/Mantainability/Availability

5. (5) Supportability

6. (6) Survivability (including nuclear)

? b. Identify potential design changes that will permit a greater use of standard or preferred parts and evaluate the trade-offs.

? c. Insure understanding of parts control program operations for selection and approval of parts in new design or major modifications.

? d. Review status of the Program Parts Selection List.

? e. Review status of all non-standard parts identified.

? f. Review pending parts control actions that may cause program slippages, such as non-availability of tested parts.

40.10.3 Assignment of Official Nomenclature:

? a. Insure understanding of procedure for obtaining assignment of nomenclature and approval of nameplates.

? b. Determine that a nomenclature conference has been held and agreement has been reached with the contracting agency on the level of nomenclature; i.e., system, set, central, group, component, sub-assembly, unit, etc.

40.11 Value Engineering.

40.11.1 Review the Contractor's in-house incentive Value Engineering Program, which may include but not be limited to the

? a. Contractor's Value Engineering organization, policies following: and procedures.

? b. Contractor's Value Engineering Training Program.

? c. Potential Value Engineering projects, studies and VECPs.

? d. Schedule of planned Value Engineering tasks/events.

? e. Policies and procedures for subcontractor Value Engineering Programs.

40.12 Transportability.

40.12.1 Review HWCI to determine if design meets contracts requirements governing size and weight to permit economical handling, loading, securing, transporting, and disassembly for shipment within existing capabilities of military and commercial carriers. Identify potential outsized and overweight items. Identify system/items defined as being hazardous. Ensure packaging afforded hazardous items complies with hazardous materials regulations.

40.12.2 Identify HWCIs requiring special temperature and humidity control or those possessing sensitive and shock susceptibility characteristics. Determine special transportation requirements and availability for use with these HWCIs.

40.12.3 Review Transportability Analysis to determine that transportation conditions have been evaluated and that these conditions are reflected in the design of protective, shipping, and handling devices. In addition to size and weight characteristics, determine that analysis includes provisions for temperature and humidity controls, minimization of sensitivity, susceptibility to shock, and transit damage.

40.13 Test.

40.13.1 Review all changes to the System/Subsystem, HWCI Development, Software Requirements, and Interface Requirements Specifications subsequent to the established Allocated Baseline to determine whether Section 4.0 of all these specifications adequately reflects these changes.

40.13.2 Review information to be provided by the contractor regarding test concepts for Development Test and Evaluation (DT&E) testing (both informal and formal). Information shall include:

? a. The organization and responsibilities of the group that will be responsible for test.

? b. The management of his in-house development test effort provides for:

1. (1) Test Methods (plans/procedures)

2. (2) Test Reports

3. (3) Resolution of problems and errors

4. (4) Retest procedure

5. (5) Change control and configuration management

6. (6) Identification of any special test tools that are not deliverable under the contract.

? c. The methodology to be used to meet quality assurance requirements/qualification requirements, including the test repeatability characteristics and approach to regression testing.

? d. The progress/status of the test effort since the previous reporting milestone.

40.13.3 Review status of all negative or provisional entries such as "not applicable (N/A)" or "to be determined (TBD)" in Section 4.0 of the System/Subsystem, hardware Development, Software Requirements or Interface Requirements Specifications. Review all positive entries for technical adequacy. Insure that associated test documentation includes these changes.

40.13.4 Review interface test requirements specified in Section 4.0 of the hardware Development, Software Requirements, and Interface Requirements Specifications for compatibility, currency, technical adequacy, elimination of redundant test. Insure that all associated test documents reflect these interface requirements.

40.13.5 Insure that all test planning documentation has been updated to include new test support requirements and provisions for long-lead time support requirements.

40.13.6 Review contractor test data from prior testing to determine if such data negates the need for additional testing.

40.13.7 Examine all available breadboards, mock-ups, or devices which will be used in implementing the test program or which affect the test program, for program impact.

40.13.8 Review plans for software Unit testing to ensure that they:

? a. Address Unit level sizing, timing, and accuracy requirements.

? b. Present general and specific requirements that will be demonstrated by Unit testing.

? c. Describe the required test-unique support software, hardware, and facilities and the interrelationship of these items.

? d. Describe how, when, and from where the test-unique support items will be obtained.

? e. Provide test schedules consistent with higher level plans.

40.13.9 Review plans for CSC integration testing to ensure that they:

? a. Define the type of testing required for each level of the software structure above the unit level.

? b. Present general and specific requirements that will be demonstrated by CSC integration testing.

? c. Describe the required test-unique support software, hardware, and facilities and the interrelationship of these items.

? d. Describe how, when, and from where the test-unique support items will be obtained.

? e. Describe CSC integration test management, to include:

1. (1) Organization and responsibilities of the test team

2. (2) Control procedures to be applied during test

3. (3) Test reporting

4. (4) Review of CSC integration test results

5. (5) Generation of data to be used in CSC integration testing.

? f. Provide test schedules consistent with higher level plans.

40.13.10 Review plans for formal CSCI testing to ensure that they:

? a. Define the objective of each CSCI test, and relate the test to the software requirements being tested.

? b. Relate formal CSCI tests to other test phases.

? c. Describe support software, hardware, and facilities required for CSCI testing; and how, when, and from where they will be obtained.

? d. Describe CSCI test roles and responsibilities.

? e. Describe requirements for Government-provided software, hardware, facilities, data, and documentation.

? f. Provide CSCI test schedules consistent with higher- level plans.

? g. Identify software requirements that will be verified by each formal CSCI test.

40.14 Maintenance and Maintenance Data (HWCIs).

40.14.1 Describe System Maintenance concept for impact on design and SE. Review adequacy of maintenance plans. Coverage shall be provided for On Equipment (Organizational), Off Equipment - On Site (Intermediate), Off Equipment - Off Site (Depot) level maintenance of Government Furnished Equipment (GFE), and Contractor Furnished Equipment (CFE). (See Section 3, Definitions, para 3.12 for levels of maintenance.)

40.14.2 Determine degree of understanding of the background, purpose, requirements, and usage of Maintenance (failure) Data Collection and Historical/Status Records. (REF Data Item titled, "Reliability and Maintainability Data Reporting and Feedback Failure Summary Reports").

40.14.3 Describe method of providing Maintenance, Failure, Reliability, Maintainability Data to contracting agency.

40.14.4 Describe how requirements are submitted to the contracting agency for Equipment Classification (EQ/CL) Codes (formerly Work Order Number Prefix/Suffix Codes) when this requirement exists.

40.14.5 Review plans for (and status of) Work Unit Coding of the equipment. Work Unit codes shall be available for documenting Maintenance Data commencing with configuration item/Subsystem Testing. (Ref. Data Item titled "Technical Orders" and the military specification on work unit coding).

40.15 Spares and Government Furnished Property (GFP).

40.15.1 Review logistics and provisioning planning to insure full understanding of scope of requirements in these areas and that a reasonable time-phased plan has been developed for accomplishment. Of specific concern are the areas of: provisioning requirements, GFP usage, and spare parts, and support during installation, checkout, and test.

40.15.2 Review provisioning actions and identify existing or potential provisioning problems - logistic critical and long- lead time items are identified and evaluated against use of the interim release requirements.

40.15.3 Review plans for maximum screening and usage of GFP, and extent plans have been implemented.

40.15.4 Review progress toward determining and acquiring total installation, checkout, and test support requirements.

40.16Packaging/SDPE (Special Design Protective Equipment).

40.16.1 Analyze all available specifications (System/Subsystem, HWCI Development, Software Requirements, Interface Requirements, and Critical Items) for packaging (Section 5) requirements for each product fabrication and material specification.

40.16.2 Evaluate user/operational support requirements and maintenance concepts for effect and influence on package design.

40.16.3 Establish that time phased plan for package design development is in consonance with the development of the equipment design.

40.16.4 Review planned and/or preliminary equipment designs for ease of packaging and simplicity of package design, and identify areas where a practical design change would materially decrease cost, weight, or volume of packaging required.

40.16.5 Review requirements for SDPE necessary to effectively support configuration item during transportation, handling and storage processes. Insure SDPE is categorized as a configuration item utilizing specifications conforming to the types and forms as prescribed in the contract. Review SDPE development/product specifications for adequacy of performance/ interface requirements.

40.16.6 Determine initial package design baselines, concepts, parameters, constraints, etc., to the extent possible at this phase of the configuration item development process.

40.16.7 Insure previously developed and approved package design data for like or similar configuration items is being utilized.

40.16.8 Establish plans for trade studies to determine the most economical and desirable packaging design approach needed to satisfy the functional performance and logistic requirements.

40.16.9 Verify the adequacy of the prototype package design.

40.16.10 Review Section 5 of Specification to insure full understanding by contractor for contractor requirements. Identify package specification used for hazardous materials.

40.17 Technical Manuals.

40.17.1 Review status of the "Technical Manual Publications Plan" to insure that all aspects of the plan have been considered to the extent that all concerned agencies are apprised of the technical manual coverage to be obtained under this procurement. The suitability of available commercial manuals and/or modifications thereto shall also be determined.

40.17.2 Review the availability of technical manuals for validation/verification during the latter phases of DT&E testing.

40.17.3 If a Guidance Conference was not accomplished or if open items resulted from it, then review as applicable provisions for accomplishing TO in-process reviews, validation, verification, prepublication, and postpublication reviews.

40.18 System Allocation Document.

40.18.1 Review the Draft System Allocation Document for completeness and technical adequacy to extent completed.

40.18.2 The format shall provide the following minimum information:

? a. Drawing Number

? b. Issue

? c. Number of Sheets

? d. Location

? e. Configuration Item Number

? f. Title

? g. Part Number

? h. Serial Number

? i. Specification Number

? j. Equipment Nomenclature

? k. Configuration Item Quantity

? l. Assembly Drawing

40.19 Design Producibility and Manufacturing.

40.19.1 The contractor shall demonstrate and present evidence that manufacturing engineering will be integrated into the design process.

? a. The contractor shall provide evidence of performing producibility analyses on development hardware trading off design requirements against manufacturing risk, cost, production, volume, and existing capability/availability. Evidence of such analyses may be in the contractor's own format but must conclusively demonstrate that in-depth analyses were performed by qualified organizations/individuals and the results of those analyses will be incorporated in the design.

? b. Preliminary manufacturing engineering and production planning demonstrations shall address: material and component selection, preliminary production sequencing, methods and flow concepts, new processes, manufacturing risk, equipment and facility utilization for intended rates and volume, production in-process and acceptance test and inspection concepts. (Efforts to maximize productivity in the above areas should be demonstrated.)

? c. Management systems to be utilized will insure that producibility and manufacturing considerations are integrated throughout the development effort.

40.19.2 The producibility and manufacturing concerns identified in the SRR and the SDR shall be updated and expanded to:

? a. Provide evidence that concerns identified in the Manufacturing Feasibility Assessment and the Production Capability Estimate have been addressed and that resolutions are planned or have been performed.

? b. Make recommendations including manufacturing technology efforts and provide a schedule of necessary actions to the program office to resolve open manufacturing concerns and reduce manufacturing risk.

40.20 Post Review Action.

40.20.1 After completing the PDR, the contractor shall publish and distribute copies of Review minutes. The contracting agency officially acknowledges completion of a PDR as indicated in paragraph 4.2.4.

40.20.2 The accomplishment of the PDR shall be recorded on the configuration item Development Record by the contractor.

APPENDIX E

Date: 2016-06-13; view: 9