Market Survey - Draft EDMS Specifications.pdf

Req.

FAA EDMS REQUIREMENT DESCRIPTION

Basic EDMS Operational & Functional Requirements

1a

All included client software must be compatible with Windows 7

All server software must be capable of running on Windows server version supporting 2003 and 2008-like security, compatible with the existing set of tools on engineers and drafters desktop systems.

2 The software must have a standard Microsoft windows desktop (look and feel for the graphical user interface) with functionality based on the average user’s prior knowledge of Microsoft products (drag and drop, multi-select, menu performance).

3 The software interface must accommodate menu-driven changes to the graphical user interface, while the database is in use.

4 The software must manage and control access to all drawing files (CADD vector and raster) and metadata.

5 The software must have ready ability to prevent CAD software utilization outside of the EDMS system.

6 The software must have ready ability to handle long filenames with 32 characters or greater.

7 The software must have ready ability for the user to preview AutoCAD 2012 and 2014 and MicroStation vector v8i and raster files as a one-step operation with no client software and no downloading of the CAD file.

The software must have the ability to set up known file types with associated applications.

The software must provide administrator capability to manually change associations.

The software must associate file types with viewing capabilities as the default option, allowing the option to check out, open and edit the file in applicable software according to the user’s system defined privileges.

11 The software must have ready ability to use event triggers to provide notification, file locking, change drawing states, etc, at critical points along the workflow.

12 a

The software should have E-mail messaging that allows event notification along various points of the workflow as identified in the workflow diagrams.

The software must have an internal messaging system that allows event notification along various points of the workflow as identified in the workflow diagrams.

The software must be compatible with the Agency’s Single Sign On (Active Directory) System.

14 The software must generate ad-hoc reports. Reports shall be based on queries of metadata and/or system statistics. Examples of metadata reporting capabilities are “All LLWAS Facilities in the Region” or “What has a given user accessed over the past several weeks”. These reports shall be easily generated via any user’s interface.

The software must provide ready ability to assign various privileges according to user’s roles and responsibilities and be able to group users dynamically.

16 The software must be able to assign one user to multiple groups to create a combined set of user privileges. (Example: similar to windows user group assignments.)

17a

The software must have ready ability to query multiple fields with wildcards with the ability to capture query results in a printable report. Reports must be customizable in format by the user.

The software must be capable of creating queries and reports for system wide use and user-specfic-reports and must be capable of saving queries.

The server software must comply with the FAA’s Fully Qualified Domain Naming (FQDN) requirements for installation.

Database Operational & Functional Requirements 19 The software must integrate with FAA’s approved version of Oracle database software.

20a

The software must leverage Oracle granularity, with object and metadata treated separately.

The software must be able to assign restrictions as finite as a single field with a record.

21 The software must be capable of administering distributed data storage vaults over the FAA’s infrastructure.

Metadata Operational & Functional Requirements 22 The software must have ready ability to create, edit, and delete metadata.

23 The software must have ready ability to attach graphic files to metadata.

24 The software must have ready ability to create metadata records without file attachments.

25 The software must ensure that each metadata record maintains an audit trail at the data element level, including who took action, what action was taken and when action occurred.

26 The software should be capable of gleaning modification history from CAD files, if the CAD software has the ability to log and track modification history within the drawing file

27 The software must have ready ability to modify existing fields to the EDMS database.

28 The software must have ready ability to add new fields to the EDMS database such that additions only affect ATO’s EDMS environment.

29 The software mustl allow the Metadata, such as location identifiers, facility types and signature block names, to be derived and editable from centralized data sources. For example: Location Ids are used in many different areas of metadata, for searching and for data validation. All use of LOC Ids shall be derived, validated, and editable from a single database table or text file within the EDMS system.

30 The software must establish and maintain relationships between multiple metadata records.

31 The software must ensure that when creating a single record the attachment and creation of metadata will be optimized to a minimum number of screens, preferably no more than three screens (wizard).

The software must include site level filtering of data, such as engineer’s names and location identifiers specific to only the pertinent region. (Compartmentalization of data elements by region)

The software must allow administration of folder access based on user and group roles.

CADD Integration Operational & Functional Requirements

The software must ensure that system performance is not adversely impacted by the actual physical location of the database and files.

The software should provide the means to help mitigate network performance issues.

The software must ensure that transparency exists for the user regardless of the location of the database and data warehouse.

The software must have validated import functionality for batch loading data with transaction log containing data source, data destination and including validation results.

The software must generate an error report upon discovery of discrepancies, such as duplicate drawing numbers in the metadata within the site.

The software must accept legacy drawings in their current condition and format at EDMS rollout and import drawings at their existing point along a workflow.

40 The software must have the ready ability to create a new CAD drawing from an electronic template (MicroStation v8i and AutoCAD 2012 and 2014) and populate the title block from the associated metadata record.

41 The software must link metadata to title block attributes and title block attributes to metadata (bi-directional) with MicroStation v8i and AutoCAD 2012 and 2014 CADD drawings.

The software must ensure that title block attribute update shall be transparent to the user upon opening the CAD file.

The software must validate the title block attributes to the metadata at check in with discrepancy notification

The software must assign drawing states as metadata attributes to indicate the position in the workflow, as follows: active, QA, QA-Completed, approval, CM-Approval, archival, closed, hardcopy, history, issued, locked, obsolete, redline, released, review, cancelled, inactive.

The software must ensure that access control is related to the state of the drawing in conjunction with user and/or group privileges.

46 The software shall provide permission types, based on which include user and group login roles which include read/write/delete/copy/link/execute/print/check in/check out, based on user and group login type.

47 The software must have the ready ability to create new project drawings based on existing graphics in other files. This function shall provide the option to copy or inherit metadata.

48 The software must embed EDMS file functionality and metadata interface into existing functions and menus of MicroStation v8i and AutoCAD 2012 and 2014 CADD and BIM software.

51 The software must embed plot stamps into MicroStation v8i and AutoCAD 2012 and 2014 plot routines initiating EDMS events associated with plotting.

52 The software must read vector file for reference file information within the EDMS to provide automatic access to all necessary files and support later relative reference file pathing.

53 The software must track all versions and revisions of drawings.

The software must generate drawing numbers in accordance with FAA drawing standards.

The software must accommodate legacy data, drawing numbers that do not to adhere to FAA drawing standards.

56 The software must enable triggers and special workflow scenarios for drawings placed under configuration management.

57 The software must have the ability to exclude specific letters for revision notation, according to the current FAA Engineering Drawing Preparation Standard, FAA-STD-002.

The software must provide an application program interface and associated software to permit adaptation of the software for FAA specific needs.

59 The software must fully integrate with CADD and BIM solutions in accordance with the provided Specification for The Procurement of Building Information Modeling (BIM)/Computer Aided Design & Drafting (CADD) Software.

Vendor Provided Support Requirements 60 The user and system administration documentation must be in the English language.

61 The software must have help screens for user features and functions as related to the software configuration and allow adaptation for FAA unique requirements.

62 Vendor support must respond to users’ issues within 24 clock hours and provide remedies within 72 clock hours.