DOC

Integrated Program Plan

By Clifford Grant,2014-06-17 08:32
21 views 0
Integrated Program Plan ...

ISP Template August 2004

    Template for Attachment 3 of the Exhibit 300

    Implementation Strategy and Planning

    (Revised 08/2004)

    This template guides the service organization when preparing Attachment 3: Implementation

    Strategy and Planning of the Exhibit 300. Part 1 of the attachment defines the overall

    implementation strategy the service organization will execute to achieve performance and benefits

    within the cost and schedule specified in the Exhibit 300 Program Baseline. Part 2 is the detailed

    project management work plan for the current phase of the program. Italicized text in the template

    identifies issues and questions you should consider as you plan your strategy for implementing and

    supporting the investment over its full lifecycle. Un-italicized text defines the format and structure

    (e.g., title page, table of contents, section heads and numbers) of the attachment. Not all sections and

    questions apply to every investment program. Use the information in the template to tailor your

    implementation strategy and planning for your investment program. Refer to the FAA Standard

    Work Breakdown Structure for additional information concerning activities that may need to be

    planned and implemented when developing the attachment.

    1

ISP Template August 2004

     EXHIBIT 300

    ATTACHMENT 3

    IMPLEMENTATION STRATEGY AND PLANNING

    (Program Name)

    Version #

    Approved by: Signature Date: Vice President or Director of the performing service organization Approved by: Signature Date: Vice President or Director of the operating service organization(s) (if different from the performing service organization)

    Submitted by: Signature Date: Appropriate preparing organization

    Service Organization Focal Point Operating Organization Focal Point

    Name Name

    Code and organization Code and organization

    Phone Number Phone Number

    FAX Number FAX Number

    Email Address Email Address

    Federal Aviation Administration

    800 Independence Avenue

    Washington, D.C. 20591

    2

    ISP Template August 2004

    Table of Contents

    PART I LIFECYCLE MANAGEMENT STRATEGY 1 BACKGROUND

    1.1 Mission Need

    1.2 Status

    2 OVERVIEW

    2.1 Description

    2.2 Objectives and Capabilities

    2.3 Key Elements

    2.4 Deliverables

    3 INTEGRATED PROGRAM SCHEDULE

    4 PROGRAM STRATEGY

    5 MANAGEMENT STRATEGY

    5.1 Management Team

    5.2 Program Control and Quality Assurance

    5.3 Contract Management

    5.4 Requirements Management

    5.5 System Safety Management

    6 PROCUREMENT STRATEGY

    6.1 Sources

    6.2 Source Selection

    6.3 Competition

    6.4 Contract Type

    6.5 Government-Furnished Property and Information

    6.6 Warranties and Data Rights

    7 BENEFITS AND PERFORMANCE

    8 SYSEMS ENGINEERING

    9 CONFIGURATION MANAGEMENT

    10 19 SECURITY AND PRIVACY

    19.1 Physical Security

    19.2 Information Security

    19.3 Personnel Security

    19.4 Privacy

    11 HARDWARE AND SOFTWARE DEVELOPMENT 3

ISP Template August 2004

    12 TEST AND EVALUATION

    12.1 Test Strategy Overview

    12.2 System Test

    12.3 Independent Operational Test and Evaluation

    12.4 Field Familiarization Test

    13 PRODUCTION

    14 FACILITIES

    15 PHYSICAL INTEGRATION

    15.1 Real Property

    15.2 Environmental Requirements

    15.3 Energy Conservation

    15.4 Heating, Ventilation, and Air Conditioning

    15.5 Grounding, Bonding, Shielding, and Lightning Protection

    15.6 Cables

    15.7 Hazardous Materials

    15.8 Power Systems and Commercial Power

    15.9 Telecommunications

    15.10 Special Considerations

    16 FUNCTIONAL INTEGRATION

    16.1 Integration With Other NAS and Non-NAS Elements

    16.2 Software Integration

    16.3 Spectrum Management

    16.4 Standardization

    17 HUMAN INTEGRATION

    17.1 Human / Product Integration

    17.2 Employee Health and Safety

    17.3 Specialized Skills and Capabilities 18 INTEGRATED LOGISTICS SUPPORT

    18.1 Staffing

    18.2 Supply Support

    18.3 Support Facilities and Equipment

    18.4 Technical Data

    18.5 Training and Training Support

    18.6 First and Second Level Repair 4

    18.7 Packaging, Handling, Storage, and Transportation

ISP Template August 2004

    19 DEPLOYMENT

    20 IN-SERVICE MANAGEMENT

    PART II PROGRAM ACTION PLAN

APPENDIX REPRESENTATIVE WORK ACTIVITIES AND PROGRAM EVENTS

    5

ISP Template August 2004

    PART I LIFECYCLE MANAGEMENT STRATEGY

