Deactivate the "Change to operational status" Business Rule?

[David Anderson2]

Situation
We are trying to build on the Common Services Data Model (CSDM) by creating a Business Application (BA) that depends on three Application Services (BA-Dev, BA-Model, BA-Prod).  However, the operational status of the application service cannot be set to "operational" as these services do not have an entry point.  

My analysis found that there is a business rule, change to operational status (cmdb_ci_services_discovered), that has been activated (we have installed Service Mapping although we are not actively using it).

Questions

1. Are there downstream issues if we choose to deactivate this business rule? 
2. What purpose does the rule serve? 
3. What would happen if it is deactivated now, to allow the organization to transition to CSDM, and activated later?  Will the "operational" application services that are missing entry points become non-operational?

[bhopkins]

David, did you ever experience any issues? We are about to turn this business rule off as well. We do plan on utilizing Service Mapping but, because the CSDM dictates the Application Services as the Class that I/P/C should leverage, we will be reclassing CIs over to this Class to preserve historical information. We will need this business rule to remain off while we make the Application Services CIs available for I/P/C as we ramp up Service Mapping. CIs need to be Operational so they can continue to be used as maps get populated.

[DuaneNMore]

having an Application Service in state=Operational causes it to be rediscovered and the map to be recomputed on a regular basis. The reason for the business rule is, that if the Application Service has no entrypoints it can't be operational. 

[Blaine Hopkins]

DuaneNMore, that does make sense. Unfortunately, we need to meet the CSDM 2.0 criteria as quickly as possible and the existing data we have as a business just means we need to do it this way to keep operations running while we progress. The recomputing makes sense but I imagine it trying to recompute something blank wouldn't have drastic consequences - error out the process at the most. Do you happen to know where the mechanism for recomputing is? I'd like to dissect it and add it to our structure documents.

[DuaneNMore]

You could start by manually adding one of the CIs to the Application Service; presumably one that is pertinent to the service. When you open the Application Service form you can add an entrypoint, and then instead of picking "Discoverable by Serviec Mapping" you pick "Manually Created". At this point you can select any CI, for example a windows or linux server that actually supports the application. 

Effectively you are creating a Manual Service (which is deprecated in NY), but you can set the state to Operational at this point.