Att 18G - IMP IMS Instructions.pdf

FA8621-12-R-6259

Attachment 18G

17 Jan 2012

Integrated Master Plan (IMP) Instructions/Formatting

The offeror shall provide an IMP as part of their proposal submittal to identify key events, tasks to be accomplished, and a description of the entrance and exit criteria for those events.

The offeror shall build an event-based IMP for the F-15 TDAS system that provides the required capability to support F-15 TDAS deliveries using the DoD Integrated Master Plan and

Integrated Master Schedule Preparation and User Guide, Ver 0.9, 21 Oct 2005 as a guide

(located in the Bidder’s Library).

The IMP must correlate to the F-15 TDAS IMS, Model Contract, Earned Value

Management System (EVMS), offeror's organizational structure, and specification hierarchy.

The offeror shall identify, based on the CWBS, a hierarchy of key program events across all functions and areas of interest that defines the F-15 TDAS Program. The offeror shall ensure that key events in software development, systems engineering, test and evaluation, and integrated risk management are included. Each key event shall have specific entrance and exit criteria. The

IMP shall consist of two sections, as described below.

IMP Section 1: Introduction. The offeror shall include any assumptions and guidelines for application of the IMP. This section should include a dictionary that contains definitions of the selected events and action words used within the accomplishment criteria in Section 2 of the

IMP. In addition, the offeror should include a description of the purpose, expected results and entrance and closure criteria for each event in Section 2.

IMP Section 2: Events/Accomplishments/Criteria. The offeror shall define the (1) events, (2) accomplishments, and (3) entrance/exit criteria.

Integrated Master Schedule (IMS) Instructions/Formatting

The IMS is an integrated, time-phased schedule of program/project tasks. The IMS shall roll up to a summary level of no more than 100 activities. All Government-directed activities and milestones shall be represented within the schedule hierarchy. All activities that rely upon

Government actions or resources shall be clearly and explicitly identified. Focus primarily on the key processes, risk drivers and key milestones of the program. These include, but are not limited to, contract award, development reviews and milestones (e.g., PDR, CDR, Integration

Complete, and Contractor Testing Complete), etc. The activities and tasks included in the IMS should be sufficient to succinctly describe the successful execution of the F-15 TDAS program.

The IMS shall reflect key IMP events, accomplishments and entry/exit criteria. The offeror shall organize the IMS submission as follows:

Section 1 - Integrated Master Schedule Network and Data Listing.

This section includes the IMS. The offeror shall provide an IMS network schedule with a start date of the contract award currently scheduled for October 2013. The program IMS shall be submitted in Microsoft Project 98 or later format. All network schedule information shall be consistent with and directly traceable to the IMPs, PWS, and dates in the Contract Volume. The schedule information will be clearly identified.

The IMS network schedule shall clearly indicate the critical path (if there is more than one critical path, document why there are multiple paths). The IMS shall contain at least one unbroken critical path that reaches from Contract Award to the last activity. Text names for activities on the critical path shall be underlined and use bold, red font. All activities, with the exception of the first activity, should have at least one predecessor. There shall be no negative total slack in the IMS. Summary activities shall not be linked.

Purely routine tasks (e.g., program management, recurring CDRL submissions, and training or other routine, on-going processes) should be avoided in the IMS. However, to the extent there are specific activities within these categories that are significant to executing the program (e.g., a one-time CDRL submission), these activities could be appropriate for inclusion.

These types of activities shall be represented as milestones.

The IMS network schedule shall contain a sufficient number of activities to provide an understanding of the program. The offeror shall use a calendar consistent with its work schedule. Elapsed durations shall not be used in assigning durations to activities. Durations in the IMS shall be the most likely duration for an activity.

The offeror shall identify each software activity in the schedule by placing a "SW" designator in the Microsoft Project Text1 field. Each Computer Software Configuration Item

(CSCI) (developed, modified or purchased requiring development or modification) required to implement the offeror's technical solution shall be represented as a separate activity in the IMS.

The duration of the CSCI activities shall be based on the total time required to accomplish all phases of development/modification for that CSCI (e.g. requirements analysis, preliminary/detail design, code and unit test and CSC integration and test) and shall correspond to the dates submitted on parametric input sheets. Unmodified legacy CSCIs shall not be represented in the

