ACC Practice Center > AT&L Knowledge Management... > Integrated Logistic... > Logistics Demonstration -

Logistics Demonstration -

Topic

Conduct a Search

Search for:

Search for: Search in: Search in Language:

Long Description

Definition General Info Policies Guides Communities Training Related

DEFINITION

GENERAL INFORMATION/NARRATIVE

a. DODI 5000.2 requires that analysis, T&E results, or independent reviews confirm the adequacy of the proposed maintenance plan and programmed support resources to meet objectives for peacetime readiness and wartime employment. It also requires that the ability to support any system be demonstrated before the system is placed in the hands of the user. The LD is conducted to confirm that support resources and tasks developed to sustain the system will function as intended. The LD data is supplemented by supportability related data obtained during developmental test and evaluation (DT&E) and OT&E to confirm the correct resources and tasks have been developed. AR 700–127 identifies the LD as a means for satisfying DOD requirements for all acquisition programs. A request for an LD waiver will be s u b m i t t e d b y t h e M A T D E V t o A s s i s t a n t S e c r e t a r y o f t h e A r m y f o r A c q u i s i t i o n , L o g i s t i c s , a n d T e c h n o l o g y (ASA(ALT)) with supporting rationale and an alternate plan for accomplishing the LD. b. The goals of the LD are to: (1) Validate the supportability of the materiel design including transportability and MANPRINT.(2) Validate the adequacy of maintenance planning for the system (such as maintenance concept, task allocation, maintenance procedures, troubleshooting procedures and test program sets (TPS), prognostics/embedded diagnostics, and support equipment).(3) Validate the final SSP to include interface compatibility of the TMDE and support equipment with the materiel system. (4) Review the technical publications.(5) Validate and update the LMI. c. LD for commercial/NDI programs may be abbreviated if existing supportability data can be obtained and adequately evaluated. Inclusion of a logistics specialist on the source selection evaluation board to evaluate such data is prudent. In some cases it may be necessary to perform a partial LD on commercial/NDI systems after source selectionto verify the maintainability and supportability of the materiel design. d. The LD is a validation process managed by the MATDEV. Maximum use should be made of existing qualitative and quantitative data such as when the item is us ed by another service, industry, or country. In order to minimize cost and schedule risk, existing qualitative and quantitative demonstrations, evaluations, analyses, simulations and tests

should be used to meet LD requirements. The extent of the LD is based on the complexity and characteristics of the system (for example, there is no need to perform a maintenance demonstration if there are no maintenance tasks.) If major configuration changes are required between test articles and production software/hardware, it would be advisable to repeat the affected portions of the LD. This would include repeating portions of the TM verification.

e. The LD is conducted on an engineering prototype item for all developmental systems (hardware and software) oron a production item for commercial/NDI. Modified items and all new changed TMDE, training devices, and support equipment intended for support of the system may also require a partial LD.

f. The LD may be conducted at contractor’s plant, Government maintenance engineering evaluation facility, or test sites. Whenever feasible, the LD should be conducted at an existing support facility similar to intended user facilities to verify facility adequacy or identify any facility deficiencies.

