Integrated Program Plan

By Clifford Grant,2014-06-17 08:32
22 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.


ISP Template August 2004

     EXHIBIT 300



    (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


    ISP Template August 2004

    Table of Contents


    1.1 Mission Need

    1.2 Status


    2.1 Description

    2.2 Objectives and Capabilities

    2.3 Key Elements

    2.4 Deliverables




    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.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





    19.1 Physical Security

    19.2 Information Security

    19.3 Personnel Security

    19.4 Privacy


ISP Template August 2004


    12.1 Test Strategy Overview

    12.2 System Test

    12.3 Independent Operational Test and Evaluation

    12.4 Field Familiarization Test




    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.1 Integration With Other NAS and Non-NAS Elements

    16.2 Software Integration

    16.3 Spectrum Management

    16.4 Standardization


    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






ISP Template August 2004



    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.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


    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.


    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

    how the SRM complies with FAA Order 8040.4, Safety Risk Management and how you intend to implement the SRM

    program in accordance with the ATO Safety Service Unit’s Safety Management System (SMS) and the System Safety Management Program (SSMP). Identify staffing issues and how you intend to develop and direct your own

    Integrated Safety Plan and the contractor’s System Safety Program Plan. Identify key milestones of each. Refer to 7 system safety management program guidance in FAST and the Safety Management System (SMS) Manual to find

    out the details on what must be done.

ISP Template August 2004


    Provide the information required in the following sub-sections for each contract you will let to implement this

    program. Identify what streamlining actions will be used (e.g., release of draft information to industry for comment,

    use of oral proposals, pre-qualification of contractors, etc.).

    6.1 Sources. Identify prospective sources that can satisfy the need as identified by market research and other means. State whether a Qualified Bidders List will be used. Discuss how small and small disadvantaged businesses

    will participate.

    6.2 Source Selection. Identify the source selection official. Define the primary source selection factors that will be used. For software-intensive procurements, the results of evaluations using Capability Maturity Model instruments

    can be used as a source selection factor to ensure the successful offeror has mature software acquisition,

    development, and maintenance processes in place. State whether past performance and vendor process capability

    and process improvement will be used as selection criteria. State whether open architecture and modular design

    will be required or scored during source selection to facilitate modernization and supportability of fielded


    6.3 Competition. Identify whether competition will be sought, and if so, how it will be achieved. FAA policy encourages competition in every phase of product lifecycle to encourage innovation and control costs. For

    developmental programs, state whether you intend to award multiple competitive contracts as a means for reducing

    risk and selecting a most advantageous design.

    6.4 Contract Type. Identify the contract type you will use. OMB requires you to employ a procurement strategy

    that mitigates risk to the Government, accommodates Section 508 as needed, and uses performance-based contracts

    and statements of work. If you do not use performance-based, fixed-price contracts, clearly define the reasons that

    prompted use of other types of contracts. Discuss whether cost-sharing or incentive contracts will be used to

    achieve key program goals such as performance, quality, and cost and schedule control.

    6.5 Government-Furnished Property and Information. Identify what property or information the FAA must

    provide to the contractor.

    6.6 Warranties and Data Rights. State whether warranties or data rights will be obtained.


    Define how benefits and performance in the Exhibit 300 Program Baseline will be tracked and verified during the

    solution implementation and in-service management of this investment program. Discuss your plans for conducting

    post implementation reviews and operational evaluations and factoring resultant data into service area analysis

    and reporting at service area reviews. When the realization of benefits is outside the control of the service

    organization (e.g., changes to regulations, actions by the airlines), describe how you will ensure necessary actions

    are taken (e.g., a responsible person from AVR could be made a member of the implementation team).


    Define how systems engineering will be applied to this investment program. For example, explain how program

    8 requirements will be allocated to different solution providers and how they will be transformed into specifications

    for prime contractor(s). Explain how value engineering; supportability, reliability, and maintenance engineering;

    and specialty engineering such as electromagnetic interference and compatibility will be factored into the solution.

ISP Template August 2004


    Define how the configuration of hardware, software, data documentation, interfaces, and tools will be managed

    throughout their lifecycle. This includes the establishment, monitoring, and administration of change control

    procedures, establishment and administration of change control boards, and formal audits to compare product to

    documentation. The approach will vary based on the product to be procured (e.g., commercial, non-developmental,

    or development). Typically, the following configuration baselines should be established and managed: a functional

    baseline of decomposed requirements, an allocated baseline of configuration items, and a product baseline.

    Software configuration management should cover source code, source-code-level programming instructions of

    programmable firmware devices, test procedures, and test cases. Identify tools that will be used to accomplish

    configuration management. Refer to configuration management guidance in FAST to determine what must be done.

    10 SECURITY AND PRIVACY 10.1 Physical Security. Explain how requirements will be satisfied related to security of the physical plant both for end-state operations and during transition to the new capability.

    10.2 Information Security. OMB requires information technology security planning to proceed in parallel with solution planning. All information technology investments must have an up-to-date security plan that meets OMB

    policy and NIST guidelines and must be fully certified and accredited before becoming operational. Program

    planning must ensure requests for IT security funding is adequate. This includes a security characterization per

    NIST FIPS PUB 199 for confidentiality, integrity, and availability. You must identify: (1) current information

    security costs; (2) IT security performance gaps; and (3) show how requested funding will close performance gaps.

    Refer to information system security guidance in FAST for a complete discussion of what must be done.

With the above in mind, define your strategy for obtaining information security throughout the lifecycle of this

    investment program.

    10.3 Personnel Security. Explain how requirements will be satisfied related to personnel, security clearances, security training, and access control.

    10.4 Privacy. OMB requires agency’s to comply with Section 208 of the E-government Act. If applicable, your

    planning must include a privacy impact assessment that evaluates privacy risks, alternatives, and protective

    measures at each stage of the information lifecycle. 11 HARDWARE AND SOFTWARE DEVELOPMENT

    Define the strategy for the design, development, fabrication, assembly, and check out of hardware and software

    configuration items. Typically these activities are performed by the contractor and managed by the service

    organization. Define contractor and FAA roles and responsibilities. Use the FAA Standard Work Breakdown

    Structure as a guide.


    12.1 Test Strategy Overview. Define the test strategy for each program stage (e.g., capability demonstration, prototype development, full-scale development, production, deployment, as appropriate). If this program is a

    commercial or non-developmental acquisition, describe the use of commercial product testing or historical usage 9 data in place of government testing. Identify any completed testing including operational capability tests and

    demonstrations. Identify any other test streamlining approaches that will be used (e.g., Operational Capability

    ISP Template August 2004 Demonstration as an element of source selection). Explain why this test strategy is appropriate for the risk

    associated with the products or capability to be provided. Identify critical operational issues and explain how the

    test strategy will mitigate risk. State whether a Verification Requirements Traceability Matrix will be used to trace

    critical performance parameters and critical operational issues from the program requirements in Exhibit 300

    Attachment 1 to test activities throughout solution implementation. Identify whether the Chief Operating Officer

    designated the program for Independent Operational Test & Evaluation, thereby requiring an Independent

    Operational Test Readiness Declaration.

    12.2 System Test. Describe the system test strategy for this program. If developmental testing is required, define

    the objectives of developmental testing. Identify criteria for starting operational testing. Explain how Critical

    Operational Issues will be used to establish test objectives for each stage. Differentiate between contractor testing

    and FAA testing. Explain how you intend to obtain needed test plans, procedures, and reports; as ell as test

    personnel, tools, training, and other test resources for both government and contractor personnel. Identify whether

    independent software verification and validation will be used. If so, explain how it will be implemented and


    12.3 Independent Operational Test & Evaluation (IOT&E). If the Chief Operating Officer designates the

    program for IOT&E, the ATO Test Team will develop the IOT&E test strategy section of this attachment. Describe

    the IOT&E approach; how Critical Operational Issues will be resolved; and prerequisites for starting IOT&E.

    Identify the criteria for selecting the site for IOT&E. Identify how all plans, procedures, resources, and reports will be developed.

    12.4 Field Familiarization Test. Explain how Critical Operational Issues will be used to establish test

    objectives for field familiarization testing. Explain how you intend to identify, plan, and execute tests to accomplish these objectives. Explain how you intend to obtain needed test plans, procedures, and reports, as well as test

    personnel, tools, training, and other test resources for both government and contractor personnel.


    Define the strategy for taking a developmental product to full production including production process

    development and documentation. Include in the strategy how testing will be conducted on each end item to verify

    conformance with applicable specifications and absence of manufacturing defects. Define contractor and FAA

    roles and responsibilities.


    Define the strategy for acquiring the physical space needed to accommodate systems, auxiliary equipment, and

    personnel both for end-state operations and during transition to the new capability. Acquisition times vary

    depending on need and complexity. Coordinate with responsible acquiring organizations at the earliest possible

    time. Include architectural, civil, electrical, mechanical, and industrial engineering, as well as construction at

    each site. Include construction and modification of research test facilities and the supporting infrastructure.

    See physical infrastructure for related activities such as space, lighting, heating, cooling, telecommunications,

    shielding, bonding, and lightning protection.


    Physical integration concerns the integration of a solution into the physical environment. Define how physical

    integration will be achieved for each element listed below when applicable to your investment program.

Report this document

For any questions or suggestions please email