Document Organization Sample Clauses

Document Organization. The remainder of this report is organized as follows:
AutoNDA by SimpleDocs
Document Organization. This document is organized in a linear fashion corresponding with the timeline of the Design-Build procurement process. Appendix A – Projects of Division Interest (PoDI) Selection Process Appendix B – Design-Build Process Flow Chart Appendix C – AJR Guidance in Design-Build Projects Appendix D – FHWA and MoDOT Confidentiality Agreement Appendix E – FHWA Approval of Final Request for Proposal Letter Appendix F – MoDOT Request for Authorization Letter Appendix G - MoDOT Request for Concurrence in Award Letter Appendix H – FHWA Concur in Award Letter
Document Organization. This Component Specification documents the physical Polaris Architecture Components from the perspective of requirements and interfaces. The main body of this document is organized alphabetically by component or group name. For each component, a summary description including descriptions of the subfunctions that have been allocated to each component is provided. For each group, a corresponding list of components contained by the group is provided to point the reader to the correct sections. Appendix A describes the requirements that have been allocated to each component. Appendices B and C describe all the input and output data flows associated with each component.
Document Organization. Section 1 provides an introduction to ASF and how to navigate this document. • Section 2 provides a high-level overview of the ASF file format organization. • Sections 3 and 4 define the various objects that comprise the ASF Header Object. • Section 5 describes the organization of the ASF Data Object. • Section 6 documents the internals of the ASF top-level index objects. • Section 7 documents various features of ASF and how to use them. • Section 8 details how to create content that is compatible with many existing ASF reading implementations; this concept is referred to as “content reach.” • Section 9 lists and describes standard ASF media types. • Section 10 contains a list of the ASF GUIDs used throughout this document. • Section 11 contains detailed information for specific codec data in ASF.
Document Organization. ‌ This IS/ND is organized as follows:
Document Organization. This technical memorandum consists of 10 chapters and an attachment. Following this chapter on methodology is Chapter 3, which briefly describes the additional public outreach and public involvement activities that have occurred since the publication of the Draft EIS in March 2004. Chapter 4 provides a detailed description of social resources of the project study area, including the expanded area. Potential operational and construction effects (both adverse and beneficial) of the Tunnel and Elevated Structure Alternatives on social resources are assessed in Chapters 5 and 6, respectively. Secondary and cumulative effects of the two alternatives are discussed in Chapter 7. Operational and construction mitigation measures are recommended in Chapters 8 and 9. Chapter 10 lists new references consulted for this technical memorandum. Attachment A is a series of updated street maps of the project study area and beyond.
Document Organization. The information in the sections below combine the content from the Alaska Health Information Technology (HIT) Strategic Plan (Master HIT Strategic Plan vNov2010.doc), the Alaska HIT Operations Plan (Master HIT Operations Plan vNov2010.doc) and the Alaska HIT Strategic Plan Addendum (HIE 2011 State Plan Addendum v 1.5) in the domain specific sections as well as the planning sections. The Landscape information from the strategic plan is not updated nor included in this document. The requirements outlined in the PIN to document changes in strategy are included in the narrative of each domain in a section labeled “2012 Update.” The requirements prescribed in the PIN to describe the current PIN Priority Strategies are included in Section 8. The PIN requirements to present the Sustainability Plan are addressed in Section 9. The table for tracking progress on key meaningful use HIE capabilities in their state and setting annual goals is included in Section 10. The description of the approach to assess the Privacy and Security Framework, identified Gaps and plans to address the gaps are included in Section 11. The description of the plans to evaluate the HIE Operations, the Lab Survey conducted in December 2011 and the Pharmacy Survey conducted in January 2011 are included in Section 13 and related appendices. 2 CHANGES TO HIE STRATEGY‌ This section includes both a table and narrative. The table contains only changes; the narrative contains a description of the previous and current strategies as well as the changes. This section combines the previous three documents into this one plan.
AutoNDA by SimpleDocs
Document Organization. This document is organized into seven sections, two appendices, and an acronym list.
Document Organization. This document is organized into six major sections and one appendix. Section 1 is the Introduction: It defines the purpose and scope of this document, the organization of this document, and a list of applicable documents. Section 2 is the system overview for Pacor-A and OPUS and a listing of the responsible organizations. Section 3 provides a description of the products delivered to OPUS by Pacor-A. Section 4 provides a description of the data transmission between Pacor-A and OPUS. Section 5 provides a description of the data accountability function. Section 6 defines the points of contacts for Pacor-A and OPUS. Appendix A provides abbreviations and acronyms.
Document Organization. This document is organized in a linear fashion corresponding with the timeline of the Design Build procurement process.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!