1 / 8

LOG 365 TLO/ELO Review LOG FIPT October 2012

LOG 365 TLO/ELO Review LOG FIPT October 2012. FIPT Action Item. “DAU will distribute ELOs for LOG 365 for review and input.”. Comments.

rafer
Download Presentation

LOG 365 TLO/ELO Review LOG FIPT October 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LOG 365 TLO/ELO Review LOG FIPT October 2012

  2. FIPT Action Item “DAU will distribute ELOs for LOG 365 for review and input.”

  3. Comments • General Comment: ELOs x.2 in several places uses “analyze.” The PSM needs to provide inputs into those documents. “Analyze” implies those documents will be provided and the PSM will “examine” or “investigate” the documents. In practice the PSM will be required to generate or provide inputs to the documents. If the teaching strategy is to proved a notional strategy with its associated notional documents, using “analyze” is okay. However if that is not the strategy, recommend changing the word. (B. Houts) • ELO 1.5: Evaluate the role of the PSM in implementing affordability initiatives directed at improving productivity and reducing life cycle costs. • Comment: Recommend including “logistics footprint.” It is a major driver of the elements listed and is included in DoDD 5000.01. (B. Houts) • TLO 2.0: Describe the role of the Product Support Manager (PSM) in deriving the operational capability  requirements of a system, assumptions for its operational use and its planned logistical support. • Comment: Shouldn’t this be suitability vice capability? The PSM is responsible for the “ility” attributes of the system, not its war fighting capability. The PSM does need to understand how maintainability, etc impacts availability, etc. as well as O&S costs (JB)

  4. Comments • TLO 2.0, cont. • Comment: I hope that discussion of TLO 2.0 activities addresses an apparent paradox, inherent to PSMs and the JCIDS/MSA phases of Acquisition: PSMs do not formally exist prior to pre-program initiation activities and the PSM "function" is not responsible for setting sustainment-related performance capability criteria, although PSMs are dependent on 2.1-2.4 outcomes for having set for them a good start towards shaping a subsequent product support program. How then, can PSMs exert influence as functional experts where there is no clear organization entrée for during these earliest processes? I believe there is a "book" answer ..but then this is a seminar. (C. Borsch) • TLO 4.0: Describe how the Product Support Manager (PSM) will interface with the Systems Engineering process and other technical activities to ensure the system is designed for reliability, availability, maintainability and cost. • Comment: TLO 4.0 and several places within the ELOs. Recommend changing “activities” to either “functions” or “organizations.” Think it more clearly describes the intent and avoids the perception that we are talking about tasks. (B. Houts)

  5. Comments • TLO 6.0: Describe how the Product Support Manager (PSM) will establish credible cost estimates, ensure program affordability and control cost growth. • Comment: Change the tone to also include the PPBE role as well as the PSM’s involvement in the financial process (all phases)) It is implied in ELOs 6.3-6.5 but the intent is not clear based on the introduction. Without a strong financial management role the PSM cannot execute the functions described in the earlier TLOs. (B. Houts) • ELO 6.5: Evaluate affordability issues and their impact on financial planning and management . • Comment: What does "planning and management" refer to specifically? In terms of their key financial management responsibilities within the annual POM process, PSMs should understand, defend and otherwise contribute to programming, budgeting and perhaps execution decisions. (“S3” MR staff) • TLO 7.0: Describe the role of contracting and contracting management in the design, development and execution of the Product Support Plan. • Comment: It is not a Product Support Plan, it should be either the Product Support Strategy or LCSP. (B. Houts)

  6. Comments • TLO 8.0: Explain PSM’s roles related to production of system Product Support Package (PSP), Independent Logistics Assessments (ILAs), operational testing, and fielding/deployment. • Comment: TLO 8 in several places. Recommend taking the ILA reference out of this section and moving it into section 1.0 (e.g. general management functions). ILAs are important even before PSMs start acquiring the Product Support Package. (B. Houts) • TLO 9.0: Describe the role of the PSM in Sustaining Engineering including the technical tasks required to ensure the continued operation and maintenance of a system with managed risk. • Comment: Change “maintenance” to “sustainment.” There is more than just the maintenance aspects of the supply chain than can be considered.(B. Houts) • ELO 9.2: Describe PSM’s responsibilities for conducting post-IOC support reviews of product support and validating system product support strategy using Business Case Analysis. • Comment: Change “validating” to “refining” and delete “using Business Case Analysis.” There is a family of processes being used to refine the strategy and a smarter way to validate the strategy then (sic) performing another BCA. (B. Houts)

  7. Way Ahead • Comments received (and any subsequent suggestions received) will be addressed when reviewing TLO/ELO recommendations from the contractor. • LOG 365 short-term schedule: • Questions from vendor--due 10/17 • Govt. responses--due 10/29 • Vendor response to solicitation--due 11/1 • Technical evaluation report--due 11/16 • Task Order Award--11/21 • Kick Off Meeting--12/5 (tent.)

  8. Questions?

More Related