Understanding Import & Export with NetPoint 4.2

Transcription

1 Understanding Import & Export with NetPoint 4.2 Eric Lowther PMA Consultants 1

2 Primary Differences Regarding Import/ Export CPM Tools F9 and Early/Late Dates Float & Total Float Gantt Charts (Waterfall layout) PDM Leads & Lags Milestones Only Database Driven Many Constraint Types Resources by hours/day and Resource Calendars Resources apply to Activities & LOE P6 Single value, Not MSP yet LOE s/hammocks vary NetPoint Planned Dates Drift, Float & Total Float Time-scaled LDM networks and AutoGRAPH Logic diagramming method (LDM) and embedded nodes Positive & negative lags Milestones & Benchmarks Object Driven 2 Types: SNET, FNLT One time unit/schedule vs day and hour/shift considerations, No resource or shift calendars Resources for activities only, not hammocks, milestones, benchmarks Single & multiple values code assignments, use 1 st behavior Hammocks do not support resources and cannot be empty + Primavera P6 and Primavera P6 API are products of Oracle Corporation * Project is a product of Microsoft Corporation 2

3 EXPORT NETPOINT 4.2 INTO PRIMAVERA P6 + USING API Demonstration + Primavera P6 and Primavera P6 API are products of Oracle Corporation 3

4 Working with the Primavera P6 API + NetPoint 4.2 Primavera API Administrative rights required to install API (application program interface) Primavera P6 v6 or v7 Transfer to V8 using xer in development P6 Menu Options Enabled When Available The API installs at the default location of Program Files > Primavera Set custom API location using menu option File>Import/Export>Set location for P6 API Administrative rights required to reset API + Primavera P6 and Primavera P6 API are products of Oracle Corporation 4

5 Plan Ahead for Export to P6 Consideration for Export to P6 Only planning units = day schedules When defining a code, select the 1 st option to set single value code assignment behavior. Set in in Code Property box. For any activity, all resource assignments should be either by day or duration, not mixed. Option to convert available in P6 Export Options New option to export global number of working hours per day to P6. Option in P6 Export Options Hammocks cannot contain disconnected milestones (Export Stops and Error Report is Provided) P6 has limit of 120-character descriptions (Export Stops & Error Report is Provided) 5

6 Manage Planned Dates Before Export What is a planned date? An object has a planned date when not on its early date, object has drift or can move earlier in time Using planned dates in NPT is easy, but this is not the case in CPM tools. Planned Dates will snap to the Early Date with F9 in CPM tools 6

7 Manage Planned Dates Before Export Strategies to consider to Address Planned Dates Conversion in NetPoint Find and review objects on planned dates Set criticality threshold to drift to see all non-critical objects that will move Use filters to see objects with drift, particularity start milestones Temporary check with Early Dates mode - positive drift objects snap to early dates except start milestones separately filter drift values > 0 for SM Address objects on planned dates Limit changes to objects that originate drift of a chain Carefully apply lags/link offsets and SNE constraints, or let go to early dates Start milestones with drift can be SNE constrained or converted to benchmark Use activity right click menu Snap to predecessor but this may not be the activity early date which is based on its network vs the object s drift Update from Excel report, include drift as a field and apply SNE constraints 7

8 Steps to Export to Primavera P6 + 1 Open plan, address CPM/GPM differences & planned dates 2 Go to File > Import/export > Export to Primavera P6 3 Enter project id Make selections for calendars, codes, resources and working hours/day, details... + Primavera P6 and Primavera P6 API are products of Oracle Corporation 8

9 Details on P6 + Export Options Calendars now are set as project calendars by default, but global may be selected Codes must be checked to transfer. Any object > one value per code assigned has those codes ignored, but accepts single value codes on transfer. *Use single value per code behavior. Resources must be checked to transfer. In P6, all resource assignments for an activity must be the same per day or per duration. Resources in NPT do not consider hours/day, but global working hours can be set for transfer to P6 using the Working hours/day options. Click OK. Review then F9 to schedule (until 5 scheduled, finish milestones may show 1 day later and hammocks not calculated yet ) 9

10 After Export to P6 NetPoint Planned dates, instant feedback Activity & delays Milestone Benchmark Hammock P6 F9 must be applied after export to go to early dates Task Dependent Milestone, need to F9 to calculate Milestone with mandatory constraint, need to F9 to calculate Level of Effort, need to F9 to calculate Activity or milestones with start constraint Activity or milestones with finish constraint Logic diagramming method and embeds Activity and milestones with Start On or After Activity and milestones with Finish On or Before Embeds converted to lags ID transfer but not required If not in NPT plan, IDs are created with prefix ~ Calendars Resources & Resource limits Resources daily only, no hours Codes iobjects Now NP_<Project Name>_<Calendar Name>, Recurring holidays become fixed holidays days In NetPoint Resources under <Project Name>-P, limits do not transfer Resources assign as a global hours/day based on export choice Export as Activity Codes named <Project ID> - <NPT Code Name> with one value code iobjects attached to object export as Documents and are assigned to the correct object. Canvas iobjects associate with the project. 10

11 IMPORTING TO NETPOINT Overview 11

12 Primary Considerations before Import from CPM Only supports transfer of day schedules Network Size Level 1 or Level 2 recommended Summarize / Subset Keep Object Names short Constraints: only SNE and FNL transfer, all others ignored Codes in P6 will transfer to NPT and lend well to AutoGRAPH Resources Resources will be supported in NPT for activities only not LOE s Resources will not have hours/day but based on daily rate only. NetPoint imports resources on a full-time basis only. If fractional durations, NetPoint rounds down if finish before noon, or up if finish after noon. Resources then distributed as /day or /duration. If per duration is chosen, rate is constant. Resource limits do not transfer LOE s/summary Activities Objects can only belong to 1 LOE/hammock Resources on LOE/ hammock will not transfer Empty LOEs will not transfer to NPT + Primavera P6 and Primavera P6 API are products of Oracle Corporation * Project is a product of Microsoft Corporation 12

