Information Technology Systems at Airports--A Primer (2012) / Chapter Skim
Currently Skimming:
Appendix A - Example Document Outlines
Appendix A - Example Document Outlines
Pages 59-69
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 59... ...
4.1 Physical Infrastructure Identifies the conditions of the telecommunications rooms and cabling infrastructure and includes: • Building facilities, including server room and telecommunications closets. • Cabling infrastructure, including copper and fiber-optic.
|
From page 60... ...
Should offer a cure for all deficiencies identified in the existing conditions. It is helpful to organize the technology plan into project-sized initiatives that are small enough to be funded and completed in a single fiscal year, which allows for systems definitions, CONOP, and value propositions to be quickly developed.
|
From page 61... ...
The intended audience includes technical and nontechnical personnel. Outline 1.
|
From page 62... ...
5.3 Service and Logistical Support Describes support elements needed to achieve effective operations, such as maintenance, supply, support personnel, facilities, and training. 5.4 Other Considerations Describes other issues that could have an impact on the system, including disaster planning, environmental impacts, and security requirements.
|
From page 63... ...
Also describes ongoing operational and maintenance cost assumptions and discusses potential funding sources for the new system. Value Proposition Purpose The value proposition presents economic and non-economic arguments about why the project should be funded and completed, defines benefits that will be measurable after the project is completed, and describes stakeholders.
|
From page 64... ...
Note: This outline for a project charter has been aligned with the Project Management Institute's A Guide to the Project Management Body of Knowledge (PMBOK Guide) , Fourth Edition, published 2008 (Project Management Institute, 2008)
|
From page 65... ...
Project Management Plan Purpose The project management plan is a management document that defines the overall plan for the project. It should describe the tasks, schedule, resources, and costs for completing the project in accordance with project objectives.
|
From page 66... ...
Project Reviews Describes formal and informal communications between the project manager and all organizations associated with the project, including stakeholders and future support personnel. Specifies the frequency of project reviews and personnel who should attend.
|
From page 67... ...
System Specification Purpose The system specification is a requirements document that establishes the functional, performance, design, and testing requirements of a system. Outline 1.
|
From page 68... ...
4.5. Documentation Specifies documentation required for the system, including specifications, drawings, technical manuals, acceptance test plan, user's manual, operations manual, quality assurance plan, and configuration management plan.
|
From page 69... ...
4. Trouble Reporting Procedures Describes how the subscriber should notify the service provider of problems, how the service provider will track and provide status on corrective actions, and how close-out procedures are handled.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.