As you probably already know, you have the possibility to export all information from Falcon. Basically you have 2 options:

  • Right-click in the project tree to export the information for individual elements (project, package or measure).

  • Using the burger menu in the lower left corner you can also export hub-spanning information (e.g. schedules for all projects at once). The information is basically identical. Via the hub-spanning download only the column for type "Hub" and the name of the concrete hub is added. By the way, as administrator you can also export the user list of your entire hub via the burger menu.

The following describes what the individual columns mean and what information is contained here. Remember that the export adapts dynamically to your elements: For example, if you export the profile of a measure, you will only see information about that measure. If you want to see information for the levels above, you must select the package or the project level.

Profile

The export of the profile contains information about the element, which can also be modified in Falcon using the Profile tab of the same name.

  • Type: Shows type of element (the element is e.g. hub, project, package or measure)

  • Hub: Name of hub

  • Hub (ID): Unique ID of that hub

  • Project: Name of project

  • Project (ID): Unique ID of that project

  • Package: Name of package

  • Package(ID): Unique ID of that package

  • Measure: Name of measure

  • Measure (ID): Unique ID of that measure

  • Measure (Tags): Tags given to the measures (e.g. New York, low-risk, strategy)

  • Measure (Phase): Current phase of the measure (e.g. in conception)

  • Measure (Phase) (Rank): Position of this specific phase (e.g. 1)

  • Freezed/Unfreezed: Distinction whether the element can be edited by normal users or not

  • Guarded/Unguarded: Differentiation whether the element is visible and editable by all users or not

  • Description: Description of the element you have created under the Profile tab

  • Position: Name of the effect that gives the element its traffic light color

  • Position (ID): Unique ID of that effect

  • Responsible: Person responsible for this element

  • Responsible (ID): Unique ID of that person

  • Modified at: Date and time when the element was modified

  • Modified by: Name of the person who edited the element

  • Modified by (ID): Unique ID of that person

  • Created at: Date and time when the item was created

  • Created by: Name of the person who created the item

  • Created by (ID): Unique ID of that person

Schedule

The export of the schedule contains all information about the individual activities of your projects. You already know some columns and their meaning from the profile export, so only the newly added columns are highlighted here.

  • Activity: Name of the activity

  • Activity (ID): Unique ID of activity

  • Aggregation: Shows whether the concrete element is included in the overall aggregation or paused

  • To Do/Done: Shows whether activities in the element are still open or all of them have been completed

  • Comment: Shows the comment for the activity (if available)

  • Start (Plan): Start date according to plan column

  • Start (Actual/Forecast): Start date according to actual/forecast column

  • Start (Delta): Delta between plan and actual/forecast column in days for start date

  • Start (Traffic Light): traffic light color resulting from the delta

  • Start (Achievement): current degree of achievement of the started elements (for activities -> green = 100%, yellow = 33%, red = 0%)

  • End (Plan): End date according to plan column

  • End (Actual/Forecast): End date according to actual/forecast column

  • End (Delta): Delta between plan and actual/forecast column in days for end date

  • End (Traffic Light): traffic light color resulting from the delta

  • End (Achievement): current degree of achievement of completed elements (for activities -> green = 100%, yellow = 33%, red = 0%)

  • Activities planned (Start): Total number of activities with existing plan start date

  • Activities ahead (Start): Total number of activities started before the actual plan date

  • Activities delayed (Start): Total number of activities started after the actual plan date

  • Activities planned (End): Total number of activities with existing plan end date

  • Activities ahead (End): Total number of activities completed before the actual plan date

  • Activities delayed (End): Total number of activities completed after the actual plan date

  • Days ahead (min) (Start): Minimum value of days for activities that were started ahead of the actual planning (example: activity was started 1 day before plan)

  • Days ahead (max) (Start): Maximum value of days for activities that were started ahead of the actual planning (example: activity was started 12 days before plan)

  • Days ahead (Average) (Start): Average value of days for activities that were started ahead of the actual planning

  • Days ahead (min) (End): Minimum value of days for activities that were completed before the actual planning (example: activity was completed 1 day before plan)

  • Days ahead (max) (End): Maximum value of days for activities that were completed before the actual planning (example: activity was completed 12 days before plan)

  • Days ahead (Average) (End): Average number of days for activities completed before the actual planning

  • Days delayed (min) (Start): Minimum value of days for activities started after the actual plan date (example: activity started 1 day after plan date)

  • Days delayed (max) (Start): Maximum value of days for activities started after the actual plan date (example: activity started 12 days after plan date)

  • Days delayed (Average) (Start): Average value of days for activities started after the actual planning

  • Days delayed (min) (End): Minimum value of days for activities completed after the actual plan date (example: activity completed 1 day after plan date)

  • Tage verspätet (max) (End): Maximum value of days for activities completed after the actual plan date (example: activity completed 1 day after plan date)

  • Days delayed (Average) (End): Average number of days for activities completed after the actual planning

