Search Knowledge Base by Keyword

Importing Generic Spreadsheets

You are here:
< Back

NetPoint allows you to import information from user-created spreadsheets. For example, you may have a list of activities you’ve compiled in Excel based on previous projects or collected from different team members. Upon importing, NetPoint will identify the fields that it recognizes and map them automatically; however, some manual correction and mapping may be necessary. If any fields remain unmapped, or if the same field is mapped to more than one column, the OK button will become disabled and warning icons will appear. For a full list of supported fields, see the notes at the end of this chapter.

Before importing, make sure the Excel file has been saved, as the content from the most recently saved file will be imported. If Excel is open, do not close it during any step of the import process, and vice versa. Also, make sure that the sheet being imported isn’t protected, as this may interfere with the import process. Data can be imported into new or previously-saved schedules.

NOTE: Upon import, any comments on cells in Excel will be removed. To avoid loss of any comments, duplicate the Excel file and import the duplicate.

Steps

  1. With NetPoint open, click File > Import/Export from the menu bar and choose Import From Excel File.
  2. Browse for the desired Excel file and click Open.
  3. To import a risk register or resources, choose Risk Register or Resources next to Data Type. Otherwise, leave it on Schedule Objects.
  4. To change to a different sheet, click the down arrow next to Sheet Name and choose accordingly.
  5. To set the data area, click the arrows up or down under Data Range.
  6. To include or exclude data from a given column, check or uncheck the box next to its name.
  7. To map a new field or correct a default mapping, click the down arrow button to the right and choose accordingly.
  8. Once all fields are mapped successfully, click OK. A report will open listing any warnings found (all warnings will be added to the cells in Excel if the file was closed beforehand).
  9. To correct any invalid data, click Cancel Import.
  10. To continue with the import, click Finalize Import.

Notes

Import from Excel Window

Field Definition
Data Type The type of data desired for import, whether Schedule Object, Resources, or Risk Register. Each type will determine which fields are available for mapping below.
Sheet Name The name of the sheet desired for import.
Header Row The row in Excel being used as column headers. NetPoint will attempt to automatically detect this.
First Row The first row of data desired for import. NetPoint will attempt to automatically detect this. Any row above will not be brought in.
Last Row The last row of data desired for import. NetPoint will attempt to automatically detect this. Any row below will not be brought in. If 10 empty rows are detected, the import will stop, regardless of whether or not it’s reached the last row.
First Column The first column of data desired for import. NetPoint will attempt to automatically detect this. Any column before will not be brought in.
Last Column The last column of data desired for import. NetPoint will attempt to automatically detect this. Any column after will not be brought in.

Schedule Object Fields

