25.02.2015 Views

Acquire Support Subsystem - Marine Corps Systems Command

Acquire Support Subsystem - Marine Corps Systems Command

Acquire Support Subsystem - Marine Corps Systems Command

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Welcome to the MARCORSYSCOM EQUIPPING PROCESS<br />

Produce/<br />

Procure<br />

<strong>Acquire</strong> <strong>Support</strong> <strong>Subsystem</strong><br />

INPUTS<br />

Draft Fielding Plan<br />

Contract<br />

<strong>Support</strong>ability Plan<br />

CPD<br />

Non-Validated System<br />

<strong>Support</strong> Package<br />

Test <strong>Support</strong> Package<br />

Configuration Baseline<br />

Updated <strong>Support</strong>ability<br />

Demonstration Plan<br />

ACTIVITIES<br />

‣ Conduct <strong>Support</strong>ability<br />

Demonstration<br />

‣ Finalize Fielding Plan<br />

‣ Prepare In-Service<br />

Management Plan<br />

‣ Begin Crafting Performance<br />

Based Agreements<br />

‣ Independent Logistics<br />

Assessment Policy Letter<br />

‣ Independent Logistics<br />

Assessment Process<br />

= Logistician Responsibility<br />

= Requires Logistician Input<br />

OUTPUTS<br />

<strong>Support</strong><br />

<strong>Subsystem</strong><br />

Final Fielding Plan<br />

Logistics <strong>Support</strong><br />

Contracts &<br />

Agreements<br />

Validated System<br />

<strong>Support</strong> Package<br />

<strong>Support</strong>ability Plan<br />

In-Service<br />

Management Plan


Roadmap Narratives<br />

<strong>Acquire</strong> <strong>Support</strong> <strong>Subsystem</strong><br />

Acquisition of the necessary and tailored supportability requirements is<br />

conducted during this phase and will provide the infrastructure necessary for<br />

Fielding and Post-Deployment sustainment. An appropriately structured and<br />

worded SOW, following the <strong>Support</strong> Planning strategies and MS B activities, will<br />

contract for the Logistics Elements and is the foundation upon which the system<br />

sustainment is based.<br />

This phase involves the critical implementation of logistics assumptions that were<br />

validated during the Design/Develop Phase. Normally performed during<br />

execution of the Production Contract, the logistics elements are acquired based<br />

on the results of the analytical data derived during the prior phase and proven<br />

during system test.<br />

Conduct of the <strong>Support</strong>ability Demonstration will confirm the validity of the<br />

planned sustainment approach and establish the logistics footprint for the<br />

production system. The critical documentation requirements include the final<br />

Fielding Plan, <strong>Support</strong>ability Plan/MCSAMP and Contract Logistics <strong>Support</strong><br />

arrangements. The critical planning event for this phase is the Independent<br />

Logistics Assessment (ILA). Significant errors or omissions of performance<br />

during this phase may seriously effect Fielding.<br />

Continued use by the Logistician of the Logistics Integrated Product Team (IPT),<br />

and dependence on the Subject Matter Experts, will ensure that supportability<br />

requirements to the technical level of detail are delivered on time and within<br />

budget. Impacts to the logistics footprint will be identified and mitigated and the<br />

required levels of support are available to support MDA decisions, fielding, postfielding<br />

and follow-on modifications, spirals, increments and obsolescence<br />

management.


4105<br />

LOG<br />

15 May 06<br />

ACQUISITION POLICY LETTER NO. X-03<br />

From: <strong>Command</strong>ing General<br />

Subj: INDEPENDENT LOGISTICS ASSESSMENT (ILA) AND CERTIFICATION<br />

REQUIREMENTS<br />

Ref: (a) SECNAVINST 5000.2C<br />

(b) SECNAVINST 4105.1A<br />

(c) NAVSO P-3692<br />

(d) MCSC Milestone Decision Process (MDP) Guide<br />

Encl: (1) ILA Process<br />

(2) ILA Report (ILAR); Template for ILA<br />

(3) ILA Brief Template<br />

1. Purpose. To implement Department of Navy (DON) ILA policy<br />

in support of the <strong>Marine</strong> <strong>Corps</strong> <strong>Systems</strong> <strong>Command</strong> (MARCORSYSCOM)<br />

Milestone Team Assessment (MTA) Process.<br />

2. Background. References (a) through (c) provide guidance for<br />

