1.2 Management of AIRPortal Data and Applications
The integrity of AIRPortal is directly related to the quality and consistency of the data it provides to end users, and data quality is a responsibility of all stakeholders working for MDOT MAA. Staff from the GIS and Engineering Technology Section (GETS) are involved with any MDOT MAA project that has a data deliverable. GETS has established highly coordinated and cooperative procedures for maintaining documents and spatial data on behalf of MDOT MAA. The success of AIRPortal and its ability to present reliable and up to date data to end users is predicated on the coordinated flow of information from MDOT MAA’s consultants to GETS to be published in AIRPortal.
GETS has the following objectives:
A. Create a consistent and uniform data management process that effectively ensures compliance with MDOT MAA’s BIM, CAD, GIS, and document management standards.
Each design project will establish a plan of action based on these guidelines to ensure that all data-related activities will comply with MDOT MAA’s standards. This will include methods to ensure compliance with existing feature class and layer definitions, geometry, and attribution; methods to establish new feature classes and layers when necessary; and a plan for submitting document deliverables that comply with naming conventions used within AIRPortal.
B. Establish and define roles and responsibilities of all participants, including MDOT MAA and its consultants.
The execution of the data management process will require coordination and cooperation from all participants. Therefore, GETS will participate in scoping meetings for tasks that involve a data deliverable to establish roles and responsibilities for each participant.
C. Establish and define guidelines for editing and updating the data inventory that are based upon validated business rules.
MDOT MAA’s BIM, CAD, and GIS standards will be the driver behind all spatial data maintenance activities, establishing the definitions for each feature class that is used to model the real world within the database. All contributors will consistently and uniformly apply the standards, with no alternative interpretations being undertaken without the express consent of MDOT MAA, and only after assessing all potential impacts that the change or alternative interpretation may have.
D. Establish and define effective and workable procedures and tools for sharing and exchanging data among participants.
Significant amounts of data will need to be exchanged between MDOT MAA and the design consultants, and steps will be taken to make this as fault-free as possible based on proven technologies. Several pre-conditions will be assumed:
1. Contributing consultants will have the ability to edit data based on one of the predefined editing scenarios established by MDOT MAA. These scenarios will leverage MDOT MAA’s current GIS and CAD architecture and represent proven practices within the geospatial industry.
2. Design consultants will establish a data exchange schedule with GETS based on the length and scope of the task. The exchange schedule will build in time for quality control and acceptance by GETS.
3. Contributing consultants will cooperate with database schema changes that may need to occur mid-task. It is reasonable to assume that at some point adjustments will be required to be made to the geodatabase schema as it matures and evolves operationally.
E. Establish a data review process for transparency.
Quality control procedures will be developed and provided to each consultant editing spatial data on behalf of MDOT MAA. These procedures will consist of automated and manual data checks to ensure data compliance with the MDOT MAA CAD and GIS Standards. Quality control of BIM data will be governed by BIM use cases within the MDOT MAA BIM Standard.
1.2.1 Roles & Responsibilities
A. GIS and Engineering Technology Section: Manage the flow of information in and out of AIRPortal. Responsibilities include:
1. Overall management of spatial data, documents, and applications at MDOT MAA
2. Fulfillment of any data requests that are not part of the self-service options available within AIRPortal
3. Management of the versioning and check out structure of the enterprise database
4. Updates to the baseline CAD templates and files available through AIRPortal
5. Performing all manual and automated quality control checks prior to reconciling and posting updates to the geodatabase version being published through AIRPortal
6. Manage editing projects to minimize or remove any overlap (minimize conflicts)
7. Maintain space allocation drawings, airfield sign and markings plans, vector and raster basemaps, and other spatial data
8. Perform quality control checks prior to accepting documents in AIRPortal for archiving purposes
B. MDOT MAA Project Managers: Oversee design and construction projects on behalf of MDOT MAA. Responsibilities include:
1. Ensure AIRPortal requirements are identified early for each project assignment
2. Coordination of data and documentation required under MDOT MAA’s Standards
3. Oversight of data deliverables to MDOT MAA from its consultants
C. Consultants: Perform work to MDOT MAA Standards and industry best practices. Responsibilities include:
1. Identification of AIRPortal impacts
2. Ensure project staff members have appropriate expertise for the subject matter and the technology being utilized
3. Processing of all updates to spatial data generated during the execution of their respective projects, including those generated by inspections, maintenance
4. activities, new construction, and any other instances as determined by MDOT MAA
5. Performing all manual and automated quality control checks prior to returning a check out geodatabase to MDOT MAA
1.2.2 Project Communications
It is expected that MDOT MAA project managers and consultant project managers will bring the GETS staff into a project early in the scoping process to ensure data and document requirements are fully identified.
1.2.3 AIRPortal Access
AIRPortal can be accessed using a web browser from the following link: http://www.airportal.maa.maryland.gov.
New users shall request a login from the AIRPortal Administrator using the “Register” link on the appropriate login screen for either MAA Employee or MAA Consultant as appropriate – DO NOT REGISTER FOR BOTH. Logins are typically granted within 5 working days.
AIRPortal is currently compatible with the following browsers:
A. Microsoft Internet Explorer version 9.0+
B. Google Chrome
C. Mozilla Firefox
User manuals associated with AIRPortal can be found in PEGS V1 Appendix 1A, PEGS V1 Appendix 1B, and PEGS V1 Appendix 1C.
If users have any questions or encounter any problems, they should contact the AIRPortal Administrator. This email account is monitored regularly.
1.2.3.1 Access to Sensitive Security Information on AIRPortal
Some of the document libraries contain Sensitive Security Information (SSI). The AIRPortal Administrator can grant users rights to view Sensitive Security Information. Refer to PEGS V7, Chapter 1.3 Sensitive Security Information for more information regarding Sensitive Security Information.
Access to SSI documents or spatial data containing SSI must be requested in writing by submitting the Digital Data Request form to the AIRPortal Administrator as described in PEGS V1, Chapter 1.2.5.2 Spatial Data Requests. The requestor must agree to follow the handling procedures outlined in the Digital Data Request form.
1.2.4 AIRPortal Data Holdings
Because of timing of projects and the potential for incomplete legacy records, all digital data carries the following disclaimer:
AIRPortal Digital Data Disclaimer
While every reasonable effort has been made to provide complete and accurate information, MDOT MAA grants access to this digital data with no guarantees of its accuracy, correctness, or completeness. The digital data provided is not survey quality, is not legally recorded, and is not intended to be used for surveying, engineering, or site-specific analysis. Any conclusions drawn from such digital data are done so at the sole risk and responsibility of the user. MDOT MAA disclaims all express and implied warranties relating to the material, including but not limited to warranties of merchantability, integration, title, and fitness for a particular purpose. All digital data is provided “as is.” The data provided is exclusively for work associated with MDOT MAA projects ONLY and should not be distributed in any form outside MDOT MAA.
As an AIRPortal user, one agrees to the fullest extent permitted by law, to indemnify and hold harmless MDOT MAA, its officers, directors, employees and consultants (collectively) against all damages, liabilities or costs, including reasonable attorney’s fees and defense costs, arising from any changes made by anyone or from reuse of the digital data files.
1.2.5 Data Requests
1.2.5.1 Self-Service Files
Many files within AIRPortal do not require a data request to access and are available for self-service. Non-SSI documents and drawings can be viewed within the application, downloaded directly, or shared with other users via AIRPortal’s Shopping Cart functionality.
SSI documents are available upon request. Individual files are noted as SSI in their filenames and with the lock icon. They are listed for reference purposes.
Spatial data is available for viewing through AIRPortal applications. There is no direct download capability for this data; it is available upon request. Spatial data that is SSI is not available for viewing through AIRPortal applications and is only available upon request.
Access to spatial data (i.e. GIS, CAD, and BIM files) must be requested in writing by submitting the Digital Data Request form to the AIRPortal Administrator. The Digital Data Request form can be found in AIRPortal > General > PEGS Reference Documents > PEGS V1-AIRPortal > Requesting Digital Data. CAD, GIS, and BIM data are provided for planning and design purposes with the understanding that existing conditions must be field verified.
When the digital data request form is completed and submitted to the AIRPortal Administrator, an authorization process is initiated to fill the request.
1. The AIRPortal Administrator confirms the availability of the files that have been requested. Some project-based AutoCAD data may not be available if it was delivered prior to the MAA requirement for digital data.
2. The AIRPortal Administrator confirms the validity of the data request with the MAA Project Manager.
3. The AIRPortal Administrator contacts the data requestor to facilitate data transfer. Data will be transferred via FTP or a file sharing site at the requestor’s direction.
4. The AIRPortal Administrator transfers the files to the requester.