Cognos data import: Difference between revisions

m Known problems with data import: These really no longer are problems now that the import is human-facilitated.
 
(8 intermediate revisions by 2 users not shown)
Line 2: Line 2:


== Process ==
== Process ==
Tina receives the data in a scheduled, automated email from [[Decision Support Services]] every morning as early as possible, usually before 8. The data is then imported into [[CCMDB.accdb]] master on Regional server and provided to collectors via regular roll-out and news and backup.
[[Decision Support Services]] sends an automated email report to Lisa and Pagasa
every morning. The data is then imported into [[CCMDB.accdb]] master on Regional server and provided to collectors via regular roll-out and news and backup.


=== Outlook Rule in Tina's profile to get data to Pagasa and Lisa ===
=== Cognos extract via email ===
Decision Support Services sends a report to Tina. The report needs to go to Pagasa and Lisa so it can be imported and rolled out; this is accomplished by outlook rule "Cognos to Pagasa" in Tina's Outlook. This was an automated process at some point but isn't at this time since no PC is reliably on the network when it should happen.  
Generally the email from [[Decision Support Services]] arrives around anytime between 0700-1100. This can be delayed if the ETL that feeds the process is delayed. If it will be delayed [[Decision Support Services]] will send an email to Lisa.


==== Process if the email does not arrive ====
==== Process if the email does not arrive ====
Generally the email from [[Decision Support Services]] arrives around 7:40 +/-1hr. This can be delayed if the ETL that feeds the process is delayed. If the email has not arrived by 9:30, see [[Decision Support Services]] for who to contact.  
If the email has not arrived by 1100, we contact [[Decision Support Services]] (see that page for contact info, it keeps changing).  


==== Steps to import and roll out ====
=== Steps to import and roll-out ===
Each morning the [[Data Processor]] or [[Database Manager]] runs [[LoadCognos.bat]] (if the .bat isn't visible, it is the file of type "Windows Batch File"). If the data collector is unavailable, the [[Process Analyst]] does this. Anyone who has the requisite email in their mailbox would be able to run this, but for now only Lisa receives it as a final fall-back.
Once the email arrives each morning we run [[LoadCognos.bat]] (if the .bat isn't visible, it is the file of type "Windows Batch File").
The import and roll-out is generally done by the first of the following who is available:
# [[Database Manager]]
# [[Data Processor]]


==== What happens in the process ====
==== What happens in the process ====
Line 26: Line 30:
}}
}}


=== Newly encountered units or services ===
=== Newly encountered units or services === <!-- linked from  VBA via [New unit or service encountered during Cognos data import], fix there if this heading is changed -->
If a unit or service is part of the import that is not already in our reference tables, an email will be sent to Tina and Lisa. Lisa will inform Tina what the new unit/service is about and Tina will add it to the master version of CCMDB.accdb accordingly.
If a unit or service is part of the import that is not already in our reference tables, the import process will catch this and an email will be sent. The recipients of the email are hard-coded in .
Lisa will investigate what the new what the new unit/service is about is about and whether it might affect our collection process or Julie's reports. She will then either add it to the master version [[CCMDB.accdb]] herself or ask Tina to do it.


==== Newly encountered units ====
==== Newly encountered units ====