1. INNER-AGENCY DOCUMENTS EXTENSION

BUG:

Categories are Limited to 34

NOTES:

N/A

SOLUTION:

Updated OPS Version 2.0.1 is proposed to contain fix

TEMPORARY-WORK AROUND:

None-Available

3. SOCIAL MEDIA SHARING PLATFORM

BUG:

Facebook API is disabled pending re-activation.

NOTES:

The Facebook “automatic sharing” API was functioning but due to API glitches, has been taken offline. The button to activate the Facebook API is still showing active in the social media setup portal, but this button is not functioning. The social media sharing boxes contained in the various modules are disabled as well.

SOLUTION:

OPS Techs are working with techs from Facebook to resolve this issue. A proposed fix timeline is pending.

TEMPORARY-WORK AROUND:

Users can still share OPS links and post to Facebook in the traditional method.

5. CAMERA BLOC

BUG:

Camera entries with remote login feature logs OPS user out when clicked on

NOTES:

N/A

SOLUTION:

Updated OPS Version 2.0.1 is proposed to contain fix

TEMPORARY-WORK AROUND:

None-Available

8. MISSING/WANTED BLOC

BUG:

The “Deactivate” function is not functioning properly and does not deactivate the flyer from appearing on the Community Interface.

NOTES:

Users can save the PDF on thier desktop and then delete the Flyer. If the information is needed again, the text can be easily copied into a new flyer and posted.

SOLUTION:

Updated OPS Version 2.0.1 is proposed to contain fix

TEMPORARY-WORK AROUND:

Deleting the flyer will remove it from the Community Interface.

NEW AGENCY SETUP – “BEST PRACTICES” HELP GUIDE

View the Best Practices Step by Step Video ▶️ HERE

The below guidance is provided as “best practice” to assist agencies with a smooth OPS Network implementation and ongoing upkeep. By following these simple suggestions, each agency should complete an OPS Network implementation within 2 to 6 weeks.

*Note* A Fusion Project OPS partnership will have diverse implementation time periods based on the size of the agency and project details.

1. ASSIGN A MANAGER:

• Assign an agency member, or members, to handle the rollout and setup of the initial network. Request the assigned personnel to spend a day or so looking through the OPS Network Learning and Resource Center, familiarizing themselves with the many aspect of OPS. (NOTE: Select a member(s) that is goal oriented and provide them with the needed time and resources to accomplish the task with minimal interruption.)

2. NOTIFY I.T.:

• Provide the agency’s IT department and staff with advanced notice that the agency will be implementing the OPS Network so that they can be aware of any IT needs and be prepared to assist. (i.e: white labeling OPS email extensions, etc..)

3. BE TRANSPARENT:

• Advise all agency staff that the network is coming and that the person(s) assigned to set up the network have the authority to make requests and will require cooperation from the staff. Keep in mind that new tools, technology, procedures, etc.., no matter how beneficial, always create some level of anxiety with some staff members. Being transparent and direct often helps prepare agency staff so they can better understand the network and its benefits.

4. PROVIDE GUIDANCE

• Download the provided agency policy template (modify as needed) and issue the OPS Network policy agency-wide. Ensure that the policy clearly states the requirements and goals of the agency’s use of the OPS Network. This will assist the agency member(s) charged with setting up and maintaining the network as well as provide guidance to agency staff.

5. SIGN UP USERS:

• Start with getting OPS Network user permission levels established and agency users signed up. Think about starting with command staff members, supervisors, line officers, support staff, etc… in controlled blocks.

6. SHARE APPROPRIATE RESOURCES:

• If your agency will be utilizing the Community Interface Module, make sure those who will be assisting with setting up and launching the Community Interface have access to the OPS Learning and Resource Center.

7. SET DEADLINES:

• While setting up your network, set deadlines to ensure the process does not stall and stays on track.

8. HIGHLITE THE BENEFITS:

• Encourage users to explore the network. Share how certain tools can benefit various aspects of the organization and community.

9. USE THE NETWORK:

• Begin utilizing the network. Example: Load critical documents and templates up to the Command Center so agency members can access them 24/7, begin making all agency-wide and critical announcements via the agency’s OPS Command Center, etc..

10. NOTIFY THE COMMUNITY:

• If the agency is utilizing the Community Interface Module, or any of the Community Modules, notify the community via press release, social media, etc…so they can begin engaging the agency via OPS. Your agency is taking a huge step in community policing and it should be a proud moment to be shared with the community.

– Following these “best practices”, and the steps in the OPS Learning and Resource Center’s setup process, will help ensure your agency’s OPS Network will be up and running quickly and with minimal effort.

– Reference the OPS Learning and Resource Center often. While most tools in OPS can be used with no training or technical knowledge, nearly every aspect of the OPS Network is covered in the center for those times when guidance or assistance is needed.

– Contact OPS Technical Support or your OPS Regional Representative when needed.