Effects

The export of the effects contains all information about the effect key figures. There are also columns here that you already know. The newly added columns are briefly described here.

  • Target-Position: Effect line (position), which is responsible for the traffic light color

  • Target-Position (ID): Unique ID of that position

  • Category: Category under which the effect lines are clustered

  • Category (ID): Unique ID of that category

  • Position (Unit): Unit of the effect line (€ or freely definable "amount")

  • Position (Period): Aggregation period

  • Position (Horizontal Aggregation): Indicates what happens mathematically to the individual periods within an effects line (e.g. all successive periods are summed)

  • Position (Vertical Aggregation): Indication of what happens mathematically with the individual periods via the project tree (e.g. via the effects line an average value is formed across different measures and passed on to the project level)

  • Position (Target): Specifies which target is pursued with the effect line (e.g. more is better or precision landing)

  • Plan/Actual/Delta: Current delta between planning and actual

  • Total: Total value of the effect according to the set aggregation period

  • Total (Traffic Light): Traffic light color of the delta evaluation

  • Total (Achievement): Degree of achievement (comparison of plan vs. actual)

  • Total (min): Minimum value of the achieved effect figures over all periods

  • Total (max): Maximum value of the achieved effect numbers over all periods

  • Total (Average): Average value of the achieved effect figures over all periods

  • Individual periods: Furthermore, you can see all your periods in the export according to the set duration of your budget or project timeline (e.g. duration from January 2020 - December 2022 -> January 2020, February 2020, etc.)

Status Reports

The status reports contain qualitative statements on the development of the respective measure. Many of the columns can already be recognized from the other exports. You can see what is newly added in the following.

  • Flagged/Unflagged: Indicates whether a Red Flag is set or not (Open status report with marking is immediately visible in the project tree with a Red Flag)

  • Status: Indicates whether the status is still open or already completed ( = checked)

  • Text: Shows the exact word content of the status report

Users

The user overview can be exported via the burger menu in the lower left corner, if you have admin rights. Here e.g. the names, mail addresses and owner rights of the individual users can be viewed.

  • User: Full name of the User

  • User (ID): Unique ID of that User

  • First Name: First name of the user

  • Last Name: Last name of the user

  • Position: Position of the user (e.g. Head of Marketing)

  • Department: Department in which the user works (e.g. Production)

  • Organization: Organization in which the user works

  • Language: Language setting the user chooses for Falcon

  • E-Mail: E-mail address of the user

  • E-Mail (Modified at): Date and time when this e-mail address was last changed

  • Logged in at: Date and time at which the user last logged in

  • Logged in from: Location from which the user last logged in

  • MFA enabled: Has the user enabled multi-factor authentication (Yes/No)

  • Sessions (Last Month): Number of sessions/logins the user had in the last month

  • Password (Length): Password length (character length only)

  • Password (Type): Identification, if own password or the randomly generated initial password is used (initial password must be changed obligatorily at login)

  • Password (Modified at): Date and time when the password was last changed

  • Passwort (Valid until): Period in which the password is still valid and must be changed afterwards

  • Status: User status that is valid in the user overview in Falcon (active/inactive)

  • Owner: Identification whether the user has owner rights ("Super-Admin") or not

  • Access: Indicates whether the user has access to the hub

  • Permission (Modified at): Date and time when the user's permission was adjusted.

  • Permission (Modified by): Name of the user who modified the user's permission.

  • Permission (Modified by) (ID): ID of the user who adjusted the permission

  • Permission (Added at): Date and time when the user was added to the hub

  • Permission (Added by): Name of the user who added the user

  • Permission (Added by) (ID): ID of the user who customized the user's permission.

Did this answer your question?