1 BACKGROUND

    1.1 Mission Need. Cite the service-level mission need statement and other high-level agency document(s) (e.g., FAA Strategic Plan) that are the basis for this program. Briefly characterize the mission or service need this program is intended to satisfy. 1.2 Status. State whether this is the initial implementations strategy and planning attachment or a revision. If

    this is a revision, briefly characterize how the program has changed. Cite any top-level management direction since

    the last approval that influences this revision

    2 OVERVIEW

    2.1 Description. Briefly describe this investment program and its status. Describe how it relates to the overall NAS or Enterprise Architecture and other interfacing systems or products.

    2.2 Objectives and Capabilities. Summarize primary objectives and capabilities this program is intended to

    provide.

    2.3 Key Elements. Identify key elements of this program and briefly explain how they shape your implementation strategy (e.g., development of hardware or software, procurement of systems or equipment,

    modification or construction of facilities, changes in the physical infrastructure, development of functional

    interfaces, procurement of installation or support services).

    2.4 Deliverables. Identify and describe briefly the key outputs of this investment.

    3 INTEGRATED PROGRAM SCHEDULE

    Display program schedule by fiscal year for key program events and milestone. Be consistent with the Exhibit 300

    Program Baseline. Appendix 1 contains representative planning elements and events that may be applicable. So

    does the FAA Standard Work Breakdown Structure. Tailor the integrated schedule to your program.

    4 PROGRAM STRATEGY Describe the overall strategy for obtaining the capability specified in the Exhibit 300 Program Baseline and

    Attachment 1: Program Requirements. Define the strategy for each key element of the program identified in Section

    2.3 Key Elements (e.g., systems/equipment/software elements, facility elements, infrastructure elements, services

    elements, etc.). For example, developmental activity is planned for hardware/software versus COTS/NDI equipment;

    new facility will be designed and constructed versus modification of existing facilities, degree to which the physical

    infrastructure (e.g., roads, telecommunications, power, space, HVAC) will be modified. Include within your

    discussion your strategy for the following, as applicable: the strategy for transforming performance requirements

    into specifications and a solution configuration; analysis, design, test, and integration of the solution; value

    engineering; supportability, maintainability, and reliability engineering; hardware and software design,

    development, and test; production engineering; and full-scale production. Refer to Section 3 of the FAA Standard 6

    Work Breakdown Structure for complete planning details related to solution development.

ISP Template August 2004

    5 MANAGEMENT STRATEGY 5.1 Management Team.

    Use table format to define the roles and responsibilities of key individuals and organizations that will implement

    this program. Include all relevant functions and disciplines such as program and contract management; facility

    design, modification, and construction; systems, human factors, and telecommunications engineering; test and

    evaluation; in-service operations and support; physical and functional integration; fielding and deployment;

    configuration management; quality assurance; and security. Include the name, office symbol, telephone number,

    and email address of team members. Identify points of contact with other programs and organizations that

    interface with or will have an impact on your program. Be sure key participants are involved in preparing this plan

    so that support will be there when needed.

    5.2 Program Control and Quality Assurance.

    Explain how program activity will be planned, measured, reported, evaluated, and revised. Explain how program

    activity will be coordinated and reported (e.g., monthly status reviews, quarterly regional reviews, annual service

    area reviews).

    Identify quality assurance controls that will be applied to both contractor and government activity (e.g., contractor

    status reporting, performance management, in-plant Quality Reliability Officers, peer reviews, independent

    verification and validation). If government standards are invoked, explain why they are required in lieu of

    commercial standards. Identify any automated tools that will be employed to manage and communicate quality

    assurance actions and activities. Define how the quality of a vendor's software processes will be monitored when

    those processes are evaluated and scored as a part of source selection.

    5.3 Contract Management. Explain how prime and support contractors will be managed. Include contract administration and contractor process capability evaluation and appraisal. Identify what kind of

    cost/schedule/performance tracking will be used to monitor contractor status and progress. OMB requires use of

    an Earned Value Management System (EVMS) that meets ANSI/EIA Standard 748, for both government and

    contractor costs, for those parts of the total investment that require development (e.g., prototypes and testing in the

    planning phase and development efforts in the acquisition phase). For investments in the operation or steady-state

    phase, describe how contractor costs will be audited during performance and at completion.

    5.4 Requirements Management. Describe how requirements will be baselined and controlled throughout the life

    of this program. Explain how site-specific requirements will be determined, controlled, and managed. Explain how

    data will be gathered and assessed to ensure requirements are being met during solution implementation in support

    of annual service area reviews. 5.5 System Safety Management. Explain your strategy for ensuring an appropriate system safety program will be

    implemented by both the service organization and system contractor(s). Identify the target level of safety for the

    service, system, or program and explain how it was derived. Identify the risk acceptance and safety risk

    management documentation approval process as planned or practiced by the program. Describe the Safety Risk

    Management (SRM) program and how it will be used to identify, assesses, mitigate, and track hazards. Explain