In Microsoft Project (MSP), click on the drop-down menu
Tools > Organizer > Toolbars (tab). Make sure that the
"toolbars available in:" field is set to
Global.MPT (bottom left) and
AzTech_--_B--.MPP (bottom right).
Now that you can see both the Global.MPT and the latest AzTech file, select the AzTech views and hit the Copy >> button and the Run!AzTech toolbars should be visible.
Either the Run!AzTech Template is not open or macros are not enabled. When working in MSP make sure you have the Run!AzTech Template .MPP file OPEN at all times. Also be sure to select "Enable Macros" when prompted after opening the template file.
File extensions need to be visible for some of the macros to work correctly. If you recently installed Run!AzTech, you may need to modify your Windows Explorer settings.
- Go to Programs > Control Panel > Folder Options > View (tab).
- Under Files and Folders > Hidden Files and Folders, make sure "Hide extensions for known file types" is UN-checked.
Setting MSP to manual calculation can help save time and speed up some processes while working in MSP. To change the calculation mode go to Tools > Options > Calculation (tab) and change the Calculation mode to 'Manual'. If this option is used be sure to hit F9 when any calculations are necessary.
- Right-click in the Toolbars area and select 'Customize...'
- De-select or delete AzTech Menu.
- Exit & restart MS Project.
- Right-click in the Toolbars, select 'Customize...' and select 'Reset'.
- Exit & restart MSP (if needed).
- Drag & drop other toolbars to set up toolbars as desired.
Super User Licenses allow for secure access to AzTech's proprietary web knowledge base for Microsoft Project, Integrated Master Plan / Schedule IMP / IMS), & Earned Value Management Systems (EVMS). Super Users receive dedicated, off-site support for Wish List items, customized functionality, & advanced implementation & analysis support. Within the off-site hours, AzTech will make a best effort to include client's desired enhancements & provide detailed off-site support.
- Run!AzTech Template for Microsoft Project Professional 2000 through 2003, plus documentation in un-editable, electronic format.
- Remote Training via periodic Webinars or AzTech Web based Flash Training Movies
- AzTech supports installation of our Template for MS Project for Super Users.
- Basic & Intermediate Training for Super Users via off-site support & Webinars. including tips for generating project-specific metrics & AzTech Schedule
- Health Stoplight Reports.
- Analysis & Technical Support within off-site hours.
- Priority customization. Client has priority input into AzTech's Wish List tracking for enhanced functionality.
Be sure to run the 'N15' command to copy the Unique IDs to the Number 15 field. The OOS report uses this field to report the Unique ID in parentheses next to each Task Name.
Select the given milestone and run the Trace function. Input the letter C to trace using total float, and F to sort the results by finish date. If the schedule is set up properly, the results should make a continuous task waterfall in the Gantt chart.
Note: You can select D instead of C, and the Trace function will output the driving path.
If you are using MSP 2003, make sure MSP Service Pack 3 is installed.
Using Run!AzTech, simply select the Program Milestone (or any other milestone or task, for that matter) and use Run! 'CPLI' to walk through the CPLI wizard. The CPLI determines the critical path length, adds or subtracts the Total Float value (adds a positive Total Float value or subtracts a negative Total Float value), then divides this by the critical path length. Thus, a Program Milestone with zero Total Float yields a CPLI of 1.0; negative Total Float yields a CPLI less than 1.0; positive Total Float yields a CPLI greater than 1.0.
Caveats: This index assumes that the Total Float is a valid value based on sound network logic and a valid Baseline Finish Date.
The AzTech Stats report does not automatically compute the CPLI, but you can compute it using the following steps:
To manually calculate the
CPLI (per DCMA's method), first you need to figure out the length from time now (or status
date) to the program end. The easiest way to do this is to create a
dummy task in the schedule, set the start date equal to the status date
and set the duration long enough to 'hit' the Program Complete
milestone's Baseline Finish Date. This duration is the distance between
time now and the program milestone and is known as the 'Critical Path Length'. There are other ways to do this, but this is the easiest way to
incorporate the project's calendars/working times on any given schedule
& any scheduling tool. Next the least amount of Total Slack/Float in the schedule should be found and is known as the 'Float Duration'. Use the following formula to determine the CPLI:
CPLI = (Critical Path Baseline Duration + Float Duration) / Critical Path Baseline Duration
The BEI is based on the Defense Acquisition University (DAU) Gold Card that contains commonly used Earned Value terms and acronyms, including formulas for variances, metrics, and indices.
The AzTech Stats report uses an algorithm that counts the number of Completed Tasks with a Baseline Finish date <= the Status Date divided by the number of Tasks with a Baseline Finish date <= the Status Date. While a project is in progress, the BEI fluctuates due to performance against the baseline plan. A BEI < 1 means the project is behind schedule in regards to the baseline, and a BEI >1 means the project is ahead of schedule or exceeding the baseline plan.As a project nears completion, the BEI will trend towards 1.0. Once the project has reached completion, the BEI will equal 1.0 (the same is true for Schedule Performance Index, SPI).
BEI = Number of Baseline Tasks Actually Completed / Number of Baseline Tasks Scheduled for Completion
Unfortunately this is an issue with MS (please talk to Bill G., not AzTech!). We have found that if you use Help to search for how to turn User Accounts off, you can uncheck User Accounts and then MS Project (& other applications) work without the constant crashing under Vista.
!! Please do this step at YOUR OWN RISK!! (but it does work)
Use the Links button or Run > Links. The driving predecessor will have an asterisk to the left of the predecessor in the Excel Links report.
It could be that the AzTech_Maps.TXT file is not in the same folder as your Project .MPP file. Or, it could be that the .TXT file does not contain a valid Map name.
Note: Maps reside in Global.MPT on each computer and must be created in Global.MPT using File Save As, and the Maps Wizard--or copied into Global.MPT using Tools, Organizer.
This usually means your .MPP file has a formula in a field that our Template uses. Check the field (most likely Number15, Text3, Flag19, Number20) by inserting that field´s column, right clicking, and choosing Customize Field, then uncheck the bottom three radio buttons.
Yes, so long as the tool can produce a .MPP file, you can use our Template. Run!AzTech works with any .MPP file
From the AzTech (Drop-down Menu) > Numbers > Convert to Days
Warning: Only works on SELECTED Tasks that are showing (not filtered out) and does not work on Tasks with ELAPSED durations (you´ll have to change those manually).
Also: We think AzTech's function works better than MS Project's 'Format Durations´ macro.
This is a known MS Project issue that occurs when the Global.MPT file becomes corrupted.
To resolve this, you will need to locate this file in your application folder, then make a backup copy of the file (simply copy and paste within the same folder), then obtain a new global.MPT from another MSP user to replace the corrupted version.
The file location will vary, but is usually under something like this:
C:\Documents and Settings\(?yourlogin?)\Application Data\MS Project\12\1033
OR
Open and save a new .mpp. Open the Organizer and copy everything except Modules from the Global.MPT to the new file (remember to look for the Task and Resource radio buttons and to switch between them on the tabs that have them). Save the new file. Open the Organizer again and one by one copy all the modules to the new file. If any that will not copy were not native to MS Project's Global.mpt file, you may need to open Project Visual Basic and copy the content of those modules to a text file or otherwise back them up. Save the backup file and close MS Project. Go to C:\Documents and Settings\(?yourlogin?)\Application Data\MS Project\12\1033 & rename the Global.mpt file. Re-open MS Project and save Project1 somewhere, to recreate a new Global.mpt file. Re-open the backup file you created earlier, and copy everything in the Organizer back to the Global.mpt.
Make sure Macros were enabled when you opened Run!AzTech.
Refer to the Run!AzTech QuickStart Guide and follow the instructions to install the AzTech Excel Add-In for your specific version on MS Excel. Download the guide
here.
Just delete within the VAR_Data records by selecting row(s) and right click delete.
Yes, but just be aware that some reports might not fit well on 8.5 x 11 afterward, but if you are mostly reviewing and not printing, that should be fine.
The AutoVAR data tends to be large for some programs and the calculation time can be excessive, so it's best to keep it on Manual. Tip: Use AzTech's Excel Add-in > Admin > Manual to set all open worksheets to Manual calculation. That is AzTech's preferred setting for all spreadsheets and having even ONE spreadsheet open that is set to Auto Calculation will cause frequent recalculation that might be excruciating to endure.
The AutoVAR data tends to be large for some programs and the calculation time can be excessive, so it's best to optimize the user of your laptop's formula calculations by maximizing your processor usage. Tip: Set your Excel tool (via Excel Options > Advanced > Formulas) to enable multi-threaded calculation and also set it so that the maximum number of processors is being used. That is AzTech's preferred setting.
Yes, but best to select those rows, right click, and delete them.
If performance is not an issue, then you can ignore this function; it is only required for very large programs where calculation time is taking too long. The Header tab has a value that determines the number of rows to copy down. Please let us know if that function is working correctly, so we can make any necessary fixes.
Right, it will leave your green cells alone. Again, let us know if you see otherwise. Always save before running this function and run two or three VARs to do a sanity check on the values.