Field Requirements
Object Type For an activity, enter as “activity,” “task,” “task dependent,” “fixed units,” “fixed duration,” or “fixed work”. For a milestone, enter as “milestone,” “start milestone,” “sm,” “finish milestone,” or “fm”. For a benchmark, enter as “benchmark,” “start benchmark,” “sb,” “finish benchmark,” and “fb”. For delay, enter as “delay”. If missing or invalid, it will be imported as an activity.
ID Can be any combination of letters and numbers (case sensitive). Characters such as “-” are supported but others such as “#” will be dropped.
Description Can be any combination of letters, numbers, and characters.
Calendar Must be defined in the file you are importing into. For example “United States” or “Calendar Days”. Case sensitive. To assign a global calendar, make sure to include [space][parenthesis]Global[parenthesis], e.g. “Calendar (Global)”.  If missing or invalid, it will be set to the default calendar for the schedule you’re importing into.
Duration Must be greater than 0 for activities and equal to 0 for milestones and benchmarks. If missing or invalid, it will be set as 1 for activities and 0 for milestones, benchmarks, and delays.
Start Date Can be entered in any date format recognized by Excel, including but not limited to: 3/14/2012; 3/14/12; 03/14/12; 14-Mar-12; 14-Mar-2012; March 14, 2012; Wednesday, March 14, 2012. If a date is entered that is not in that object’s calendar’s work days, the object goes to the next work day for that calendar. If missing or invalid, it may be set to its early date. NOTE: If a cell hasn’t been formatted as a date, then the date will be brought in according to the date format of the operating system. For example, 1/2/13 will be brought in as February 1st if Windows is using a UK format but January 2nd if Windows is using a US format.
Finish Date Can be entered in any date format that is recognized by Excel, including but not limited to: 3/14/2012; 3/14/12; 03/14/12; 14-Mar-12; 14-Mar-2012; March 14, 2012; Wednesday, March 14, 2012. If a date is entered that is not in that object’s calendar’s work days, the object goes to the next work day for that calendar. If missing or invalid, it may be set to its early date. NOTE: If a cell hasn’t been formatted as a date, then the date will be brought in according to the date format of the operating system. For example, 1/2/13 will be brought in as February 1st if Windows is using a UK format but January 2nd if Windows is using a US format.
Predecessor Enter as EITHER [Row #][Relationship][Lag] OR if ID’s are being defined, [ID][Relationship][Lag], e.g. “12FS1″ or “ABFS1″. In either case “[Lag]” is optional, e.g. “12FS” or “ABFS”. If ID’s are being defined, row numbers can NOT be used. Possible relationships include SS, FS, FF, or SF. If the relationship or row #/ID is not recognized, the link will not be imported.
Successor Enter as EITHER [Row #][Relationship][Lag] OR if ID’s are being defined, [ID][Relationship][Lag], e.g. “12FS1″ or “ABFS1″. In either case “[Lag]” is optional, e.g. “12FS” or “ABFS”. If ID’s are being defined, row numbers can NOT be used. Possible relationships include SS, FS, FF, or SF. If the relationship or row #/ID is not recognized, the link will not be imported.
Color Enter as EITHER R,G,B (for example, 255, 50, 50) OR by name. A list of supported names can be found at http://www.rapidtables.com/web/color/RGB_Color.htm. If invalid or not recognized, it will be set as the default color for that object.
Grid Enter any number greater than 1. Unrecognized input (negative numbers or characters) will result in being placed on the first grid. An object placed on a grid number greater than the highest being displayed will still be successful, but will only be visible after increasing the page tiling.

Resource Fields

Field Requirements
Resource Name The description of the resource. Can be any combination of letters, numbers, and characters.
Category The type of resource. Can be “Commodity,” “Construction Equipment,” “Dollars,” “Equipment,” “Labor,” “Manpower,” “Material,” or “Professional.” If empty or invalid, set as equipment.
Cost/Unit The cost per unit of resource, used when exporting to Excel or viewing the WBS roll-up. If empty or invalid, set as 1.00.
Pattern A visual cue for identifying resource bars on the histogram. Can be “Solid,” “Dots,” “Dk Horizontal,” “Dk Vertical,” “Dk Trellis,” “Dk Grid,” “Dk Up Diagonal,” “Dk Down Diagonal,” “Dk Horiztonal,” “Lt Vertical,” “Lt rellis,” “Lt Grid,” “Lt Up Diagonal,” or “Lt Down Diagonal,” If empty or invalid, set as solid.
Color The color of the resource bars on the histogram. Enter as EITHER R,G,B (for example, 255, 50, 50) OR by name. A list of supported names can be found at http://www.rapidtables.com/web/color/RGB_Color.htm. If empty or invalid, set as default.
Intensity The darkness of the resource bars on the histogram. If empty or invalid, set as 100%.

Risk Register Fields

Field Requirements
ID The reference number for the risk.
Risk Description A short explanation of the risk
Owner The person responsible for tracking a risk, and for ensuring an appropriate response is selected and implemented if it occurs.
Status The current state of the risk in the project. Can be “New,” “Open,” “In-Progress,” or “Closed”.
Category A designation of type. Can be “Threat” or “Opportunity”.
Strategy The type of response to a risk, depending on if it’s a threat or opportunity. For threats, it can be “Accept,” “Mitigate,” “Transfer,” or “Avoid”. For opportunities, it can be “Accept,” “Enhance,” “Share,” or “Exploit”.
Duration Probability The chance that a risk could occur, as defined in the probability/impact matrix. Can be “Ultra High,” “Extremely High,” “Very High,” “High,” “Moderate,” “Low,” “Very Low,” “Extremely Low,” or “Ultra Low,” as well as their abbreviations: “UH,’” “EH,” “VH,” “H,” “M,” “L,” “VL,” ‘”EL,” “UL”.
Duration Impact The degree to which the risk could affect activity durations. Can be “Ultra High,” “Extremely High,” “Very High,” “High,” “Moderate,” “Low,” “Very Low,” “Extremely Low,” or “Ultra Low,” as well as their abbreviations: “UH,’” “EH,” “VH,” “H,” “M,” “L,” “VL,” ‘”EL,” “UL”.
Response Notes for detailing the approach for handling the risk.
Comments Notes for summarizing team discussions or including additional information about a risk.

 

 

RELATED RESOURCES