Public safety statement of requirements by the safecom program




















Do Not Sell My Personal Information When you visit our website, we store cookies on your browser to collect information. Allow All Cookies. Cookie List A cookie is a small piece of data text file that a website — when visited by a user — asks your browser to store on your device in order to remember information about you, such as your language preference or login information. Sale of Personal Data We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience.

Social Media Cookies We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience. Targeting Cookies We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience.

FCW uses cookies for analytics and personalization. By continuing to use this site, you agree to our use of cookies. Read our Privacy Policy to find out more. Almost There! Full Name. I Work For Please Provide Your Org. Phone Number. Zip code. Country Name. Yes, I want to receive occasional updates from partners. I agree to the use of my personal data by Government Executive Media Group and its partners to serve me targeted ads. Learn more. Get top federal technology stories and news alerts in your inbox.

Sign up for Nextgov Today My email is I work for Also get CIO Briefing, the need-to-know federal technology news for current and aspiring technology executives.

Sign up. Help us tailor content specifically for you: Full Name. Homeland Security Department officials filled the gap with the release of a comprehensive statement of requirements last week.

Until now, there's been no nationally accepted definition of what interoperability means or when and why it's needed, said David Boyd, director of the Safecom program, which developed the page document. This consensus is important not only because of the breadth of needs outlined in the document but also because it represents the needs of the users at every level of government, said Stuart McKee, chief information officer for Washington state.

Although communications interoperability has been a priority for officials nationwide for years, this is the first time there has been a document developed with this level of consensus, McKee said. Boyd characterized the statement of requirements as a living document that will grow and address future needs to include data, images, video and other capabilities. Therefore, it is not technology-specific. The document, he said, will provide industry with information about the capabilities they should incorporate into systems for first responders.

But he also said it provides state agencies and local communities with a powerful tool to justify their communications needs to lawmakers.

Safecom's statement of requirements comes eight years after the last major federal report issued by the now-defunct Public Safety Wireless Advisory Committee on wireless communications for the 50, public safety agencies nationwide.

But unlike that document, Safecom's new report does not focus on spectrum issues. Boyd said the White House Task Force on Spectrum Management will issue a report on radio spectrum by the end of the year.

Officials wanted to focus on baseline requirements that will help address spectrum, technology and other problems. The statement of requirements also addressed a recent General Accounting Office report that criticized the Safecom program in the past for its slow progress and cited the need for detailed agreements among all involved. Safecom officials have at least one solicitation for interoperability solutions already lined up to be based on the requirements.

When you visit our website, we store cookies on your browser to collect information. The information collected might relate to you, your preferences or your device, and is mostly used to make the site work as you expect it to and to provide a more personalized web experience.

However, you can choose not to allow certain types of cookies, which may impact your experience of the site and the services we are able to offer. Click on the different category headings to find out more and change our default settings according to your preference. You cannot opt-out of our First Party Strictly Necessary Cookies as they are deployed in order to ensure the proper functioning of our website such as prompting the cookie banner and remembering your settings, to log into your account, to redirect you when you log out, etc.

For more information about the First and Third Party Cookies used please follow this link. You can set your browser to block or alert you about these cookies, but some parts of the site will not work as intended if you do so.

You can usually find these settings in the Options or Preferences menu of your browser. Visit www. Under the California Consumer Privacy Act, you have the right to opt-out of the sale of your personal information to third parties. These cookies collect information for analytics and to personalize your experience with targeted ads.

You may exercise your right to opt out of the sale of personal information by using this toggle switch. If you opt out we will not be able to offer you personalised ads and will not hand over your personal information to any third parties. Additionally, you may contact our legal department for further clarification about your rights as a California consumer by using this Exercise My Rights link.

The architecture framework will provide public safety agencies with the necessary tools to compare and integrate legacy communication and information systems and allow them to leverage resources and migrate towards interoperability. The PSAF provides practitioners with a set of tools and a common lexicon for describing the elements of their local communications systems and enables practitioners to compare capabilities and equipment to achieve interoperability between jurisdictions.

In addition to assisting the SAFECOM program in identifying needed standards by highlighting compatibility problems at key communications interfaces, the PSAF will also serve as a guide for localities planning for interoperability or technical capability upgrades.

The PSAF enables engineers and planners to document their current public safety communication capabilities and analyze their system in relation to other systems.

Ultimately, the PSAF will provide public safety with the ability to examine and develop both their operational and communications system capabilities. With the publication of the PSAF in early , OLES and SAFECOM are moving forward with a trial to demonstrate the utility of architecture framework principles within the public safety community by developing a database driven application which doesn't require enterprise architecture expertise.

The CASM tool's baseline capabilities, which gather operational data, will be extended to gather more technical details of a communications system. Public safety agencies participating in the trial activity will apply their real world experience to shape and define the tool and ensure it and the underlying architecture framework process are user friendly.

In early three Project 25 interfaces were identified as crucial for public safety agencies to purchase and implement both operable and interoperable Pcompliant systems. Those interfaces are listed below and represent where the most effective acceleration of the P25 Standards occurred in the past year and a half. While the initial releases will not fully satisfy all of the users' requirements, they will allow manufacturers to build interoperable equipment possessing the most common, basic features.

Since then OLES has worked with representatives from both user and industry communities to focus the efforts of the program and to develop an initial framework for the assessment program. A key accomplishment of this group was a memorandum of understanding stipulating the basic assumptions for testing and the means by which test results would be collected and disseminated.

That group has established a basic framework for the program and decided upon a fi rst-party testing regimen to back a Supplier's Declarations of Compliance. OLES representatives drafted and the committee accepted a work plan that prioritized the various conformance and interoperability test procedures—the test procedures that underpin the compliance assessment program. Testing of the CAI begins with evaluations of interoperability for both trunked and conventional mode operation and are on track for completion by the end of calendar year Work is ongoing to update and publish more complete interoperability test procedures, and conformance test procedures for the CAI will follow.

Testing of wireline-based interfaces such as the ISSI poses additional challenges not the least of which is the need for new test equipment and metrology. In addition, the tool will include a packet capture and visualization tool that will support system analysis and troubleshooting.

OLES is driving the broadband standardization effort on behalf of public safety. OLES leadership in this area is evidenced by its sponsorship of the Chair for the APIC Broadband Task Group, and its support from the public safety community derives from its commitment to faithfully representing their requirements. The goal is for public safety to be able to quantify their specific spectrum needs and tie these needs directly back to a repeatable simulation effort.



0コメント

  • 1000 / 1000