Академический Документы
Профессиональный Документы
Культура Документы
Contents
Contents ...........................................................................................................................................2
1. GETTING STARTED ................................................................................................................ 16
1.1 Technical Requirements/Recommendations .......................................................................... 16
1.1.1 Internet and Network Connectivity ............................................................................................ 16
1.1.2 Browser ...................................................................................................................................... 16
1.1.3 Java ............................................................................................................................................ 16
1.1.4 Security ...................................................................................................................................... 16
1.1.5 Screen Resolution ...................................................................................................................... 16
1.2 General Remarks................................................................................................................... 16
1.2.1 Back Button ............................................................................................................................... 16
1.2.2 Action Confirmation .................................................................................................................. 16
1.2.3 Idle Time Out ............................................................................................................................. 17
1.2.4 Parallel Account Usage .............................................................................................................. 17
1.3 Logging On ............................................................................................................................ 17
1.3.1 Log on to IPM ............................................................................................................................ 17
1.3.2 Forgotten Password .................................................................................................................... 17
1.3.3 Create/Update User Profile ........................................................................................................ 18
1.3.4 Change NOLS Password............................................................................................................ 18
1.3.5 Access Project Homepage .......................................................................................................... 18
2. DEFAULT PROJECT FUNCTIONALITIES ............................................................................................ 19
2.1 General Navigation ................................................................................................................ 19
2.1.1 Upper Navigation Menu Bar ...................................................................................................... 19
2.1.2 Select Project ............................................................................................................................. 19
2.1.3 Project/Site Links and Site Process Guide ................................................................................. 20
2.2 Project Homepage ................................................................................................................. 21
2.2.1 Project Details ............................................................................................................................ 21
2.2.2 Search......................................................................................................................................... 21
2.2.3 Advance Search.......................................................................................................................... 23
2.2.4 Mass Create and Copy functionality .......................................................................................... 25
2.2.5 Link Search ................................................................................................................................ 29
List of Figures
Figure 1: IPM Homepage Header ................................................................................................................ 19
Figure 46: Mass Update Data Upload Functionality Error Page ................................................................. 59
Figure 97: Site Search Result Grid Meta Info ............................................................................................ 125
List of Abbreviations
Abbreviations Expansion
ACL Access Control List
AP Acceptance Punchlist
ChM Change Management
CL ID Checklist ID
CR Change Requests
DC Deficiency Tracking
DWP Default Work Packages
1. GETTING STARTED
This section explains technical requirements, general requirements and logging information of IPM
project.
1.1.2 Browser
Use your default browser settings for Security and Internet Options. Configure the browser to
accept cookies and have correct Security Setup (use SSL).
Enable (optional) and allow per-session cookies that are stored on your computer.
1.1.3 Java
Use Oracle JVM 1.6 or later versions
According to the browser settings, enable JavaScript with your browser using Java as the default.
1.1.4 Security
It is required that your Secure Sockets Layer (SSL) encryption be version 3.0 or later, active, and
uses a 128-bit encryption cipher strength.
1.3 Logging On
Request a user account prior to accessing IPM. To request an account, contact your project
administrator (IPM Key User).
2. Enter your username and type your password in the Log-in section of the log on page (note:
password is case sensitive).
If your password is rejected three (3) times or more, your user account will get
locked.
Only have access to one (1) project, IPM will default to the Project Homepage.
Have access to multiple projects, the IPM homepage will be displayed listing
multiple projects of your selection.
Note:
It is also possible to enter IPM using the Nokia Networks Online Services (NOLS)
main page by clicking the Deployment tab at the top of the screen.
2. On the NOLS Password Reset page, fill in your username and email account information and
click Submit.
Version 4.0 Page 17
IPM User Guide
NOTE: If your account has become locked due to multiple unsuccessful log on attempts, you will
need to send an email to: Support, Nols (Nokia - Global) nols.support@nokia.com
3. Your password will be sent through email to corresponding NOLS user mail Id.
1. In the NOLS upper navigation panel, select the My Profile link. The My Profile page will
appear.
On this page it is possible to modify the following:
User Information
Title
2. Click Save after you have created/updated your information (all mandatory fields are
marked in bold and marked with a * sign). All information is immediately updated within the
system.
In the IPM homepage, default project or last project worked on by the user, will be selected by
default.
If you want to change the project, select the project from the Select Project drop-down List as
displayed in IPM Homepage Header.
Apart from this, the application has Maintenance/Tip of the day section. Any maintenance
information for IPM application will be displayed in this section and some general tips for usage
of IPM application will be displayed.
On the Project homepage, the following information is displayed in the Project Details section.
Project ID (automated number assigned by IPM)
Project Name
Project Director (name)
Project Key User (name + hyperlink)
2.2.2 Search
The Search section is visible from the Project homepage. But, user can access search from any
page at the top-right menu bar. From this section it is possible to search if you have been granted
access.
1. Select the predefined field from the drop-down list and enter search records by inserting the
value. The Search Combo Fields are available on all IPM pages:
The following fields are available:
CRID (*)
Cust. Site Code (*)
Ext. System ID (*)
Link Cust. Name
Manual CBM #
Manual CPO # (*)
Manual SO #
Manual SPO #
Manual SvO #
Phase (*)
RTI CBM #
RTI CPO # (*)
RTI SO #
RTI SPO #
RTI SvO #
RTI WBS Code (*)
RTI Invoice #
Site Conf. Sys. ID
WP ID
ZI Partner
All Custom fields/combos (except check boxes and/or Site Log fields)
Business Rules
Wild cards are allowed for the fields with (*).
Default maximum result to display for each search criteria is 5000 records.
If searched records are more than 5000, it will display total number of records found but
in the grid only 5000 records will be displayed.
For the quick search result, the search result grid displays only default columns and also
column setting button will not appear.
For the quick search result grid in-line editing will be not be available.
Customer Site Code is having hyperlink to open the site in the same page in a new tab.
User is allowed to open maximum of 10 sites.
If Search result is only one, it will automatically open the site/WP along with site search
result.
Column selection button is available only for advance Site/WP search to select the list of
columns in Site/WP search result grid.
User can export searched record to excel using “Export To Excel” Button.
User can view the WPs by clicking on expand view button in the site search result grid.
User can select any search in any tab that is Site, WP, and Custom Data.
After selecting the tab, user will get predefined filtering fields.
Enter the search criteria in required field(s).
Save Search option is available under advanced search option for Site and Work
package tabs.
User can save search criteria by giving some name to it, which user can use later by
simply selecting the search name from drop-down list available under advanced search
tab (Available after search saved).
User can Update/Delete an already saved search.
Each user can save up to 20 searches per project, 10 for advanced search-site and 10 for
advanced search- Work packages tab.
Business Rules
Wild cards (*) are not allowed for the advance search fields.
Default maximum search result for each Searching Criteria is 5000 records per page.
If searched records are more than 5000, it will display total number of records found but
in the grid only 5000 records will be displayed.
Customer Site Code is having hyperlink to open the site in the same page in new tab.
- From the search result grid, user has to click Edit present against each row; it will
enable all the editable fields for editing. Update the field value(s).
- Click Update.
If Search result is only one, it will automatically open the site along with site/WP search
result.
Column selection button is available to select the list of columns in Site search result
grid.
When Open deficiency check box is selected, then user will get list of Sites with Open
deficiency
When Open deficiency check box is not selected, then deficiency information for sites is
not shown in Site search results
User can view the WPs by clicking on expand view button in the site search result grid.
Advance search grid also support export to excel functionality for the searched data.
Cancel
Commit
New WP
Copy WP
2.2.4.1 Create WP
This functionality enables the mass DWP call-off.
1. To select the site(s), click on the checkbox.
2. Click New WP, where you get a pop up of Create Work Package as shown in figure
12.
5. Work Packages are created and the following message is displayed at the top of the
page:
‘Successfully created <number> of <default work package name> work packages’
NOTE: Maximum 10 WPs we can call-off or copy at a time.
Work Package is copied and the following message is displayed at the top of the page
‘successfully copied <WP ID / Name> to (<#>) selected sites.
The following fields are copied (Note: Everything in the existing called-off work package
is copied, except for the dates and customer purchase order information (manual CPO
and/or RTI CPO):
Default WPID
WPName
Invoicing Notes
TI / CW / NPSA WP
Status
Scope
Change Request WP
Phase
Custom
Partial Payment WP
WBS
Product Configuration
Dimension
Notes
Weight
Workitem Fields that will be copied are
Id
DefaultWIID
ItemType
ItemSubType
SiteProcessPhase(SPP)
Notes
CustomerInvoiceTrigger
SupplierInvoiceTrigger
SupplierPaymentTrigger
DOP Trigger
Site Trigger
ProjectSpecificMilestones
NewGlobalMilestones
GlobalInchstone
PlannedDateRequired
SpmDescription
SpmPercentage
SogNumber
WI’s SOG
CompletedByCompany
CompletedByPerson
smsEnabled
timestampWorkItem
Copy Date functionality will be available and this will make coping the
Planned/Forecast/Actual Date to the new WPs created.
3. Select the sites (results section) and work packages (optional – for association) they
would like to have the configuration copied to.
4. Click Copy. Site Configuration is copied and the following message is displayed at the
top of the page:
2.3 Documentation
2.3.1 Documentation Navigation
The (project) Documentation link is accessible through the Documentation field present on
the Menu bar.
Once clicked, the links displayed within this bar vary depending on access rights; however
the default links are as follows:
Project Documents – Link to the Project Documentation page (visible to all users
having a valid document management account)
Tasks – Link to the DM Tasks page (visible only to users having document/CSF reviewer and/or
approver rights).
Document Admin
Management
The Project Documents link is accessible through the Documentation drop-down list.
The purpose of the Project Documents page is to centrally manage all associated project
documentation. For example, project plan, resource plan, and so on. Visibility to the folder and
documents are based on folder/ document permissions (ACLs).
2. Click the sign next to the project folder you would like to open.
The folder will open displaying all subfolders and/or documents to which you have access to.
As the project and site-level basic document management functionalities are similar, refer to the
Site Document Management chapter of this guide for additional functionalities.
2.3.3 DM Status
The purpose of the DM Status page is to quickly view the status of all documents you are marked
as the owner for.
To browse the DM Status page, perform the following steps:
By default, the page will open with the Date filter set to Due within 7 days (that is the document
due date is within the next seven day time period).
2. Select those filters which you would like to limit the results to and click the Filter.
The page will refresh displaying all documents meeting the defined filters/ criteria.
Note:
Only document/folder owners are able to see this link (otherwise the ‘Status’ link will
remain hidden)
If a document is linked to a work package (WP) work item (WI), the DM column will be
set to ‘Y’.
If a document is a project document, the DM, Permission Zone, and CSC columns will
remain blank.
Clicking the name of the document will open the Document Details page.
Clicking View next to a document will open the latest version of that document.
By default, inactive documents (those documents not in an active workflow which have
not been accessed for six months) are automatically archived. The archive column
displays the date on which the document will be archived. If you have sufficient
permissions (‘change state’), it is possible to reset the time of the automatic archiving
(ticking this box again starts the six month countdown).
2.3.4 DM Tasks
The purpose of the DM Tasks page is to highlight those documents/customer site folders (CSF),
which are awaiting the logged on user’s review and/or approval.
By default, the page will open with the Date filter set to This Week (that is the document
due date is within the next seven day time period)
2. Select those filters which you would like to limit the results to and click Filter.
The page will refresh displaying all documents meeting the defined filters/criteria.
Page will refresh with the completed objects moving to the ‘Completed’ DM Tasks page.
At any time, you may view those tasks you have already completed as follows:
1. Access the DM Tasks page (through the Project Documentation side navigation links).
The Completed DM Tasks page will be displayed highlighting all tasks as read-only.
Note:
Only users having either Reviewer and/or Approver rights will be able to see this
link.
Sorting is done on each page as follows: Date, Permission Zone, CSC, Name,
and then Type.
When completing a task, the status of the object is displayed making it so that if
an object is ‘In Internal Approval’, selecting the Review/Approve radio button
will mark the object as ‘Internally Approved’. If rejected, the object will gain the
status of ‘Internally Rejected’.
2.3.5 DM Search
Click the DM Search tab present under Advance Search. A sub panel is displayed allowing you
to search for documents and folders/document within the selected permission zones you have
been granted access.
2. Click Search.
Version 4.0 Page 33
IPM User Guide
The Search Results page will be displayed highlighting those folders meeting the defined
criteria.
Mass Delete
Mass Export
Note:
It is possible to use wildcards (*) when searching by CSC and Folder Name.
When Folder Type = CSF the following fields are also visible:
Status
Linked to Work Package (will only display those WPs (WP ID + Name) containing
DM type WIs)
Linked to Work Item (will only show DM WIs based on selected WP)
On the Search Results page, only users with Delete rights will see the Delete column
(otherwise is hidden).
1. Specify none, any or all of the available search parameters. By default, Location = Site and
Permission Zone is mandatory.
2. Click Search.
The Search Results page will be displayed highlighting those documents meeting the defined
criteria.
Mass Delete
Note:
It is possible to use wildcards (*) when searching by CSC and Document Name.
Sub-function/Phase
Values displayed depend on whether location = Site or Project
Linked to Work Item (will only display DM WIs based on selected WP)
On the Search Results page, only users with Delete rights will see the Delete column
(otherwise is hidden).
The excel sheet will be created and you will be prompted asking if you would like to open, save,
or then cancel the operation. If you select open or save the metadata associated with the selected
objects will be visible within the excel file.
Note:
This does not export the actual object, but instead all of the data/info associated with that
object.
2. REPORTING
The Reporting link is accessible through the Upper Menu bars. Once clicked, you will be taken
to the Project Reports page.
The purpose of this page is to centrally manage all associated project reports. Visibility to the
folders and documents are based on the defined access rights.
2. Click the sign next to the report folder you would like to open.
3. The folder will open displaying in the right hand panel all subfolders and/or reports to
which you have access to and have a Display Name defined.
Note:
Files and folders that you do not have access are not be displayed. If you try to access
them directly (for example, bookmarked URL and so on) the system will not allow it.
– WBS
– Candidate Status
– Work Package ID
– Item
– SPO# /CBM#
– Days old
– Permission Zone
– Item → Work Package Details page with the relevant Work Item open
Also displayed is whether a Supplier PO and/or Customer Billing Milestone exist (or
not) for that item, the number of days the acceptance has been pending and the
permission zone the site belongs to.
Note:
Based on your user rights you may have access to one or both of these
sections.
You only will see those work packages containing the work item types (network
planning/site acquisition; construction works; implementation) that you have been
granted access to.
The Supplier PO and Customer Billing Milestone fields are only applicable for
projects using RTI (SAP – IPM interface).
Note:
Acceptance check boxes will remain unavailable until the WI has an actual date.
For RTI projects (SOG>1), acceptance tick box remains unavailable until SPO has been
aligned to “SPO #” field for WI.
Once selected, the system will automatically store the individual’s username and date.
The acceptance is saved only after the Update is clicked.
SPO #
Note:
Acceptance check boxes will remain unavailable until the WI has an actual date.
For RTI projects (SOG>1), acceptance check box remains unavailable until CBM
has been aligned to “CBM #” field for WI.
After selection, the system will automatically store the individual’s username and
date.
The acceptance is saved only after the Update is clicked.
After the BB rel. (manual or RTI) is completed, no changes are allowed to the Customer Billing
Milestone combo (if no value selected, the field remains editable until the selection made)
A pop-up window will appear asking if you would like to open, save, or cancel:
– Save –A file download pop-up window will appear asking you to specify the location
where you would like the export to be saved.
2. Select whether to open the file (without saving) or then save the file and then open.
4. The Excel export will be visible detailing the information from the Acceptances
required page.
4.1.2 HERA
HERA is the lead tool in productive use within OPS IDS. Today, HERA is used to manage all
projects that are having OEM components and are requiring pre-installation or pre-integration.
This is typically the case for systems like IMS or One-NDS.
The PMs will be able to find all the HERA SOs, which have been tracked in an IPM Work
Package (RTI or Manual) or a match on Customer Name is found.
The HERA button will re-direct the PM to the HERA Tool log-in in order to retrieve more
information about the Delivery Info for that particular order.
The HERA button will be also available in In Order Details Page as well Equipment Page, if the
HERA SO# is found in IPM.
4.2 My Tasks
4.2.2 My WIs
The access rights/visibility for the new link My WIs are:
User which is Resource for that IPM Project
The results will be displayed in search results grid with the capability to Update the fields and
Export to xls; no pagination and max 1000 records (ASIS)
Performance can be low if too many records are in the search.
Company assigned to that WI is equal to the current NOLS User Name’s Company
The results will be displayed in search result grid selected with the capability to update the fields
and Export to Excel; no pagination and maximum 1000 records will be displayed.
Performance can be low if too many records are in the search.
Custom fields may be text fields, dates, URLs, combo boxes with project specific selection, and check
boxes. The administration is done by the Project Key User in the Project Administration link. WP/WI
Custom fields can be localized at DWP/DWI level so that each field can have a different property for
called off WP/WI.
If a Custom Field (txt or combo) is set-up as Hide, then the field won’t be visible in:
User Interface
If a Custom Field (txt or combo) is set-up as Search, then the field will be visible in Site bar Search and
in the Advanced Search. A “More >> / << Less” link will be available in the Mass Update Work Item
Search page. After Clicking on that link, It will display more Search fields.
Search result page will open list of search record in smart table. The purpose of these
pages is to quickly update multiple work items, work packages, change requests, and
Custom data.
In the result table first row is column Name and sorting, second row is for filtering,
third one to enter data to be populated, fourth row is for column level selection to
populate data and reset. After this, records will be displayed.
The same business rules apply as on the Work Package Details page that is only the
fields/data/information which you have access to will be displayed and/or is
updatable.
Only those WPs to which the user has access to will be displayed.
If a WP is selected, the displayed WIs should be limited to only those included to that
WP.
The selected filter values of the last executed query are always displayed on the page
(above the query buttons).
Work Items from Cancelled Work Packages should not be visible in WI Mass Update
since they cannot be edited in WP details either.
Otherwise, it is possible to reset these values by selecting Clear All at the top of the
page. This will clear:
All filter selections
1. On the Mass Update – WP tab, specify the search parameters, only Mandatory field is Work
Package Name, the others are used to fine tune the search criteria.
2. Click Search. User will get records as per the following screen.
Export to Excel: For selected mandatory and optional filters user can able to export the
query results to an Excel file.
Populate: To populate the entered data to all the selected rows and columns.
Mass Update from DWP can be performed by clicking the relevant WPs and Update
(Update DWP).
Only the Custom fields not hidden for that Default Work Package will be available for
updating.
4.4.3 Mass Update – Work Items/Work Packages
After the Search has been executed and the results are displayed, it is possible to perform the
mass update. Performing a mass update will allow you to populate selected field values for
multiple rows.
To update multiple rows with the same value, perform the following steps:
1. Fill in the data entry row fields which you would like to mass populate to the identified
work packages (results displayed are based on your WI &WP Search)
2. Select/Clear all rows for updated by selecting the data entry row check
box or manually select all rows which you would like to have update with this
information.
3. Select the columns which you would like to have updated with this
information:
Editable fields will follow the same business rules as defined in the Work Package
Details page.
If you select a column without filling in a value for that column, an empty value will
be populated.
4. Click Populate.
All uncommitted changes (that is those changes which have not yet been saved to the system) are
highlighted with a blue background.
A column counter (displayed under the Reset text) displays how many rows have
uncommitted changes.
5. Review your proposed updates and when satisfied, click Update to save the changes to the
system.
6. When completed, a confirmation message will appear at the top of the page detailing the
number of updated rows. Additionally, a green checkmark will appear next to the successfully
updated rows.
Should any rows encounter validation errors, a yellow exclamation row marker is displayed
along with an error message at the top of the screen and behind the rows with the error.
1. Fill in the data to those fields you would like to populate to the identified
Work packages (results displayed are based on your WP Query)
2. See steps 4-6 in the earlier subsection.
Note:
Refresh refreshes the values for the selected rows from the database.
The Reset hyperlink returns the original query values for the respective column.
From the Mass Update - WI page, it is possible to mass trigger the Generate Planned,
Generate Forecast, and Update Forecast actions for the selected records. However, it
should be noted that this will update the whole Work Package even though on this page
only one Work Item is displayed.
Time Stamp work items can also be updated through Mass update WI page. However, TS
work items are not colored (like in a WP).
Cancelled Work Packages should be visible in WP Mass Update where Notes field can be
edited.
As CR related data size is huge, user can restrict the search by selecting Number of CRs in the
search criteria.
CR View can be also selected during search: NEW, Ready for Authorization, and Closed.
CR View and Number of CRs:
New - CR Status = New; Ready for Authorization is Null
Latest 200 CR records - listed in reverse CR ID order.
Ready for Authorization – CR Status = New; Ready for Authorization is not Null
Latest 200 CR records - listed in reverse CR ID order.
Closed – CR Status = Closed
Latest 200 CR Records – listed in reverse CR Closed Date order
After the search, user will be able to see the records as per the searched criteria.
Note: On this page some fields are always read-only (for example, Liability, Executing
Organization), and some functions cannot be performed (for example, Supplier selection, Internal
Rejection and Customer Rejection) so the user should select the CR ID hyperlink and update the
data record individually.
RECOMMENDATION – to use Google Chrome, for best performance.
Hyperlinks
Selecting the hyperlink will check the user access and, if passed, open the data record in
another browser window:
Customer Site Code
CR ID
CR WP
Original WP
The browser window for the Mass Update - Change Request page remains open, but any
changes committed in individual data records should be retrieved by re-selecting the
Query button.
Tool tips
Tooltips are applied to Column headings
Display the tooltips from the Edit Change Request pages
Tooltips are applied to result values
Tooltips are applied to CR ID – CR Name value
Tooltips are applied to CR Work Package Name – WP status from CR WP value
Buttons:
Query – Execute query
Excel Export – Export results to excel
Update – Updates all rows with any uncommitted changes
Clear All – Clears everything on the page
A moving tool tip on the data record will display Customer Site Code/Site Name/CR
Name, and also the field name for the check boxes.
This is to support navigation to the right side of the page, and correct data record updates.
8. Pop-up box
Selecting the information button will open a pop-up box, listing all the fields in read
mode for Change Request data record. Access control is as per user rights on the Edit
Change Request page.
9. Button actions
Query
Based on the values selected in the Optional filters and Column filters, each tab is
refreshed to display a maximum of 200 CR records that meet the tab business rules and
user permissions.
Any unsaved changes to the Change Requests records are discarded. The user will be
prompted about uncommitted changes.
The current tab is refreshed, and when selecting another tab the data for that tab is then
fetched.
The Optional Filter link is closed to the more link.
Query can also be selected after successful updates to enable the next set of data records
that meet the tab and filter criteria to be displayed.
Excel
Export to excel will Exports complete data to Excel and is presented with the Column
headings and data as displayed on the tabs.
Any unsaved changes to the Change Requests records are discarded. The user should be
prompted about uncommitted changes. Export to Excel should be as per user permissions.
Clear All
Will remove ALL the filters applied in the Optional Filter section, AND ALL filters
applied to the columns in EACH tab.
Discard any unsaved data, and refresh the page with saved data that meets that tab’s
criteria.
For example, if from the Ready for Authorization tab a CR is now in status Closed, it
will no longer be displayed on this tab.
It refreshes the page data as if the page has been opened through the Mass Update –
Change Requests link – runs the query again, and displays the New tab.
Update
Row level – (red box) – Tool tip on the box notifying the user of the validation
errors. Display the column heading(s) in red where uncommitted changes exist.
On the existing Mass Update WP and WI pages, the following validation notifications are
used, and they are utilized for Mass Update - Change Request page:
- committed change
Validation error – Error message text as per Edit Change Request page
Data and validation checks for mandatory fields – as per business rules on Edit Change
Request page.
4.4.5 Mass Update – Custom Data
Similarly we have Mass update Custom data search to update multiple custom data fields in a
single go.
User can perform following mass update operations from the Mass Update via Data File Page
present under Tools tab present in menu bar.
Update from DWP
Call-off WP
Both WP and WI Update
User can download the default template from the same page by selecting operation name present
under Download the Template to upload drop-down list.
Current limit on number of rows for ‘Update from DPW’ is 500 rows.
Current limit on number of rows for ‘Mass call-off WP’ is 1000 rows.
For this operation, first two rows are having field Names that is Cell A1, B1, and C1 will
have Project ID, DWP ID and WP ID respectively. Rest of the columns starting from Cell
D2 are for the WP and WI fields. If for the second row field name respective first row
field Cell is empty it means it’s WP field else respective WI ID field.
The Data File template can be created in Excel by adding following values per cell (must
be saved as anyname.xls):
Header:
1. A1 = Project ID
2. B1 =DWP ID
3. C1 = WP ID
D2 values: You can freely choose the number of work item/fields and add them to the
Data File as columns based on the following list of allowed fields.
Phase
Product Config
Dimension
Notes
Custom Date WP 1
Custom Date WP 2
Custom Date WP 3
Custom Date WP 4
Custom Text WP 1
Custom Text WP 2
Custom Text WP 3
Custom Text WP 4
Custom Text WP 5
Custom Text WP 6
Custom Check Box WP 1
Custom Combo WP 1
Custom Combo WP 2
Custom Combo WP 3
Custom Combo WP 4
Custom URL WP 1
(*) If the WI does not require a planned date, then the as-is business rule is still
valid, that is a planned date cannot be entered. Submitting a planned date through
Data File will lead to a validation error.
That all necessary data to satisfy the work item´s business rules are provided
within the uploaded Data File or within the work item and Data File. As an
example, now it´s not required to upload two times a data file in case the user
wants to update a work item with Forecast and Actual dates.
It is used the same Data File template, no changes were done at this level.
2. After uploading, wait until the Data File is processed by the backend, this can take
several minutes depending on queue position and file size. (Please consider several
minutes for bigger files)
NOTE: Every 40 seconds queued Processing tab data will get refreshed.
7. If errors are detected while processing, the Data file will be listed in the error tab
page. By clicking on the Data File name you can see error description, or in case of many
errors, download an error log file containing error details.
If no errors are found, the Data File will be listed in the processed tab.
Work item completion actual date cannot be Work item completion actual date and
provided simultaneously with completion forecast completion forecast date cannot be provided
date simultaneously in same row for WP
Work item internal acceptance date may not be Work item internal acceptance date may not be
later than today later than today
Work item completion actual date may not be later Work item completion actual date may not be
than today later than today
Actual date can be entered only within 7 days after Actual date can be entered only within 7 days
work completion after work completion
Work item customer acceptance date may not be Work item customer acceptance date may not
later than today be later than today
Internal Acceptance missing while trying to enter Internal Acceptance missing while trying to
GR in SAP enter GR in SAP
Customer Acceptance missing while trying to enter Customer Acceptance missing while trying to
Billing Block Released enter Billing Block Released
The valid format for Actual Start Time for work
The valid format for Actual Start Time for work item item is dd-MMM-yyyy HH:mm:ss. Please modify
is dd-MMM-yyyy HH:mm:ss. Please modify the field the field accordingly to proceed with the work
accordingly to proceed with the work item update item update
Invalid actual completion time 'xxxxxx' on work Invalid actual completion time 'xxxxxx' on work
item, valid range is 00:00 - 23:59 item, valid range is 00:00 - 23:59
Invalid planned completion time 'xxxxxxxx' on work Invalid planned completion time 'xxxxxxxx' on
item , valid range is 00:00 - 23:59 work item , valid range is 00:00 - 23:59
Customer billing milestone must be unique within a Customer billing milestone must be unique
work package. within a work package.
Supplier purchase order must be unique within a Supplier purchase order must be unique within a
work package. work package.
WBS is valid formats :If length is 17 valid format
is : "X-XXXX-XX-XX-XXXX", If length is 17 valid
SAP WBS format not acceptable format is : "G-XXXXXXXXX-XXX-XXX-XXXXX"
Could not process file. File not found! File cannot be processed
The uploader of the file %s is no more a valid IPM
user. File not processed! User is not authorized to update
No project ID found from cell A2. File not Project id is not given in .xls file and it is a
processed! mandatory field.
No project with ID found from IPM. File not Given project id is not a valid.
processed!
DWP ID is invalid Given DWP is invalid, DWP should be a number.
DWP does not belong to project. File not
processed! Given DWP is not in that project.
A non-valid WI number found from cell This
number does not exist in the DWP. File not
processed! Given work item id is not exist in given DWP.
User does not have access to project. File not
processed! User does not have access to project
User does not have write access to any zones in User does not have write access to any
project File not processed! permission zones in project
An unknown WI field identifier found from cell. File
not processed! Unknown WI field Name
Wi field should not be repeated for same work
Field is in multiple columns. File not processed! item
File has more than the allowed rows. File not File has more than the allowed rows (1000 max
processed! limit) which is configured in database.
File has more than the allowed columns. File not File has more than the allowed columns (10 max
processed! limit) which is configured in database.
No WP with ID exists in project. Row not
processed! Given work package is not exist in given project.
WP is not linked to DWP. Row not processed! Given WP is not linked to given DWP.
User is not authorized to update WP User does not have permission to update WP
Invalid (check box) value for (XXX) field. Row not Valid values for check box : 1 is for check, 0 is for
processed! un-check
WI# in WP cannot be modified, as it is not Active Given work item is not an active work item, In-
(N/A). Row not processed! active work items cannot be updatable.
WP does not have WI# , even as has been
submitted for it. Row not processed! Work item not belongs to work package
As per business rule planned date is disabled
As per business rule WI Completion Forecast
Date is disabled
As per business rule WI Completion Actual Date
is disabled
As per business rule WI Actual Start Time is
disabled
As per business rule WI Completion Actual Time
is disabled
As per business rule WI Completion Forecast
Time is disabled
As per business rule WI Completed By Person is
Field disabled due to business rules disabled
Note:
Data Files has a limit number of rows to be processed, up to 15,000 rows
including header.
When processing a row, if error is detected on one field, the whole row will be
skipped.
5. SITE FUNCTIONALITIES
5.1 Site Side Navigation Bar
The Site Side Navigation bar is only visible once a site has been selected (using the site search
functionality found on the project homepage).
Links displayed within this bar vary depending on access rights; however the default links are as
follows:
Customer Site Code – Shown behind the Site text, this takes users to the Site/Candidate
Details page.
2. If multiple results are found, you must select a site/candidate from the available list on the
Site Search Results page.
If, based on your search criteria, only one match is found you will automatically be redirected
to the Site Details page for that site.
3. On the Site Details page, the following information is displayed as read-only.
Site Details: This displays the basic geographical location for the site, site type, required user
permissions to view the page, customer site code and whether or not this site belongs to a cluster.
Candidate Information: This section displays the status of the candidate, its location as well as
the other basic information regarding equipment, building type, and ownership. From here it is
also possible to see whether or not a site folder exists yet for the site. User can switch between the
candidates for TK projects.
Access Info: Scrolling to the bottom of the Site Details page displays the necessary information
and/or instructions for accessing the site.
- Latitude Degrees (Search string is created from the following fields: Latitude degrees and
Longitude degrees)
- Latitude Decimal (Search string is created from the following fields: Latitude decimals and
Longitude decimals)
The reason for the varying links is the fact that the coordinate location may differ from the
address location. Should any of the locations be invalid (not found on the map application) then
the system will default to the other locations. For example, if the Address is clicked the system
will first try Decimals and then Degrees. Should these fail to produce a valid location, an error
message is displayed. When one of the links is selected, a pop-up message of the Site Map is
displayed:
The displayed map is dynamic with all normal map functions enabled (Zoom, Pan, Driving
Directions). By clicking on either the location link under the title or the site place marker on the
map, will open the Driving Directions controls.
If a contact exists for the site (it is possible to have multiple), their name, role and contact
information will be displayed.
If no contacts exist for the site, a “No Contacts Assigned” message is displayed:
To browse the project documentation folder, in the left panel the site folder tree should be visible.
Folder name = Customer Site Code
Default structure is maintained by the project administrator (Key User)
1. Click the sign next to the folder you would like to open.
The folder will open displaying in the right panel, all subfolders and/or documents to which you
have access to.
As the project and site level document management functionalities are similar, refer to the
Document Management chapter of this guide for additional functionalities.
3. Fill in the mandatory fields plus any/all optional fields. Mandatory fields include:
Permission Zone
Updated information will be saved to the system and the new “Site Details” page for the site will
open.
Note:
If a site is created in an Implementation (TI) project, the default candidate (A) will also
be created. It is only possible to have one candidate per each TI site.
– Candidate Level: Service area, country, customer, project, zone, system site
code, candidate, status changed date, candidate status, create site folder
You must select the zone from those which you have write access to (read access is not
enough)
When you select a region, the zone list is updated to only display those within the
selected region. If you select a zone first, the region it belongs to will automatically
populate.
There is NO link between the Permission Zone and the Project Region/Zone
The Customer Site Code must be unique within the project and its value is NOT case
sensitive.
Only one of the coordinate pairs (Degrees or Decimals) needs to be filled. The system
will automatically convert the degrees to decimals and vice versa.
After creating a Site/Candidate in IPM, we are able to track the following data through
the Reporting Solution:
i. Candidate Creation Date
Available for turnkey projects only, this functionality allows you to create multiple
candidates for a site.
The Site Details page for the new candidate will be displayed.
4. Fill in the mandatory field (Candidate ID) plus any/all optional fields.
You will be returned to the Site Details page with the new candidate information and a message
at the top of the page stating that your candidate was successfully created.
Note:
Candidate ID must be unique to that site (duplicates not allowed).
It is recommended to use alphabets rather than numbering for the candidate number. The
reason is that the system only supports a single character to this field. If you use numbers,
the maximum number of candidates would be 9, whereas if you use the alphabet you
would have up to 26 candidates.
Your project must be defined as a Turnkey project for you to create new sites.
For example, Candidate = 0 otherwise by default for the TI project the site
created will be candidate = A and no additional candidates can be created.
–Note that the Customer Site code and Permission Zone which you
specify for Candidate 0 will be the Customer Site code and Permission
Zone that will be used for all other candidates
– The System Site code for all candidates will stay the same as was
created for the nominal site
The Customer site code has to be unique for the IPM project.
The following candidate fields are automatically filled by the system and are
read-only:
– Service Area
– Country
– Customer
– Project
– Zone
– Site Folder
After the System Site Code is created, Customer Site Code and Permission Zone
are read-only.
It is possible for the project administrator (Key User) to update the Customer Site
Code and/or Permission Zone if required.
Changes are saved to the system, the page refreshed and an update notification displayed
at the top of the page.
Note:
Even with update rights, the Permission Zone and Customer Site Code fields
are read-only by default. To edit these, you must select the individual edit
buttons located next to the field. Once updated/saved, these become read-
only again.
If the Customer Site Code is updated, the site folder name/path will also be
updated.
The same business rules (for example, drop-down logistics) are the same as
when creating a site (previous chapter).
If you would like to update the details, remember to click Update before
you create another candidate otherwise your changes will be discarded.
2. Change the candidate status to either Rejected or On-Hold and fill in the Change
Reason (if these are not changed, an error message will appear).
3. Remove any associated links for the site (if not removed an error message will appear)
5. If you confirm the deletion, the selected site plus all related records/information will be
removed.
Note:
If multiple candidates exist for a site, the site delete button will NOT be
enabled till site is selected.
If site documentation exists for a deleted site, these folders are not removed by
default.
If you wish to delete the site folder, follow the instructions provided in the
document management chapter of this handbook to remove the folder contents
prior to deleting the site. Otherwise, contact your project administrator for
support.
6.2 Contacts
The contacts functionality are accessed through the Contact link found in the Site Side Navigation bar.
6.2.1 Create New Contact
To create a new contact in the IPM system:
1. On the Contacts page for the selected site, fill in the mandatory fields along with
any/all optional fields in the Create New Contact section in Contacts page. Mandatory
fields include:
Last name
First name
3. The new contact will be displayed in the Assigned Contacts section of the page with
its complete details available for editing.
Note:
To avoid creating duplicate entries, thoroughly check all available contacts carefully prior to
creating a new contact.
Contacts are not project specific, so contacts created here are visible for use in other projects.
After creation of contacts, it is not possible to delete the contacts (it can only be removed them
from the site).
On creating a contact, it will automatically be assigned to the selected candidate.
On updating a contact for the candidate, it will update the contact details for the project. (For
example, the contact details will be updated for all the sites holding the contact).
1. Select the contact(s) from the list of available contacts. (To select multiple contacts, hold
the CTRL button and click on the contacts you wish to add.)
Note:
The contacts are not project specific, so is allowed to be shared across programs.
2. On completion of all required updates, click Update available at the bottom of the
contact’s section.
3. Changes are then saved to the system and the page gets refreshed.
Note:
If any changes are made to a contact, those changes are reflected on all projects where
that contact is being used. Therefore, it is recommended not to modify the contacts until
the project administrator confirms (through reporting) the projects using that particular
contact.
It is only possible to update single contact at a time, as each contact has its own Update
button.
On trying to make changes to several contacts at one time, only the changes for the
contact whose update button is clicked will be saved.
6.2.4 Remove Assigned Contact
To remove an assigned contact from a site, perform the following steps:
1. On the Contacts page for the selected site, in the Assigned Contacts section, select
the contact to be removed from the site. (To select multiple contacts click on all those
contacts to be removed.)
Note:
On failure to click the Update button after the changes are made, the contacts
will still be visible on the Contacts page.
If you have access to the Change Management (ChM) module, the Change Requests link is
found in the Site Side Navigation Bar.
The purpose of the ChM module is to record any additional works and/or sellable additional
works required for the site. In other words, this module is used to track change/claim
management for the site.
6.3.1 Change Requests (Browse)
The purpose of the Change Requests page is to Initiate change requests, Copy change requests,
or View existing change requests on site. For each site, this is the ChM homepage from which
most activities occur and access the Work Package (WP) CR functionalities.
Note:
Change Requests link is always visible if you have one of the basic change requests
permissions (otherwise, link is not visible).
An exclamation mark is visible next to the Change Requests link on the navigation panel
if the site has a CR on any WP with a status other than Closed.
To create a new CR, click Create/Copy Change Request present on Change Requests page:
1. Select an Original WP from the drop-down list.
2. Click Create. A pop-up message will appear asking for confirmation
3. Click OK.
You will be directed to the WP Create Change Request page.
4. Clicking Cancel will end the operation and direct you back to the Change
Requests page.
Note:
Original WP field:
Shows WP ID and names sorted in ascending order.
Lists all WPs not having a CR WP Flag for the current site.
Shows only those accessible WPs.
Is visible to those having create rights.
Fields shown with “*” are mandatory fields.
CRs cannot be created for 0 candidates (Search Rings).
Currency by default is the Default Currency for the Project, and if there is no
Default Currency, then it is EUR; however, it is possible to select a different
value from the drop-down list if there are values that have been added to the
Project Currencies list (through Project Info).
Internal Approver drop-down list contains only the names of individuals
allowed to approve/authorize a CR on behalf of NOKIA NETWORKS for the
project.
Customer Approver (not shown), is only displayed if the Liability is equal to
the Customer Name. That drop-down list only shows the names of individuals
within the project who are allowed to approve/authorize the CR on behalf of the
Customer.
Call-off CR WP
4. Click OK. You will be directed to the WP Edit Change Request page.
5. Clicking Cancel will end the operation and return you to the Change Requests
page.
Note:
Original WP field:
Shows WP ID and names sorted in ascending order.
Lists all WPs for the current site which do not have a CR WP Flag or CR Closed Flag.
Reference CR field:
If this field is null, a new CR is created for the given Original WP.
If this field has a valid value, a copy of the existing Reference CR is created for the
specified Original WP.
No wildcards allowed.
It does not matter which site or site type the Reference CR is on. If the CR ID is typed
correctly and you have sufficient permissions, then the CR should be copied.
To view an existing CR, Click the CR ID hyperlink for the selected CR.
The WP Edit Change Request page will open.
Note:
CRs are grouped by the WP (original) to which they are linked to.
Both WPs and CRs are sorted in descending order (newest first).
If the CR has a CR WP attached, clicking the name hyperlink will open the WP
Details page.
To update an existing CR, perform the following steps:
Note:
2. Click Delete.
3. Click Ok (Clicking Cancel will end the operation and revert to the Change
Requests page).
Note:
It is possible to delete multiple CRs.
6.4 Quality
If you have access to the Quality module, the Quality link is found in the Site Side Navigation
bar.
The purpose of the quality pages is to track the site quality history including on-site training,
quality status during the course of work, assessments and/or customer Punchlists. Clicking on the
Quality link will navigate to the Site Quality page.
The purpose of the Site Quality page is to give an overview of the site quality activities. It is
possible to browse all open and closed deficiencies and associated project quality checklists, from
this page. For each site, this is the quality homepage from which most activities occur and/or get
access to site quality functionalities.
Note:
Depending on user rights, access is provided to one or more checklist types (Not all of
these sections may be visible all users).
1. Select the checklist that you would like to assign to the site from Assign a Project Checklist to
this Site section from Checklists drop-down list. The displayed checklists are project specific
and are maintained by the project administrator (Key User).
3. Select the Checklist Type (only those whose access has been granted, are visible from the drop-
down list).
4. Click Assign.
You will be returned to the Site Quality page where the new checklist is visible.
Note:
Only work packages you have access to for that site are visible in the drop-down list.
It is not possible to change the Checklist Type once it has been selected.
You must have create rights, otherwise The Assign Checklist to Site button and associated page
is not visible.
If a Deficiency Checklist is assigned to a site, the ID, Name and Opened Date are
displayed by default.
From this page it is possible to view: The checklist details (associated WP, opened date, opened by
organization, and assessment date/assessor for the other checklist types) and item information (open
deficiencies). In addition, one has the possibility to directly open and close defects as well as edit the WP
association to which work the checklist is related to.
Quality Item Comments field is not directly visible on this page. However, the View Checklist
page includes a tooltip functionality that becomes activated when user moves the mouse cursor on
top of the Quality Item text. The tooltip will display any possible text that has been entered to the
comments field.
Note:
If user only has Read rights for the checklist type, no Open/Close checkboxes will be
available.
If user has Update rights for the checklist type, the Item Description will be a
hyperlink through which the Deficiency page can be accessed in case the
deficiency:
If a defect has been assigned to a Responsible Company other than the one user
works for, no hyperlink will be displayed.
The Checklist Details section is mostly automated. Opened by, Opened by Co and Opened by
Org sections are automatically filled in, for cases where the IPM User is correctly linked to a
Resource entry within the IPM database.
The Opened by Person combo box must be manually filled in cases where the Opened by fields
are not automatically populated. It is enough that one chooses the person’s name and the
remaining fields are filled in by the system.
To modify the general checklist details after it has been assigned to a site, you need to:
1. Access the View Checklist page (see Chapter 6.4.3 for reference).
2. In the Checklist Details section, make the necessary changes to the editable
fields.
Based on you access rights, you may also have the possibility to update the
opened by company and/or person.
Note:
Opened date is the system date on which the checklist was assigned to a site
(edit/select is not possible).
Individuals having Restricted access rights to the checklist type are able to view
the Comments fields (otherwise these are hidden).
To update the assessment information, perform the following steps available on Self-
Assessment, Acceptance Punchlist and Assessment Checklist types:
1. On the “Site Quality” page, Click Edit located at the end of the selected checklist
row.
Optionally, the Assessment Details can be updated in the View Checklist page.
Note:
If an open deficiency exists for a site, a red exclamation mark is shown on the Site Side
Navigation bar next to the Quality link:
In the Site Quality page, all open deficiencies for the checklist type(s) you have access to
(belonging to the company or are unassigned) are shown at the top of the page in the
Open Deficiencies section.
Within this section, only the basic information is displayed for each deficiency including:
Item – This is the project item number having a default value based on project
default quality checklist.
Severity – Values range between 1-4 for deficiencies. These are defined in the
global organization per quality item with level one (1) being the most severe and
level four (4) the most minor.
Dates:
Opened – Date deficiency was reported.
Forecast – System generated date based on project default lead-
times for each severity level (for example, the default lead-time
for severity one (1) defects is typically 24hrs or one (1) day).
To view the more detailed information regarding the deficiency (for example, deficiency
description information), open the View Deficiency page. If a checklist has an open
defect on it, a red exclamation mark is also shown next to the checklist ID.
The purpose of this section is to store the historical information regarding deficiency
corrections done for the site. It is located on the Site Quality page. This section can be
accessed by clicking the Show Closed Deficiencies button at the top of the page under
the Open Deficiencies section.
Once clicked, the Closed Deficiencies section will appear.
Within this section, only the basic information will be displayed for each deficiency,
similar to Open Deficiencies section, including:
Item – This is the project item number and its default value is based on project
default quality checklist.
Severity – Value ranges between 1-4 for deficiencies. These are defined in the
global organization per quality item with level one (1) being the most severe and
level four (4) the most minor.
The purpose of this page is to present all details associated with a created deficiency.
3. Click the Item Description text which is a hyperlink to the open deficiency.
Deficiency section lists the information provided when the defect was raised (opened
date, description, responsibility, and due date)
Deficiency closing section: If the deficiency is open, this information will be blank. For
closed deficiencies, this section shows the closing details (organization which closed the
deficiency, date, and actions taken).
Note:
The following fields are only visible if you have Restricted visibility else its
hidden:
Deficiency Section: Opened by Org, Opened by Co, and Opened by.
If a defect is open, a close check box is displayed. If closed, the close date is
displayed.
SMS messages can be sent only to responsible persons with valid IPM
accounts with phone number, access rights, and other set-up. Message will be
sent 24 hours prior to the defect clearance due date and is valid for 48 hrs.
To be able to record a deficiency, you must first assign the associated checklist to the site
(see Chapter 5.3.2). Once assigned:
1. Access the View Checklists page by clicking the selected checklist name link.
2. Expand the quality folder tree to show the item you wish to record.
3. Select the checkbox Open for the item you wish to record a deficiency for.
4. Additional fields appears. These are used to assign the Responsible Person for the
deficiency and for providing additional details/comments.
5. To finish recording the deficiency, fill in all/some/or only the mandatory information:
Mandatory Field:
6. Click Update found at the bottom of the page as well as after the checklist header
details.
Note:
User will be redirected to Edit Deficiency page if they open only one
deficiency or else user will be in same page.
Opened date is automatically populated (system date).
Responsible Person field is only visible if the defect has been assigned to the
company (Responsible Co) or if they are working for NOKIA NETWORKS
and have Restricted permissions.
SMS defect closure functions also works in the same manner and same fields
will be populated except Description.
2. Fill in and/or update the required information (the responsible org field is mandatory).
2.Select Ok (clicking cancel will end the operation and revert to the Record or Edit
Deficiency page).
Note:
If there are documents linked to a quality item, when collapsed (Initial state), five
most recently modified documents will be shown.
Only those documents to which user has access to are displayed based on
document permissions.
If a site folder has not been created for the site and the add document button is
pressed, an error message will appear at the top of the page.
If you try to upload more than ten (10) documents, an error message is shown.
Only documents having the quality item attribute (such as, those created within
the quality module) are visible in the Deficiency page (not the whole content of
the Quality folder).
The Quality Subfolder including contents are visible in the Site Documentation
folder structure.
It is possible to add documents from the Site Documentation area to the Quality
subfolder. However, documents/folders added in the Site Documentation area are
not shown in the Deficiency page (as they do not have the quality item attribute).
To delete a deficiency:
2. Click Delete” found at the bottom of the page (under the Deficiency Closing section).
A confirmation window will appear.
. After the confirmation of the deletion, the selected deficiency and all related
information will be deleted and you will be directed to the Site Quality page.
2. Fill all/some/only the mandatory information for the newly appeared fields.
Optionally, one can open the Deficiency page through the Item Description hyperlink:
1. Fill in all/some/only the mandatory information in the Close Deficiency
Section:
A message will be displayed at the top of the page informing about the successful
update.
To export a quality checklist to excel you will need to save the export template to your
computer prior to completing the following steps:
1. Click the Export button behind the checklist to be exported on the Site Quality page
(for the selected site).
2. Click Browse to select the export template that you saved to your computer.
4. Once you have selected the template (and it shows in the template file window), click
Export.
5. The file download pop-up window will appear asking if you would like to open, save
or cancel this operation.
Open – Selecting this option will open the exported excel in a new
window.
Save – Selecting this option a File Download pop-up will appear asking
you to specify the location where you would like the export saved data.
Note:
You cannot export unless you have the export template.
When you export the checklist, the default name = checklist – [checklist
number].xls
To be able to import a site checklist, you must first save the exported checklist to your
computer.
1. In the exported excel sheet, all fields normally displayed in the Deficiency page are
shown. Using this excel it is possible to record a new deficiency, edit an existing
deficiency and/or, close existing deficiencies in an offline mode.
2. Once you have filled in and/or updated all required information, .click Save.
3. When you are ready to upload the checklist back to IPM, enter the Site Quality page
for the selected site.
7. Once you have found the correct checklist (and it is visible in the file import field),
click Import.
The Validate Imported Checklist page will be displayed. On the page, two sections are
displayed:
Checklist Details: This read-only section shows the Checklist ID, Name,
and Type.
8. In the Modified Checklist Items section, check if all information displayed is correct
and if all mandatory fields have been filled in (see previous deficiency chapters for
complete list).
9. Once all information has been filled in the correct format and validated, click Submit.
11. If there is a problem, an error message will be displayed at the top of the page (For
example, if a mandatory field is left empty, an error message will be displayed).
If the import is successful, you will be returned to the Site Quality page and a message
will be displayed at the top of the page displaying the number of deficiencies recorded,
updated, and/or closed.
Note:
It is not possible to update deficiency details for defects that are closed. On trying, the
following messages will be shown:
The error message will be displayed if you try to update read-only fields.
It is possible for others to modify the checklist in IPM from the time you have
exported; therefore, it is strongly recommended that you carefully validate all
modified information prior to clicking Submit.
When importing a checklist only those fields which have been modified and
mandatory fields are displayed for validation (for example, you must modify
non-mandatory fields in order to display them in the Validation page).
The purpose of the configuration pages is to provide basic information regarding the planned
and/or installed configurations on WP level (including Civil Works related configurations).
6.5.1 View Site Configuration
To view the details of an existing site configuration, perform the
following steps:
1. On the Site Configurations page, click the More link or Edit located behind the
configuration that you would like to view.
4. You will be returned to the Site Configurations page with the new configuration now
being displayed.
Note:
2. Fill in all Optional fields and the Mandatory fields. Custom ID (CID) is optional and
can be used to identify the Ae System.
You will be directed to the Site Configurations page with the new configuration now
being displayed.
Note:
It is not mandatory to link to a WP (although recommended). Additionally, IPM
supports multiple WP linkages.
Once the antenna is created, it is no longer possible to edit the Equipment type.
To add additional sectors, first save and then edit the page – You will now have
the ability to add new sectors.
1. On the Site Configurations page, click Edit. The Edit page will open.
4. Changes are updated in the system, page is refreshed and updated notification is
displayed at the top of the page.
Once a WP has been called-off to a site, the actual planning or work can be done. The purpose of the
work package page is to provide information regarding the planned/actual work as well as information on
milestone (work item) levels for progress tracking and follow-up.
6.6.1 Navigation
The WP top Menu bar is only visible once a WP has been selected for a site. Links shown
within this bar varies depending on access rights; however the default link provides WP
details.
6.6.2 Browse Work Packages
It is possible to browse all existing work packages for a site from the Work Package
page.
Depending on your access rights, it is from this page that you will be able to call-off new
work package and/or view/edit/delete existing work packages.
6.6.3 Work Package Details (View)
To view the details of a WP, perform the following steps:
1. In the Work Packages page, select an existing WP that you want to view.
Work Package Details: This displays the basic information pertaining to the
WP.
Work Item Details: This section includes the Work item description, Progress
dates, Responsibility, Certification and any Additional notes/info that the project
would like to be displayed.
6.6.4 Call-Off
Within IPM, the Project Administrator is responsible for setting up a series of Default
Work Packages (DWP) according to the defined project scope/sales packages. When
calling-off a new work package for a site, only those default WPs having access to are
displayed. The DWP set-up is defined in greater detail in the IPM Administrator Guide.
To call-off a new work package for the site:
1. On the Work Packages page for the selected site, click the Call-off work package
link at the top of the page.
The Call-off Work Package page will be displayed showing those WP which you have
been granted access to.
2. Select the WP to be added on the site and click Call-Off present at the bottom of the
page.
The Work Package Details page will be displayed (see previous chapter).
The information will be updated, page will be refreshed and WP update notification will
be displayed at the top of the page.
Note:
By default, the WP status is set to Created upon creation.
Network Planning and Site Acquisition Work Packages (NWP and SA WP)
Call-off is allowed for all candidate IDs.
WPs contain:
Call-off is only allowed if the candidate ID is not 0.
Information will be updated in the system, the page will be refreshed and updates
notification will be displayed at the top of the page.
4. For Audit information, Audit info link is available in WP under expanded view of
Work Item. Once user clicks that link, pop-up window will appear with audit details.
User can see when the following fields were updated and by whom:
Planned date
Forecast date
Actual date
Person and Company
Applies to both Site and Project level WPs for last six months only. It should be
displayed even when updates happen from Mass update WI search or Mass update by
data file for the mentioned fields.
Note:
CR WP Flag
If a WP has been linked to a CR record as Original WP or CR WP this flag is
not selected and read-only. Only if the CR link is removed, the flag will
become editable again.
Partial Payment WP
Marks the WP for having partial payments.
Default value is taken from the DWP at call-off (non-editable).
If selected, the SPT section is enabled for the WP.
If selected, it is possible to remove if no
SPO number is recorded to any SPT WI.
Payment internally accepted to any SPT WI.
SPB Released (SAP) to SPT WI.
If SPT selection is cleared, the associated fields remain hidden (those fields
defined in the expand section).
Purpose: When creating a CR, a WP with this Flag applied is not available to
select as Original WP.
N/A Flag
Allows you to mark a work item as non-applicable.
Capability, through a check box on top of the column, to select all the
illegible work items as N/A.
This will disable all work item fields and mark this row to be skipped in the
planned/forecast date auto populated/updated.
Removing a N/A Flag will make the fields editable again.
It is not possible to mark a work item as N/A if it has an actual date or
invoicing trigger linked to it.
Once a work item is marked as N/A, it is no longer visible in the list.
It is possible to view all N/A items by clicking the All link located above the
N/A column.
All N/A items are dimmed and are read-only until the N/A Flag is removed.
N/A items are not visible on the Order Details or Mass Update pages.
SMS Column
IPM is enabled with the possibility to send SMS messages to the responsible
person of the work item and to allow them to updated start and end times as
well as forecast dates. Also reassignment of the work is possible through
SMS.
If automatic sending is enabled, messages will be sent 24 hours prior to the
item forecast date.
Messages can be sent manually by selecting the check box for the work item
in the SMS column.
Red exclamation mark means that only manual messaging is enabled for this
particular work item.
Green exclamation mark is an indication that at least one (possibly multiple)
message(s) has been sent from the item. Additionally, this has a tooltip
showing all of the SMS messages sent from the work item. This becomes
visible when mouse cursor is set on top of the area.
If an SMS is sent the following fields will become read-only: Forecast,
Actual, SMS check box, Actual Start Time, and Actual Compl. Time.
All SSPs are rejected. The entire Sales Order’s background will be ORANGE.
The Sales Order number may be cleared; thus, disassociating the work
package from the Sales Order.
If the Sales Order number is cleared, all Customer Billing Milestone and
Supplier Purchase Order associations on all of the work package’s items will
also be cleared.
If the work package has multiple customer purchase orders, only the first one
is considered. (There can be max 10 customer POs).
Work Package WBS Code
When a sales order number is entered for the work package’s only (or first)
customer purchase order, the system looks up the WBS code for that sales
order number from the data in the SAP Staging Area.
If the work package’s WBS code field is empty, the system sets this to the
value found from the sales order (see previous step).
If the work package’s WBS code is already the same as the sales order’s
code, no action is taken.
If the work package’s WBS code is different than the WBS code of the sales
order, this is clearly and visibly flagged to the user but the system takes no
action and preserves the existing value—both the work package’s existing
value and the value from the sales order are displayed clearly and the user
may update the value as desired.
If the work package has more than 1 SO linked to it with a different WBS
code, the field will be filled in with the text MULTI.
When a WP is called-off from call off work package page, the SAP WBS
code field is always editable and value in the field is null.
Completion Dates
If the DWP requires a planned date and no dates have yet been filled in the
Work Item section, only the “Completion Planned” dates are editable (others
are non-editable).
Once the Actual completion date for the work item has been filled, the
“Completion Forecast” date will be read-only (however, this lock can be
reversed by deleting the Actual date).
Work Package Completed Date
This date cannot be edited by a user.
The work package closed date is set by the system according to the following
rules:
– When all Work Items for a selected Work Package are completed
(that is at the time when the last work item is marked completed), the
current date is set as the work package’s completed date.
– If, for a completed Work Package, any of the already completed
Work Items is reopened, the work package’s completed date is
cleared.
– If, for a completed Work Package, any of the Work Item completion
dates is updated, the work package’s completion date is updated to be
the current date.
For RTI projects (SOG>1) acceptance, check box remains unavailable until
SPO has been aligned to “SPO #” field for WI.
The GR is only enabled when the Internal Acceptance has been completed.
For RTI projects (SOG>1) acceptance, check box remains unavailable until
CBM has been aligned to “CBM #” field for WI.
The billing block released date is only enabled when the Customer
Acceptance has been completed.
Note that there is NO business rules that specify which acceptance should be
done first as this is project specific (in case the milestone is both a supplier
and customer invoice trigger).
Later changes are done to the DWP, including changes (additions, removals,
etc) to the DWP’s DM WIs – including changes to Reviewers and
Approvers.
In the “DM Work Items” page, if one now links (using the “Add’) a
document to one of the DM WIs, then that document will get the Reviewers
and Approvers ad they are in the DWP as per the latest updates.
progress of the project from start to closure including mandatory Mass Rollout work
items.
Project work packages can be searched from IPM Home page by using the Work Package
Id.
In the below screenshot we can see Product Details section of PWP for SUS Care. All the
fields marked in * are mandatory fields and needs to be filled.
To generate the Completion Planned date (for items requiring a planned date), perform
the following steps:
1. In the Work Items section, fill in the Completion Planned date for the first work
item.
All subsequent work items’ Completion Planned date will be populated based on the
default lead times and the fields will turn read-only.
Note:
This functionality finds the last available value in the tree in the planned column.
Last available value in the planned column can be either of the following:
Manually entered just before using Generate Planned button (without
saving the value to the database).
A value that was saved to the work item earlier. In this case column is read-
only.
Beginning from the starting value (row), the function calculates a date for each
Work Item row = the previous work item’s date plus the lead time.
After the button is pressed the column is read-only and cannot be changed.
3. All subsequent work items’ Completion Forecast date will be populated based on the
default lead times and the page will be refreshed.
Note:
This functionality finds the last non-empty value in the forecast column which is not
situated above a locked row.
If no such row exists, an error message is displayed.
If such row exists, the system goes down the list starting from the next row and
calculates a forecast time for each work item so that the row's forecast date
becomes the previous date plus the default lead time.
If the last work item has a date, pressing the Generate Forecast button will do nothing.
1. In the Work Items section, fill in the Completion Actual date for the work item
(optional).
All subsequent work items’ Completion Forecast date will be populated based on the
actual completion date + default lead times and the page will be refreshed. The work
items may have sequential or parallel scheduling.
Note:
The Completion Actual field will only be shown for those work items having a
Completion Forecast date listed.
This functionality finds the last non-empty value in the actual column:
If actual completion date is found, the system goes down the forecast
column starting from the next row and calculates a new time for each
work item forecast date (actual date + default lead time)
If the last work item has a locked date, pressing the Update Forecast
button will do nothing.
A pop-up window will be displayed showing all matching objects within that Site folder
which match the criteria and are not yet attached to another work item. Select the object
to associate with the work item.
3. Once associated, the status of the object will be displayed (see screen shot).
Note:
For documents, if there is more than one applicable workflow date, the last to one
be completed is shown, for example:
Doc 1 workflow date = 02 Feb 2009 (Int Approval Required / ext
Approval N/A).
Doc 2 workflow date = 31 Jan 2009 (Review & Int Approval Required /
Ext approval N/A).
Doc 3 workflow date = 20 Feb 2009 (Int Approval & Ext Approval
Required / review N/A).
All fields are read-only and populated based on the selected DWP WI default
values.
The N/A check box will be dimmed (only marking the WI applicable in
the WI page will make this check box editable again).
The SMS checkbox becomes editable if the item has a forecast date (today or in
the future), responsible person with adequate access rights and IPM account with
a phone number. Additionally the project must have a time zone set for it in the
project set-up pages.
After the message is sent the receiver has 48h time to reply. IPM can receive the
item start time (field: Actual Start Time) as well as end time such as, Actual Date
+ Actual Compl. Time. In addition, the item forecast date can be adjusted with an
SMS reply as well as the work being reassigned to another person.
Reply SMS in most cases needs only one letter and no IDs.
When the work completion message is received, the fields Person and Company
are set to read only.
SMS entries for the work item will be made read-only, and can only be changed
via IPM Support with a valid approval.
Access rights are validated when messages are sent, as well as when they are
received back to IPM.
Red exclamation mark means that only manual messaging is enabled for this
particular work item.
One user can have 16 concurrent SMS dialogues on-going. The 17th message will
be delivered once one of the earlier messages has been answered.
Once actual date is entered and WP updated, actual date becomes non-editable
and Actual Compl. Time is automatically populated based on the current time.
Actual date cannot be older than seven days, such as, actual date needs to be
entered within seven days after work completion.
Note:
Current date can be entered to the actual field by hovering on the field.
Both actual date and actual compl. time fields become non-editable once actual
date is entered and WP updated.
A pop-up window will appear asking if you would like to open, save or cancel:
Open – Selecting this option will open the file in a new window.
Save – Selecting this option, a File Download pop-up will appear asking you to
specify the location where you would like the export saved.
2. Select whether to open the file (without saving) or to save the file and then open.
The excel export will be visible displaying the work package details on the following
three sheets:
Work Items
6.6.13 Remove
To remove a work package from a site, perform the following steps:
1. On the Work Packages page, select those WPs you wish to remove.
3. The WP (along with all associated records/information) will be removed and the page
will be refreshed.
Note:
A WP cannot be deleted, if it has an associated Site Log, CR, Customer Purchase
Order, or Quality Checklist.
No confirmation message is given when deleting a work package.
Remove button will not be visible if you do not have the associated delete
permissions.
WP are sorted by Name and WP status.
If all the WP are in the same status, the WPID will be used to sort the packages
in descending order.
Automatic Updates:
Once the Actual date of the Master WI is filled, IPM to perform the following
actions for each Linked WI(s) (they can be in the same WP or in Slaves).
IPM to copy/populate the Planned (if foreseen)/Forecast/Actual Date,
copying/transferring it from the Master WI, if null in the Linked WI(s) (if not
greyed out in the UI, dependency required/permission zones/SPP to be
validated).
Once the IA/CA is filled in in the Master WI, IPM to perform the following actions
for each Linked WI(s) (they can be in the same WP or in Slaves).
IPM to copy/populate the IA/CA acceptance data (check box + time stamp +
username), copying/transferring it from the Master WI, if null for the Linked
WI(s) (WI set up as SIT/CIT) without breaking any rules, and eventually send
RTI IDOC if enabled for that particular item.
IPM to reverse/erase the IA/CA acceptance data (check box + time stamp +
username) w/o breaking any rules (if not greyed out in the UI, access rights on
Permission Zone to be validated) if the Linked WI(s) IA/CA Date is = Master WI
IA/CA Date as well the Username
IPM to consider the highest value in case we have more than one successful update
on the same WI.
After having done the DWP setting, we can link the Slave WP to a Master in two
way:
Call-Off button
Manual Linkage
If the Call-Off button is pushed, IPM will open the Call-off Work Package page for
selecting the WP to be linked to the Master (as Slave).
In case the WP # is updated directly to the WP # field in the “Linked WPs” section,
IPM after the UPDATE button is pushed, performs the following check prior to
committing the transaction:
Once the validation is successful, IPM to link the Linked WP to the Master WP and
fill in the Master WP and Linked WPs data in the new section as described earlier.
In case of (retrospective) manual linkage, then IPM posts ONLY the Actual Date to the
Slaves w/o breaking any rules just after the UPDATE. After this initial transaction the auto-
updates will continue normally, such as, whenever an Actual Date, IA or CA is added or
removed, IPM needs to investigate whether auto-updates to linked WIs are needed.
The Call Off on DWI level will enable the following Call-Off button in the WP.
If I want to link a WP to the WI, Call-Off button should be used and picked up the
right WP
NOTE: The Actual Date of the WI which has been linked to a WP won’t be editable.
The Actual Date will be filled in by IPM automatically once the Linked WP
Completion date is filled in automatically by IPM. If Forecast Date, as well Planned
Date if required, are null, then IPM to copy the same date in the WI. If for any reason
The Links Side Navigation bar is only visible once a link has been selected (either by
selecting on a site or then by using the link search functionality found on the project
homepage).
Once selected, the Site Side Navigation bar is replaced with the Transmission Links side
navigation bar. From here it is possible to access the A or B end (site details page) for the
link.
To view a new transmission link for the site, perform the following steps:
2. Click View.
The Transmission Links Details page will appear. On the details page, the following
information is displayed as read-only.
Link Details – General information pertaining to the link: ID, status, type, name,
priority frequency, remarks, and so on.
Link Map – Shows the link between the end points on a map. On clicking the
place markers on the map, user can navigate to the respective site.
WP Association – Associates the link with the relevant work package (optional).
Note:
Site map is defined based on the site/candidate locations. The order in which the
locations are checked for validity is:
Decimal coordinates, Degree coordinates, Address - if none are valid, no link
map is shown.
1. In the View Transmission Links page, fill in the Customer Site Code and Candidate
ID for the link and click Create.
The Transmission Links Details page will be displayed along with the successfully
created notification.
Note:
When creating a link on a site, it will be by default the A-end of the Link.
You cannot create a Link to the same Candidate (creating a link with itself).
You cannot create a duplicate link (or reverse link)! (A<>B vs. B<>A).
5. Changes are updated in the system, page is refreshed and an update notification is
displayed at the top of the page.
Note:
Link ID is a system generated field and cannot be edited (only visible from the
View Transmission Links page.
It is not possible to change the A or B end site (can only be deleted and re-
created).
Note:
If Link has Link folder, it is not deleted (this must be deleted manually prior to
deleting the link).
2. Click the sign next to the folder you would like to open.
The folder will open displaying in the right panel all subfolders and/or documents to
which you have access to.
As the project and site level document management functionalities are similar, refer to
the Document Management chapter of this guide for additional functionalities.
6.8 Health & Safety
If you have access to the Health & Safety (H&S) module, the Health & Safety link is found in
the Site Side Navigation bar.
The purpose of the H&S pages is to record any health and safety information, potential/existing
hazards and risks found on the site. Clicking on the Health & Safety link will take you to the
Health & Safety Information page.
The Health & Safety Information page will be displayed. On this page, the following
information is displayed as read-only:
Candidate H&S Info – General information about the type of H&S assessment
to have taken place as well as who provided the information and if any additional
information has been requested.
Site Info – This section details the emergency/accident procedures, rules and
other welfare/environmental information for the site.
Risk Assessment – Any potential risks found at the site should be documented
here as well as the risk type, rating and any provisions necessary.
H&S Hazards – This section documents any hazards currently existing on a site.
Information stored here includes: Type, Instructions, Affected parties, and
Control measures as well as when it was created and cleared.
2. Click Update Health & Safety Information (located after the Site Information
section).
Note:
The H&S module is not available for zero candidates.
6.8.4 Create Risk Assessment
To create a Risk Assessment for the site, perform the following steps:
1. In the Risk Assessment section, click Create a new risk assessment link.
The assessment will be saved with the date and username filled in automatically.
Note:
The Risk Assessment ID is automatically assigned by IPM when you click the update button.
The Document Reference and Assessment Provisions are project specific and maintained
by the project administrator.
3. When you have made all required updates, click Update Assessments located
beneath the Risk Assessment section.
Changes will be saved to the system, page will be refreshed and an update
notification will be displayed at the top of the page.
2. The risk assessment will be removed, page will be refreshed and a deletion
notification will be displayed at the top of the page.
Note:
No confirmations are given on clicking delete.
1. In the Risk Assessment section, click the Create new health & safety
hazard link.
People affected – Who does this hazard affect, for example, self,
self and others, and so on.
5. The hazard will be saved with the date and username filled in automatically.
Note:
The Hazard ID is automatically assigned by IPM on clicking Update button.
The Cleared by/Date Cleared fields will remain blank until the Corrective
Actions field has been filled.
3. When you have made all required updates, click the Update Hazards button
located beneath the H&S Hazard section.
Changes will be saved to the system, page will be refreshed and the update
notification will be displayed at the top of the page.
Note:
Once you fill in the Corrective Actions Taken field, the Cleared by/Date
Cleared fields will automatically populate with the current date + your user
name and will no longer be editable.
The hazard will be removed, page will be refreshed and a deletion message will be
displayed at the top of the page.
Note:
No confirmation is given prior to deleting.
If you have access to the Site Logs functionality, the Site Logs link is found in the Work Package Side
Navigation bar.
The purpose of the Site Logs pages is to provide a notebook like feature to record any daily actions,
issues, and so on, for the site. Clicking on this link will take you to the Site Logs page.
Note:
If no Site Logs currently exists; a message will be displayed on the page.
The information is saved, page is refreshed and the creation message is displayed at the top of the
page.
Note:
It is only possible to create Site Logs for non-0 candidates.
A work package with associated Site Logs cannot be deleted until these are removed.
Work Item subtype is mandatory if the Work Item type field has been filled in.
A site log’s associated work package may not be changed after the site log has been created.
It will be possible to add site level documents linked to Site Logs. A new Add Document will be
available for this purpose on the Edit Site Log page.
The information will be saved, page will be refreshed and an update notification will be displayed at
the top of the page.
2. On confirming the deletion, the site log (and all associated information) will be deleted and the
page will be refreshed.
7.2.1 Navigation
The Create CR link:
Is visible if the WP is not a CR WP.
No CR currently exists
Directs to the Edit Change Request page if:
WP is an Original WP with 1 CR
CR WP
Directs to the Change Requests page if:
WP is an Original WP with more than 1 CR
2. Fill in the mandatory fields plus any/all optional fields. Mandatory fields include:
Cost Estimate – Initial estimate of how much the change will potentially cost the project.
3. Once you have filled in all of the desired information, click Create.
The Edit Change Request page will be displayed with the saved information.
Note:
CRs cannot be created for zero candidates (Search rings)
‘Currency’ is the default currency for the project, and if there is no Default Currency it is
EUR; however, it is possible to select a different value from the drop-down list.
Scroll Down if there are values that have been added to the Project currencies list (using
Project Info)
Internal Approver drop-down list contains only the names of individuals allowed to
approve / authorize a CR on behalf of NOKIA Networks for the project.
Customer Approver (not shown), is only displayed if the ‘Liability’ is equal to the
Customer name. That drop-down list only displays the names of individuals within the
project allowed to approve/authorize the CR on behalf of the Customer.
For a Default Work Package to be available for call-off it has to be in ‘Active’ status and
have the CR WP check box selected.
4. The information will be updated as follows and the page gets refreshed as shown in the
following screenshot.
It is possible to have up to five (5) suppliers for a single CR. Click the Add Supplier link
to add a new section (Supplier, Custom Field 3, VOA Number and VOA Line Number).
Once there are five (5) suppliers, the link is no longer visible.
If you want to remove a supplier, merely change the Supplier value back to ‘(none)’ and
click the Update button (Supplier will be removed along with all associated information).
Authorizations section
If Liability = Customer (name), then the additional Customer Authorization fields are
also displayed: Discussions Started, Recorded by and Recorded date.
Note: Recorded info (by and date) are visible as Tooltips on the Authorizer labels, and
visible to users with Res or Administrator rights.
Documentation section
Related Defects section
This section will display those defects linked to the site which are available for linking to
the CR.
Only those quality checklists/items are displayed which have been associated with that
site.
An exclamation mark is displayed next to the quality item if the defect is still open.
7.2.4 Select CR WP
To select a CR WP (existing in drop-down list), perform the following steps:
1. Select a value from the drop-down list.
2. Click Update .
Note:
Only WPs having the CR WP Flag and not already linked to a CR are displayed as values.
Only existing WPs which do not have a CR already attached to it and/or SAP data will be
displayed in the drop-down list.
It is possible to change the WP up until the Ready for Ordering flag has been selected. Once
selected, this becomes read-only.
7.2.5 Call-Off CR WP
Follow these steps to call-off a CR WP:
1. Click the Call-Off Work Package link
2. Click Ok (clicking Cancel will end the operation and return you to the Edit Change Request
page).
Note:
If the CR has a CR WP already selected, the Call-Off Work Package link is not displayed.
Proceeding to the call-off will result in any unsaved changes to be lost (so save your page
prior to clicking)
If you click the back button and perform any operation there, then an error message
will appear.
The listing of available WPs for call-off is limited to those having the CR WP flag.
If only one WP with this flag exists, then the call off is done automatically.
2. Select Ok (clicking cancel will end the operation and return you to the Edit Change Request
page).
4. Fill in any optional information (name / description) and any mandatory (document type)
Note:
If there are documents linked to a CR, when collapsed (Initial state), five most recently
modified documents will get displayed.
Only those documents which user can access will get displayed (based on doc ACLs)
If you try to upload more than ten (10) documents, an error message is displayed.
Only documents having the CR ID attribute (that is those created from the Edit CR page)
are visible in the Edit CR page (not the whole content of the CR document folder).
The CR Subfolder (including contents) are visible in the Site Documentation folder
structure.
It is possible to add documents from the Site Documentation area to the CR subfolder.
However, documents/folders added in the Site Documentation area are not displayed in
the Edit CR page (as they do not have the CR ID attribute).
Order Details page can be accessed through the tab at the top or through the navigation link
to the left of the page. These are highlighted in red if the WP has one or more unlinked
objects, and in orange, if SO is cancelled in SAP.
More/Less link in RTI CPO section is highlighted in red or orange according to the color of
Order Details tab, refer the page shown above. The RTI CPO section opens by default when
accessing Order Details page, if there is at least one item not linked to the WP, which is
Order Details tab highlighted in red. The following screenshot explains this:
Create RTI CPO button is available. Max RTI CPO per WP is 15, along with Sales Order Groups.
SOG Name can be given in order to better recognize the service for the SO
SPO value, currency and creation date are displayed in the SPO value section
Manual CPO section can be used for manual order tracking. These fields are not checked for
validations by the system. Maximum numbers of rows are 15.
Linked WPs/Master WP section between Manual CPO and WI section, will display the WP#,
CSC, Site Name, Master WI# of the WP linked to it. The following screenshot explains this:
More/Less link: Displayed, if the WI has a SPT, or if RTI4 messaging has been activated
for the WI: IA/CA Message and (SAP Confirmation) IDOC#
Note:
SO # and SvO # fields in RTI CPO section are unavailable, if either customer acceptance
or internal acceptance has been performed for one of the WIs in the WP and one of the WIs
belongs to the particular SOG
Delete check box for RTI CPO row is enabled when
RTI CPO has no linked SvO (‘SvO #’ is empty)
RTI CPO has no related WI (based on SOG#), which would have a (selected
and) locked CIT, SIT or SPT, or an un-editable SO Group
If the RTI CPO is deleted by the user (that is user selects the check box and
clicks Update), IPM has to set SO Group as ‘0/null’ to all the WIs that were
linked to the RTI CPO(s) just deleted (user can delete more than one at the
same time) and automatically un check any selected CIT/SIT/SPT.
SO Group is disabled, if CBM or SPO exists or SPT field is disabled.
By changing the SOG from 1 to 0 in the WI the CIT, SIT and SPT will be unchecked and
dimmed. Additionally, SPT related fields are emptied and hidden.
The CIT (Customer Invoice Trigger) is unavailable when there is data linked to the
following fields:
Customer Acceptance
BB Released (RTI or manual)
Cust. Billing Mlst.
Manual CBM #
The SIT (Supplier Invoice Trigger) is unavailable when there is data linked to the
following fields:
SPO # (RTI)
Manual SPO # (SAP/Manual)
Internal acceptance
GR Date (RTI or manual)
SPT:
WIs cannot have SPT, if none of the WIs in the WP has SIT.
SPT is unavailable, if one or more of the following fields have the following
value:
Order Details tab WI section:
Supplier Payment PO
WI Details tab WI section:
Pymt Internally Accepted
SPB Released (SAP)
For RTI Projects and SOG=0, if CIT/SIT are select, IPM will display only manual fields such as
GR/BBR.
Tool tip is available for many of the fields in Order details page. If the tool tip displayed is
depending on the browser used.
Only user groups with SAP permissions (Extended permission SAP user group linked to Work
Item type and Work Item level permissions (Read or Update)) will have access to Order Details
page.
Equipment page displays the equipment delivery information, based on RTI Sales Orders that are linked
to the WP:
Sales Order Group (SOG): Grouping of work items according to SAP Sales Orders
Customer Purchase Order data, SO number, Latest delivery date (LDD) and SVO#
All PCI line items from the SO: PCI line number, PCI description, and (Qty)
Ship to Party: DOP information in DOP delivery case, Site information in direct Site
delivery case
The following screenshot explains the Equipment
Note:
The equipment data is visible for projects who have selected ‘Full scope’ in SAP P20 for
the RTI data scope
The Planned delivery date is based on ‘SO IDOC’ data, Sales orders that have been
created in SAP P20
The Actual delivery dates are based on Equipment delivery postings in SAP P20 and this
data is delivered to IPM with ‘EGR’ idoc messages automatically
The check boxes become locked once some plan/actual dates have been received through
RTI
Once the ‘DOP’ is selected for a WI, DOP Forecast Date is filled in automatically based
on SAP latest schedule DOP date, but only in case if there is no Forecast date entered
manually
Scheduled date is copied to Planned date in case it has not been entered manually (with
‘RTI’ next to the date)
Both dates should remain editable (that is, manual changes possible) according to the
current rules in WI
Actual Date is populated automatically only if Complete Delivery of the SO has been
performed in SAP. Complete delivery means that all PCIs, which are included in the SO,
have the actual delivery date received from SAP P20 in EGR idoc messages
In case of ‘retrospective’ data linking in IP (case where the delivery is already completed
in SAP P20 before data linking in IPM), planned and actual dates are also automatically
updated, once the SO has been linked to WP
7.5 Permits
If your project is responsible for permitting and you have access to this functionality, the Permits link
will be present in the Work Package Side Navigation bar (Note: This will read ‘Create Permit’ if no
permits currently exist for the site).
The following page provides a general framework in which the permits for a site can be successfully
followed-up.
2. The Permits page will get displayed containing the following information:
Number of Permits – This section displays the number of permits currently existing for
the work package.
Permit Package Info – This section covers the basic information related to the permit
package. Most information present here is project specific and managed by the project
administrator.
Permits –This section provides detail information about all the permits belonging to the
permit package for example. Name, dates, responsibility, fees and so on.
Note:
Project number field only allows positive numbers.
Actual dates can only be today’s date or then +1 (allowing for time zone differences). No
future dates are allowed.
It is possible to delete a work package which has permits attached to it (so be careful
while deleting work packages).
7.6 Leases
If your project is responsible for leasing and you have access to this functionality, the Lease/s link will be
present in the Work Package Side Navigation bar (if no lease records currently exist for the site, it will
read Create Lease/s).
The purpose of this page is to support the tracking, monitoring and follow-up of lease related information.
This is accomplished by providing a structured framework in which local flexibility can be achieved by
tracking the locally required information.
3. Click the names of the lease that you would like to view. The following page appears:
4. The Information for Lease XXX page will get displayed including the following:
Any work package may contain lease information (irrelevant of work item types).
The new leases will get displayed in the Existing Leases section.
Note:
When entering the number of leases, only positive numbers are allowed.
The system will automatically generate a unique Lease number for the leases
created.
2. Update/edit the desired information on the Information for Lease XXX page
Note:
Project number field only allows positive numbers.
Actual dates can only be today’s date or then +1 (allowing for time zone
differences). No future dates are allowed!
Note:
If a record (or records) exists for a lease you must manually remove it (them)
prior to deleting the lease.
If a work package has any leases attached to it, it may still be deleted without
having to remove those leases. Should it be deleted, all lease information /
records are also deleted.
2. In the Lease Records section, select those lease records that you would like to delete.
The lease records will be removed and the page gets refreshed.
Note:
- No confirmation is provided while deleting a lease record.
8. DOCUMENT MANAGEMENT
8.1 Folders
8.1.1 View
To view existing folder contents, follow the relevant browse documentation instructions
presented in earlier sections (Project Documentation Chapter 2.4; Site Documentation
Chapter 4.4; Link Documentation Chapter 5.7.6).
4. Select Folder Details option from the menu. The following screenshot explains this:
Folder Name – This is visible within the folder tree and should represent either
the information contained (for example, quality) or information about
responsibilities / stakeholders (for example, Supplier ABC).
Description – This section is visible only from the folder details page, and
provides any additional information necessary (for example, contact individual
name prior to uploading any documents here and so on).
Owner – This refers to the current folder owner (normally the project
administrator).
Date Created – This refers the date the folder was initially created in the system
(automatic system time stamp).
Date Modified – This refers the date the folder was last modified (automatic
system time stamp).
Current Owner – This refers the current folder owner (normally the project
administrator).
Show Locations button – This navigates you to the Linked Folder Locations
page
View Contents button – This displays the contents of the folder (including
missing items if defaults are in use).
Send Link button – This navigates you to the Send a Link page.
Note:
After sending the folder for approval, time stamp will be visible and available as object in
IPM universe for reporting. The following screenshot explains this:
2. The Linked Folder Locations page will get displayed as shown in the following
screenshot:
Note:
4. Select the group whose user(s) you would like to send the notification to.
5. Select the user(s) from the given list (To select multiple users, hold down your Ctrl
button and click on the users you want to add).
6. Click the button to select the users who will receive the notification (To select
all users of a group by default, you need to click the button).
7. (Optional) Type the message you would like to display in the email.
9. Click Send.
11. Your link will be sent and you will be navigated back to the Folder Details page
where a notification message will be displayed at the top of the page.
Note:
- Selecting the recipients to be removed (by holding the CTRL button and
selecting several) and clicking the button.
Priority is mandatory.
From here you can also copy (CTRL + C) the link to the folder.
The link in the e-mail will direct recipient(s) to the Folder Details page.
8.2 Documents
8.2.1 Browse
To view existing folder contents, follow the relevant browse documentation instructions
presented in earlier sections (Project Documentation Chapter 2.4; Site Documentation
Chapter 4.4; Link Documentation Chapter 5.7.6).
The Document Details page will get displayed as shown in the screenshot.
7. From the top right corner of the Site Document Details page you are able to add up
to 10 upload tabs.
8. Select a file for all the upload tabs and ensure that the supporting information is
correct (will be copied from one tab to the next).
9. Click Create.
A progress bar will get displayed during the upload process indicating the percentage of
uploaded data.
Note:
- When selected, this field will automatically populate the document name,
type, permissions, reviews and/or approvers.
- You must select process phase/sub function to view the list of available
default values set up for that unit/phase.
Permissions
- Only system permissions are available when selecting a permission set for a
document.
Document Name
- When uploading a document, the name is set by default as the filename.
- Can be modified.
The version of a document that is added to IPM for the first time takes by default
the value 1.0.
The Remove button can be used to take away undesired upload tabs before the
upload process has been initiated.
Owners
- The owner of the document will be set as default as the IPM login name.
1. Access the documentation page from which you would like to access the folder details.
5. The Document Details page will get displayed. From this page the following
information and functionalities (based on user rights) are accessible.
Default Doc Name – This refers the project specific values specified for use by
default.
Document Name – This is visible within the folder tree and should be based on
agreed project naming conventions/deliverables.
Description – This is visible only from the folder details page, and supplies you
with any additional information necessary (optional)
Document Root Id – This refers to the Unique Id for all documents stored in
IPM. It remains the same throughout the lifecycle of the document.
Last Modified – This refers to the date the document was last modified
(automatic system time stamp).
Reviewer – If the document was routed for review, the reviewers name will get
displayed here.
Date reviewed – If the document was routed for review, date the document was
reviewed.
Internal / External Approver – If the document was routed for approval, the
approvers name will get displayed here.
Due Date – If the document was routed for approval and a due date was
specified, it will get displayed here.
Date approved – If the document was routed for approval, date the document
was approved will get displayed here.
Show Locations button – This will navigate you to the Linked Document
Locations page.
Send Link button – This will navigate you to the Send a Link page.
View Document – This will open the document for viewing.
Edit Document – This will lock the document and open it for editing.
This functionality allows you to edit the document details (depending on your user
rights).
1. Follow the steps listed in the View Document Details chapter to access the Document
Details page.
3. When you have made all of the required modifications, click Update Details (located
below the details section).
Changes are saved to the system and the page gets refreshed.
Note:
The same business rules (for example, mandatory fields) apply while uploading a
document.
From here it is possible to modify the document owner (all users belonging to the
project main user group are displayed in the drop-down list).
1. Select Permission Zone and CSC (list is displayed based on permission zone).
The new linked location should be visible within the Site Details page.
3. The Version Details page showing all previous versions will get displayed.
4. A. To view a previous version, merely click the Name link (document will open).
5. B. To delete a previous version, select those documents to be deleted (check box) and
click the Delete button.
Note:
It is not possible to delete a document version which has been linked to a CR; QDN
and/or WP WI.
4. A pop-up window will appear asking if you would like to open, save or cancel. The
options are explained as follows:
Save –Click Save, a file download pop-up window will appear asking you to
specify the location you would like the document saved to.
5. Select whether to open the document (without saving) or then save the file and then
open.
Note:
The View Document button is also present on the Document Details page.
This functionality allows users to send a direct link (URL) to the selected document
through email to identified project users.
The Send a Link page will get displayed as shown in the following screenshot.
2. (Optional) Change the link to be copied by selecting one of the other options and
clicking the Get Link button.
Show Document Details of this version – This will send a link to that specified
version’s Document Details page.
Show Document Content – This will open the document without showing the
Document Details page.
Show Document Details of the latest version – This will send a link directing
the user to the latest version’s Document Details page (irrelevant of what that
version is).
4. Select the group whose user(s) you would like to send the notification to.
6. Select the user(s) from the provided list (To select multiple users, hold down your
CTRL button and click on those users you want to add).
7. Click the button to select the users who will receive the notification (To select all users
of a group by default, you need only click the button).
8. (Optional) Type the message you would like to have displayed in the email.
11. Your link will be sent and you will be returned to the Document Details page where
a notification message will get displayed at the top of the page.
Note:
Once assigned, it is possible to remove recipients by:
Selecting the recipient to be removed and clicking the button.
Priority is mandatory.
From here you can also copy (Ctrl + C) the link to the document.
If you select the users, without providing the information, as soon as you
click the Get Link button all the other information will be cleared.
After changing the copied link to be displayed, you must click the Get
Link button otherwise the default (latest version link) will be sent.
When sending the link, recipients of the email will be directed to the Document
Details page, unless you select to send the link to the document content.
2. Click the Edit Document button (present at the end of the details section).
4. If you confirm the edit, the file download pop-up window will appear asking if you
would like to open, save, or cancel:
Open – If you click the Open button it will open the document in a new
window.
Save – If you click the Save button, a file download pop-up window will
appear asking you to specify the location you would like the document
saved to.
5. The Document Details page will display that the document has been locked and two
new buttons have been added:
Save Document button – It lets you save the edited document back to
the system.
6. Make the necessary modifications to the document and then click the Save Document.
7. Fill in the mandatory fields and / all optional fields. Mandatory fields include the
following:
File to save – Either manually enter the folder location or then click
Browse to open a pop-up window which will let you select the file from
your local drive.
Version – The default value is the minor version. This may be changed
to a major version or same version.
10. The document will be saved, unlocked and you will be returned to the Document
Details page.
Note:
It is not possible to edit a document when it has already been checked out (being
edited) by someone else.
It is not possible to edit a document when it has already been sent for review and/or
approval.
Undo Edit
The Undo Edit button is only available when the document has been
checked out (that is someone is editing it).
Only the person who started the edit can undo the edit
If you click the Undo Edit button, the operation will be cancelled and
the document unlocked.
Versioning:
7. If you confirm the link; a new pop-up window will appear stating that the document
has been linked successfully.
8. Click Ok and you will be navigated back to the documentation page where the page
will be refreshed and the new link is displayed.
Note:Note:
It is not possible to add a link to a location where a link already exists (you will get
an error message).
The purpose of this functionality is to display all of the locations where this selected
document has been linked.
2. Click the Remove Link button for the link you would like to remove.
3. Click Move.
5. If you confirm the move; a new pop-up window will appear stating that the document
has been moved successfully.
6. Click Ok and you will be navigated back to the documentation page where the page
will be refreshed and the new location gets displayed.
Note:Note:
This option is available only for the document owner and project administrator.
Project documentation can only be moved within the project documentation area.
Site documentation can only be moved within that specific site’s documentation area
(that is, cannot move from one site to another)
Reset button refreshes the folder structure if the transaction fails or you want to
cancel the move.
To send a document for review, internal approval and/or external approval, perform the
following steps:
1. Follow the steps listed in the View Document Details chapter to access the
Document Details page.
3. (Optional) Select Due Date (this is automatically populated with the work item
forecast date if linked (through the DM WI functionality)
Note:
It is possible to select up to three (3) reviewers, three (3) internal approvers and/or
three (3) external approvers per document / CSF.
Document/CSF is not sent to the workflow until the send has been selected and
update button pressed.
A document/CSF will automatically send the object to the next applicable workflow
when the current workflow has been completed (for example, if two reviewers are
selected and one external approver, the object will not move to external approval
until both reviewers have successfully reviewed the object).
If the document been sent to approval workflow again, the actual date will be
removed (nullify). The new Actual Date will be set in the work item after the user
approved it in the workflow.
In the case of IA/CA already exist for a WI, the rule is still valid where
the Actual Date cannot be changed.
3. Click Delete.
OR
1. Follow the steps listed in the View Document Details chapter to access the Document
Details page.
2. Click Delete .
4. If you confirm the deletion, the document will be deleted and you will be returned to
the documentation page.
Note:
The delete option is available for the document owner and project administrators.
9. CUSTOM DATA
A generic Form, named Custom Data, in IPM is available to perform fast deployment of eventually
‘local’ processes.
Access rights: User Group named Custom Data is required to have access to the Form.
In the Custom Form, the following Custom fields will be available:
Project Fields:
- Seven Date
- 17 Text (length: 256 bytes, out of those two Notes fields (4000 bytes)
Note:
If required, a Custom Data record can be created on browser directly from the Work Package itself. Two
links are available for this, Create Custom Data and Custom Data. The first will allow to create and
link directly a Custom Data record to the Work Package, the second to browse directly the Custom Data
record(s) in case created and linked to that Work Package.
Once the user clicks on Project WPs, auto Search will be triggered. And user will get the
records.
Copy Project WP, Create Project WP and Delete Project WP functionalities are available.
There are two phases of RTI integration which are explained as follows:
RTI3 can be used without RTI4, but RTI4 can only be taken to use after RTI3.
11.1 Navigation
If you have access to this functionality, the RTI link will be visible in the Upper Menu bar. Once
selected, the following RTI Side Navigation is displayed:
Each IDOC message is carrying the required data, which has been specified for Progress tracking.
IDOCs are sent from SAP to NAIP within two minute processing cycles (Site data approximately. 5
min).
NAIP sends an acknowledgement message to SAP once data has been received. Logistics users can
monitor the IDOC status in SAP.
NAIP converts the IDOC data into suitable format for IPM database and delivers the data there.
Once the data has been saved to IPM database, it becomes visible to you and can be used in IPM
processing, site creation, WP call off and supplier allocation. Service GR and billing block released data
is automatically processed in IPM.
Before Real Time Interface can be used with the semi-automated functionalities, following setups are
required:
Project alignment
Supplier alignment
Project Alignment-It means that all SAP Projects, which have appeared through RTI- data
exchange, need to be linked to an IPM Project. This is done through Project alignment page:
1. Activation of WBS in Project Alignment page is crucial in order for IPM to be able to
sort the data to correct IPM project. If WBS alignment has not been done and idoc with
data for an unknown IPM project arrives in IPM, IPM stores all incoming idocs for this
unknown project.
2. When a WBS is linked in Project alignment page retrospectively, IPM checks during
scheduled batch operation all stored data for this WBS and links the data to the project
accordingly. Batch operation is run daily. This functionality ensures, that no idocs are
discarded due to missing WBS alignment.
Note: Data is removed from IPM, if WBS not aligned within 90 days.
During specific period end timelines GR and customer invoicing is not allowed and by using Outbound
Message Blocking functionality it is still possible to do IA and CA in IPM. System blocks message
sending towards SAP during blocking period and then messages are automatically processed and sent to
SAP after period end break.
Outbound Message blocking period alignment is mandatory for projects using automatic GR triggered by
IA and Automatic Customer Invoicing triggered by CA in IPM. When a new SAP project is aligned also
the blocking period shall be aligned according to sales mode in SAP and country. Blocking periods are
available under drop-down list as in Project Alignment picture.
Region-Zone alignment
This is carried out through Zone alignment page, by selecting the correct Permission Zone in IPM, for
each Region-Zone combination which has arrived from SAP:
Zones become locked as soon as any SAP transactional data has been linked to them in IPM (WP call-off,
SO linkage).
Supplier alignment
This is done using the Supplier Alignment page, where IPM Suppliers can be picked up from a drop-
down list and linked to Vendors which have appeared through RTI:
Default WP Alignment
This is done through the DWP Alignment page, where all of Project’s DWP are available to be linked to
SAP Service Sales Packages that is Service PCI descriptions.
Manual linkage
Site creation from SAP-data- It means that no site exists in IPM before SAP site-creation for the
Customer Site Code used in SAP as Ext. Sys. ID. The sites which require Site creation are listed in Site
Alignment page.
In the Site alignment page, the user is presented with all the sites (ZI Partners) that have been created
in SAP, but not automatically or manually linked to any site for the respective project in IPM.
Manual Link – This option moves the site to the bottom section indicating that the site
will be manually linked to an existing site later.
Auto-Create – This option enables the user to create a site based on SAP data
automatically. Note that this option is only available for TI projects.
No Action – This keeps the site in the current status. This is also the default value when a
site has been detected.
Note:
If the Ext.Syst.ID information is missing from SAP, it will be highlighted in Red. Ask the LC / SAP
logistic user to update the information. In addition, if the Ext Sys. ID is missing, you will not be able to
select any of the options for action.
The Auto-Create option is only available if the Ext. Sys. ID is available, the respective zone mapping
has been made and you have right permission Zone for the respective Zone and Site Details (C)
permission.
If you have Site Details (U) permission or even (C) permission but no permission zone access, it will
be displayed like this:
Note that the same Customer site code cannot be used to create another site within the project for
example if a site already exists in the database with that Customer site code, you will not be able to create
another site.
It is possible to set several sites to different statuses at the same time even create multiple sites at the
same time, note that if even one site created failed due to validation error, the additional sites will not be
created.
This file excludes SAP- ZI Partners on Project, Region and Zone level for example. Only sites or data
linked to a WBS with format X-XXXX-XX-XX-XXXX will be included into this report
Any changes to the Ext. Sys. ID in SAP will be reflected in IPM, changing the Customer Site Code
accordingly if conflicts are not occurring. Otherwise the Site will be listed in the section Linked ZI
Partners with conflicting Ext. Sys. ID in Site alignment page
Note:
As you have the ability to create several sites from SAP data, you are not automatically
navigated to the created site after your update.
It is important to check the differences between the site details in SAP versus. the data held
for the site in IPM.
SAP is the master for the site data in ZI-partner section, and this data is also automatically
refreshed if new /changed data arrives from SAP
Several fields are put to read-only as the site has been created from SAP data. If you would
like to have this updated, it will have to be done from SAP.
These include
Site Name
Customer site code -Note that Customer site code is unavailable, if the site has been
created from SAP data
Status
Address
Postal code
City
Region
Country
3. Click Update.
4. Once the ZI Partner code has been linked to the respective site, the ZI Partner details
will get displayed.
Note:
A ZI Partner code can only be linked to one IPM site. If you try and link it to multiple sites,
you will get an error message.
If you try to manually link a ZI Partner code by entering a ZI Partner code that is not
recognized by the system, you will get an error message and when you load this record again,
your previous value would be gone
ZI Partner code can be shared over more than one (1) IPM project (from RTI6 Wave 2
Release onwards).
When you create a new site that the correct permission Zone is selected upon site creation so
that it is aligned with the respective SAP region/zone combination.
If you have manually linked the site with a ZI Partner, the Customer Site Code change option
is not available anymore.
SAP will automatically update the ZI-partner data if any changes are made in SAP; therefore
it is crucial that these codes are the same that is Ext. Sys. ID is equal to the Customer site code
Unlinking a site
It is possible to unlink a ZI-partner from the site; this is done through Unlink button (below ZI-
data). As soon as a ZI-partner is unlinked, it can be used again for another IPM site.
A hyperlink (WP) will be available if the Site is already created/linked in IPM with at least one WP which
is a Multi SO Work Package (amount of different SOG linked to WIs > 1) and the tool tip will be as
Candidate / Candidate Status WP Name
WBS – This field is red if no mapping for the respective Project-Region-Zone has been made.
Once this mapping is made, it changes to white.
SO # (WP ID / SOG) – This field is red if no WP has been linked to this Sales Order. Once a
link is made white and a navigation link becomes available. A hyperlink (WP) will be displayed
when the SO has been linked to a WP. In case the IPM WPID and IPM SOG are updated in SAP
side, those information will be available if the SO is not ‘automatically’ linked otherwise (WP)
will get displayed.
WP ID and SOG shall be a number, no other characters nor additional spaces are allowed. for
example WP ID: 6824832, SOG: 2. System shows SO with WP ID and/or SOG in SOS page, if
WP ID and/or SOG field data is in wrong format according to IPM definition. Same behavior in
Sellable Additional Works and Excluded Sales Orders pages. Additionally error message is
shown in RTI Import Status page, as WP ID, SOG cannot be found in IPM DB due to incorrect
format.
If the respective PCI has not been mapped to a Project Default WP (through Default WP
Alignment page), color is red
Vendor not mapped with Supplier (through Supplier Alignment page), red
SC Scenario Code mapping defined in SAP side in the WBS Milestone
Sales order has not been linked to WP, and has at least one Service Sales package
(Service PCI)
Note:
Only open Sales Orders are displayed on this page – for example If all the respective Customer
Billing Milestones for the Sales Order have their Billing blocks released and for all the Supplier PO’s the
respective Good Receipting has been done – the Sales order will not get displayed on this page.
Only Sales Orders on Site WBS level will be displayed for example. if Sales Orders have been created
for other entities like Region or Zone level, they will not be included into this page
The SAP SO number may have leading ‘0000’s’ in the SAP SO number – IPM will remove the
leading ‘0000’s’ so remember when searching in SAP
Once linkages have been made to Site or WP, a navigation link becomes available for you to easily
navigate to the data record.
2. Click Call-Off .
3. The Project Default Work package that has been mapped to the PCI/Service Sales Package
will be displayed.
4. In Case of Multi SO Work Package, the Sales Order Groups should be selected through the
radio button in order to proceed with the next steps. In case of mistakes when selecting SOG the
button Reselect SOG can be used to reset the selection.
5. You should now link all the respective entities for the Work package – Customer Billing
Milestones and Supplier PO’s
6. Here, you have the option to add or remove Customer and Supplier Invoice Triggers for the
called-off work package
If you have selected a SO with Service tasks defined and the respective Purchase scenarios have
been defined for the DWP, the system will automatically, based on the PS defined, link the
Supplier PO’s to the work items (refer Note section below for further details). If additionally the
SO includes Scenario Codes and the respective Billing Scenarios have been defined for the DWP,
the system will automatically, based on the BS defined, link the CBMs to the work items (see
Note section below for further details).
Once the call-off has been made, you will be navigated to the Work Package page.
If you did not already link the entities (CBM and SPOs) at the time of call-off, they will still be
highlighted in red in the Sales Information box for user update – you will now have to manually
update and link the respective entities
You are now able to update the relevant Work package details.
Note:
You must consider the related rules for Work Package call-off
If there is only one (1) CBM and one (1 ) SPO and the DWP has only one (1) CIT and (1)
SIT, the system will automatically link the entities
If one CBM and multiple SPO and no purchase scenario defined, then manual linkage needed
If one CBM and multiple SPO, purchase scenario defined and all SPOs available in IPM, then
automatic linkage needed.
If you decide to increase the CIT/SIT the respective Customer Billing Milestones and
Supplier PO fields will be enabled.
You can select another DWP even if the system proposed a DWP to be called-off
Do not create more customer and supplier invoice triggers than are required for the sales
order, this will affect your internal and customer acceptance processes
If a Purchasing Scenario (PS) has been found for the call-off, the system will automatically
assign the Supplier PO’s to the WI based on the Service tasks used in the Supplier PO’s and
based on the DWP PS defined.
o The suggested linkage above can only be changed by changing the supplier invoice
trigger setting or changing the PS in the DWP.
o If however, the Supplier PO linkage is changed from the above, note that IPM will
overwrite the user change once any updates for the Supplier PO’s are received through
the RTI interface. But the SPO will not to be ‘moved’, even if match is found, if the SPO
is already linked to a WI that has been internally accepted.
If a Billing Scenario (BS) has been found for the call-off, the system will automatically assign
the CBM’s to the WI based on the IPM SC used in the SAP WBS Milestone and based on the
DWP BS defined.
Once the call-off is made, the following fields are automatically updated by the system:
SAP Sales Order number
Again, once all the entities have been linked, the Sales Order information will disappear from
Sales Order Status page
In Multi Sales Order WP, once the WP is called off, the SO will be linked to the SOG
selected during the call off WP from SO. Additionally all the SOGs defined in the DWP will
be available for further manual linkage. Maximum number of RTI CPO is 15 and those can
be created using the button Create RTI CPO in Order Details Page.
In case more than one SAP SO/SvO is assigned to the same WP and more than one WBS
elements linked to them, the WBS field on the WI Details page will be updated as
MULTIPLE
As you link the respective entities for the Sales Order, the colors will change to white
indicating that the link has been made.
Note:
Keep in mind that the SAP SO number can only be linked to one WP in IPM, if you try and
link another WP with the same SAP SO number , you will get the following error:
If you tried to link a SO number to a site which has a different ZI Partner code, the error will
be displayed:
Once the linkage is made, the following fields are automatically updated by the system:
SAP Sales Order number
If the Sales Order only had one SPO and one CBM and the DWP had only one SIT and one
CIT defined, the system will automatically link the entities to the WI.
If the original WP has a WBS code that does not correspond to the new SAP Sales Order
number it will be overwritten.
Remember that once you have linked this SAP SO number, the color in the Sales Order Status
report will change to white, indicating that the link has been made.
Note:
Note that latest delivery date information excludes all locally purchased items
2. Once the work has been completed, the customer acceptance is completed.
Based on the Customer acceptance, the billing block is released (LC responsibility and done in
SAP) – once this is done in SAP, through RTI, the data will be available in BB Released (SAP)
field in read-only mode.
Note:
The Work Item has to be a Customer Invoice Trigger for you to be able to link a Customer
Billing Milestone number to it, check your default WP.
A Customer Billing Milestone can only be linked to one SAP SO and one Work item – for
example, only one WP.
For RTI Phase 3 upwards – The manual input of Billing block released is not required as the
system will automatically check when this is done in SAP and make the information available in
read-only mode. Note however that you had to ensure the linkage of the Customer Billing
Milestones first.
Note that the Customer Billing Milestone combines the actual billing milestones number from
SAP and the description for easier recognition.
For RTI projects (SOG>1) acceptance check box remains unavailable until CBM has been
aligned to CBM # field for WI.
Based on the Internal acceptance, the GR in SAP is completed (LC responsibility and done in
SAP), once this is done in SAP, through RTI, the data will be available in GR date (from SAP)
field in read-only mode.
Note:
• The Work Item has to be a Supplier Invoice Trigger for you to be able to link a Supplier PO to
it, check your default WP.
• A Supplier PO can only be linked to one SAP SO and one Work item – for example only one
WP.
• The Supplier PO combines the PO number and Vendor name for easier recognition.
• For Phase 3 upwards – The manual input of the GR in SAP is not required as the system will
automatically check when this is done in SAP and make the information available in read-only
mode. (If the SPO was linked to this WI first).
• For RTI projects (SOG>1) acceptance check box remains unavailable until SPO has been
aligned to SPO # field for WI.
The selector lists only those SAP Projects which have Sales Orders.
Below each listed SAP Project, the page displays the total number of not marked Closed SOs
in each of the SAP Projects. Closed marked SOs have all the CBMs BBR'd and all the SPOs
GR'd. This should help to predict the loading time (page load time correlates with the SO count).
As the last item selector offers ALL (that is, data is loaded from all SAP Projects).
For small IPM projects (those with less than 1000 sales orders) the ALL option is defaulted
so that when you click on the Sales Order Status link the page displays immediately all the Sales
Orders
For large IPM projects (those with at least 1000 sales orders) the project is defaulted and no
Sales Orders are displayed until the user selects one of the SAP Projects (or ALL)
Safety Features:
For large IPM projects (those with at least 1000 sales orders) the user is asked for
confirmation if they click the ALL link
All links in the SAP Project Selector have double-click detection, that is, if the user
clicks any of the links while the page is already loading, they will be alerted
For the largest IPM projects (those with at least 10.000 sales orders); the ALL link is
unavailable for performance reasons. Clicking the link results in a pop-up window
explaining that the link has been dimmed for this reason.
Excel Export – This exports the same (SAP Project specific) data as is displayed on the
screen. The file name contains the Project ID (as previously) plus the SAP Project Code.
With the ALL option the file naming is unchanged from earlier releases
Usability
Sales Order Status page ‘remembers’ your latest SAP Project selection for the
duration of the session; that is if you chose a certain SAP Project and then go to
some other page , for example to call-off a Sales Order , then the previously
selected SAP Project is defaulted when you next return to the Sales Order
Status page.
The selected SAP Project is displayed in the header of the Sales Order listing:
The same SAP Project Selector as in Sales Order Status page has been added
also to the Excluded Sales Orders page.
Selected SAP Projects are remembered between these two pages, that is, if one
chooses a certain SAP Project on Sales Order Status page and then clicks the
Excluded Sales Orders link, one is displayed the Excluded Sales Orders for
the same SAP Project.
11.6.1 How to activate the Full Scope data flow from SAP
Projects are activated to the RTI Data exchange using a special controlling table in SAP.
• Transaction: YCSIPM
• Enter Project ID
• Select Data transfer method
• 00 No Transfer
• 01 Batch file transfer
• 02 Real-time transfer (Service Only)
• 03 Real-time transfer (Full Scope)
• Add Username in column User
• Cost and Progress Managers have the authorization to activate/change projects into this
table
• Once the transfer method has been changed to Full Scope, all new Sales Orders will
include all types of PCIs and all Customer Billing Milestones (also SO changes that
generate IDOCs)
• This kind of WP selection impacts to how other than service PCIs (non-service PCI) are
linked in IPM. Incoming non-service PCI is automatically linked to H type DWP if
available
• If WP has H, by default PCIs are hidden (but can be uncovered)
• Non-service PCI is based on SAP master data (item category)
•There is a setting on SAP-project level to activate/ remove the automatic hiding.
• Project team can choose if they like to hide or display the non-service PCIs as default.
• It is possible also to hide a service PCI by manually linking the incoming PCI to H type
DWP (through Default WP alignment).
New Auto Hide check box to enable or disable automatic link of PCI to hidden DWP.
Updated by and Updated on is automatically populated by the system based on today’s date
and using your NOLS username when changes are done on Auto Hide field Default value is
‘auto hide active’.
Note:
Steps to activate Automatic Hiding:
• Select on Project Alignment the Auto Hide check box
• Define a DWP for example. Hidden PCI and give the DWP a weight of ‘h’
• In the DWP alignment page, map all detected PCI to the newly created DWP Hidden
PCI with weight of h
Version 4.0 Page 198
IPM User Guide
Customer Acceptance done in IPM will automatically release the Customer Billing Milestone
in SAP, and this step will automatically bring the Sales Order to Invoicing list for logistics.
There is a message Monitoring process in IPM and SAP. IPM monitoring is T2 support task. SAP
monitoring is SAP Logistics Key User task.
IPM Project level activation must be requested from IPM Support through RMT process:
After IPM Project level activation, SAP Region-Zone activation is available in Zone alignment page, and
it is selectable for GR and BBR separately.
Note: Activations can also be removed in IPM, but then you will need to be very careful and agree with
Logistics / SAP users beforehand, to ensure they will continue with manual processing instead.
Note: Only RTI3 projects can start to use RTI4 solution. Automated Goods Receipt will only take place
when all the following criteria has been met:
IPM Project set to SAP Phase 4 - To allow IA message creation, and data flow to SAP
SAP Region-Zone for the SPO has been activated for RTI4
Automated Billing Block Release will only take place when all the following criteria has been met:
IPM Project set to SAP Phase 4 - To allow CA message creation, and data flow to SAP
SAP Region-Zone for the CBM has been activated for RTI4
If the RTI4 criteria are met, and RTI4 messaging is about to happen from the acceptance, lightning strike
symbol is displayed next to the Acceptance check-box:
Message triggering:
Acceptances can only be marked once the Actual date is given for the work item, this will enable
the check box.
Internal Acceptance (IA) in IPM will generate an IA-message in IPM, which is sent through
NAIP to SAP P20, and will trigger the GR posting in SAP.
Customer Acceptance (CA) in IPM will generate a CA-message in IPM, which is sent through
NAIP to SAP P20, and will trigger the BBR posting in SAP.
In addition to the Internal Acceptance and Customer Acceptance in IPM, no further acceptances
are required, but SAP transactions are allowed directly based on the IPM data.
Order Details page includes information concerning IA and CA messages on WI level as soon as an
acceptance has activated the automated GR or BBR.
Message number by IPM
Note: The user shall create a RMT to IPM T2 Support including the information displayed above (if
available), if:
– A faulty message status (Failure (IPM), NAIP NACK) is found
– A message is not in status ‘SAP Received’ even two hours later than time stamp
IPM Support uses a RTI4 message monitoring tool for traffic monitoring and problem solving.
11.11.1 Definitions
In standard customer order -driven execution process:
The normal scope of works is agreed with customer.
If the scope of work changes after this, one of these processes needs to be followed:
Extra works process (Non-quality costs or Project extra work), non-
sellable.
In case of non-sellable extra works, these cases are further categorized based on the
reason of extra works, to enable follow up reporting locally and globally.
If the SO has only one SPO and the WP has only one Supplier invoice
trigger, link the SPO to the respective WI
For Extra works – Check if the WP has a SvO# linked to it – If not the system will
automatically link the SAP SO# to the respective WP on SOG = 1
If the SvO has only one SPO and the WP has only one Supplier invoice trigger, link
the SPO to the respective WI
If the ‘intelligent updating’ did not meet this criteria, the end-user will have to
manually link the entities, for example, link the SO# or SvO# and respective CBM
and SPO.
However, if the CR ID was missing and updated in SAP and a new IDOC resent (as
this change will not automatically create a new IDOC), the same logic will be used to
check if any automated updated can be made
If a suitable PS match is found, the system will automatically link the SPO to the WI and it is
displayed in Order Details page in Service Task field.
Matching is attempted only in case the counts of SITs and non-deleted SPOs match
(for example. two of both).
In case of match the user is still able to change the SPO selections.
If user has manually changed the SPO selection, next SPO message will update
according to created PS.
PSs are ‘considered’ in the same order as they are on the PS Management page.
If a match is found, the later scenarios are not considered anymore, but instead the
linkages are done based on the found scenario.
PS matching logic does not take place, if IA done for one or more SPOs within the
PS/SOG.
Same rule applies for the order if it has only one SPO and one SIT, the system will
automatically link the SPO to the WI defined as a SIT – irrespective of the fact that PS and
Service tasks might be defined.
If a suitable BS match is found, the system will automatically link the CBM to the WI and it
is displayed in Order Details page in SC field.
Matching is attempted only in case the counts of CITs and non-deleted and non-
EE (Excluding Equipment) CBMs match (for example. two of both).
In case of match the user is still able to change the CBM selections.
If user has manually changed the CBM selection, next SO message will update
according to created BS.
BSs are ‘considered’ in the same order as they are on the BS Management page.
If a match is found, the later scenarios are not considered anymore, but instead
the linkages are done based on the found scenario.
BS matching logic does not take place, if CA done for one or more CBMs within
the BS/SOG.
However, note again that if order has only one CBM and one CIT, the system will
automatically link the CBM to the WI defined as a CIT– irrespective of the fact that BS and SCs
might be defined.
Define a Default Work Package – for example Excluded SO and give the DWP a weight of e.
In the Default Work Package alignment page, map all detected SSP to the newly created
DWP Excluded SO with a weight of e.
All SO that has a SSP mapped to a DWP with a weight of e will be moved to the Excluded
Sales Order Status page.
Examples:
• If SO only contains one PCI (SSP) and mapping to DWP with weight is e – not in SOS page but
in Excluded SO.
• If SO contains multiple PCI’s (SSPs) and even one DWP mapping indicates weight of e – not in
SOS but in Excluded SO.
Any “Non Conformance” update is logged towards a non-conformance table in IPM. Log details can This
table/s to be mapped towards reporting (creation BO objects), to enable reporting containing all the
details related to the non-conformance update stored in IPM.