plc.myforum.ro

deveshjoshi101 · Junior Joined: 29 Jul 2019 Posts: 1

i have installed win server 2016 and sql server 2016 and management studio v18. after that i installed factory talk asset center acc. to installation guide and when i opened asset center client it is not showing the "design" button :weep:

. design is in gray mode. Please help :-(

. How to stil in Asset center????

DBShenker · Junior Joined: 26 Jun 2019 Posts: 1

Try this maybe help you
https://letsupload.cc/P2uaA81fnf/FactoryTalk_AssetCentre_Design_Considerations_pdf

Question
Is there a set of common guidelines or checklist to go through when designing a FactoryTalk AssetCentre system?
Answer
The topics below are intended to cover implementations of FactoryTalk AssetCentre versions 4.10 and higher in a checklist style, overview fashion. For more information on Design Considerations, Refer 57483 - FactoryTalk AssetCentre System Design Considerations.

Is there a Windows domain?

Architectures of 10 or more FactoryTalk computers require a Windows domain. Less than 10 computers may use a Windows workgroup or domain.
If FactoryTalk AssetCentre will be required to communicate across multiple Windows domains then trusts need to be established between the domains for FactoryTalk AssetCentre to properly communicate.
Host name resolution must be set up correctly, either through Domain Name Service (DNS) or HOST files.
Will Time Synchronization be used?

Time Synchronization is strongly recommended, but not required for FactoryTalk AssetCentre. By default, computers that are members of a domain will synchronize time with their domain controller.
Is this installation an upgrade from RSMACC?

Any RSMACC components must be fully uninstalled prior to the installation of FactoryTalk AssetCentre on the same computer. Remember that RSMACC and FactoryTalk AssetCentre software component cannot co-exist on the same computer.
Where will the FactoryTalk Directory server be located?

When possible, the FactoryTalk Directory server should be installed on an independent computer. Refer 58803 - FactoryTalk Services Platform Best Practices for more information.
FactoryTalk AssetCentre uses the FactoryTalk Network Directory and cannot run in the FactoryTalk Local Directory.
The FactoryTalk Directory server should be located on the same Local Area Network (LAN) as the FactoryTalk AssetCentre server.
If it must be co-located with another FactoryTalk AssetCentre component, it should be installed on the server computer (as opposed to the client or agent computers).
How many FactoryTalk Network Directories are needed?

A single FactoryTalk AssetCentre server can only reside in a single FactoryTalk Network Directory.
If multiple FactoryTalk Network Directories are required (possibly for segmented networks, multiple FactoryTalk View SE installations, etc), then FactoryTalk AssetCentre will only be able to service one FactoryTalk Network Directory per server.
How will security be handled?

If the FactoryTalk AssetCentre application is hosted within a domain, then Active Directory users/groups may be linked into FactoryTalk security.
If the FactoryTalk AssetCentre application is hosted within a workgroup, then it is recommended to use native FactoryTalk users/groups (i.e., do not link to Windows users/groups.)
Where will the Microsoft SQL server be installed?

FactoryTalk AssetCentre requires Microsoft SQL Server. Other relation databases such as Oracle are not supported.
It is fully support to locate the Microsoft SQL Server with the FactoryTalk AssetCentre server, but this is not required.
It is possible to install the AssetCentre database on a Microsoft SQL cluster server, but the FactoryTalk AssetCentre server cannot be co-located with it.
It is possible to install the AssetCentre database on a mirrored Microsoft SQL server. Refer 609423 - FactoryTalk AssetCentre with Microsoft SQL Server Mirroring for more information.
It should be on the same Local Area Network (LAN) as the server computer – not separated by a slower connection (<100mbps) over a Wide Area Network (WAN). It is possible but not recommended to separate the two with a firewall.
Will Remote Desktop Services be used?

Remote Desktop Services is recommended when client communications are needed over a wireless connection or Wide Area Network (WAN) with network speeds of less than 100mpbs, or when communicating through a firewall.
The Remote Desktop Services server should be on the same Local Area Network (LAN) as the FactoryTalk AssetCentre server, and should have the FactoryTalk AssetCentre client installed.
Since the FactoryTalk AssetCentre client will be used to check out files from the FactoryTalk AssetCentre archive, any engineering workstation software should be included on the Remote Desktop Services server (e.g., RSLogix 5000)
It is recommended to use more than one Remote Desktop Services server to eliminate a single point of failure.
Refer 567658 - Using FactoryTalk View SE with Windows 2008 R2 Remote Desktop Services - Getting Started Whitepaper for more information. While the document is created for use with FactoryTalk View SE, the esteticÄƒ elements apply to FactoryTalk AssetCentre as well.
Where will the FactoryTalk AssetCentre server be installed?

See the FactoryTalk AssetCentre installation guide for recommended system requirements.
The FactoryTalk AssetCentre server should be on the same Local Area Network (LAN) as the FactoryTalk Directory server and Microsoft SQL server.
How many FactoryTalk AssetCentre servers are there?

Only one FactoryTalk AssetCentre server may reside in a single FactoryTalk Network Directory.
If numeroase servers are required (possibly for multiple FactoryTalk Directories), there is no way to aggregate the data into one database.
All servers will be independent, and will require their own instance of Microsoft SQL server.
Adding FactoryTalk AssetCentre servers is not necessary to increase system resources. To increase the system’s throughput, adding agents is necessary (see How many agents will be installed? below).
How many clients will there be?

For version 9.0, a maximum of 100 concurrent clients are supported, including each instance of a client running through Remote Desktop Services.
For version 8.0, a maximum of 60 concurrent clients are supported, including each instance of a client running through Remote Desktop Services. For more information on this, see technote 57483 - FactoryTalk AssetCentre System Design Considerations
For versions 7.1 and lower, a maximum of 50 concurrent clients are supported, including each instance of a client running through Remote Desktop Services.
Where are the clients going to be installed?

See the FactoryTalk AssetCentre installation guide for recommended system requirements.
Clients should be located on the same Local Area Network (LAN) as the FactoryTalk AssetCentre server. See the Will Remote Desktop Services be used section for information on bridging Wide Area Network (WAN) or wireless communications.
Clients are used for schedule creation, meaning that at least one client must have the same access path(s) to the asset(s) as the agent component(s). i.e., it is recommended to have a client installed on at least one agent for configuration purposes only.
The FactoryTalk AssetCentre client is required to gather audits from all other FactoryTalk software. Thus, it is necessary to co-locate the FactoryTalk AssetCentre client on all computers from which the user wishes to receive audits.
It is generally recommended to have a client installed on all Engineering Workstations to get the most out of the Archive abilities (i.e., the client should be co-located with editing software, thus enabling the operators to check out/in the necessary files) and auditing.
How many assets will FactoryTalk AssetCentre be servicing, if using disaster recovery?

Assets conÈ›ine any controllers (PLCs, SLCs, CLXs, etc), PanelView Plus’s, drives, robots, remote computers, FTP devices, or custom devices that will be configured as part of a Backup, Backup and Compare, or Change Detect operation.
Asset count does not include files to be checked into the FactoryTalk AssetCentre Archive.
How many agents will be installed?

All FactoryTalk AssetCentre systems require at least one (1) agent, whether they're using Disaster Recovery or not. Agents are used to perform all scheduled activities, including scheduled searches.
If using Disaster Recovery, agent count is determined by the number of assets to be serviced and the amount of time in which they are to be serviced.
A single agent may service approximately one hundred (100) assets every twelve (12) hours, depending on network loading, asset programming, etc.
Refer 106118 - Determining the Necessary Number of FactoryTalk AssetCentre Agents for more detailed calculations on the time needed to service different types of assets.
In version 9.0, there can be up to 35 FactoryTalk AssetCentre Agents per installation, one Agent per PC (25 FactoryTalk AssetCentre Agents if less than v9.0, 15 if less than version v8.0).
In versions 5.0 and lower, five (5) agents per FactoryTalk AssetCentre system have been officially tested, ten (10) are supported.
Where will the agents be installed?

See the FactoryTalk AssetCentre installation guide for recommended system requirements.
It is supported but not recommended to install an agent onto an Engineering Workstation due to the frequent processing requirements, as well as complications with secured editors.
It is possible to co-locate an agent on the FactoryTalk AssetCentre server. This determination must be made based on the system resources of the server PC, as well as the size of the system (i.e., number of assets the agent will service, number of FactoryTalk AssetCentre clients the server will service) and should be monitored after installation to ensure no performance degradation.
In versions 5.0 and lower, if using Disaster Recovery, all agents must have the same communications path to all assets.
Do the agents have all required software packages?

In versions 5.0 and lower, each agent must be configured identically. This means that the required software packages must all be installed on all agents.
An agent performing Disaster Recovery operations must have the matching communication and editing software for that asset installed locally (e.g., ControlLogix requires RSLogix 5000 and RSLinx Classic).
These software packages do not require activation, with the exception of Drive Executive.
Is there other FactoryTalk Software in the system?

Ensure that all software is capable of running on the same FactoryTalk Services Platform (FTSP) major version (e.g., CPR9).
If audits are desired from these FactoryTalk software packages, a FactoryTalk AssetCentre client must be installed locally. Additionally, these software packages must be in the same FactoryTalk Directory as the FactoryTalk AssetCentre server.
The exception to this is for PanelView Plus products running FactoryTalk View ME, which can be configured for remote diagnostic and audit logging.
Is Calibration Management being used?

In versions prior to v5.00, the default installation of Calibration Management requires the 32-bit version of Microsoft SQL Server. To support 64-bit, refer 499769 - Microsoft SQL for 64-bit processors with FactoryTalk AssetCentre.
Where is the ProCalV5 server being installed?

The ProCalV5 server must be installed on the same computer as the Microsoft SQL Server hosting the ProCalV5 database.
Should be on the same Local Area Network (LAN) as the FactoryTalk AssetCentre Server and Clients.
Where is/are the ProCalV5 client(s) installed?

Must be co-located with the FactoryTalk AssetCentre client.
Should be on the same Local Area Network (LAN) as the ProCalV5 server.
Users of the ProCalV5 software must have security permissions to edit the Windows registry. These privileges are not related to FactoryTalk Security.
Is Process Device Configuration being used?

DTMs must be installed on each client that will make use of them. i.e., no DTMs are pushed from the server to the clients.
The 1756 Backplane DTM requires RSLinx Classic activation, meaning that each client using this DTM must have the DTM itself, as well as RSLinx Classic activation.