Sample Book Document – Unfortunately, this book cannot be printed from OpenBook. If you need to print pages from this book, we recommend downloading it in PDF format.
For more information about this book, to purchase it in print or to download it as a free PDF, visit /10766.
Sample Book Document
Below is the uncorrected machine-readable text of this chapter, our own search engines and external systems designed to provide the richest, most searchable chapter-representative text of each book. Since this is unedited material, consider the following text a useful but insufficient proxy for the book’s official pages.
R Bookdownplus Textbook
PURPOSE OF THE IT MASTER PLAN The purpose of the IT Master Plan is to assess the state of the existing system and reflect its applicability to the Airport Master Plan. The IT Master Plan aligns all of the IT department’s goals and includes plans to support the airport’s goals and keep the IT infrastructure up to date. Outline and Contents 1. Executive Summary A high-level executive summary is designed to give senior executives a quick read of one or two pages of the entire document. 2. Terms and Abbreviations Lists the terms and abbreviations used in the IT master plan and provides their definitions. 3. Methodology describes the methodology used to construct the IT master plan. 4. Evaluation of existing systems. An assessment of each stand-alone system and its readiness to meet the airport’s needs over the next 4-8 years. Verifies system operability, compliance with new and evolving requirements, compliance with standards (especially new ones), and ability to support the airport master plan. System architecture reflects the layers presented in the section, from more physical to more software. The International Organization for Standardization (ISO) Open Systems Interconnection (OSI) model and parallel systems organization in this example. 4.1 Physical infrastructure defines the conditions for telecommunication rooms and cable infrastructure and includes: • Building premises, including server and telecommunication cabinets. ⢠Cable infrastructure including copper and fiber optic cables. 59 APPENDIX Scheme of documents
4.2 The network architecture describes the current state of the wired and wireless networks at the airport or managed by the airport authority. • Local network topology. • Global network topology. • Wireless networks. • Addressing, virtual local area networks (VLANs) and routing. Security including firewalls, remote access, etc. ⢠Network administration and operation. 4.3 Applied systems • Airport operational systems. ⢠Passenger handling systems. ⢠Business, Finance and Human Resources. ⢠Security systems. ⢠Basic office systems. • Building systems. 4.4 Interoperability and IT management systems The lower levels of the model document the current state of systems designed to provide interoperability between other systems. Includes systems management tools and integration tools. 5. Management defines the existing staff organization, IT department charter, project management methods, IT guidelines and budgets. It may be appropriate to include a 360-degree assessment of the IT department based on stakeholder interviews. 6. Business Models Describe any tenant business models, pricing, rates, etc., as well as cost allocation schemes and work calculation methods in the schemes. 7. Benchmarking provides benchmarks for comparable airports, including system types and numbers, staffing and organization, and capital and operating budgets. It is useful to include key airport comparison metrics such as passenger numbers, airport arrivals and/or traffic composition. 8. The technology plan addresses the key evolutionary changes required to maintain the current IT environment that meets the needs of the airport and its tenants and passengers. All deficiencies identified in the existing conditions must be eliminated. It is useful to organize technology planning into project-sized initiatives that are small enough to be funded and completed in one fiscal year, allowing rapid development of system definitions, CONOPs, and value propositions. 9. The transition and action plan prioritizes the recommendations from the previous sections and organizes them into a roadmap with recommended funding, presents an annual capital budget, and includes a gap analysis that summarizes existing system and technology gaps. to plan 10. Management and staff recommendations in light of the newly created technology plan explain how management should adapt to the implementation of these changes. May include recommendations for personnel reorganization, redeployment and/or retraining; business model changes; Changes in IT principles; evaluation of outsourcing alternatives; and a 5-year forecast O&M budget. 60 Information Technology Systems at Airports Primer
Operational goal concept Used to ensure consensus among users, administrators, and developers. Concept Operational Document Describes the effort required to maintain the new system after deployment. It should briefly describe system and user expectations, the new system, operating environment, operating scenarios, support environment, and implications for other systems and organizations. The target audience includes both technical and non-technical personnel. Scheme 1. The scope includes the title and overview of the new system. 2. Terms and Abbreviations List of terms and definitions of abbreviations used in the document. 3. Applicable Documents Lists by title any documents that are referenced or that apply to the system. 4. Current system or situation An analysis of the current system’s capabilities and limitations and the motivation for the new system. Describes the current user and support environment. 5. Description and justification of the new system Describes the characteristics, capabilities and interfaces of the new system, summarizes the benefits to be achieved and provides details of the justification, such as the operations, objectives and limitations of the existing systems. 6. Concept of the new system 6.1. A description of the new system, which includes: • The operating environment. • Main components of the system. • Interfaces and data flows to other systems. • New system features or functions. ⢠Data flows. • Performance • Quality characteristics (reliability, accuracy, flexibility, availability). • Safety/security requirements. 6.2 Operating policies and procedures Hours of operation, staffing restrictions, equipment restrictions, space restrictions and procedures such as standard, non-working, maintenance, emergency and backup. 6.3 Organizational structure 6.3.1. System users identify the users of the system and how they interact with the system, the organizational structure, and the skill level required. 6.3.2. Support Organization Defines the support organization, facilities and equipment, management concepts, and delivery methodology. 7. Work scenarios. A step-by-step description of how the new system should and should not work in various situations. Each scenario describes a specific sequence of Appendix A 61 actions
Describes the functions of a system and its interaction with users and other systems and includes events, actions, inputs, and data. 8. Expected Effects Describe the operational implications of the new system from the user’s perspective, allowing the affected organizations to prepare for the changes that the implementation of the system will bring. Purpose of System Definition A system definition is a high-level requirements document that describes the need for a new feature. It is the first attempt to define the scope of the system, it serves as a starting point for defining the requirements (which will be detailed later in the system specification), and should be written by both users and technical staff to understand it. The system definition may refer to business studies and feasibility studies. Outline and Contents 1. The area identifies the required system by name, briefly describes the required application or product, and indicates whether the system is an upgrade or modification to an existing system. 2. Terms and abbreviations List of terms and abbreviations used in the document and their definitions. 3. Applicable Documents Lists by title any documents referenced or applied in the system definition. 4. The business environment describes the necessary sphere of activity and relations with other spheres of activity. 5. A system specification describes the required system or capabilities in terms of deficiencies in existing systems or required new functionality. 5.1 Functional capabilities describe the functional needs of applications and interfaces with other systems. 5.2 Operational capacity refers to operational requirements and objectives such as system capacity and throughput. 5.3 Maintenance and Logistics Support describes the support elements necessary to achieve effective operations, such as maintenance, supplies, support personnel, equipment, and training. 5.4 Other Considerations Describes other issues that may affect the system, including disaster planning, environmental impacts, and security requirements. 6. Proposed Solutions Describes the proposed solution, acquisition strategy, system results, testing strategy, and alternatives that may be followed to meet the requirements, such as upgrading the existing system. 7. Planning Discuss the desired capacity availability schedule. 62 Information Technology Systems at Airports Primer
How To Format A Book Manuscript
8. Cost estimation and financing provides a general estimate of the total costs of implementing the system and identifies the reference resources used. Describes current assumptions about operation and maintenance costs and discusses possible sources of funding for the new system. Purpose of the Value Proposition The value proposition presents the financial and non-financial arguments for why the project should be funded and completed, describes the measurable benefits after the project is completed, and describes the stakeholders. Scheme and content 1. Description of the system
Project proposal sample document, business process sample document, sample nda document, sample loan document, sample rfp document, briefing document sample, sample workflow document, sample process document, lease document sample, sample it strategy document, sample onboarding document, sample process flow document
Post a Comment for "Sample Book Document"