planning, conducting, and reporting ILAs within the DON.<br />

Additionally, several recent initiatives have driven the need to<br />

revise current policy and procedures for establishing and<br />

conducting ILAs. These initiatives include the establishment of<br />

Product Groups composed of program centric teams, the<br />

implementation of the MTA process and teams to support the<br />

Milestone Decision Processes (MDP), reference (d) which<br />

represents DON guidance on ILAs, and codifying the Program<br />

Manager’s (PM’s) total life cycle management responsibilities.<br />

3. Policy. For all acquisition programs in which the <strong>Command</strong>ing<br />

General (CG), MARCORSYSCOM serves as the Milestone Decision<br />

Authority (MDA), the Assistant <strong>Command</strong>er, Logistics (ACLOG), or<br />

his designee, shall conduct ILAs to support Milestone B,<br />

Milestone C, and Full Rate Production decisions. For those<br />

programs in which MDA has been delegated to the Product Group<br />

Director (PGD), Strategic Business Team personnel will be<br />

responsible for conducting ILAs IAW DON and ACLOG Guidance. The<br />

ILA shall be considered an integral part of, or predecessor to,<br />

the MTA.


4. Responsibilities<br />

a. ACLOG shall:<br />

(1) Conduct ILAs per enclosure (1), references (c), and<br />

this policy when the MDA is the CG MARCORSYSCOM.<br />

(2) When the MDA is the CG MARCORSYSCOM,serve as, or<br />

designate, the command ILA team leader for joint programs in<br />

which we are a participating Service.<br />

(3) Serve as the MARCORSYSCOM process owner for the ILA<br />

process.<br />

(4) Maintain the command record of ILARs.<br />

b. Assistant <strong>Command</strong>er, Programs shall:<br />

(1) Include the ILAR as an appendix to the MTA.<br />

(2) Ensure that the Acquisition Decision Memorandum<br />

(ADM) includes ILA findings as exit criteria in the Milestone<br />

ADM.<br />

(3) Update reference (d) to reflect this policy.<br />

c. PGDs shall:<br />

(1) When the PGD is the MDA, ensure ILAs are conducted<br />

per reference (b) and (c).<br />

(2) Maintain a list of all scheduled MTAs.<br />

(3) Provide copies of ILAs to ACLOG.<br />

(4) Include unresolved findings as exit criteria in<br />

the ADM.<br />

(5) When the PGD’s Strategic Business Team Logistician<br />

is not available to conduct an ILA, request assistance from the<br />

ACLOG office or another SBT.


d. PMs shall:<br />

(1) Ensure ILAs are conducted on their programs per<br />

enclosure (1) and enclosure (3), reference (c), and this policy.<br />

(2) When serving as MDA, execute all responsibilities<br />

assigned to the PGD in this policy.<br />

(3) Engage the SBT Logistician prior to informing the MDA<br />

of an upcoming milestone decision.<br />

e. ILA Team Leader shall:<br />

(1) Compile the ILAR using enclosure (2) as a guide.<br />

(2) Ensure that the ILAR identifies integrated logistics<br />

support and supportability factors assessed during the review.<br />

(3) Provide rationale for each area not assessed.<br />

(4) Sign the ILAR and certification memo and forward it<br />

to the MTA Lead and ACLOG.<br />

f. MTA Lead shall:<br />

(1) Include the ILAR as an appendix to the MTA.<br />

6. Applicability. This policy letter is not applicable to<br />

MCTSSA.<br />

Distribution: A<br />

W. D. CATTO


ILA Process<br />

PGD<br />

PM informs<br />

PGD/SBT<br />

of upcoming<br />

Milestone Decision<br />

PGD<br />

Forms Milestone<br />

Assessment Team<br />

(MAT)<br />

PGD tasks the SBT<br />

Log to Form ILA<br />

Audit Team<br />

Who is<br />

the<br />

MDA?<br />

CG<br />

PM informs<br />

AC PROG/ SBT<br />

of upcoming<br />

Milestone Decision<br />

AC PROG/ SBT<br />

Forms Milestone<br />

Assessment Team<br />

(MAT)<br />

MAT LOG<br />

Forms ILA<br />

Audit Team<br />

ILA Team<br />

Conducts ILA<br />

Unresolved ILA<br />

Findings Enclosed<br />

in ADM<br />

ILAR Submitted<br />