g. The LD is normally conducted on those tasks performed at field level and some sustainment level. h. For ammunition items, the LD normally consists of verification of render safe and EOD procedures. i. The requirements for an LD will be summarized in the system TEMP. 12–5. Procedures a. Review of requirements. The ILSM and SIPT members review the CD, supplemental documentation, and contract specifications to ensure that the requirements are clearly defined and input data to the analyses are available and agreed upon. b. Review of analyses. The results of the LORA, various supportability analyses, LMI, provisioning analysis (see AR 700–18), MANPRINT assessment (see AR 602–2), and transportability analysis (see DODI 4540.7) are reviewed to identify logistic resources, tasks, and issues to be addressed in the LD. c. LD plan. The MATDEV with support of the SIPT prepares the LD plan based on the outcome of the requirements review and initial analyses of the system. The plan should address all opportunities for collection of data to confirm adequacy of the planned support. d. Support resources. These need to be programmed to include use of existing data from the contractor or other users, TM validation and verification, maintainability and prognostics/embedded diagnostics demonstrations, transportability analysis and testing, MANPRINT assessment, TMDE evaluation, and software evaluation. e. Conduct of the LD. Generally the LD is accomplished in increments. LDs may be conducted on system 34 DA PAM 700–56 • 21 April 2006 components and major subassemblies with a final system level LD to verify the component interface. Other tailored LD procedures may be required. In any event, the LD plan provides for a complete and adequate LD to verify the ability of representative support personnel to perform each new task with the support resources included in the SSP in an environment that approximates the expected operational profile. The LD normally consists of— (1) Physical tear down. All operator tasks and specified field-level maintenance tasks contained in the TMs are performed by Target Audience Soldiers. This portion of the LD also serves to review the TM for accuracy/completeness.This portion of the LD also serves as the TM validation to meet the intent of MIL–STD–40051. (2) Maintainability and prognostics/ embedded diagnostics demonstration. Maintenance and troubleshooting tasks as the result of operations or fault simulation or insertion are to be accomplished by typical user personnel to meet the intent of MIL–HDBK–470. Complex systems may require additional demonstrations prior to fielding of TPSs or other support capabilities that are not available for the initial fielding. f. Packaging and handling evaluation. Packaging requirements are validated to meet the intent of AR 700–15. g. MANPRINT assessment. MANPRINT assessments are conducted by the DCS, G–1 for ACAT I and ACAT II programs or by TRADOC for other programs to determine the status and adequacy of MANPRINT efforts and identify any unresolved issues or concerns (see AR 602–2). Based on DA Pam 73–1, the assessment of MANPRINT is an essential element of a system’s evaluation strategy at each decision point. Also, AR 602–2 directs ATEC to include MANPRINT considerations in system T&E, of which the LD is an important source of data. h. TMDE evaluation. TMDE requirements and supportability statement from the U.S. Army TMDE Activity is evaluated for interface compatibility during the LD. i. Software evaluation. Prognostics/diagnostic software will be demonstrated during the LD by fault insertion. The faults inserted will include operator procedure errors and software processing errors that the operator and/or maintainer should be able to detect, fault isolate and correct. MIL–HDBK–470A may be used to determine fault insertion sample size. The designated center for software engineering conducts testing of software and evaluation of PPSS plans and capabilities. j. Transportability engineering analysis. MSDDC–TEA conducts transportability analysis and determines transportability testing needed to ensure transportability requirements are met in accordance with DODI 4540.7. A transportability demonstration may be required if analysis are insufficient to prove otherwise. k . TM/DMWR verification. Government personnel verify the contractor’s previous validation effort if production version of the system is available. Verification may range from typical user personnel performing 100 percent of all operating and maintenance procedures in the publications, to witnessing the validation reviews performed by the contractor to meet the intent of MIL–STD–40051. Complex systems may require a verification of preliminary draft manuals prior to developmental tests/operational tests and a reverification of changes in the final draft manuals prior to fielding. The designated depot works closely with the MATDEV and SIPT to conduct the DMWR verification or pilot overhaul and reports on status and results. l. Final evaluation and report. (1) The PEO/PM/MATDEV prepares the final LD report with the SIPT.

(2) The LD report includes the LD strategy, details on the conduct of the LD, data collection,

analysis results, all quantitative and qualitative findings, and a description of all necessary follow-on actions. LD report findings may come from data existing prior to the LD, development and operational test data, and data derived from the LD Corrective actions are incorporated and verified before the production decision. (3) The LD report is completed at least 45 days prior to the next decision review and provided to the SIPT. (4) The PM, with support from the SIPT, is responsible for the preparation of the LD Plan. The LD Plan is distributed prior to the SIPT meeting that will address the LD. The recommended format is—(a) General.(b) Scope.(c) System description.(d) LD strategy.(e) Participating organizations, responsibilities, and milestones for delivery of SSP.(f) Procedures, detailed plans, and milestones for demonstration activities.(g) Reports (describe who will provide input and the due dates).(h) References.(i) Acronyms.

(j) Distribution.

Logistic Demonstration (LD) Report: The LD report includes the LD strategy, details on the conduct of the LD, data collection, analysis results, all quantitative and qualitative findings, and a description of all necessary follow-on actions. LD report findings may come from data existing prior to the LD, development and operational test data, and data derived from the LD Corrective actions are incorporated and verified before the production decision.The LD report is completed at least 45 days prior to the next decision review and provided to the SIPT.The PM, with support from the SIPT, is responsible for the preparation of the LD Report.

8915	Page Views	0	Pages Emailed
0	Meta-card Views	0	Documents and Videos
0	Questions	0	Attachments Downloaded
0	Answers	0	Videos downloaded
0	Relationships and Highlights

ID	247034

Date Created	Tuesday, November 18, 2008 11:24 AM
Date Modified	Friday, October 9, 2009 11:36 AM

Version Comment:

User Name:
Password:
	Forgot your password?

Logistics Demonstration -

DEFINITION

GENERAL INFORMATION/NARRATIVE

POLICIES, DIRECTIVES, REGULATIONS, LAWS

BEST PRACTICES, LESSONS LEARNED, STORIES, GUIDES, HANDBOOKS, TEMPLATES, EXAMPLES, TOOLS

COMMUNITIES OF PRACTICE

TRAINING RESOURCES

RELATED ARTICLES

List of All Contributions at This Location

Popular Tags

Page Information

Login with your CAC

Login with your Password

Browse

Tags

ACC Practice Center Version 3.2