IMS. Additionally, the IMS shall contain a milestone titled "SW Complete", which indicates the completion of all SW development, modification, integration and verification activities.

The offeror shall provide the schedule in tabular Gantt format containing the following data (if applicable) for each event, activity, task, and milestone in the IMS:

Unique ID (CWBS)

IMP Reference/Code (Text3 field)

Name

Start

Finish

Duration (most likely)

Total Slack

Predecessors

Successors

Constraint Type

Constraint Date

SW Designator (Text1 field)

CWBS (Text4 field)

PWS Reference (Text5 field)

Risk level (Text6 field for Moderate-to-High risk activities)

Integrated Risk Management Plan Reference (Text7) (to be populated after award)

Block (Text 10 field)

The IMS shall be constructed using only activities (summary and non-summary) and milestones. Schedule reserve shall not be represented as an activity in the schedule. Any activity with duration greater than 90 workdays should be divided into activities with smaller durations or justified in the narrative. The narrative should include descriptions of the sub activities that are included in any activity with a greater than 90 workday duration and the relationships among those sub tasks. DO NOT submit supplemental network schedule for these activities. Relationships with excessive lead or lag time should be avoided in the IMS submittal.

Any activity with lead/lag greater than 90 workdays should be broken down into activities with smaller durations or justified individually in the narrative.

The offeror shall let the logic determine the network and minimize the use of constraints.

Directed dates or any other conditions that would limit the ability of the Government to perform a SRA (such as Finish No Later Than (FNLT) or Start No Later Than (SNLT) constraints) shall be avoided altogether. Each constraint other than "ASAP" and/or directed dates shall be justified individually in the narrative. The offeror should avoid Finish to Finish or Start to Start relationships.

Section 2 - Schedule Rationale.

Section 2 includes narrative explanations of the durations, rationale, logic and environment of the proposed IMS, and IMS definitions.

The offeror shall provide ground rules and assumptions used to develop and understand the IMS.

Any unusual aspects of their proposed approach to the program shall also be described.

The offeror shall provide ground rules, assumptions and rationale for the assigned durations for all activities designated as moderate or high risk. The offeror shall describe how the duration was derived. If past history is cited as the primary methodology for deriving the duration, the offeror will cite the specific program which forms the basis for the duration.

The offeror shall identify risky activities and highlight them in the IMS. If any moderate to high risks activities are identified in the IMS, the offeror shall provide comments explaining the risks. The offeror shall provide as part of the schedule narrative, a tabular listing of all customized fields used to build the IMS. This listing shall include the IMS column title, the MS

Project field name and a brief explanation of what the field is used for. Similarly, the offeror should list and explain any customized filters provided as part of the IMS. The IMS is not included in the Technical Approach volume page counts.

The following Government definitions will apply to the IMS:

Milestone - A specific definable accomplishment in the program/project network, recognizable at a particular point in time. Milestones do not consume time or resources.

Activity - A task or measurable amount of work to complete a job or part of a project.

Duration - The length of time estimated to accomplish an activity during normal working hours.

Elapsed Duration - The amount of time needed to complete a task, based on a 24 hour day and a 7 day week, including holidays, weekends, and other non-working days.

Constraint - A limitation or restriction set on the start or finish of a task.

Finish-to-Start (FS) - An activity must finish before another can start

Start-to-Start (SS) - An activity depends on the start of another activity

Finish-to-Finish (FF) - One activity cannot finish until another activity finishes

Total Slack or Float - The amount of time a task can slip without affecting the project's finish date

Lead - The amount of time of the overlap between where a successor task begins and a predecessor task completes

Lag - The amount of time between the completion of one task and the start of its successor task

Critical Path -The series of tasks that must be completed on schedule for a project to finish on schedule. Activities along the critical path have zero slack/float. It should be easily distinguished on the report formats. Ideally the offeror will propose one Critical

Path.

Gantt Chart - A graphical display of program activities and key milestones that depict work activities in an integrated fashion. Represent activities by bars showing the length of time for each activity