to MAT and LOG<br />

ILA Team<br />

Leader Prepares and<br />

Signs ILAR<br />

LOG Records<br />

ILAR in Repository


TEMPLATE FOR INDEPENDENT LOGISTICS ASSESSMENT<br />

MEMORANDUM<br />

From: Assistant <strong>Command</strong>er, Logistics<br />

To: Assistant <strong>Command</strong>er, Programs<br />

SSIC Code: 4105<br />

Office Code<br />

Date Signed<br />

Subj: INDEPENDENT LOGISTICS ASSESSMENT (ILA) CERTIFICATION<br />

FOR THE “PROGRAM NAME”<br />

Ref: (a) SECNAVINST 4105.1A<br />

Encl: (1) Attendance Roster<br />

(2) ILA Brief<br />

1. An ILA was conducted in support of the Program Name on<br />

Date. The ILA was accomplished per the reference. Enclosure<br />

(1) contains the list of attendees and enclosure (2)<br />

contains the program brief that includes discussion of<br />

applicable individual logistics elements. Name,<br />

Organization, chaired the ILA.<br />

(Note: Information only; do not insert this text. Regarding<br />

the ten (10) ILS Elements and ILS-related disciplines,<br />

identify ILA results using “stoplight” evaluations i.e.,<br />

RED (not-ready-to-proceed), YELLOW (conditionally ready-toproceed),<br />

or GREEN (ready-to-proceed). Identify<br />

deficiencies and any plans for remediation.<br />

2. Assessment Results<br />

a. The following logistical elements were reviewed and<br />

found to be GREEN with no outstanding issues.<br />

b. The following issues were found to be YELLOW with<br />

minor issues requiring resolution prior to fielding.<br />

c. The following logistical elements were reviewed and<br />

found to be RED with major outstanding issues.


3. The ILA team leader identifies his recommendations. For<br />

example, “A favorable Full Rate Production decision is<br />

recommended. It is further recommended that fielding not<br />

be approved prior to the resolution of the category yellow<br />

issues”.<br />

4. The point of contact at this command is (Enter Full<br />

Name, Title, commercial or DSN phone number).<br />

I.L. ALEADER<br />

Copy to:<br />

PM<br />

ACLOG


Independent Logistics Assessment Certification Criteria<br />

Reference: (Draft) SECNAVINST 4105.X<br />

Green (Ready to Proceed)<br />

A program is logistically ready to proceed when there are no major<br />

issues or risks to be resolved or actions required before the Program<br />

Decision Meeting and there are commitments and realistic completion<br />

dates set for all other important matters affecting supportability or life<br />

cycle affordability.<br />

Yellow (Conditionally Ready to Proceed)<br />

A program is conditionally ready to proceed when there are major<br />

issues, risks or actions outstanding, provided that those can be<br />

addressed and resolved subsequent to a milestone without unduly<br />

compromising supportability, readiness, or life cycle cost.<br />

Red (Not Ready to Proceed)<br />

A program is not ready when there are major issues, risks or actions<br />

outstanding which require resolution before the Program Decision<br />

Meeting or when realistic resources, plans, or commitments are not in<br />

place for major risks or actions that are to be addressed after the<br />

Program Decision Meeting. Examples are:<br />

- Logistics planning and execution are inadequate to ensure<br />

delivery of fully supportable systems.<br />

- Accomplishments do not satisfy intent of DOD/DON policy.<br />

- Operational requirements do not adequately address<br />

supportability.<br />

- Valid support requirements are not fully funded and no approved<br />

workarounds are in place.


Management:<br />

Summary:<br />

Rating<br />

(Circle One):<br />

Green<br />

ILS Management<br />

Yellow<br />

Red<br />

ILS Budgeting and<br />

Funding (i.e., LRFS)<br />

Green<br />

Yellow<br />

ILS Element:<br />

Summary:<br />

Red<br />

Rating<br />

(Circle One):<br />

Green<br />

Design Interface<br />

Yellow<br />

Red<br />

Maintenance<br />

Planning<br />

Green<br />

Yellow<br />

Red


ILS Element:<br />

<strong>Support</strong> Equipment<br />

Summary:<br />

Rating<br />

(Circle One):<br />

Green<br />

Yellow<br />

Red<br />

Supply <strong>Support</strong><br />

Green<br />

Yellow<br />

Red<br />

Manpower and<br />

Personnel<br />

Green<br />

Yellow<br />

Red<br />

Training and Training<br />

<strong>Support</strong><br />

Green<br />

Yellow<br />

Red<br />

Packaging, Handling,<br />

Storage, and<br />

Transportation<br />

Green<br />

Yellow<br />

Red


Green<br />

Facilities<br />

Yellow<br />

Red


ILS Element:<br />

Technical Data<br />

Summary:<br />

Rating<br />

(Circle One):<br />

Green<br />

Yellow<br />

Red<br />

Computer Resources<br />

and Software<br />

<strong>Support</strong><br />

Green<br />

Yellow<br />

Red<br />

ILS Related<br />

Discipline:<br />

Configuraton<br />

Management<br />

Summary:<br />

Rating<br />

(Circle One):<br />

Green<br />

Yellow<br />

Red<br />

Environmental,<br />

Safety and<br />

Occupational Health<br />

Green<br />

Yellow<br />

Red<br />

Transportability<br />

Green<br />

Yellow<br />

Red


ILA Process (5-23-06).igx<br />

PMT<br />

1<br />

PM requests<br />

MS / MCPDM<br />

8<br />

PM and PMT<br />

ILSO Provides<br />

ILA Brief to ILA<br />

Team<br />

(Mech 03)<br />

11<br />

PM and PMT ILSO<br />

Provides Program<br />

<strong>Support</strong>ability<br />

ILA Documentation<br />

to ILA Team<br />

14<br />

PMT Reviews<br />

Findings for<br />

Concurrence /<br />

POA&M<br />

17<br />

PMT Review /<br />

Comment<br />

Draft ILAR?<br />

21<br />

MTA<br />

Conducted<br />

23<br />

Provides<br />

MCPDM<br />

Package to<br />

MDA<br />

MTA Lead /<br />

Team<br />

2<br />

ACPROG /<br />

PM Notifies<br />

MDA of MS /<br />

MCPDM<br />

3<br />

ACPROG/<br />

PGD assigns<br />

MTA Lead<br />

5<br />

ACPROG /<br />

SBT BM<br />

Forms MAT<br />

6<br />

Schedules/<br />

Conducts<br />

Pre-Planning<br />

meeting<br />

22<br />

MTA Lead<br />

Advises PM<br />

on Readiness<br />

ILA Lead /<br />

Team<br />

4<br />

ACLOG / SBT<br />

LOG Assigns<br />

ILA Team<br />

Lead<br />

(-90 Days)<br />

7<br />

ILA Lead<br />

Schedules ILA<br />

and Forms ILA<br />

Team<br />

9<br />

ILA Team<br />

Conducts Pre-<br />

ILA Planning<br />

Meeting<br />

(-60 Days)<br />

Is<br />

Program<br />

Ready<br />

for ILA?<br />

No<br />

10<br />

ILA Team Lead<br />

Coordinates<br />

Final Decision<br />

with ACLOG /<br />

PGD<br />

Yes<br />

12<br />

ILA Team<br />

Members<br />

Conduct<br />

Independent<br />

Assessments<br />

13<br />

ILA Team<br />

Prepares ILA<br />

Findings<br />

15<br />

Formal ILA<br />

Conducted to Make<br />

Overall Assessment<br />

of <strong>Support</strong> <strong>Subsystem</strong><br />

(-30 Days)<br />

16<br />

ILA Team<br />

Lead Prepares<br />

Draft ILAR<br />

18<br />

ILA Team Lead<br />

Prepares and<br />

Submits Final ILAR<br />

and Findings to<br />

ACLOG / SBT<br />

LOG for Signature<br />

19<br />

Signed ILAR<br />

(0 Days)<br />

20<br />

Signed ILAR and<br />

Findings Placed in<br />

ACLOG Repository<br />

(Mech 04)<br />

MDA<br />

24<br />

MDA<br />

Conducts<br />

Paper /<br />

Formal<br />

MCPDM<br />

25<br />

Issues ADM<br />

Mechanisms<br />

Mech: 01<br />

NAVSO P-3692<br />

ILA HDBK<br />

Mech: 02<br />

MCSC ACQ<br />

Policy Ltr X-06<br />

Mech:03<br />

ILA Checklist<br />

Brief<br />

(8)<br />

Mech:04<br />

ACLOG<br />

Repository<br />

(20)<br />

Legend<br />

Activity &<br />

Input/Output<br />

External<br />

Activity<br />

Decision<br />

Informal<br />

Communication<br />

as Task<br />

TASK SHAPE LEGEND<br />

Off-page<br />

Connector<br />

On-page<br />

Connector<br />

Participant<br />

Participant<br />

with<br />

Action<br />

Org<br />

Document<br />

Business<br />

System


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Introduction<br />

Independent Logistics Assessments (ILAs) are a part of the Milestone Team<br />

Assessment (MTA) process and are conducted at Milestone (MS) B, C, and Full<br />

Rate Production (FRP) to assess the planning, development, funding, and<br />

maturity of the supportability strategy and the support subsystem. ILA<br />

certifications are time base decisions and presume successful completion of all<br />

agreed upon tasks and activities. If there are significant program changes after<br />

the ILA, but before the MS decision, the Strategic Business Team (SBT)<br />

Logistician will determine whether another ILA is required.<br />

When there is a MS C decision for Low Rate Initial Production (LRIP) decision, a<br />

preliminary supportability assessment (vice a formal ILA) will be held with the<br />

Program Management Team (PMT) to establish mandatory exit criteria for full<br />

rate production ILA. The MS C Acquisition Decision Memorandum (ADM) will<br />

establish formal ILA exit criteria for full rate production decision.<br />

ILA findings that cannot be corrected before MS C or FRP decision should be<br />

documented as exit criteria for the fielding decision. The review of ILA findings<br />

associated with a fielding decision should be incorporated in the fielding decision<br />

checklist and signed by the ILA lead.<br />

Program Managers (PMs) are responsible for providing resources necessary to<br />

conduct an ILA as required.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ACLOG / SBT LOG Assigns ILA Team Lead (-90 Days)<br />

Number: 4<br />

When the Milestone Decision Authority (MDA) is <strong>Command</strong>ing General (CG)<br />

<strong>Marine</strong> <strong>Corps</strong> <strong>Systems</strong> <strong>Command</strong> (MCSC), Assistant <strong>Command</strong>er, Logistics<br />

(ACLOG) assigns an ILA team lead. This should be an NH-IV, DAWIA Level III<br />

Certified , MCSC Certified Level C Logistician. The team leader can be from<br />

ACLOG Staff or within the <strong>Command</strong>.<br />

When the MDA is the Product Group Director (PGD), the SBT Logistician is the<br />

ILA team lead. HOWEVER, based on program complexity, SBT workload, or<br />

level of independence, the ILA team lead can be requested from another Product<br />

Group or ACLOG Staff.<br />

Education: DAWIA Level III or equivalent certification in Logistics, <strong>Systems</strong><br />

Engineering, Management, or Production, Manufacturing and Quality career<br />

fields 1 .<br />

Experience: Team leaders must have participated in at least one ILA 2 .<br />

1 NAVSO P-3692 October 2003 Independent Logsitics Assessment Handbook p. 1<br />

2 NAVSO P-3692 October 2003 Independent Logsitics Assessment Handbook, p.1


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Lead Schedules ILA and Forms ILA Team<br />

Number: 7<br />

As a result of discussions with PMT during MTA Pre-Planning Meeting, ILA team<br />

lead will schedule ILA and select ILA auditors* and advisors for the Assessment<br />

Team (PMT logistician present preliminary <strong>Support</strong>ability Matrix**). ILA auditors<br />

are subject matter experts from various supportability functional areas. ILA<br />

advisors are short-term consultants to the ILA auditors, possessing program<br />

specific technical expertise.<br />

Education: DAWIA Level III or equivalent certification in Logistics, <strong>Systems</strong><br />

Engineering, Management, or Production, Manufacturing and Quality career<br />

fields 3 .<br />

Experience: Team members must work in a systems engineering or logistics<br />

related function 4 .<br />

*Note: MCSC uses the term ILA auditors / advisors for ILA team members.<br />

**Note: The <strong>Support</strong>ability Matrix can be found in the ILA Checklist Brief<br />

3 NAVSO P-3692 October 2003 Independent Logsitics Assessment Handbook p. 1<br />

4 NAVSO P-3692 October 2003 Independent Logsitics Assessment Handbook, p.1


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: PM and PMT ILSO Provides ILA Brief to ILA Team<br />

Number: 8<br />

When ILAs are conducted by ACLOG, the PMT must use the ILA Briefing<br />

Template developed by the LOG FIT. The briefing template resides in the<br />

ACLOG Knowledge Center. The PMT may provide other documentation or<br />

slides at their discretion.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Team Conducts Pre-ILA Planning Meeting (-60 Days)<br />

Number: 9<br />

During PMT ILA Brief, ILA team members will provide guidance and additional<br />

documentation requirements needed to assess supportability during the<br />

Independent Assessments. The team along with the PMT will determine the<br />

medium used to access ILA documentation.<br />

Exit criteria and findings from previous ILAs should be resolved prior to<br />

conducting another assessment.<br />

After completion of the ILA Brief, the ILA team members will assess whether the<br />

program should proceed with a formal ILA.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Team Lead Coordinates Final Decision with ACLOG / PGD<br />

Number: 10<br />

If ACLOG/ PGD concurs that the program is not ready to proceed with an ILA,<br />

the ILA team lead will notify the MTA Lead.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: PM and PMT ILSO Provides Program <strong>Support</strong>ability ILA<br />

Documentation to ILA Team<br />

Number: 11<br />

The required supportability documentation should have been identified during the<br />

ILA pre-planning meeting. PMT ILSO will notify ILA team lead when<br />

supportability documentation is available and ready for review.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Team Members Conduct Independent Assessments<br />

Number: 12<br />

The ILA team members conduct an independent review of the required<br />

supportability documentation which relate to their subject matter expertise.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Team Prepares ILA Findings<br />

Number: 13<br />

ILA team members either provide by proxy or meet to discuss findings. The ILA<br />

team lead will review all findings for validity.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: PMT Reviews Findings for Concurrence / POA&M<br />

Number: 14<br />

The PMT has the opportunity to provide to the ILA team lead a mitigation plan<br />

(Plan of Action and Milestones (POA&M)) for any findings.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: Formal ILA Conducted to Make Overall Assessment of <strong>Support</strong><br />

<strong>Subsystem</strong> (-30 Days)<br />

Number: 15<br />

The ILA Team will use the MCSC ILA Policy Letter and Template to conduct the<br />

ILA and make the final assessment.<br />

The ILA team will establish the program’s exit criteria for the next ILA, Fielding<br />

Decision, or FRP decision.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Team Lead Prepares Draft ILAR<br />

Number: 16<br />

The ILA team lead is responsible for preparing the draft Independent Logistics<br />

Assessment Report (ILAR) with the recommended ILS program certitifcation<br />

based on the MCSC ILA Policy Letter and template developed during the formal<br />

ILA.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: PMT Review / Comment Draft ILAR<br />

Number: 17<br />

If desired, the PMT can review and comment on the draft ILAR and offer rebuttel.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: ILA Team Lead Prepares and Sumbits Final ILAR and Findings to<br />

ACLOG / SBT LOG to signature<br />

Number: 18<br />

Once the PMT review and comment on the draft ILAR, the ILA team lead<br />

prepares and submits the final ILAR for signature.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: Signed ILAR (0 Days)<br />

Number: 19<br />

The signed ILAR is provided to the MTA Lead.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Title: Signed ILAR Findings Placed in ACLOG Repository<br />

Number: 20<br />

The signed ILAR Findings are placed in the ACLOG Repository to serve as a<br />

MCSC lessons learned library and a historical reporting tool.


Independent Logistics Assessment Process Narratives<br />

23 May 2006<br />

Acronyms<br />

Acronym<br />

ACLOG<br />

ADM<br />

CG<br />

FRP<br />

ILA<br />

ILAR<br />

LRIP<br />

MCSC<br />

MDA<br />

MS<br />

MTA<br />

PGD<br />

PM<br />

PMT<br />

POA&M<br />

SBT<br />

Definition<br />

Assistant <strong>Command</strong>er, Logistics<br />

Acquisition Decision Memorandum<br />

<strong>Command</strong>ing General<br />

Full Rate Production<br />

Independent Logistics Assessment<br />

Independent Logistics Assessment Report<br />

Low Rate Initial Production<br />

<strong>Marine</strong> <strong>Corps</strong> <strong>Systems</strong> <strong>Command</strong><br />

Milestone Decision Authority<br />

Milestone<br />

Milestone Team Assessment<br />

Product Group Director<br />

Program Manager<br />

Program Management Team<br />

Plan of Action and Milestones<br />

Strategic Business Team

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!