13 IMPORT PRIMAVERA P6 + INTO NETPOINT USING API Demonstration + Primavera P6 and Primavera P6 API are products of Oracle Corporation 13

14 Before Importing from P6 1 2 Check LOES: Linked to members only, must be connected to fragnets at start with SS and at end with FF links, each member belongs to one LOE only Set Relationship lag calculation to be based on Predecessor Calendar (P6 + ) 3 4 F9 to schedule/calculate using CPM forward/ backward pass Also must Summarize in P6 + to commit changes to database + Primavera P6 and Primavera P6 API are products of Oracle Corporation 14

15 Steps to Import from Primavera P6 + Preset NPT page size to accommodate better first view. 1 In File > Import/export > Import from Primavera P6 3 Select Project and Click Import 2 Login with Admin Privileges 15

16 Steps to Import From P6 continued 4 Review import report changes/ omissions. Save, it cannot be recalled! 5 Accept the import + Primavera P6 and Primavera P6 API are products of Oracle Corporation 16

17 Review NetPoint Plan after Import 1 Set page size and adjust schedule calendar dates for best view Address Pre import report, i.e., add back omitted logic To maintain CPM dates address imported negative lags before affecting network with filter for links with gap < 0. Change to SS/ FF logic and/or add negative link offset Review/address imported constraints or link offsets added in CPM to fix to something other than early date not be required with GPM planned dates Run AutoGRAPH or manually layout schedule. Plan will remember layout and grid info if originally in NPT, then brought back into P6 + Primavera P6 and Primavera P6 API are products of Oracle Corporation 17

18 IMPORT/EXPORT WITH MS PROJECT New feature via MSProject xml * Project is a product of Microsoft Corporation 18

19 The Basic Approach New process developed in NetPoint 4.2 NetPoint 4.2 MSProject XML MSProject 2007 & Later No API requirements 19

20 NETPOINT EXPORT TO MSPROJECT VIA MSPROJECT XML Demonstration * Project is a product of Microsoft Corporation 20

21 Plan Ahead for Export to MSProject XML Only supports transfer of day schedules Manage planned dates in NPT prior to export of Project xml Resource assignments ignored run NPT resource report Codes do not transfer run NPT code report No special hammock considerations to MSP Limit use of link lags - NPT lag calculation is based on the predecessor object, but MSP the lag calculation is based on default calendar review lags exported to MSP MSP limit of 255 character-descriptions, otherwise truncated 21

22 Steps to Export NetPoint to MSProject xml 1 2 In NPT, go to File > Import/export > Export to Project xml, select location and name In MSProject, Go File > Open and to navigate to the xml file, check that xml is selected in dropdown. Click Open 3 Select As new project to be able to easily review import results. Click Finish 22

23 After Export to MSP NetPoint Planned dates are instantly calculated Activity & delays Start & Finish Milestone Start & Finish Benchmark Hammock Activity or milestones with start constraint Activity or milestones with finish constraint Logic diagramming method and embeds ID transfer but not required Calendars Resources & Resource limits Resource definitions and assignments Resources daily only, no hours Iobjects Codes MSP Schedules automatically, if manual setting is used press F9 to schedule Fixed Duration Milestones: Start milestone sets start at 8am, finish milestone set finish at 4pm Milestone with mandatory constraint set at 8am for start benchmark and 4pm for finish benchmark Transfer directly as a Summary without complications Activity and milestones with Start On or After Activity and milestones with Finish On or Before Embeds convert to lags, review for lag calendar that was based on predecessor in NPT but now is based on project calendar in MSP Activity IDs do not transfer, System IDs are transferred as unique IDs. Project calendar with exact name, or append with 1, 2 if a matching calendar exists. Recurring holidays accepted. Names match NPT resources, or append with 1, 2 if a matching resources exist in MSP, limits do not transfer Resource definitions export, but assignments do not export Resources export with 8hr/day 8am to 4pm only Iobjects do not transfer Codes do not transfer 23

24 IMPORT MSPROJECT XML TO NETPOINT Demonstration * Project is a product of Microsoft Corporation 24

25 Steps to Import Project XML into NetPoint 1 If manual setting used, F9 to schedule/calculate 2 In MSP, open the project file and NPT, go to File > Save as > and name and select location of file, changing the Save type as XML Format (*.xml) 3 In NPT, go to File > Import/export > Import from MS Project xml and navigate to xml. Click Open. 25

26 Steps to Import MSP xml into NetPoint, cont d 5 Go to Pre Import report. Save this, it cannot be recalled! 5 Accept the import 26

27 Review NetPoint plan after xml import 1 Set page size and adjust schedule calendar dates for best view Address Pre import report, i.e., add back omitted logic To maintain CPM dates address imported negative lags before affecting network with filter for links with gap < 0. Change to SS/ FF logic and/or add negative link offset Review/address imported constraints or link lags from CPM to fix to something other than early date not required with GPM planned dates Review lags to see any calendar discrepancies which are based on predecessor calendar in NPT vs default calendar in MSP Check Milestones conversion as per rule: If no predecessor, then Start Milestone. Else if before noon then Start Milestone. Else Finish Milestone. Run AutoGRAPH or manually layout schedule. 27

28 Questions & Answers? PRESENTED BY: ERIC LOWTHER 28