Best Examples Projects of Reduced Logistics Cost

Document Sample
Best Examples Projects of Reduced Logistics Cost Powered By Docstoc
					Project Concept                                                                                                                CASI 2006 Program

                                             2006 CASI Project Concept
                A project concept submitted to the OC-ALC/ENE for funding consideration in CASI Program.
                             Technology Insertion Lifecycle Execution (TILE)
Submitted by:                       Project Sponsor                                    Technical Lead (if known)
                            Name: Richard Heyman                                       Name: Edwin Kincaid
                            Organization: OSSG/KSM                                     Organization: OC-ALC/ENET
                            E-mail Address:                                            E-mail address:
                            Richard.heyman@wpafb.af.mil                                Edwin.kincaid@tinker.af.mil
                            Phone Number:                                              Phone Number: 405 736-2577


1.0    Background......................................................................................................................................... 1
2.0    Problem Statement .............................................................................................................................. 1
3.0    Anticipated Tasks /Methodology ........................................................................................................ 1
       Description ......................................................................................................................................... 1
       Anticipated Major Tasks .................................................................................................................... 2
4.0    Anticipated Schedule .......................................................................................................................... 2
5.0    Anticipated Deliverables .................................................................................................................... 3
6.0    Anticipated Benefits ........................................................................................................................... 3


1.0 Background
The OSSG/KSM community has implemented an Acquisition Lifecycle Execution (ALE) methodology
that is an integrated and collaborative infrastructure that leverages the integration capabilities of the IBM
Rational suite (lifecycle management), Proforma ProVision (process modeling and simulation) and Oracle
(database and workflow) applications to automate and support systems engineering, software engineering,
program management and acquisition disciplines. In addition to the integrated tooling, the ALE also
provides a robust process framework describing the roles, artifacts, workflows and activities for those
disciplines. The processes, artifacts and efforts involved in the ALE process is based on the Integrated
Defense Acquisition, Technology & Logistics Life Cycle Management Framework which is derived from
industry best practices and historical project data.


2.0 Problem Statement
The Technology Insertion Program (TIP) at OC-ALC has been established but needs to be more
documented in processes, workflows, rules/roles defined and established with System Engineering and
Program Management disciplines as well as industry best practices.


3.0 Anticipated Tasks/Methodology
      Description
A research effort needs to be performed in taking the best examples, templates and tools in the ALE and
establishing them into a Technology Insertion Process as began at OC-ALC. A review of ALE needs to be
performed and how best to incorporate ALE tools into the TIP in the development of a small scaled
Technology Insertion Lifecycle Execution (TILE) that can be utilized by the ENET technology program
managers.

The TILE can be described as a set of interconnected data repositories and workflows that provides the
backbone to support the complexities of systems engineering, software engineering, program management
and acquisition disciplines for the execution of the technology insertion processes. A global connectivity
avoids duplication and gives Program Managers the ability to more efficiently manage and oversee
programs and projects. Program Managers gain the benefit of near real-time views into program and project
artifacts.



                                                                        Page 1
Project Concept                                                                              CASI 2006 Program

                                  2006 CASI Project Concept
             A project concept submitted to the OC-ALC/ENE for funding consideration in CASI Program.
The TILE is flexible enough to support programs and projects that merely need access to individual
applications such as version control or need the power of full integration of all the applications such as
Unified Change Management.

The TILE applications provide a centralized oversight and guidance capability from the Program Manager
level down to the software engineering level. Programs and projects regardless of size or complexity will
not start from “scratch” through the use of standard templates, guides, checklists, forms and file structure.
Programs and projects created from the TILE enforce good engineering and management principles along
with consistency and traceability which yields better knowledge transfer from program to program and
project to project. Programs and projects that are in the TILE will also benefit from having engineering
support, product support and training integral to their existence in the TILE. The TILE pools software
licenses to provide better license utilization and access.

In addition, to provide direction to the RFP and subsequently to the proposal developer (the professor
and/or students), please define the requirement (if any) for the use of the particular task:
     o if a particular task/approach is to be followed and proposals that do not plan to use this task will
         not be considered, so state;
     o if a particular task is suggested but alternate tasks can be proposed, so state;
     o if the task is to be determined by the proposer (the professor and/or students), so state, e.g.,
         include a statement like the following:
          [ ] The anticipated task must be used in this study,
          [X ] alternative tasks may be proposed (by the professor and/or students), and will be
                   considered,
          [ ] best task is unknown at this time and is to be included in proposal (by the professor and/or
                   students).
        Anticipated Major Tasks

    o    Kick-off and other Meetings/Interactions with OSSG and OC-ALC Sponsor
    o    Development and Review of ALE Methodology and Data Requirements
    o    Data Gathering – Current Operations
             o Interviews
             o Observation
             o Use/Conversion of Existing Data
    o    Generation of Solution for insertion into TIP Processes
    o    Data Gathering for TILE development
             o Interviews
             o Observation
             o Use of Existing Data/Processes
             o Interface to Program Book
             o Construction and Evaluation of Prototypes
                       Development of Pilot TILE
                       Evaluation/Testing of Prototypes
    o    Analysis of TILE Pilot
    o    Development and Submission of Final Report and Briefing

4.0 Anticipated Schedule
Please provide the anticipated Project Period of Performance. For the 2006 CASI program, the following
schedules/periods of performance are allowed if you have no idea then so state and it probably can be
figured out by your expected tasks descriptions (you may wish to include this list and check all of the
periods of performance that you would accept, i.e.) (note: during the summer the professors can work on
the project fulltime but during the academic year they can only work part time):
     [ ] Execution and Completion of Project between June 1 and August 31, 2006.
     [X ] Execution and Completion of Project between June 1 and May 31, 2007
          [ ] Executed as a single project, or

                                                     Page 2
Project Concept                                                                              CASI 2006 Program

                                  2006 CASI Project Concept
             A project concept submitted to the OC-ALC/ENE for funding consideration in CASI Program.
         [ ] Executed in two or more phases with an intermediate set of deliverables and successful
              completion of the intermediate deliverables required before funding successive phase(s).
              NOTE: CASI research phases will normally have completion dates that correspond to the
              academic researcher’s semester schedule, i.e., August 15 or December 31.
    [ ] Execution and Completion of Project between August 15, 2006 and May 31, 2007
         [ ] Executed as a single project, or
         [ ] Executed in two or more phases with an intermediate set of deliverables and successful
              completion of the intermediate deliverables required before funding successive phase(s).
              NOTE: CASI research phases will normally have completion dates that correspond to the
              academic researcher’s semester schedule, i.e., August 15 or December 31.
    [ ] Execution as the first phase of a multi-year project. NOTE: Due to funding mechanisms, only the
         effort between June 1, 2006 and May 31, 2007 can be funded by the 2006 CASI program. The
         project must produce a set of intermediate deliverables at the end of the 2006 funding cycle and
         funding of successive phases/years is contingent upon funding availability, project priority, and
         performance.

5.0 Anticipated Deliverables
Monthly Reports
Draft TILE Design, Cost, infrastructure system requirements, interfaces, and support requirements
Final Report
Pilot TILE for ENET

6.0 Anticipated Benefits

       Reduced startup cost (time and schedule) by providing a standardized pre-existing
        platform, process and infrastructure.
       Greatly improved use of resources (hardware, people and licenses)
       Better Program Management, insight and predictability

.




                                                     Page 3

				
DOCUMENT INFO
Description: Best Examples Projects of Reduced Logistics Cost document sample